Hello!
I'm working on an open-source ham radio project ( T41 ), which has a Teensy 4.1 connected to a 5 inch Buydisplay LCD via SPI. Not sure which version of TeensyDuino I have, but it's a recent one.
The problem in a nutshell: Sometimes the display comes up, and sometimes it doesn't.
More specific: If I start the prototype up cold - power's been disconnected for a while - the display does NOT come up.
If OTOH I do a quick power cycle - pull the power plug and reinsert - the display will come up fine.
ALSO: when the display does NOT come up, the loop() function is not executed. However, setup() *is* executed. I verified this
with a scope hooked to an unused pin, I have it toggle the pin at the top of loop(). When the display does come up, I see pulses
at that pin. Display didn't come up? No pulses. So loop() is not being executed. I had it light a LED at various points inside setup() -
that worked, and verified that setup() is being executed, and proceeding to its end, regardless of whether the display came up or not.
I thought that setup() was getting at the video too fast, and I stuck a delay at the beginning. Tried various delays, up to THIRTY SECONDS - no difference.
The LCD has an RA8875 controller.
Pulling out my few remaining hairs on this one
. Thinking that the RA8875 library is doing video stuff when the video object
gets instantiated.
Nah....I found the library, stuck a five second delay at the beginning of the startup code - no difference.
I'm working on an open-source ham radio project ( T41 ), which has a Teensy 4.1 connected to a 5 inch Buydisplay LCD via SPI. Not sure which version of TeensyDuino I have, but it's a recent one.
The problem in a nutshell: Sometimes the display comes up, and sometimes it doesn't.
More specific: If I start the prototype up cold - power's been disconnected for a while - the display does NOT come up.
If OTOH I do a quick power cycle - pull the power plug and reinsert - the display will come up fine.
ALSO: when the display does NOT come up, the loop() function is not executed. However, setup() *is* executed. I verified this
with a scope hooked to an unused pin, I have it toggle the pin at the top of loop(). When the display does come up, I see pulses
at that pin. Display didn't come up? No pulses. So loop() is not being executed. I had it light a LED at various points inside setup() -
that worked, and verified that setup() is being executed, and proceeding to its end, regardless of whether the display came up or not.
I thought that setup() was getting at the video too fast, and I stuck a delay at the beginning. Tried various delays, up to THIRTY SECONDS - no difference.
The LCD has an RA8875 controller.
Pulling out my few remaining hairs on this one
gets instantiated.
Nah....I found the library, stuck a five second delay at the beginning of the startup code - no difference.