Post Go back to editing

How to avoid corrupting the USBi's EEPROM

After downloading self-boot code to my target EEPROM, my USBi isn't recognized anymore by my computer. What's wrong and how do I fix it?

Parents
  • You should also keep this in mind when you have other I2C masters on the control bus. You need to be careful not to overwrite the USBi's EEPROM at address 0xA2 from a device in your system such as the microcontroller. If your design has another I2C EEPROM set to address 0xA2, you should be very careful not to write to that device while your USBi is plugged in for programming, tuning, or debugging. Of course, it will be best to avoid using EEPROMs with address 0xA2 for any of your SigmaDSP-based designs.

Reply
  • You should also keep this in mind when you have other I2C masters on the control bus. You need to be careful not to overwrite the USBi's EEPROM at address 0xA2 from a device in your system such as the microcontroller. If your design has another I2C EEPROM set to address 0xA2, you should be very careful not to write to that device while your USBi is plugged in for programming, tuning, or debugging. Of course, it will be best to avoid using EEPROMs with address 0xA2 for any of your SigmaDSP-based designs.

Children
No Data