CCS/IWR6843ISK: Not able to run vital signs demo under debug mode

Yiran Li1

Part Number: IWR6843ISK
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Dear all,

I was trying to run the vital signs demo under debug mode using IWR6843ISK. I believe I strictly followed the users' guide and tried quiet a few times. But I am still not able to get the demo running under debug mode. I am not sure if it is because of the XDS110 connection. Here are some of my observations:

1. From CCS, after I created the "new target configuration" for the first time, I tested the connection by pressing the "Test Connection" button. I got the message as bellow and I think the message tells me the connection is fine:

2. The I followed the guide to connect target and load the program. After I connect the target, I went to back to "Test Connection". The test failed this time and it gave me the message below:

3. I run the program anyway. The Console stuck at message "Debug: VitalSignsDemoMSS Lanuched the Initialization Task". I clicked "Start" on the GUI but it didn't work as expected. I also post the cmd screen shot below:

Here are some information about the versions of files and software I used:

xwr68xx_ccsdebug.bin from mmwave_Sdk_03_02_00_04;

ccsv9.1

vital_sings_68xx_dss.e674 and vital_signs_68xx_mss.xer4f from the prebuild_binaries folder from vital_signs lab under mmwave_industrial_toolbox_4_0_0

(I also tried rebuilding the project and used the binaries files generated by the rebuilding from my workspace folder. But I got the some problem).

So, my question is,

1. is it normal that the connection test failed in my step 2 above? If it is not, what maybe the cause of it?

2. Do you think the demo not working under debug mode is because the connection issue?

3. As it mentioned in the message, it seems that the connection test failed because the firmware and drives updates. But base on my understand, if the connection passed at the beginning, it means the firmware and drives are all up to date. Is this true?

4. Is there any other thing I should look at to make the demo working under the debug mode?

Thanks a lot!!!!!!

Lola

over 5 years ago

0 Yiran Li1 over 5 years ago

Intellectual 265 points

Just want to add one more thing,

1. I tried run xdsdfu -e in the cmd file and it detected one device as follow:

2. I tried run the same command again after I clicked "connect target" in CCS. It showed me found no device as below:

3. Under both conditions above, I could see "XDS110 Class Data Port" and "XDS110 Class Debug Probe" listed under my device manager.

Is this normal?

Thanks,

Lola

0 Akash Gondalia over 5 years ago

TI__Guru 50240 points

Hi Yiran,

Two things, first the Vital Signs Demo uses version 3.1.1 of the mmWave SDK. You should also use version 8.3.1 of CCSTUDIO.

Let me know if this doesn't work for you.

Cheers,

Akash

0 Yiran Li1 over 5 years ago in reply to Akash Gondalia

Intellectual 265 points

Hi Ahash,

Thank you for the reply. I installed ccs 8.3.1 and mmwave_sdk_03_01_01_02. But I still got the error showed above.

Another thing I noticed is that, everytime after I clicked "connect target", I will get a message

"Break at address "xxxxx" with no debug information available, or outside of program code."

To be more specific, I got message

"Break at address "0x58a8" with no debug information available, or outside of program code." for Cortex_R4, and got

"Break at address "0x7ea900" with no debug information available, or outside of program code." for C674x.

Is this some error I should look into?

Thanks,

Lola

0 Yiran Li1 over 5 years ago in reply to Yiran Li1

Intellectual 265 points

Hi Akash,

I tried using Tera Term to open the UART port. Nothing showed up.

I found a post with similar issue here: https://e2e.ti.com/support/sensors/f/1023/t/759524

One guy mentioned he suspected "an issue with the boot procedure of the device that is stopping the BSS from booting properly". But he didn't mentioned a solution (or I may didn't understand his solution).

Do you think this problem is related the boot procedure? If so, how can I fix this?

Thanks,

Lola

0 Yiran Li1 over 5 years ago in reply to Akash Gondalia

Intellectual 265 points

I want to add a few more things here:

After loading and running the programs for debug mode, the console stuck at "Debug: VitalSignsDemoMSS Launched the Initialization Task". I stopped the program. It gave me the messages as shown in the picture below. Do you think this indicate the problem is at the BSSPowerUp step?