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.

TMS320F28P659DK-Q1: Issue with Interrupt_nmiHandler() Function Execution in Different Flash States

Part Number: TMS320F28P659DK-Q1
Other Parts Discussed in Thread: CCSTUDIO

Hello

I'm reaching out regarding an issue I've encountered with the Flash_Check() function in my project. I've noticed that when all flash memory is blank, the function executes without any problems. However, when the flash memory starting from, for example, the address of flash bank 0 + 0x100 has been programmed, the function encounters errors and jumps to another function as depicted in the second screenshot attached.

I'm puzzled by this behavior and would appreciate any insights or suggestions from the community on why this might be happening. Could there be a specific condition or configuration affecting the Flash_Check() function's behavior when certain areas of flash memory are programmed?

Here are a few additional details that might help in understanding the issue:

  • IDE/Toolchain: CCSTUDIO 

    Code Composer Studio

    Version: 12.6.0.00008

  • Flash Programming Method: XDS110 via JTAG
  • flash bank 0 : 0x80000

I've attached screenshots for reference, and I'm happy to provide further details or clarify any points as needed.

Thank you in advance for your assistance and insights.

Best regards,
Mario