LP-EM-CC2745R10-Q1: How to ensure that the car node project of SDK 9.10.00.83 runs normally as an Overwrite mode APP when both SSB and APP exist?

Peisheng Yang

Part Number: LP-EM-CC2745R10-Q1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Question: How to ensure that the car node project of SDK 9.10.00.83 runs normally as an Overwrite mode APP when both SSB and APP exist?

Issue description: In order to realize the Car node CAN OTA function, we configure the Car node to Overwrite App mode. The Bootloader project can run independently as SSB, and the car_node project can also run independently as APP. However, when SSB and APP are loaded to the development board at the same time, SSB and APP can switch between each other, but APP cannot run normally. When using the basic_ble_oad_image project as APP, SSB and APP can run normally at the same time. The security configuration of the two APP projects is consistent. Can you help us check why the car node App cannot run normally when SSB exists?

Load image：

App v2.0 jumps to SSB; SSB jumps to App v3.0;

App v3.0 only prints one log and does not print the loop test logs.

Security Configuration：

The added log printing code is as follows:

Expected Result：”Car node Ble app test log.” Print once every 2 seconds in a loop.

Actual Result: After jumping to App V3.0, the test log did not achieve the 2-second loop printing.

Could you please check why it is different from the expected result?

Best regards

Preston

4 months ago

0 Nima 4 months ago

TI__Genius 14945 points

Hello,

I'm a little confused on this, so I apologize if I'm not understanding the question.

The issue lies within app v3.0 and not that the SSB can't boot into it? Based on the image you attached of the logs, we are successful in booting in app v3.0, but it's not executing the test log thread? Have you debugged the project to see what state of device is in? It's hard to say what could be going wrong without more debug information. If we are booting into app v3.0 and we see a print statement but not the thread, it could be that the thread creation failed.

Can you provide some more debug information? For instance, when you're in app v3.0 but nothing is printing out, where are you in code?

Best,

Nima Behmanesh

0 Peisheng Yang 4 months ago in reply to Nima

Intellectual 700 points

Hi Nima:

The table shows the debugging methods I tried; The image is in the attachment.You can try to load my image.

Strangely, the only load car_node app can enter TestLog_Thread; However, when the bootloader and car_node app are loaded together, TestLog_Thread does not run. Can you tell me how to debug the bootloader and car_node app when loading them simultaneously?

The base_ble_oad_dual project does not have this issue, only the car_node project has this problem