This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R: Change in response of CRC

Part Number: CC2642R
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am following the below sequence for flashing TI chip in backdoor boot loader mode,

Sender:PING

Received:ACK

Sender:CRC

Received:ACK & Got CRC

Sender:Bank Erase

Received:ACK

Sender:Status

Received:0x40(Success)

Sender:Download

Received:ACK

Sender:Status

Received:0x40(Success)

Sender:Send_Data

Received:ACK

Sender:Status

Received:0x40

I am trying to flash 352KB(whole flash region) 128bytes per command

After flashing i am checking the CRC of flashed image and CRC calculated from TI chip(response of CRC(0x27)) both are matching

Hence resetting the PIN(BLE_RST) to boot the TI chip

TI chip also booting with flashed image but after that if i try to calculate CRC there is a mismatch

Is this expected? or something missed in sequence?

  • Hi,

    Thank you for reaching out.

    The behavior you are describing is probably expected.

    Several examples (especially the BLEStack examples) will trigger a write to the flash at their first boot. This is typically to initialize the NVS (non-volatile storage in flash) and, if needed, store keys and bond information. This of course impacts the CRC calculated on the whole flash.

    If you want to confirm this, I recommend the two following points:

    - Still assuming you are using a BLE example, if you dump the device's flash content and compare it to the initial binary, you should observe modifications only in the NVS region (cf. SysConfig to check its placement).

    - The NVS is not meant to be used by the the drivers "empty" example - you should then not experience the flash content to be modified

    I hope this will help,

    Best regards,