ERROR: EEPROM verify failed

[k6lcm]

I am getting the following in the terminal when attempting to flash a P8X32A-D40.

proploader.mac -k -D baud-rate=115200 -p /dev/cu.usbserial-P97z9aa5 "~/pixelmusic3000e.binary" -e
Opening file '~/pixelmusic3000e.binary'
Stepping down to 460800 baud
Stepping down to 230400 baud
Stepping down to 115200 baud
Using single-stage download
Downloading file to port /dev/cu.usbserial-P97z9aa5
12156 bytes sent                  
Verifying RAM
Programming EEPROM
Verifying EEPROM
ERROR: EEPROM verify failed
ERROR: Download failed
Press return to continue...

[PropGit]

Hi Levi, That's an unusual error. If you've wired up your P1 yourself, make sure to follow EEPROM connections like shown in this diagram. If you did wire it yourself, most likely this is a case where something isn't connected as recommended. If you are using something like a Propeller FLiP or some other board that already includes a P1 + EEPROM, then most like the problem is something else, including the possibility that the EEPROM is actually bad or worn out, in which case you'll need to contact ***@***.*** to request an RMA and replacement. [image: image.png] The fact that it downsteps the baud rate first means that it's having trouble communicating with the Propeller, so perhaps it's a board (or self-wired unit) that doesn't have a fast Crystal attached? (ie: it's using the internal fast RC Oscillator only). That could also be caused by a poor-quality USB cable; some don't have very good shielding and may allow for a lot of communication noise. *Jeff Martin, R&D + IT* 916.625.3002 ***@***.*** www.parallax.com and learn.parallax.com [image: See Sale Details] <https://www.parallax.com/parallaxs-microbit-shop-is-a-one-stop-source-for-curriculum-and-hardware/>

…

On Sun, Jul 7, 2024 at 6:54 PM Levi ***@***.***> wrote: I am getting the following in the terminal when attempting to flash a P8X32A-D40. proploader.mac -k -D baud-rate=115200 -p /dev/cu.usbserial-P97z9aa5 "~/pixelmusic3000e.binary" -e Opening file '~/pixelmusic3000e.binary' Stepping down to 460800 baud Stepping down to 230400 baud Stepping down to 115200 baud Using single-stage download Downloading file to port /dev/cu.usbserial-P97z9aa5 12156 bytes sent Verifying RAM Programming EEPROM Verifying EEPROM ERROR: EEPROM verify failed ERROR: Download failed Press return to continue... — Reply to this email directly, view it on GitHub <#55>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVFDRLCBX4PBRBNXWJ37LZLHWN7AVCNFSM6AAAAABKP4G4M6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TINBSGI2TEMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Foxbud]

I'm getting the same issue with both the baud rate stepping down until it reaches 115200 and the EEPROM verification failure. Curiously, it still appears to have flashed the EEPROM correctly, as when I restart the P1 without a PC connection, it successfully reads and begins executing the image from the EEPROM.

For context, I'm using proploader V1.0-37 on Linux and the P8X32A-D40 in a custom breadboard setup with a 20MHz crystal oscillator (no PLL multiplication). For the EEPROM, I'm using a Microchip 24FC512-I/P PDIP. I attempted to wire it up exactly as specified by Page 17 of the P1 manual V1.2. However, that didn't work at all, and I then noticed that I had wired SCL and SDA backwards. I then rewired them to be correct (including the 10k pull-up), and that's when I started to get the same error as @k6lcm.

Since I thought there was a chance I could've damaged the EEPROM (since SDA is open-drain), I then tried using a brand new EEPROM (same make and model as the first). This resulted in the same error. Perhaps I damaged the P1's I2C pins? Sadly, I don't have another to test.

Let me know if there are any other details I could provide to help out.

EDIT: After some more testing, it looks like simply including -r in the flags passed to proploader causes the EEPROM to get successfully verified in my case.