• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 69 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.

AM2632: AM263x All of Nor flash memory change to 0x0

Wei Yao
Prodigy 220 points

Part Number: AM2632

All of Nor flash memory (0x6000,0000-0x607F,FFFF) change to 0x0 when I debug procedure using CCS.

And it will lead to our main code erased. So do you know why it is happend and in which situation.

 
I used Flash_eraseBlk() Flash_write() in my project. And I debug in QSPI boot mode.
 
  • +1
    TI__Expert 7345 points

    Hi Wei Yao,

    Apologies for the delay in response. 

    Can you please help me understand more regarding the issue.

    1. In your application, are you seeing the same observation in the memory browser in CCS as well?

    2. Can you please run the qspi_flash_transfer example and see if the observation is consistent?

    3. After Flash_eraseBLK() is executed, are you seeing the memory region as 0xFFFF_FFFF or 0x0 ?

    4. Is it observed only during CCS  debug? Are you using gel scripts? 

    Can you also provide me details regarding the SDK version used?

    Thanks & Regards,

    Aswin

  • 0
    Prodigy 220 points

    There is a problem with the hardware connection from PC  to XDS110. Now the phenomenon no longer occurs after our PC connect to XDS110 directly.