- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear,
I am testing the OTA Update using the program of snip.ota_fr in WICED SDK v2.4.1.
The comments in this ota_fr.c told me that the first step is running this command as follow:
snip.ota_fr-BCM943362WCD4 OTA=waf.ota_upgrade SFLASH=app-dct-ota-download
The platform I used is BCM9WCDUSI09, so I changed the command as:
snip.ota_fr-BCM9WCDUSI09 OTA=waf.ota_upgrade SFLASH=app-dct-ota-download
But it failed. Is the RAM too small?
The Log is in the attachment.
Could anyone help me to find the problem? Thanks.
BTW, the SPI Flash in my board is 4MByte.
Solved! Go to Solution.
- Labels:
-
Over The Air Updates (OTA)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not modify the file,you can fine sflash_get_size() func,and in the func you can know,it only supports SFLASH_SUPPORT_MACRONIX_PARTS and SFLASH_SUPPORT_SST_PARTS menufacture`s device,and the flash id must be SFLASH_ID_MX25L8006E or SFLASH_ID_SST25VF080B.Acturally i do not know bcm do like this.if your flash does not match,you will get the size of flash 0 size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The platform I used is BCM943362WCD4 ,but i got the same error as you.like this:
16384 bytes written at address 0x2000001c
downloaded 16384 bytes in 0.234375s (68.267 KiB/s)
****************** Result: Size too big for chip
writing 16384 bytes at 65536
loadimage address 536870940 foffset 65536 16384
16384 bytes written at address 0x2000001c
downloaded 16384 bytes in 0.218750s (73.143 KiB/s)
****************** Result: Size too big for chip
writing 16384 bytes at 81920
But there is another error message before that:
Building the OTA-Upgrade App
Skipping building bootloader due to commandline spec
Making .gdbinit
Could not find start/end addresses of Flash
waf_ota_upgrade-BCM943362WCD4-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you mean that it is likely to be a bug of the SDK V2.4.1 and that I can't fix it by myself?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure,did you connect the FAE of BCM?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, I haven't yet. I will try it.
Thank you all the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have resolved the question...,It is because the flash ID is not match.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you only modify the SFLASH_ID_XXXXXX in spi_flash_internal.h(SDK\Wiced\Platform\common\drivers\spi_flash\ )?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not modify the file,you can fine sflash_get_size() func,and in the func you can know,it only supports SFLASH_SUPPORT_MACRONIX_PARTS and SFLASH_SUPPORT_SST_PARTS menufacture`s device,and the flash id must be SFLASH_ID_MX25L8006E or SFLASH_ID_SST25VF080B.Acturally i do not know bcm do like this.if your flash does not match,you will get the size of flash 0 size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you modify anything else?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think so.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In your Log, I found this:
waf_sflash_write-NoOS-NoNS-BCM943362WCD4-
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
App | 0 | 22071 |
Host MCU-family library | 0 | 8211 |
Interrupt Vectors | 0 | 436 |
libc | 0 | 25126 |
Platform | 0 | 676 |
SPI Flash Library | 0 | 1236 |
Startup Stack & Link Script fill | 0 | 5536 |
WWD | 0 | 196 |
----------------------------------+---------+---------|
TOTAL (bytes) | 0 | 63488 |
----------------------------------|---------|---------|
In my Log:
waf_sflash_write-NoOS-NoNS-BCM9WCDUSI09-
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
App | 0 | 22071 |
Host MCU-family library | 0 | 8207 |
Interrupt Vectors | 0 | 436 |
libc | 0 | 25126 |
Platform | 0 | 760 |
SPI Flash Library | 0 | 1236 |
Startup Stack & Link Script fill | 0 | 5552 |
WWD | 0 | 196 |
----------------------------------+---------+---------|
TOTAL (bytes) | 0 | 63584 |
----------------------------------|---------|---------|
Is there any other critical difference?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not sure.
Actually I removed some printf like "Platform xxxx initialised".
But it doesn't affect this I think.