We are looking at these issues and will provide an update shortly.
I'm facing same problem with WICED Sense firmware 1.2 (new version).
Moreover, I'm facing this problem not only wiced_sense app but also sample apps of WICED Smart SDK 2.1.1.
(hello_sensor, speed_test, proximity, etc.)
I followed instructions from Programming the TAG2/TAG3 Board using command line tools Section 6 to convert cgs file to hex and use ChipLoader to load the file to the Wiced Sense device.
So, basically, I copied the following files from SDK/Tools and SDK/Platform/BCM920737TAG_Q32 into a folder:
and launched following command lines (with appropriate values) :
- cgs.exe -I output.hex -A 0xFF000000 -B 20737_EEPROM.btp -D . Wiced_Sense-Image_V1_2.cgs
- Chipload.exe –BLUETOOLMODE –PORT COM1X –BAUDRATE 115200nfc –MINIDRIVER uart_DISABLE_EEPROM_WP_PIN1.hex -CONFIG output.hex -BTP 20737_EEPROM.btp -NODLMINIDRIVER
Unfortunately, I got the following error:
Download minidriver successfully had written 64 bytes to address 0x00201000
Download minidriver successfully had written 64 bytes to address 0x00201040
Download minidriver successfully had written 64 bytes to address 0x00201080
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Terminated with error
Download minidriver error trying to write 64 bytes to address 0x002010C0
Any clue on what's happening ?
Another point: looking at the difference between the cgs file I generated and the one you provided showed me that my "entries" are made of "compressed data" and yours are only "data".
e.g ENTRY "Compressed data" = ".text from ../../build/wiced_sense-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-wiced_sense-rom-ram-spar.elf" vs ENTRY "Data" = ".text from ../../build/wiced_sense-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-wiced_sense-rom-ram-spar.elf"
I think this is quite normal as the files in the build folder are .ccgs (i guess it means compressed cgs), but could this be the reason we can't get functional firmware ?
I read in BCM20732 Memory Map Architecture that SFLASH uses uncompressed images. So, should I load your firmware into SFLASH instead of EEPROM ?
Hello Alex and Brownie,
Thanks for your patience on this issue.
The compressed data and data is the reason why you can't program with the cgs file
However, I have a work-around for fixing the original issue and I will post the changes today.
We have a crystal warm-up issue and I will post the video on the BLOG site for you to see.
Crystal Warm-Up Workaround
Please change the Crystal Warm-up time from the 2800 value to 5000 in the mandatory.cgs file located at: C:\Users\jtate\Documents\WICED\WICED-Smart-SDK-2.1.1\WICED-Smart-SDK\Wiced-Smart\tier2\brcm\mandatory\bld\20737\mandatory.cgs
ENTRY "PMU Crystal Warm up Time"
"Crystal warm up time" = 5000
Short video showing the change is on the BLOG:
1 of 1 people found this helpful
Try the Crystal Warm-Up Workaround on the BLOG.
We tested and it works.
It worked fine!
And other samples of WICED Smart SDK are worked fine too
It works now perfectly.