Hi Ben,I hope you're doing well. I'm following up on this thread to see if there has been any progress regarding the "virtual pins" feature and the IO expander integration you mentioned.Were you able to test the display, or has this feature been bumped up the priority list since your last post? I ...

Hi Martin,
Thank you for your response and for taking the time to look into the files.
I tested the modified project on the real hardware, but unfortunately, the physical screen and backlight are still completely dead. To find out why, I compiled the project and audited the generated raw .c file ...

Hi chipfryer2 and Matrixtsl Team

Following up on my previous post, I have spent the last few days trying to bypass this limitation by developing a custom component and testing different approaches, but unfortunately, there has been no success in getting the physical display to work.

The breakdown ...

Hi chipfryer27 and Steve,
Unfortunately, checking the lines with a physical logic analyzer is not feasible on this specific hardware layout. The mikromedia+ for PIC32MX7 board is a highly integrated, multi-layer PCB where the entire 8/16-bit parallel data bus and control lines run directly from the ...

Hi Steve,
I have just performed the 1-second LED blinking test exactly as you suggested, embedding it directly into the main application loop. To provide absolute proof, I monitored the pin behavior using an oscilloscope.
I am attaching the screenshot of the waveform measurement below, which shows ...

Hi Steve,Thank you for the quick look.
Yes, I have carefully verified the Connections properties in Flowcode. I must mention that my pin mapping was indeed compromised (incorrect) before, but I have now corrected it to match the hardware layout exactly.
To prove that the hardware and the physical ...

Hello Matrix TSL Team,

I am experiencing a critical issue with the gLCD SSD1963 (Parallel Mode) component in Flowcode 11.2.17 when targeting the PIC32MX795F512L microcontroller on a Mikromedia+ board.

Even with standard properties configurations, the compiler (XC32) outputs three consecutive ...

Hi Benj,
Thank you for your guidance. Following your instructions exactly, I completely removed any custom C code blocks from my program to eliminate any potential interference. The flowchart now relies 100% on the native component macros (Start, Clear, PrintString) in a clean, purely visual ...

Hi Ben and team,
I hope you are well.
I am writing to ask for a little help with this component, as I am currently stuck on this issue and unable to get a simple "Hello World" to display on my hardware after flashing the HEX file.
I’m using Flowcode v11 (Professional Version) and trying to get the ...

Hi Ben,Thank you for the component update! Looking at the newly generated C code from this version, I can confirm that the hardcoded parallel PORTB bit-banging conflict from the base LCD library is now completely gone. The new RawSend routine correctly routes everything through the expander logic ...