TIDA-010024: TIDA-010024 - Issue

Hi Yash,

From the error message, it looks like you have some issues with the hardware connection on JTAG. Refer to the following link to see if this helps in addressing your issue.

http://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

Do you get this error only after the breakpoint?

Can you please also confirm the version of SDK that you are using?

With Regards,

Hello Prasanna,

Appreciate your quick response.

1.  I am using the same hardware for different codes(15.4 Sensor and Collector) as well and they work as expected. If I am not wrong, if there was a problem with JTAG(Hardware per se) other codes also wouldn't have worked properly, right? I will still check the link you provided for any help.
   
   ****EDITED -
2. No, I get this error after I hit the play button. Actually had to wait for a few seconds before the error started showing up in the Debug window. (Previously I was hitting the play and stop buttons almost immediately one after the other, the error didn't show up in that short window).
   ****
   
   
3. Were you asking for the Simplelink SDK or TIDA version?
   Anyways,  I am using simplelink_cc13x2_26x2_sdk_3_20_00_68 and for TIDA-010024 I am using 6LoWPAN_Mesh_TI_15_4_Example_CC1312R_V2.0.0.0  .

Furthermore, are there any specific requirements of CCS to run 6LoWPAN_Mesh_TI_15_4_Example_CC1312R_V2.0.0.0  ? 

Thanks and Regards,

Yash.

Hi Yash,

3. I think this may be due to SDK version you are using. For this TIDA example, simplelink_cc13x2_26x2_sdk_2_40 version has to be used. 

With Regards,

Hi Prasanna,

I am sorry. Since I have the 3.20 SDK as the latest installed, I assumed the TIDA project is using that. I have both the SDK's installed (3.20 as well as 2.40). Is there any way to know which SDK is the TIDA project using?

I tried to search it and I can see this that the SDK install directory shows the path to 2.40 SDK.

(under Linked Resource -> Path Variables -> COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR -> C:\ti\simplelink_cc13x2_26x2_sdk_2_40_00_81)

Does this mean that the project automatically detected the 2.40 SDK and is using it? If yes, then the above problem persists.

******************* EDIT 

I confirmed that the project is using SDK_2_40_00_81.

I can see that under Properties -> General -> Products -> SimpleLink CC13x2 26x2 SDK -> SDK 2.40 is checked.

Are there any other things that I can verify? 

There is this warning I am getting, but I get this warning with the older version also. It says another compatible version will be used. Although I doubt it but could this be the reason?

"This project was created using a version of a compiler that is not currently installed - 18.1.1.LTS [ARM]. Another version of the compiler will be used during build - 18.12.1.LTS." 

**********************

Thanks and Regards,

Yash.

Hi Prasanna,

An update since the last time -

I downloaded and tried again with 18.1.1.LTS [ARM] compiler, but I am still facing the same issue.

So, just to be sure that I am using the correct environment/setup. I will just list it down again, Let me know if anything is aberrant - 

CC1352R,     

REV E,

SDK 2.40,

CCS - Version: 9.0.1.00004,

 18.1.1.LTS [ARM] compiler

Also, as you mentioned earlier that " For this TIDA example, simplelink_cc13x2_26x2_sdk_2_40 version has to be used. " 

But as I was referring to this document http://www.ti.com/lit/an/tida027/tida027.pdf I saw the following Abstract -

The 6LoWPAN mesh TI designs implemented the 6LoWPAN mesh stacks based on the SimpleLink™ CC13xx SDK (Software Development Kit) TI-15.4 stack example. As the SimpleLink SDK is evolving with new features or bug fixes, developers might need to integrate the existing 6LoWPAN mesh software into a new SimpleLink SDK TI-15.4 example. As the TI-15.4 stack supports 2.4-GHz frequency bands in the SimpleLink CC26x2 SDK, developers might be also interested in integrating the 6LoWPAN mesh stacks into the 2.4-GHz-based TI-15.4 example. This article aims to provide details on how to achieve this. The corresponding TI designs are TIDA-010003 and TIDA-010024.

If I am understanding it correctly, I can merge the 6LowPan example into 15.4 Sensor of any SDK 2.40 and above, also it is independent of the SDK being used. Having said that, I am finding contrast in your statement and the functionality of 6LowPan described in the abstract above.

Does it mean that the 6LowPan example is to be ported/migrated for the newer SDK accordingly by the user?
If yes, which documentation is to be followed for the same? 

I am a bit confused and I know that I might be wrong with my interpretations here, so please feel free to point out my mistakes.

Thanks and Regards,

Yash.

Hi Prasanna,

Any updates on this issue?

Thanks and Regards,

Yash.

Hi Yash,

Sorry for the confusion. Statement on the TIDA-010024 ( http://www.ti.com/lit/an/tida027/tida027.pdf ) is correct. You can merge this example on any SDK version above 2.4. 

However, the example build works only with the CC1312, it does not work for CC1352. To work with CC1352R, the example has to be ported based on the CC1352 sensor example available in the SDK v2.40.

Alternatives, the quick/easy fix would be to use CC1312R EVM instead. 

With Regards,

Hi Prasanna,

Understood that part. Thanks.

Also, the question I asked prior to that is still unanswered.

I will ask it again here -

I had tried the 6LowPan example some time back with the older version of TIDA and REV C (SDK 2.30) boards and at that time it worked seamlessly. 

Now the setup is just modified, I am using the 6LoWPAN_Mesh_TI_15_4_Example_V2.0.0.0 and REV boards (SDK 2.40 (selected automatically by CCS from the available SDK's)). And building and debugging this setup gives me DAP errors(attached a screenshot above).

So is that this newly updated 6LowPan is not compatible with CC1352?

Thanks and Regards,

Yash.

Hi Yash,

Yes, you are right. In earlier versions of SDK (2.3 and prior), projects were compatible with CC1312 and CC1352. You could seamlessly switch between these two devices.

Unfortunately, on later versions of SDK, they are not directly compatible. You have explicitly port projects from CC1312 to CC1352.  This has affected not only 6lowPan project, but it is across all the projects using CC1312 and CC1352. 

With Regards,

Hi Prasanna,

Now it's clear. Thanks. My initial issue is resolved.

But I still have a couple of questions,

If you don't mind, may I ask why was the compatibility for CC1352R removed in the newer 6LowPan?

Also, will you please point me to the porting/migrating guide that is needed to port the 6LowPan project to CC1352?

Thanks and Regards,

Yash.