This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

I2C EEPROM writer fails when device is in I2C bootmode

Hi,


I apologize if this turns out to be a silly question, but I haven't been able to find the answer anywhere.  I am running the I2C eeprom writer application by loading it via JTAG, as per the MCSDK instructions.  I observe that it always succeeds when the device as been powered up in "no boot" configuration and it always fails when the jumpers are in the "I2C boot" configuration.  This is not a problem for me currently, because spin1 of our device has jumpers for all bootmode pins.  However, with spin2, we are replacing these jumpers with hard-coded pull-up/pull-downs to configure the device for I2C boot.  When that happens, we must be able to write the eeprom with the device in I2C boot mode, or it will require hand removing resistors, flashing, and re-adding the resistors.

Can someone tell me what is preventing the eeprom from being correctly written?

Thanks,

Joel