Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
On the 20732-tags, there is a way to recover the device if a FW download fails. (Or some other catastrophic event should occur.) This involves holding 'BOOT' button while applying power. Is ther a similar mechanism (GPIO pin requirement) for the BCM20732S SIP device?
The QSG Appendix describes holding down the BOOT_ROM switch during reset to put the board into a known state for recovery.
This procedure prevents the on-board ARM from being able to access the EEPROM that is on the module. Upon boot, the ARM reads the contents of the EEPROM (and in the case of pressing the button, the read of the actual content is negated due to the switch pulling the internal EEPROM SDA line "high") and since it does not find a valid image, it enters its 'programming' mode.
In looking at the SDA line "inside" the module, it appears to get connected to Pin 22 - outside- of the module. By chance do you have Pin 22 brought out to a test point where you can assert it high (to VDDIO) during boot?
I don't know if this actually works, ... just speculating.
Per the TAG board schematic provided within the SDK (Doc/Schematics/BCM920732TAG_Q32/), your logic seems correct in that the ROM switch (SW5) on the TAG Board (SOC based) applies VDDIO to the SDA pin on the EEPROM, preventing the device from reading the image stored in the EEPROM and forcing it into programming mode.
Pin 22 is SDA on the module, so a similar approach should provide the same result: