• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 354 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.

Abnormal program erasure after CC2530HF256 is used for a period of time

liuzhiming
Prodigy 10 points

Other Parts Discussed in Thread: CC2530, Z-STACK

1. Problem description

A.Based on CC2530F256 hardware platform to develop air-conditioning energy-saving products (application scene base station room), there is an abnormal situation in the product operation (abnormal probability of 20%), after positioning, it is found that the FLASH internal program or data in CC2530F256 chip is inexplicably modified (different from the initial program segment data).

Abnormal comparison of B. FLASH data (abnormal on the left, normal on the right)

Note: The above is just an example. After analysis, the internal FLASH data of CC2530 of different products is randomly erased or abnormally changed, and the location of the erased FLASH is not fixed.

C.I hope to give some constructive and executable bug fixes.

2. Software framework design

Task scheduling management is based on ZigBee protocol stack OSAL, and some TI function modules are used to complete data acquisition and business processing functions.The engineering structure is shown in the figure below:

  • 0
    TI__Guru**** 223187 points

    Hi liuzhiming,

    Please clarify how the issue is being observed, as it would help isolate the root cause of the behavior between HW or SW. 

    • Are these devices failing after being deployed and the flash is read during debug, if so how long have they been in circulation?
    • Are these devices programmed before being populated onto hardware during production? 
    • How many flash pages are erased and what are their precise locations inside of memory when the issue is observed? 
    • Can this be replicated on any device after "positioning" multiple times? 
    • Will the issue occur again if these devices are re-programmed? 
    • Do the chip markings bear any common resemblance to each other or their working counterparts?\
    • What version of Z-Stack software is being used?

    Regards,
    Ryan