Hein (fub) wrote,
Hein
fub

  • Mood:

EEPROM progress

The serial buffer on the PIC is only 2 bytes large, and all the processing is done in the interrupt that is triggered when a byte is received. If the PC would keep sending, bytes would get lost due to buffer overflows -- the processing of a single byte is fast, but not that fast. Which is why the PIC echos every byte back to the PC at the end of processing -- and the PC waits until it receives input before it sends the next byte.

It turned out that I had not one but two procedures in place that processed incoming bytes independently from my sending routine -- and because the echo'd bytes never reached my sending routine, a deadlock was created.
I cleaned up those two routines, and now I can sequentially write a 64Kbit (that's 8 kilobytes!) EEPROM without a hitch.

I also added a preliminary sequential reading routine, which I will have to modify a bit so that I can read the contents of a whole EEPROM back into the PC-side of things.
Subscribe

  • Sinterklaas & rhymes

    On a whim, I had bought chocolate capitals for the two colleagues who are in my project, plus for the key people at the client. I wrote Sinterklaas…

  • BlinkenLEDs -- the final frontier

    This evening, I produced the final version of the firmware for the single-matrix BlinkenLEDs circuit. This one has it all. If you recall, I have two…

  • Another day, another blinkenLEDs mode

    So I had this idea yesterday... if I make a large display with multiple LED matrices on top of eachother, wouldn't it be cool to have a…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 6 comments