Skip to content
This repository has been archived by the owner on Aug 27, 2023. It is now read-only.

Teacup does not start, if a defined 4-bit-bus LCD is not conected #326

Open
arcimede opened this issue Mar 31, 2020 · 0 comments
Open

Teacup does not start, if a defined 4-bit-bus LCD is not conected #326

arcimede opened this issue Mar 31, 2020 · 0 comments

Comments

@arcimede
Copy link

Since my 4-bit-parallel-LCD display is conected on a front panel I noticed, that if the display was not connected Teacup did not start. This happend also when I did some test with the "naked" CPU print.
Since the LCD is not a critical device it would be nice that the printer would work even if its not connected or broken.
As I have programed some drivers for similar LCD´s, I think it is a busy check of the BF flag that causes this effect. A closer look to the "parallel-4bit.c" file has shown that exactly this is the case....
So it would be nice, if there was a timeout that causes leaving the routine after the maximum processung time of the controller or even more elegant a check at the start of Teacup disabling the LCD if it does not working, and maybe telling something via the serial interface....

I know this is not verry important, but maybe helpful for some users.

By the way: tips for the fuse settings are also helpful, specially if somebody is new to AVR´s and has a device without bootloader.
After hours of debugging I found out:
for my 644P this line in the "AVR upload" line was helpful:
-U lfuse:w:0xf7:m -U hfuse:w:0xd9:m
the LOW fuse puts the oscillator and divider in the rigth "mood" the HI fuse disables the JTAG interface and my X and Y output worked!

Saluti Jörg

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant