Hi,
In our BCM20736S-based design we have noticed that we cannot enter recovery mode. Our design exposes SDA (pint 22) so we can drive it high when necessary. But the normal sequence: 1. hold SDA high. 2. reset 3. release SDA does not put the device in recovery mode. When attempting a recovery, the download logs show the following message:
11:17:29.077 Will be downloading 0 bytes of code and 4931 bytes of data without a minidriver
11:17:29.077 BTP file: Platforms/BCM920736TAG_Q32/20736_EEPROM.btp
11:17:29.077 The config data is coming from the following files
11:17:29.077 build/proximity-BCM920736TAG_Q32-rom-ram-Wiced-release/proximity-BCM920736TAG_Q32-rom-ram-Wiced-release.hex
11:17:29.077 Sending bytes to HW:
4 bytes: 01 03 0C 00
11:17:29.081 Received bytes from HW:
8 bytes: 04 1C 08 04 0C 60 00 F0
(...)
11:17:29.179 Received bytes from HW:
8 bytes: 04 1C 08 04 0C 60 00 F0
11:17:29.179 ERROR: Failed to execute HCI Reset
This happens on boards that we can program normally, so we have ruled out UART/cable problems.
We can also observe activity on SDA on boot, so we know that SDA is properly accessible. Below is SDA activity on a normal reset.
Anyone out there has experienced similar recovery problems?
Best,
Javier