cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Smart Bluetooth

Anonymous
Not applicable

I have to firmware upgrade in 20732 and SDK 1.1.0

I've replace EEPROM 64Kbyte. but I can't find to set EEPROM

Let me know how to set EEPROM

0 Likes
1 Solution
9 Replies
JaWa_2142591
New Contributor II

I am trying to understand your question but sorry if I don't answer your question please elaborate your question again.

Yes, firmware upgrade does need 64KB memory to execute the function. And you don't have to change settings for this, FW and App will set it automatically. You can use the board as usual as when you are using 32KB EEPROM.

0 Likes
MichaelF_56
Moderator
Moderator

I think they provide some additional detail on the issue over here in this thread: Re: Why error occur when I open WsOtaUpgrade.exe?

Thanks in advance for your help janusw.

arvinds

0 Likes
Anonymous
Not applicable

Sorry, I need to upgrade firmware using uart.

I heard that 20732 needs enough space(64Kbyte) to upgrade in EEPROM.

So I've replace the EEPROM from 32Kbyte to 64Kbyte and

function(ws_upgrade_verify() return value is ture) has done well

but it is not working after booting

Let me know how to upgrade using uart.

1. I downloaded a beacon-BCM920732TAG_Q32-rom-ram-Wiced-release.ota.bin to EEPROM.

    I wondering if beacon-BCM920732TAG_Q32-rom-ram-Wiced-release is true. I'm using a UART

2. I know that upgrade fuction writes a firmware binary to DS2 region ,and  SS2 is updated ,and SS1 is marked

const WS_UPGRADE_NV_LOC_LEN nv_loc_len[2] =
{

    {
        /* .ss_loc = */     {0, 256},
        /* .ds1_loc = */    0x4C0,         // ConfigDSLocation
        /* .ds1_len = */    0x7B00,        // ~31KB
        /* .ds2_loc = */    0x8000,
        /* .ds2_len = */    0x7B00,        // ~31KB
        /* .vs1_loc = */    0x140,         // DLConfigVSLocation
        /* .vs1_len = */    0x200,         // DLConfigVSLength
        /* .vs2_loc = */    0,             // No VS2 for EEPROMS
        /* .vs2_len = */    0              // No VS2 for EEPROMS
    },

0 Likes
JaWa_2142591
New Contributor II

Can you please upload a trace which is just like what you did in another thread?

http://community.broadcom.com/message/5768#5768

(they are same issue, right?)

so we can check what happened from after you replaced a 64KB EEPROM.

0 Likes
Anonymous
Not applicable

Yes, they are same issue.

I didn't know that EEPROM is configured automatically.

0 Likes
Anonymous
Not applicable

Thanks in advance for your help janusw and mwf_mmfae

This problem is cleared.

0 Likes
MichaelF_56
Moderator
Moderator

Can you share with us what you did to resolve the issue?

0 Likes