Skip to content
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

Open
micha-uhl opened this issue Jan 2, 2025 · 5 comments
Open

Some files won't burn #78

micha-uhl opened this issue Jan 2, 2025 · 5 comments

Comments

@micha-uhl
Copy link

micha-uhl commented Jan 2, 2025

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

@TomNisbet
Copy link
Owner

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?

@micha-uhl
Copy link
Author

Hello, I think it's because of the EEPROMS. They are seeq DQ28C256-250. Also with the apparently working file come errors, whole blocks are falsified. See picture, should everything be FF.
Bildschirmfoto 2025-01-02 um 15 53 40
I ordered others.
regards Michael

@TomNisbet
Copy link
Owner

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:

  • Z 5000
  • Z 5030
  • Z 5060

@micha-uhl
Copy link
Author

micha-uhl commented Jan 3, 2025

Hallo Tom, I tried your Suggestions, but In both cases it now aborts at 3F00, with both EEPROMS!
The Z command works. Maybe the Arduino works not correct? I use an Nano with 328PB!
Bildschirmfoto 2025-01-03 um 10 05 10

Bildschirmfoto 2025-01-03 um 10 06 03 Bildschirmfoto 2025-01-03 um 10 06 49

@micha-uhl
Copy link
Author

Hi, now I bought new AT28C256F 15PU. With or without page write, the first bytes up to $80 are misspelled. With the "Z" test it works. The rest of the file appears to be error-free.
Bildschirmfoto 2025-01-11 um 09 29 51
Do you have another sketch for only 28C EEPROMs?

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

No branches or pull requests

2 participants