Shop OBEX P1 Docs P2 Docs Learn Events
EEPROM verify failure — Parallax Forums

EEPROM verify failure

bxgirtenbxgirten Posts: 79
edited 2005-11-07 16:36 in BASIC Stamp
Is this a BS2 chip issue? I cannot download code from desktop or Mac.

Comments

  • bxgirtenbxgirten Posts: 79
    edited 2005-11-07 14:58
    As a follow-up, I've moved the BS2 from the Parallax Carrier Board back to the BOE. Same problem. Its getting power from an AC adapter set to 9V.
  • allanlane5allanlane5 Posts: 3,815
    edited 2005-11-07 15:04
    Hmm. I'm assuming it passes the loop-back test, and chip found test.

    This can happen if you write to the EEPROM using a BS2 program, that writes again and again and again... The EEPROM is good for about 1e6 writes, which is a long time if you reprogram it once a minute, but not a long time if your program writes to it once a millisecond.
  • bxgirtenbxgirten Posts: 79
    edited 2005-11-07 15:08
    Yes, it passes the loopback test and the IDE finds the stamp.

    I hardly ever use the BS2. I've spent the last 6 months toying with the Javelin Stamp. Now, Ive been back for 2 weeks, going through the Robotics! book from Parallax learning how to use a BS2.

    Is this a permanent error? If not, is there a way to reset this?
  • Chris SavageChris Savage Parallax Engineering Posts: 14,406
    edited 2005-11-07 15:16
    How are you connecting to the computer (USB or Serial) and what type of computer (Desktop or Laptop)?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Chris Savage
    Parallax Tech Support
    csavage@parallax.com
  • allanlane5allanlane5 Posts: 3,815
    edited 2005-11-07 15:16
    So, did you write a program that wrote to the eeprom again and again?

    If so, it's possible your eeprom has a 'worn-out' location. Parallax may be able to replace it, if you send it back to them.

    It's also possible this is a serial port error -- are you using a USB cable? Have you set FIFO's to zero on that port?
  • bxgirtenbxgirten Posts: 79
    edited 2005-11-07 15:26
    Chris,

    First, I was using Mac, connected via KeySpan USB to serial. Then I moved it over to a brand-X Win2K desktop and connected via serial. Same problem. So then I tried moving it from the Carrier Board back to the BOE. Same error.


    Allan,

    No. I've just been going through the Robotics! book (Servos chapter 2, page 44).
  • Chris SavageChris Savage Parallax Engineering Posts: 14,406
    edited 2005-11-07 15:33
    Okay, the reason I asked is you should try to disable the FIFO buffers on the USB Serial Port Advanced Setting to see if that helps (It usually does).

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Chris Savage
    Parallax Tech Support
    csavage@parallax.com
  • bxgirtenbxgirten Posts: 79
    edited 2005-11-07 15:40
    Chris,

    I'm not using USB, I'm using a serial cable connected to com port 1.
  • bxgirtenbxgirten Posts: 79
    edited 2005-11-07 16:22
    Chris,

    Is this just a situation where we can call it "when EEPROM goes bad"? I've had this chip for over 6 months and its misbehaving now. Should I just call in for a replacement?
  • Chris SavageChris Savage Parallax Engineering Posts: 14,406
    edited 2005-11-07 16:36
    Perhaps...A damaged interpreter could generate this message as well.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Chris Savage
    Parallax Tech Support
    csavage@parallax.com
Sign In or Register to comment.