Other Parts Discussed in Thread: CC1354P10, SYSCONFIG
Tool/software:
Hello,
I am working on porting a codebase using SDK 3.40.00.02 and IAR 8.32.2 running on the CC2642R1 to simplelink sdk 7.41.00.17 and IAR 9.40.2 running on the CC1354P10. In the previous codebase I was able to carry out ECDSA signature verification without issues. However with this new codebase I notice that ECDSA_verify fails for one of my signature verification operations if a BLE connection is active, but works fine if the device is not in an active connection (even if the exact same public key, message, and signature is used). In the case where the operation fails, ECDSA_verify returns -1, which i'm assuming is the error code returned if the signature was found to be invalid. In SysConfig I have tried using both a single instance of the ECDSA module as well as 2 instances (in case the BLE stack was using the first one). But I run into the same issue in both cases. In summary, my questions are:
- What could be causing ECDSA_verify() to return bad status when a connection is active but return success otherwise, for the same key, message, and signature?
- Do I need to include ECDSACC26X4_s.c, ECDSACC26X2.c or any other stack file for successful operation of the ECDSA driver? I have tried with and without ECDSACC26X2.c included in my project, but I get the same results either way. When I attempt to include ECDSACC26X4_s.c in the project, I get the compilation error seen in the following screenshot:
Please advise.
Thanks,
Keron