You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firmware/OCWare Describe the issue found
This is a hardware issue that we've seen on multiple boards that I'd like get to the bottom of. Firmware will need to be made robust enough to handle SCL being held low anyway , but on SDR 33, the bus locks up if we don't read from the EEPROM first. Very strange, and a bit worrying that the entire bus can be taken down but partially fixed with software if things are done in the correct order.
To repro, run latest Rev_C_Changes on SDR 33 - POST will stop shortly into SDR. To fix, simply add
[Originally commented by imgraham]
Seems that this is related to our EEPROM chip - I can get i2c7 to lock up simply by trying to write to one of the GBC's EEPROM while WP is asserted. By the data sheet, the IC doesn't ACK any of the data bytes in this scenario. This is easily reproducible, so I'd like to probe the lines to see what's up. It's really unfortunate if it's that easy to screw up Tiva - we might have to muck around with the TI drivers afterall.
Product: (OC-SDR, OC-LTE, OC-LTE, OC-Power, others)
OC-SDR
Category: (Hardware, Software/stack, Firmware/bootloader, Documentation)
Firmware/OCWare
Describe the issue found
This is a hardware issue that we've seen on multiple boards that I'd like get to the bottom of. Firmware will need to be made robust enough to handle SCL being held low anyway , but on SDR 33, the bus locks up if we don't read from the EEPROM first. Very strange, and a bit worrying that the entire bus can be taken down but partially fixed with software if things are done in the correct order.
To repro, run latest Rev_C_Changes on SDR 33 - POST will stop shortly into SDR. To fix, simply add
in
sdr_init()
right before the call tosdr_fx3_reset();
Please provide all necessary steps to reproduce the issue
A clear and concise description of steps to reproduce the bug.
The text was updated successfully, but these errors were encountered: