LAUNCHXL-CC1310: rfPacketErrorRate code, CCS 901, and cc1310 launchpad

Hi Alexis,

Thanks for the rapid response. The cc1310 SDK was added by restarting CCS v901 install and then selecting the kit. That went fine, Then I went to the software drivers and imported the rfPacketErrorRate into CCS. No issue. Build, no issue. The issue is running the debugger and single stepping into the code. It seems some sections of the code were object only or pre built and I can not single step thought them. Get that error and can view disassembly only. I solved the first one, power_init call by including the software source right before the call and that worked, but on the second problem, the source is no where to be found or at leas I can not find it. Can you try single stepping. It only a few step before I run into the issue. Thanks.

Other question is, what is the difference between the Free CC1310 SDK and the one that is $29.00? Does the purchase SDK work with the Launchpad? If so, I'll buy it but if it just has the same examples and more than I need to focus on getting the sample to work. I also imported the RTOS tx from the free SDK today, and it does not build. 

Where do you find that the SDK cost anything? The SDK is free. You are not looking at the launchpad by any chance? 

I installed the CC1310 SDK first using Code composer install. It is simplelink_cc13x0_sdk_3_10_00_11. I noticed debugger code stepping error uses a different SDK.

Here was the debugger code stepping error.

Can't find a source file at "/db/vtree/library/trees/mcpi/mcpi-4.10.01.00/exports/coresdk_cc13xx_cc26xx_4_10_01_00/kernel/nortos/dpl/ClockPTimer_nortos.c"
Locate the file or edit the source lookup path to include its location.

I then searched for the kit named in the above error, coresdk_cc13xx_cc26xx_4_10_01_00, but it apparently does not exist either in code composer install or in resource explorer via import.

I downloaded the cc13x2_26x2_sdk_3_10_01_11 SDK to see if this might come close as it is a device combination kit, but this kit does not have the cc1310 launchpad listed in the code example and other code for other devices did not build on the cc1310 launch pad.

Any ideas where this particular SDK might be or suggestions on location of the cc1310 demo source code that does not generate the above error in the debugger looking for missing source?

Thanks.

Dan 

Hi Dan,

Can you post a screenshot of your workspace?

Thanks,

Alexis

Alexis, 

Yes. Below are 3 screen shots of my debugging session using CCS v9, the CC1310 launch pad, and rfpacketRx code. The first is initial condition after hitting the debug button and can see main_nortos.c source. The second is single stepping into CC1310_LAUNCHXL.c to the Power_Init function call. The third is what happens next stepping into this function, no source found. So, I can copy that code file locally and get past that problem but then I get all kinds of other problems similar, missing source for kernel files etc.... So something is very strange that it is possible to build, load and execute code but then the debugger seems to no longer find the source and is looking at some pointer in an SDK that does not exist.

Alexis,

Ok. I did all of the above including deleting the project and then importing it the way you suggest. I get the exact same path error. Can you check if you have access to that path? If you do, perhaps you might try disabling your access then single stepping through the code again. Might duplicate it that way.

I also check for any unresolved includes and it comes up as zero. This is an odd issue because the code builds installs but then there are pointer problems with the single stepping. Wondering if you are inside TI or doing the example on a computer outside. Maybe still something I'm missing but it seems to be some kind of debugger pointer problem that is stuck to the legacy source code in some kit that was used when the example was built. 

Ok. So I clicked on the down arrow next to the debug symbol and then selected Debug Configurations. I then selected the Source tab. I noticed the source lookup path said "Device Library Source - no 'src" folder for CC1310F128. Not sure why but that is that default setup. And I did start with a brand new workspace and reloaded this example for a brand new project.

CCS debugger apparently does not know where the SDK source code resides. I manually added the paths by clicking on Add button to the right, then selecting Absolute File path and browsing to the source code under the SDK\Kernel\nortos\dpl, SDK\source\ti\drivers, I added these paths and hit apply. Then hit debug again and started single stepping and it works now. the source is found, at least for as far as I have single stepped which is past both of my initial problems.

I would consider this closed, but wonder why SDK code source paths don't get added to CCS when the SDK is loaded. The workspace is added, but the kit source is not. Appears to be a bug, but not sure. Anyway. Thanks.