• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 95 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.

TMS320F28P650SH: C2000 F28P650SH Secure Boot Startup Jump Failure When ECDSA/SHA384 Libraries Are Fixed in Flash

Hailey Quan
Prodigy 10 points

Part Number: TMS320F28P650SH

Hi team,

We are currently designing an ECDSA secure boot solution based on the C2000 F28P650. The TI team provides an ECDSA library, and signature verification requires the use of SHA384_hashByteWise() and ecc_verify_hash().

By placing the above library functions into a specific Flash region in P650 BANK0 using the linker command file (for example, .text : > flash_section), an abnormal startup jump occurs after power-on, and execution fails to reach the main() function of the boot project.

If the ECDSA library functions are removed (excluded from the build), the system can successfully jump to and execute main(). This behavior indicates that the issue is clearly related to the ECDSA library.

What could be the root cause of this behavior, and how can this issue be resolved?

ECDSA library:

ECDSA library.jpg

 

Thanks

Hailey

  • 0
    TI__Guru 60300 points

    Hi Hailey,

    Hailey Quan said:

    By placing the above library functions into a specific Flash region in P650 BANK0 using the linker command file (for example, .text : > flash_section), an abnormal startup jump occurs after power-on, and execution fails to reach the main() function of the boot project.

    If the ECDSA library functions are removed (excluded from the build), the system can successfully jump to and execute main(). This behavior indicates that the issue is clearly related to the ECDSA library.

    What could be the root cause of this behavior, and how can this issue be resolved?

    This seems to be relaed to how the application was placed, do you know here you have placed the code, i.e.l address, also before integrationing the library, did you test the example working from flash without the library