Does the board have any external pull ups on either SDA or SCL? If yes, apply a short across the pull up resistor to recover the bricked board.
You seem to imply in the post that you does not have access to the SCL/SDA lines, so I’m guessing that the part is buried somewhere within the design.
I’m guessing that there is no way to resolve this outside of accessing the HW (i.e. through SW).
I need to ask around to verify.
I described the issue to the development team and they confirmed that the firmware is probably not running or is in the weeds, so there really is no software solution.
On the hardware side, they thought that maybe you should check to see if RXd is connected and driven high (just connect to Vio), then power cycle and wait a couple of seconds. At this point, see if it will respond to download/recover from the SDK (or try using the MBT tool from the new SDK to send a reset command). If this does not work, SDA to GND during boot is really the only solution.
We've got exactly the same problem as @odbol in one of our boards: bricked and no access to SDA. Since we cannot modify our boards, can you provide some advice on how to avoid bricking the board in the first place? In particular, I am not clear on how downloading new app firmware, even if faulty, can affect/destroy the firmware that is loaded in download mode (i.e. on RX high + RESET). Aren't those two different firmware images? Or is the "download mode firmware" also included in the app firmware? What would be the best documentation for the different boot stages?
Hi we just unbricked following these instructions and noticed that there was an error in this answer:
> If this does not work, SDA to GND during boot is really the only solution.
... should say
> If this does not work, SDA to VDD during boot is really the only solution.
It is still a mystery to me why it is so easy to brick these boards. Why reset + asserted RX doesn't just ignore the EEPROM and enter download mode? That would provide a more pleasant programming experience rather than having to recover everytime there is a faulty firmware...