Shop OBEX P1 Docs P2 Docs Learn Events
EEPROM Verification — Parallax Forums

EEPROM Verification

allen123allen123 Posts: 10
edited 2009-06-19 21:04 in Propeller 1
What are some solutions when I try loading a program into the propeller's EEPROM and it tells me that there was an EEPROM verification error?

-Allen

Comments

  • Mike GreenMike Green Posts: 23,101
    edited 2009-06-19 04:01
    Have you ever been able to download a program to this EEPROM? Is there anything unusual about the program? What kind of Propeller setup are you using?

    This is one of those "It shouldn't happen" type problems. You could have a defective EEPROM. There could be a power problem during EEPROM programming.

    I used to get this problem when running the Propeller Tool under Windows which was being run under Virtual PC on a Mac, but that's an unusual circumstance.
  • SRLMSRLM Posts: 5,045
    edited 2009-06-19 04:28
    I believe you also get this error when the EEPROM is too small (in terms of memory).
  • allen123allen123 Posts: 10
    edited 2009-06-19 04:33
    I havent been able to ever download a program to the EEPROM for this Propeller. I noticed the problem when I first attempted to download it to the EEPROM. However, the problem is unusual because I have another Propeller chip just like this problematic one but I am able to download programs into the EEPROM. I am using the P8X32A-Q44 Propeller chip
  • Mike GreenMike Green Posts: 23,101
    edited 2009-06-19 04:41
    It's possible, but unlikely that the problem is with the Propeller. More likely, there's a problem with the EEPROM chip or the connections between them. Make sure the write protect pin on the EEPROM (/WP) is high (Vdd). As SRLM implied, the EEPROM has to be at least 32K bytes in size (24C256 or equivalent). It can be larger (up to 128K - 24C1024B). The compiled program still has to fit in the 1st 32K, but the additional space can be used for other things and you can have multiple devices on the boot EEPROM I2C lines.
  • allen123allen123 Posts: 10
    edited 2009-06-19 05:21
    I had to solder wires to pins 28 and 29 which are special purpose pins used for EEPROM communication. Could the soldering quality affect communication between the EEPROM and the computer?
  • SRLMSRLM Posts: 5,045
    edited 2009-06-19 05:52
    Did you follow the schematic (including the pullup resistor)? Demo Board Schematic
  • Toby SeckshundToby Seckshund Posts: 2,027
    edited 2009-06-19 10:11
    I was a bit worried about there only being the one pull-up for the EEPROM clk and data lines, so I·have always put two onto my bds. I have only used 512s

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Style and grace : Nil point
  • allen123allen123 Posts: 10
    edited 2009-06-19 20:51
    I have a Propeller Proto USB Board so everything is already connected and setup by Parallax. Furthermore, the EEPROM is 32KB so that requirement is met. Therefore, I don't understand why it proceeds to give me the EEPROM verification error.
  • Mike GreenMike Green Posts: 23,101
    edited 2009-06-19 21:04
    I suggest you call Parallax Tech Support since you have never been able to download a program successfully to the EEPROM on the Protoboard. By the way, the Protoboard does use a 64K byte EEPROM. The 2nd 32K is available for other uses. The Protoboard also has both pullups (SCL and SDA).
Sign In or Register to comment.