- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I purchased BCM92073X_LE_TAG4. I downloaded the WICED smart SDK and was able to download hello_sensor and communicate with the Windows 10 client example provided in the SDK. Now I am unable to download anything. I get the following console output:
20:43:59 **** Build of configuration Release for project WICED-Smart-SDK ****
"C:\\Users\\RothsMark\\Documents\\WICED\\WICED-Smart-SDK-2.2.3\\WICED-Smart-SDK\\make.exe" hello_sensor-BCM920736TAG_Q32 download
Linking target ELF
OK, made elf.
Call to hello_sensor_spar_crt_setup @ 00206195
OK, made C:/Users/RothsMark/Documents/WICED/WICED-Smart-SDK-2.2.3/WICED-Smart-SDK/Wiced-Smart/spar/../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor-rom-ram-spar.cgs. MD5 sum is:
1180812d92f07aac93b91d5b37fcf8bd *../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor-rom-ram-spar.cgs
--------------------------------------------------------------------------------
Patches start at 0x00204568 (RAM address)
Patches end at 0x00205988 (RAM address)
Application starts at 0x00205554 (RAM address)
Application ends at 0x00206191 (RAM address)
Patch size (including reused RAM) 5152 bytes
Patch size 4076 bytes
Application size 3133 bytes
------
Total RAM footprint 7209 bytes (7.0kiB)
--------------------------------------------------------------------------------
Converting CGS to HEX...
Conversion complete
Creating OTA images...
Conversion complete
OTA image footprint in NV is 9394 bytes
Detecting device...
Device found
Downloading application...
****Download failed - Press the reset button on the device and retry ****
20:44:02 Build Finished (took 3s.137ms)
Pressing what I assume is 'reset', a button labeled 'sw3', has no effect on the problem.
In Windows device mgr I see that connecting the TAG4 board creates 2 COM ports, COM3 and COM4 which are set to 9600 baud. that seems slow...
Not sure how to debug at this point. My kit did not contain either a cable or a 'getting started' guide that supposedly come with the board. But it did work fine but now it fails to download. If anyone has a soft copy of the 'getting started' guide I would appreciate them sending it to me.
I'm using:
WICED Smart IDE - Eclipse IDE for C/C++ Developers 2.2.3
Version: Juno Service Release 2
Build id: 20130225-0426
Solved! Go to Solution.
- Labels:
-
ispn:41242:1:0
-
l1:314:1:0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
huangj, following your note I change my recover command to:
proximity-BCM920737TAG_Q32 download recover UART=COM4
previously I did not have the 'download' parameter. This worked correctly and the board was recovered.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may refer to the tag4 board information from the below thread:
Tag 4 Platform Specific Hardware Information
Otherwise, you may have to do a recovery procedure which is detailed in the QSG document.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the link last night, but the recovery procedure failed much like the download.
One thing was that the recovery note said to specify 'the' uart. The USB-serial driver creates 2. I tried both but neither recovered the board.
Another thing I found odd: switch 8 was set to the exact opposite of what the startup guide specified.
Mark Roths
Intrinsix
Mobile: (831) 428-1004
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the result of my ‘recovery’ attempt:
"C:
Users
RothsMark
Documents
WICED
WICED-Smart-SDK-2.2.3
WICED-Smart-SDK
make.exe" proximity-BCM920736TAG_Q32 recover uart=COM4
Linking target ELF
OK, made elf.
..\..\Tools\ARM_GNU\bin\Win32\arm-none-eabi-objdump: section '.data' mentioned in a -j option, but not found in any input file
Call to proximity_spar_crt_setup @ 002056f9
OK, made C:/Users/RothsMark/Documents/WICED/WICED-Smart-SDK-2.2.3/WICED-Smart-SDK/Wiced-Smart/spar/../../build/proximity-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-proximity-rom-ram-spar.cgs. MD5 sum is:
50dd86dd78a51c41b7359ce0b69cfa7c *../../build/proximity-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-proximity-rom-ram-spar.cgs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mroths,
There is a download log in the folder(WICED-Smart-SDK-2.X.X\WICED-Smart-SDK\build\your app name\download. You can see the reason.
You also can add some parameter in your make target.
For example:
hello_sensor-BCM920736TAG_Q32 download BT_DEVICE_ADDRESS=1234567890CD UART=COM7
or
proximity-BCM920737TAG_Q32 download recover UART=COM13
Here is the my successful recovery message:
--------------------------------------------------------------------------------
10:29:01 **** Build of configuration Release for project WICED-Smart-SDK ****
"C:\\Users\\Jack\\Documents\\WICED\\WICED-Smart-SDK-2.2.2\\WICED-Smart-SDK\\make.exe" proximity-BCM920737TAG_Q32 download recover UART=COM13
Linking target ELF
OK, made elf.
..\..\Tools\ARM_GNU\bin\Win32\arm-none-eabi-objdump: section '.data' mentioned in a -j option, but not found in any input file
Call to proximity_spar_crt_setup @ 00205445
OK, made C:/Users/Jack/Documents/WICED/WICED-Smart-SDK-2.2.2/WICED-Smart-SDK/Wiced-Smart/spar/../../build/proximity-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-proximity-rom-ram-spar.cgs. MD5 sum is:
f0f524a9a2d66f8cede34c18b1cd8c90 *../../build/proximity-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-proximity-rom-ram-spar.cgs
Patches start at 0x00204568 (RAM address)
Patches end at 0x002056B0 (RAM address)
Application starts at 0x002052A0 (RAM address)
Application ends at 0x00205444 (RAM address)
Patch size (including reused RAM) 4424 bytes
Patch size 3384 bytes
Application size 420 bytes
------
Total RAM footprint 3804 bytes (3.7kiB)
--------------------------------------------------------------------------------
Converting CGS to HEX...
Conversion complete
Creating OTA images...
Conversion complete
OTA image footprint in NV is 5983 bytes
Downloading application...
****Download failed - Press the reset button on the device and retry ****
Recovering platform ...
Recovery complete
Application running
10:29:13 Build Finished (took 12s.163ms)
Jack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
huangj, following your note I change my recover command to:
proximity-BCM920737TAG_Q32 download recover UART=COM4
previously I did not have the 'download' parameter. This worked correctly and the board was recovered.
Thanks!