• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 1013 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2430: How to check the flash lock protection bit status?

Terry Deng
Intellectual 2485 points
Part Number: CC2430
Other Parts Discussed in Thread: CC2652R, CC2530

Hi All

Customer would like to add function in their code to check CC2430 flash lock protection bit status. Could you help advice which address to check the data?

  • 0
    TI__Guru**** 207357 points

    The flash lock protection byte is stored at location 0x000 of the flash information page which is located in the lowest 2 KB part of flash. As this part is NRND and not competitively priced I highly recommend that the customer consider migrating to the CC2530 or evaluating the new CC2652R.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Intellectual 2485 points
    Hi Ryan

    Thanks your advice.

    I see CC2430 datasheet say "The Flash Information Page and hence the Lock Bits is only accessed through the Debug Interface", May I double confirm if customer code can read flash address 0x000 to know the flash lock bit status?

    BTW, thanks your remind for upgrade the device. Customer already developing CC2530. The CC2430 is their old product and they need read flash lock bit to do some maintain task.
  • 0 in reply to Terry Deng
    TI__Guru**** 207357 points
    The lock protect bits are written as a normal flash write to FWDATA (see section 13.3.2), but the Debug Interface needs to select the Flash Information Page first instead of the Flash Main Pages which is the default setting (WR_CONFIG -> SEL_FLASH_INFO_PAGE). However I am not sure if the same can be said for reading the bits. READ_STATUS can determine if DBGLOCK is set and the customer can re-write BBLOCK and LSIZE if desired. BBLOCK should remain write protected and the customer can attempt reading pages of the flash area to determine the value of LSIZE.

    Regards,
    Ryan