No display on Color Weather

Question

Assembled, configured, complied OK. No display at all.  Compiler Data:

Executable segment sizes:
ICACHE : 32768           - flash instruction cache
IROM   : 467256          - code in flash         (default or ICACHE_FLASH_ATTR)
IRAM   : 28737   / 32768 - code in IRAM          (IRAM_ATTR, ISRs...)
DATA   : 1656  )         - initialized variables (global, static) in RAM/HEAP
RODATA : 11648 ) / 81920 - constants             (global, static) in RAM/HEAP
BSS    : 28576 )         - zeroed variables      (global, static) in RAM/HEAP
Sketch uses 509297 bytes (48%) of program storage space. Maximum is 1044464 bytes.
Global variables use 41880 bytes (51%) of dynamic memory, leaving 40040 bytes for local variables. Maximum is 81920 bytes.
esptool.py v3.0
Serial port COM3
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: e8:db:84:da:78:78
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 16MB
Flash params set to 0x0290
Compressed 513456 bytes to 318196...
Writing at 0x00000000... (5 %)
Writing at 0x00004000... (10 %)
Writing at 0x00008000... (15 %)
Writing at 0x0000c000... (20 %)
Writing at 0x00010000... (25 %)
Error opening serial port 'COM3'. (Port busy)
Writing at 0x00014000... (30 %)
Writing at 0x00018000... (35 %)
Writing at 0x0001c000... (40 %)
Writing at 0x00020000... (45 %)
Writing at 0x00024000... (50 %)
Writing at 0x00028000... (55 %)
Writing at 0x0002c000... (60 %)
Writing at 0x00030000... (65 %)
Writing at 0x00034000... (70 %)
Writing at 0x00038000... (75 %)
Writing at 0x0003c000... (80 %)
Writing at 0x00040000... (85 %)
Writing at 0x00044000... (90 %)
Writing at 0x00048000... (95 %)
Writing at 0x0004c000... (100 %)
Wrote 513456 bytes (318196 compressed) at 0x00000000 in 7.3 seconds (effective 565.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Serial Monitor Data:

10:52:19.692 -> .......connected.
10:52:24.258 -> Connected, IP address: 192.168.1.26/255.255.255.0
10:52:24.258 -> Connected, MAC address: E8:DB:84:DA:78:78
10:52:24.258 -> Initializing touch screen...
10:52:24.305 -> Mounting file system...
10:52:24.398 -> SPIFFS opened: OK
10:52:24.398 -> Configuring time for timezone EST5EDT,M3.2.0,M11.1.0
10:52:24.490 -> .
10:52:24.909 -> Local time: Mon Feb  7 10:52:24 2022
10:52:24.909 -> UTC time:   Mon Feb  7 15:52:24 2022
10:52:25.003 -> [HTTP] Requesting resource at http://api.openweathermap.org:80/data/2.5/weather?id=4931050&appid=e5648f2c965d7928e59cb8b498043214&units=imperial&lang=en
10:52:25.049 -> [HTTP] connected, now GETting data
10:52:25.095 -> start document
10:52:25.189 -> [HTTP] Requesting resource at http://api.openweathermap.org:80/data/2.5/forecast?id=4931050&appid=e5648f2c965d7928e59cb8b498043214&units=imperial&lang=en
10:52:25.236 -> [HTTP] connected, now GETting data
10:52:25.283 -> start document
10:52:25.797 -> Free mem: 13944

Have 3.3vdc to display and the touch is reported in the terminal window.

Please help me out with diagnosis.

Thx, Mike

Comments

Hi Marcel,

You are 100% right!  My eyes are not as good as they used to be.  Under the magnifier, I found a cold solder joint.  After touching it up, the display works great.

Couple questions:

1. I don't know how to invoke the touch calibration .

2. I only have one screen available. Tapping the screen changes the hours display between 12 and 24 hr format, but I am unable to access any other screens.

Thanks much for your help,

Mike

Answer 1

In addition to the QA done by the manufacturer all our display modules are tested on a custom test rig before they are added to the kit. Hence, we are quite confident the display itself is/was fine.

Not too surprising the majority of issues people faced are cold or otherwise bad solder joints. Please (re)examine those first.

Also, we have a little test sketch at https://github.com/ThingPulse/color-display-testbed for only testing the display + touch functionality.