CC1352P: Debug prints are not coming on the debug console when flashed through uniflash

JDJ

Part Number: CC1352P
Other Parts Discussed in Thread: UNIFLASH

Hello!

We are currently having an issue where debug prints are not coming on the debug console when it is flashed through uniflash. Whereas the debug prints come if entered to debug mode through the GUI in CCS studio.

Key Details :

1.Private-Public key pair is generated by python keys/key_generate.py within the OAD tool folder. [ ${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad ]

2.Customer private key provided to the tool, the OAD Image tool generates the image header file with the security information segment that includes the image signature.

3.Image signature is added as part of the image header during the OAD image tool post build step.

4.Image header is appended to the .hex and .bin file.

OAD tool is enabled as post build step into build configuration by adding "${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad/oad_image_tool --verbose ccs ${PROJECT_LOC} 7 -hex1 ${ConfigName}/${ProjName}.hex -k ${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad/private.pem -o ${ConfigName}/${ProjName}"

We have added application code to sensor_oad_onchip_secure example code. We are able to build the code with release configuration.

https://dev.ti.com/tirex/explore/node?a=pTTHBmu__4.40.04.04&node=ABcXiRL2ylAmi3hZkCM6cg__pTTHBmu__LATEST&r=pTTHBmu__4.10.00.78&r=pTTHBmu__4.20.00.35

Build environment details :
IDE : CCS 10.1.1.00004
SDK : simplelink_cc13x2_26x2_sdk_4_40_04_04
Compiler version : TI v20.2.1.LTS

Can you please advise on next steps to fixing this problem?

Thanks!

over 4 years ago

0 Siri over 4 years ago

TI__Guru* 86721 points

Someone is assigned to look into this for you.

Siri

0 Marie H over 4 years ago

TI__Guru* 82431 points

Hi,

1) When you say "Debug prints", can you point me to the exact print statement(s) that is not showing up?

2) Did you check whether the device is behaving as expected, i.e. that the sensor is able to connect to a nearby collector or coprocessor?

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

1. We have added a start up print to indicate the device is booted. One print is added in the main() after the HW initialization and before BIOS_start() and another print after the BIOS_start(). We don't see both prints when the image is flashed through Uniflash. When we use CCS debug icon to run the program, we can see the both prints.

2. Our application code does wait for a command from the debug UART to join the near by collector. So we haven't checked the RF.

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

1. What API are you using for your prints? If you are using e.g. display driver to set up a UART display it should work. However if you are trying to use a debug function that relies on a debug session it's no wonder...

2. Ok

3. Since you are using an OAD process, did you go through the full OAD process? E.g. did you add a BIM image? Please see the Example Usage section of the example README.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

1. We have a custom print statement which sends the Bytes over UART, it uses UART2 driver.

2. We have not followed the OAD process, We have flashed both the BIM and Application images. We have not flashed any persistent application.

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

Ok I understand.

You will need to follow the whole OAD process to be able to run the application image on the device.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

We have followed the OAD process , we added the persistent image as well still we are not seeing any debug prints coming on console.

0 venkatesh B over 4 years ago in reply to venkatesh B

Intellectual 260 points

Hi Marie,

We have built the BIM image in debug mode and other images in release mode. With this we are able to get the log's.

Can you point us if there is any setting that we need to configure in BIM for the UART working ?

Regards

Venkatesh

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

Based on your screen shot, the main difference I am seeing is that in your July 1st post you are programming the device with application hex file, while in your July 7th post you are using the bin file. As you know, the bin file is the one which contains the OAD image header, so please make sure to use this one (not the hex file9).

Please see this guide regarding using BIM in Release configuration: https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-oad/creating-a-production-image.html

Cheers,

Marie H.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

Sorry for the confusion, we have tried the application file as '.bin' file as well but the shared image doesn't show it. Even if we flash the application in ".bin " (release mode) , and BIM in release mode, It doesn't work. It works only if we flash the BIM Image generated in Debug mode.

We see that debug mode is not performing Signature verification hence it is working in debug mode. In release mode the signature verification is failing, so it is not working.

Even example also, is not working in Release mode.

Below is the procedure we followed to generate key's. Please let us know if we missed any.

1.Private-Public key pair is generated by python keys/key_generate.py within the OAD tool folder. [ ${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad ]

2.Copied [ Public key X,Public key Y,Signer Info ] these 3 to the bim_main.c file and then BIM is build in Release mode

3.Application is build in Release mode which will use private.pem from oad tool folder

OAD tool is enabled as post build step into build configuration by adding

"${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad/oad_image_tool --verbose ccs ${PROJECT_LOC} 7 -hex1 ${ConfigName}/${ProjName}.hex -k ${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/tools/common/oad/private.pem -o ${ConfigName}/${ProjName}"

Below is the procedure followed in flashing

Regards

Venkatesh

0 venkatesh B over 4 years ago in reply to venkatesh B

Intellectual 260 points

Hi Marie,

Any inputs ?

Regards

Venkatesh

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

The steps look ok.

Can you open the .bin file with BTool, this tool will read the fields in the OAD image header and let you know if it sees any issues.

Cheers,

Marie H

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatsh,

BTool is bundled in the SDK, e.g.:

C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\tools\ble5stack\btool\Run_BTool.bat

Cheers,

Marie H

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

Below is the observation with BTool.

Regards

Venkatesh

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

Looks like the CRC is valid. However I don't see a security header. Can you double check the .bin file that it's actually added?

Cheers,

Marie H.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

Below are the security header details

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

Ok that looks good. Good to see, but harder to understand why the device seemingly doesn't boot into this image.

Can you go through Task 4 of this SimpleLink Academy lab? Specifically the section on Debugging from the BIM to the application : https://dev.ti.com/tirex/content/simplelink_academy_cc13x2_26x2sdk_5_10_00_00/modules/ble5stack/ble_enhanced_oad/ble_enhanced_oad.html

Cheers,

Marie H.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

Thanks for quick reply. We will go through and try to debug.

Regards,

venkatesh

0 venkatesh B over 4 years ago in reply to venkatesh B

Intellectual 260 points

Hi Marie,

While we are debugging , we are thinking to share our example project with you for your review and test , how can we share it with you ?

Regards

venkatesh

0 venkatesh B over 4 years ago in reply to venkatesh B

Intellectual 260 points

Hi Marie,

Is it possible to share your email , so that we can share our project in drive ? OR please share a drive link where we can upload the project ?

Regards

venkatesh

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

Were you able to jump from BIM into the application?

Cheers,

Marie H

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

BIM is not jumping to Main application as it is failing at image verification step.

if(readSecurityByte[SEC_VERIF_STAT_OFFSET] != VERIFY_FAIL) { signVrfyStatus = Bim_verifyImage(iFlStrAddr);

Regards

venkatesh

0 venkatesh B over 4 years ago in reply to venkatesh B

Intellectual 260 points

Hi Marie,

Once again, we have reviewed with respect to OAD process. We see every thing seems Ok, so we tried re installing the tool chain. After reinstalling the tool chain, Secure boot works now.

Regards

venkatesh

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Hi Venkatesh,

I'm happy to hear it works now. When you say you reinstalled the tool chain, it's specifically the SDK?

Cheers,

Marie H.

0 venkatesh B over 4 years ago in reply to Marie H

Intellectual 260 points

Hi Marie,

It's the Python Tool chain present in the requirement.txt file under OAD folder.

Regards

venkatesh.

0 Marie H over 4 years ago in reply to venkatesh B

TI__Guru* 82431 points

Aha. Thank you for posting.

Cheers,

Marie H.

Sub-1 GHz

Sub-1 GHz forum

CC1352P: Debug prints are not coming on the debug console when flashed through uniflash