Component: LCD SPI (MiniClick) (Alphanumeric)

[andeug]

Hi,

The LCD Mini Click component from Mikroe / Mikroelektronika appears to have a component in the library, which is documented on https://www.flowcode.co.uk/wiki/index.p ... hanumeric).

On the description page, it says "Generic alphanumeric LCD display based on the standard Hitachi HD44780 controller IC", but when I looked into the datasheet of the LMB162XFW LCD, it gives references to ST7065 and ST7066U, and not HD44780:

lmb162xfw-manual-rev0.pdf

(207.44 KiB) Downloaded 178 times

Is there an error on the Matrix TSL Wiki page regarding the controller of the LMB162XFW LCD? Additionally, it is not entirely clear to me whether the component referred to as Mikroe "LCD Mini Click" (MIKROE-2453) is being documented on the Wiki page, or if it is another product.

Regards,
Andreas

[medelec35]

Hello.
As far as I'm aware the HD44780 is compatible to LMB162XFW
The ST7066U timings, instruction set and interface is compatible with HD4478
There is a document that mentions the mini click and HD44780
https://onlinedocs.microchip.com/oxy/GU ... AEA87.html
At the time of creating the Component: LCD SPI (MiniClick) (Alphanumeric), research would have been carried out first.
I don't believe that page is wrong.

[r_teixeir]

Hi Medelec and Team,I am having trouble configuring the pin connections for the LCD Mini Click component in Flowcode v11 while targetting the BL0032 board.By default, the component's SPI properties point to Port C pins (C2, C3, C4, C5). However, looking at the pin mapping for the BL0032, Port C only physically exposes pins C13 and C14. The standard lower pins needed for the SPI bus are not physically available on this target chip/board configuration.Is there a way to unlock or expand the available pin selection dropdowns in the component properties so I can remap these signals to an entirely different port (such as Port D or Port B)? Currently, Flowcode is restricting my choice of pins, and I cannot select the alternative digital I/O lines that are physically routed on my board.I have attached a screenshot of my Flowcode workspace and the pin allocation table for reference.Any guidance or component updates to allow custom pin routing would be greatly appreciated!Best regards,

LCD_Mini_Click.jpg (135.6 KiB) Viewed 590 times

[Steve-Matrix]

Thanks. It looks like there could be an issue with that LCD component that is preventing it from using the software SPI channel. Hopefully we'll have a fix soon.

[BenR]

Hello,

Many thanks for letting us know, I have hopefully resolved the issue for you now via the help -> library updates.

[r_teixeir]

LCD_Mini_Click_Error.jpg (88.07 KiB) Viewed 548 times

Hello MatrixTSL Team,

I am encountering a compilation error in Flowcode V11 when trying to compile a project using the "LCD SPI (MiniClick)" component targeting the dsPIC33EP256MU806 microcontroler.

The compilation fails using the xc16-gcc compiler, reporting syntax bugs inside the core CAL file "PIC16BIT_CAL_SPI.c". It seems the file contains generic 8-bit registers ('tris' and 'port') written in lowercase, which the 16-bit compiler does not recognize for this device.

Here is the compiler output log:
- PIC16BIT_CAL_SPI.c:232:2: error: 'tris' undeclared (first use in this function)
- PIC16BIT_CAL_SPI.c:357:2: error: 'tris' undeclared (first use in this function)
- PIC16BIT_CAL_SPI.c:410:2: error: 'port' undeclared (first use in this function)

I have attached the screenshot of the compiler messages window showing the full error trace.

Could you please provide an updated CAL component patch or a fix for this 16-bit SPI compilation issue?

Thank you!

[BenR]

Hello,

Have you assigned pin connections to the various pin properties of the display component? If you have then please can you attach your project and I'll investigate for you.

[r_teixeir]

Hi Ben, here is the Flowcode v11 program. Please let me know if you need any adjustments or further assistance.

[BenR]

Hello,

Thanks for attaching your project.

If you select the display component and look at the properties panel you will see that the MISO Remap Pin property has no pin specified.

RemapPins.png (18.58 KiB) Viewed 402 times

Please choose the remap pins you would like to use and that should then start compiling correctly for you.

[r_teixeir]

Hi Ben,

Here is the attached

WhatsApp Image 2026-06-09 at 00.28.55.jpeg (43.18 KiB) Viewed 337 times

photo of my physical hardware setup. As you can see, the BL0106 adapter is correctly plugged into the PORTD 0-7 slot of the BL0032 board. I have also tested this setup with two different physical LCD Mini Click displays to rule out a hardware defect, but neither shows any signs of life (backlight/characters remain unresponsive).Here is my current configuration and what I have already tested in software:Component Settings: I am using the LCD SPI (MiniClick) component. The External Address is set to 0 (0, 0, 0) because A0, A1, and A2 are grounded on this Click board.Pin Mapping: I am targeting PORTD. Based on the Matrix BL0106 adapter pinout, I have configured:CS: $PORTD.2MOSI: $PORTD.3MISO: $PORTD.4CLK: $PORTD.5Communication Channel: I tried using the hardware SPI channels (Channel 1 and Channel 3 with Fosc/4). I also tried switching the Channel property to Software mode to force bit-banging on those specific pins, but without success.Software Logic: In my flowchart, I call LCDMiniClick1::Start() right after the BEGIN block. Inside the main loop, I have a 1000ms delay to prevent over-spamming the display controller. The simulation on the 2D Panel works flawlessly.Since I have verified that the hardware connection to PORTD is correct and the code compiles/flashes successfully via mLoader, I suspect there might be a multiplexing or register issue on the dsPIC33. For example, does PORTD.2 (CS) have analog functionalities (like ANSEL bits) that need to be explicitly disabled in Flowcode before the component can control it?I have attached my .fcfx project file for reference. Any help, guidance, or patches regarding this specific dsPIC33 / E-blocks2 configuration would be highly appreciated.Thank you in advance!"