• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 488 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: reprogramming parts and possible OTP areas

Lenio Cacula
Genius 16900 points

Part Number: CC2430

If a customer decides to re-use CC2430 parts by reprogramming them, is there any OTP or EPROM area that could interfere with a new application? In other words, are there any risks in using parts that have been programmed before?

Thank you!

  • 0
    TI__Guru**** 221017 points

    Hi Lenio,

    You can review Section 12.4 of the CC2430 datasheet.  If the Debug Lock bit, DBGLOCK, is set to zero then all debug commands are disabled except for CHIP_ERASE, READ_STATUS, and GET_CHIP_ID.  It is also possible to lock flash area (LSIZE) and the boot sector page (BBLOCK).  Note that CHIP_ERASE can be used to clear the Debug Lock bit.

    As noted on its product page, the CC2430 is not recommended for new designs and should not be used for Zigbee or IEEE 802.15.4 certification.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Genius 16900 points

    In other words, nothing overrides CHIP_ERASE, correct? 

    The customer is reusing parts for an older project and needs to know if they can be reprogrammed. All the documentation indicates so, but I need certainty that no surprises will emerge during the process.

    Thank you!

  • +1 in reply to Lenio Cacula
    TI__Guru**** 221017 points

    CHIP_ERASE is a debug command and cannot be disabled.  The customer should be capable of reprogramming these devices.

    Regards,
    Ryan