EB3 GLCD Timeout

[mnfisher]

I might be doing something wrong... On an ebocks-3 esp I tried to get the display working.

I couldn't find the source to glcd_eb3 (auto included in project).

--- 0x4200e678: task_wdt_isr at C:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:509
--- 0x403770ed: _xt_lowint1 at C:/Espressif/frameworks/esp-idf-v5.5/components/xtensa/xtensa_vectors.S:1240
--- 0x40041a79: ets_delay_us in ROM
--- 0x4200bbcd: FCD_029f2_gLCD_EB3__ReceiveReply at D:/Projects/Flowcode/eblocks3/main/esp-project.c:1868
--- 0x4200bc6b: FCD_029f2_gLCD_EB3__SendCommand at D:/Projects/Flowcode/eblocks3/main/esp-project.c:2054
--- 0x4200bd5b: FCD_029f2_gLCD_EB3__ClearDisplay at D:/Projects/Flowcode/eblocks3/main/esp-project.c:2705
--- 0x4200becb: app_main at D:/Projects/Flowcode/eblocks3/main/esp-project.c:2968
--- 0x4201dbf0: main_task at C:/Espressif/frameworks/esp-idf-v5.5/components/freertos/app_startup.c:208
--- 0x4037b2a9: vPortTaskWrapper at C:/Espressif/frameworks/esp-idf-v5.5/components/freertos/FreeRTOS-Kernel/portable/xt

[BenR]

Hello,

Just tried your program here and it's working great for me first time. The hope is that this should be very plug and play.

There is a problem in that the colour is very dark and so you might not instantly recognise it redrawing. The colour bit depth is masked from the top end so you can just call random() or if you want to mask to the bit depth then random() & 0b11111000. It's done like this so it correctly works with 24-bit RGB input.

The component itself can be found under Displays -> Graphical Colour. Maybe I should also include it in the Hardware ->? EB3 section.

Are you saying you get watchdog related resets?

When you power up the E-Block board do you get the Matrix splash screen? I wonder if it's missing its firmware?

[mnfisher]

Hi Ben,

Yes - it's giving WDT restarts (as per messages above)- and the display doesn't seem to clear?

Martin

[mnfisher]

... I did get the splash screen until I re-flashed with the above. Now - just lights on nobody home

If I added a UART - I could print Hello World - before the loop and that worked AOK.

[mnfisher]

I found a link to the component source in the Wiki - but it's 404 page not found

[mnfisher]

Did a bit of experimenting - and I might have done something bad to the board

However - I 'guessed' that the display is an ILI9488 (it doesn't seem to be mentioned in the docs) - and uploaded a program to the 'main' esp32 board (using the USB port on the main board rather than the eblock port.

I got lucky - first program I tried was parallel connection - and first program I tried worked AOK However - I think the 'munged' part holds true too - as, for example, the reset button doesn't.

How do I reinstall the firmware of the 'control' s3? I'm assuming I've overwritten it!

Martin

[chipfryer27]

Hi

I too have an EB3 board but mine is a PIC, arriving just before I started some lengthy travels and I forgot to take it with me. I was annoyed with myself for that because it is essentially a pretty cool development board with WiFi, Bluetooth, a 2GB SD card and a very useful touch screen inbuilt.

Anyway I'm only now getting a chance to play. When I power up I'm greeted by the Matrix logo and build details (think v3,0 but is is only on screen briefly) then the screen goes blank for a few minutes. It then produces a thick horizontal white line across the middle of the screen. If I touch the screen it produces a small dot at contact and I can draw. Pressing Reset surprised me as I thought it would be like powering up again. However upon release, a few seconds later the screen goes blank and I can start drawing again.

With them being fairly new I appreciate the WiKi may not have too much details yet so it would be helpful if the "components" were documented as suggested above, such as display / touchscreen driver, BT and WiFi details etc as I think it would be beneficial to those developing. Also if possible make available the initial code used in the "demo" as that I think would be a good example in itself of both using the components and FC itself.

I'm looking forward to using it more as the PIC, a 18F67K40 running at 64MHz is a powerful 8-bit device and having the ports broken out to both pins and connectors will allow easy experimentation.

I notice there is a "scope" test point / connection on the board too, but can't seem to find details on where it is connected or how to utilise.

I'm sure the WiKi will be updated in due course.

Regards

[BenR]

Here's the firmware and reflash instructions for the GLCD module.

Firmware binary files

Firmware.zip

(2.42 MiB) Downloaded 9 times

SD card files

SD Files.zip

(1.41 MiB) Downloaded 9 times

Instructions

Cap Touch Display Factory Test Routine.pdf

(68.55 KiB) Downloaded 11 times

Fingers crossed this solves the problem for you but shout if not.

If you want the source for the module firmware then let me know and I'll share it.


Regarding this...

It then produces a thick horizontal white line across the middle of the screen.

We have recently encountered this in production and solved the issue.

The cause is the top casing pressing down on the touchscreen and causing touches right at the edges of the screen.

I've fixed the bug in software for the ILI9488 and other screens but not yet rolled out the fix to the display module firmware.

We have fixed the hardware by using a slightly taller threaded spacer to provide more room and avoid the top cover applying pressure to the screen.

If you have some M3 washers available then unscrew the top cover plate from the display and add one or two washers to go under the cover plate on each pillar. This will help to space off the protective cover and avoid the false touches which draw the white rectangles.

[chipfryer27]

Hi Ben

I had some slightly taller PCB spacers so used them to raise the cover. So far so good !

Regards

[mnfisher]

Thanks Ben,

Re-flashed the 'main' esp32 via one of it's USB ports - and then I can program the board using the main USB port connected to the (I assume) 'control' device.

Phew....