- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using the Wiced IDE, I see this when sending the compiled program to the eval board:
Downloading Bootloader ...
No changes detected
Downloading DCT ...
No changes detected
Downloading Application ...
Download complete
And everything works.
I'm at the point where I'd like to JTAG program my eval board. I have an ST-Link that I use and I normally take a *.bin and program and verify it. However, when I take the bin file from Wiced and program it using my JTAG programmer it doesn't work (nothing starts up, but the program is there in memory)
For example (using the uart snippet)
I have my binary in:
WICED-SDK-3.1.1\WICED-SDK\build\snip_uart-ISM43362_M3G_L44\binary\snip_uart-ISM43362_M3G_L44.bin
When I upload this, it doesn't work.
I feel like I'm missing something obvious here. Do I need to up load these files as well?
WICED-SDK-3.1.1\WICED-SDK\build\snip_uart-ISM43362_M3G_L44\binary\DCT.bin
WICED-SDK-3.1.1\WICED-SDK\build\waf_bootloader-NoOS-NoNS-ISM43362_M3G_L44-SDIO\binary\waf_bootloader-NoOS-NoNS-ISM43362_M3G_L44-SDIO.bin
If so, how do I do it (do I put them in a different address space?)
If there any documentation on doing this? I'm a little in the dark here.
Solved! Go to Solution.
- Labels:
-
SPI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
For BCM943362WCD4
1.downloaded bootloader(Wiced-SDK/build/waf_bootloader-NoOS-NoNS-BCM943362WCD4- SDIO/Binary/waf_bootloader-NoOS-NoNS-BCM943362WCD4-SDIO.bin) to 0x08000000.
2.downloaded dct(/Wiced-SDK/build/snip_scan-BCM943362WCD4-NetX/DCT.bin) to 0x08004000.
3.downloaded app(/Wiced-SDK/build/snip_scan-BCM943362WCD4-NetX/Binary/snip_scan-BCM943362WCD4-NetX.bin) to 0x0800C000.
Then snip.scan is working fine for me.Got the values from DCT.map.. Hope this helps..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Binaries, doesn't include addresses, we usually use the stripped elf (eg. snip.scan-ISM43362_M3G_L44-SDIO.stripped.elf) files as input for openOCD. have a look at download target in standard_platform_targets.mk (in tools/makefiles). This should give you an Idea of the command line we send to openOCD.
Regards,
Bassem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ST-Link does not support the programming of *.elf files. Only *.bin, *.hex and s-record.
I will look at standard_platform_targets.mk, but it appears Wiced does not support the ST-Link programmer in downloading *.bin files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As of today WICED only supports programming using OpenOCD and FTDI chips (within the evaluation board) or using Olimex-ARM-USB-TINY-H.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
For BCM943362WCD4
1.downloaded bootloader(Wiced-SDK/build/waf_bootloader-NoOS-NoNS-BCM943362WCD4- SDIO/Binary/waf_bootloader-NoOS-NoNS-BCM943362WCD4-SDIO.bin) to 0x08000000.
2.downloaded dct(/Wiced-SDK/build/snip_scan-BCM943362WCD4-NetX/DCT.bin) to 0x08004000.
3.downloaded app(/Wiced-SDK/build/snip_scan-BCM943362WCD4-NetX/Binary/snip_scan-BCM943362WCD4-NetX.bin) to 0x0800C000.
Then snip.scan is working fine for me.Got the values from DCT.map.. Hope this helps..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes! this is the answer I was looking for, thank you. You can use an ST-Link for JTAG programming.
I hope this helps someone else in the future.