- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have download my software on a personnal BCM20736 board. And today I want to re-download a new vesion of this software but this message apper:
****Download failed - Press the reset button on the device and retry ****
With the VERSBOSE=1:
@
"Tools/common/Win32/echo.exe" Converting CGS to HEX...
Converting CGS to HEX...
Tools\CGS\Win32\cgs.exe -D Platforms/BCM920736TAG_Q32 -O DLConfigBD_ADDRBase:123456789018 -A 0xFF000000 -B Platforms/BCM920736TAG_Q32/20736_EEPROM.btp -I build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.hex --cgs-files build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor2-rom-ram-spar.cgs > build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/cgs2hex.log 2>&1 && "Tools/common/Win32/echo.exe" Conversion complete || "Tools/common/Win32/echo.exe" "**** Conversion failed ****"
Conversion complete
"Tools/common/Win32/echo.exe"
"Tools/common/Win32/echo.exe" Creating OTA images...
Creating OTA images...
Tools\CGS\Win32\cgs.exe -D Platforms/BCM920736TAG_Q32 -O DLConfigFixedHeader:0 -B Platforms/BCM920736TAG_Q32/20736_EEPROM.btp -I build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.ota.hex --cgs-files build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor2-rom-ram-spar.cgs > build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/cgs2hex.log 2>&1 && "Tools/common/Win32/echo.exe" Conversion complete || "Tools/common/Win32/echo.exe" "**** Conversion failed ****"
Conversion complete
Tools\IntelHexToBin\Win32\ihex2bin.exe build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.ota.hex build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.ota.bin
"Tools\common\Win32\perl.exe" -e '$s=-s "build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.ota.bin";printf "OTA image footprint in NV is %d bytes",$s;'
OTA image footprint in NV is 7264 bytes"Tools/common/Win32/echo.exe"
"Tools/common/Win32/echo.exe"
"Tools/common/Win32/echo.exe" Downloading application... && Tools\ChipLoad\Win32\ChipLoad.exe -BLUETOOLMODE -PORT COM16 -BAUDRATE 115200 -MINIDRIVER Platforms/BCM920736TAG_Q32/uart_DISABLE_EEPROM_WP_PIN1.hex -BTP Platforms/BCM920736TAG_Q32/20736_EEPROM.btp -CONFIG build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release.hex -CHECKCRC -NOVERIFY -DLMINIDRIVERCHUNKSIZE 251 > build/hello_sensor2-BCM920736TAG_Q32-rom-ram-Wiced-release/download.log 2>&1 && "Tools/common/Win32/echo.exe" Download complete && "Tools/common/Win32/echo.exe" && "Tools/common/Win32/echo.exe" "Application running" || "Tools/common/Win32/echo.exe" "****Download failed - Press the reset button on the device and retry ****"
Downloading application...
I have try with the SDA to gnd, without. Or with the HCI UART Rx to gnd at the power up or after...
Always the same error...
The recover command failed and I have the same problem with other custom board
Do you have an idea to solve my problem?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use a 20736S and I download he software with a FTDI USB-UART
I have solved my problem, The Tx connexion between my UART and the custom board was corrupt (cut off)
The recovery procedure works and the programmation too
Sorry for the desagrement and thanks a lot for your time
Have a nice day
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The application seemed to have been compiled properly including the cgs-to-hex conversion.
I did a download and compared my verbose log against yours and found that you are missing a portion where it should report "Detecting device...". I suspect that the uart ports were not detected/installed properly.
Can you plug in your board to the cable which you used for downloading, go to Device_Manager/Ports, and confirm that you see the two serial ports?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I used the BCM20737TAG board I see the two serial port and I download my software properly but when I used my custom board I see one serial port and the failed error
I have no pull up to P1
SDA, SCL floating
All gpio non used (floating)
reset pull up with 10k
My old software run if I power up the board (without HCI uart)
And I can't dowload my new software on this board
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some questions:
1) Are you using SIP module or SoC?
2) How do you download your app onto your board? Do you use the SDK or via a cable like FTDI USB-to-UART?
3) Can you post your download.log file in your build folder?
For recovery, can you use the following make target?
proximity-BCM920737TAG_Q32 recover UART=COMxx VERBOSE=1
I know you have tried to recover the chip by tying SDA to gnd and Vcc. But I just need to confirm that you carry out the below
steps and still you cannot recover. To recover:
1)Power off the device
2)Short SDA to GND
3)Connect the HCI UART
4)Power up the device
5)Wait 3 seconds and remove the short
6)Execute your recovery target build
HCI_Rx must be exerted upon powering up in order to enter Programming Mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use a 20736S and I download he software with a FTDI USB-UART
I have solved my problem, The Tx connexion between my UART and the custom board was corrupt (cut off)
The recovery procedure works and the programmation too
Sorry for the desagrement and thanks a lot for your time
Have a nice day