-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some files won't burn #78
Comments
There shouldn't be any data-specific differences, but maybe there could be a loose or incorrect data or address connection to the EEPROM that only shows up with specific data. Can you post the output of the Write command for a failed file followed by the output of an Info command? |
I've never tried that particular chip, but the data sheet looks like it would be compatible. Two things you might want to try: In TommyPROM.ino, find the PromDevice64 line that isn't commented out and replace the 64 with 0. This will disable page writes. If that works then there may be a timing issue or something else that is broken in the block write code. You can also try the Zap command to see if it writes correctly on the page boundary. It would be interesting to see that same memory block after these three commands:
|
Hello, I have the problem that some files can not be burned or crash after a few blocks. other similar ones work. why is that? I use the same EEPROM 28C256
The text was updated successfully, but these errors were encountered: