Bruce Tomlin
Experienced Member
I've been looking at the board pictures to make a sort of netlist, and I finally got my first good look at that KiCad partial schematic by opening it in KiCad. (Whatever you used to make PDFs made really broken ones that drove the PDF handling in OS X nuts, as in the "trying to allocate every byte of memory in the system" kind of nuts.)
So a few more things:
- the segment pins may actually be on P0
- write_segments might be possible to write as "P0 = data" instead of messing with each bit separately
- delay_ms should probably instead be a function that does a bunch of 1ms delays, and checks for comm input in between them (do not busy-wait for more bytes when you get comm data, just update variables and move along)
- main() would clear display_mem first, then a while(1) loop to call scan_display and then scan_keypad and then check what's up with the comm stuff
So a few more things:
- the segment pins may actually be on P0
- write_segments might be possible to write as "P0 = data" instead of messing with each bit separately
- delay_ms should probably instead be a function that does a bunch of 1ms delays, and checks for comm input in between them (do not busy-wait for more bytes when you get comm data, just update variables and move along)
- main() would clear display_mem first, then a while(1) loop to call scan_display and then scan_keypad and then check what's up with the comm stuff