A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
CCS/LAUNCHXL-CC26X2R1: Error: There is no AET resource to support this job.
Other Parts Discussed in Thread: CC2652RBHi George,
I try your proposal and i have now a new message in th econsole:
Cortex_M4_0: AutoRun: Target not run as breakpoint could not be set: Error enabling this function: There is no AET resource to support this job.
and also this message: in th editor space:
Can't find a source file at "/db/vtree/library/trees/mcpi/mcpi-3.70.00.12/exports/coresdk_cc13xx_cc26xx_3_70_00_12/kernel/nortos/startup/startup_cc13xx_cc26xx_ccs.c"
Locate the file or edit the source lookup path to include its location.
Cortex_M4_0: AutoRun: Target not run as breakpoint could not be set: Error enabling this function: There is no AET resource to support this job.
After a program is loaded to the target, the debugger will automatically try to set a breakpoint at the start of the 'main' function and run to it. The error message is telling you that it could not set that breakpoint because it lacks the AET resource to set it. It is likely that your program is in Flash. If so, hardware breakpoints must be used. There a limited number of hardware breakpoints available and if too many are set, then you get the error message above when you try to set another one. Note that other actions like enabling the profile clock or using C I/O also uses breakpoints under the hood.
Samuel CREGUT said:
and also this message: in th editor space: Can't find a source file at "/db/vtree/library/trees/mcpi/mcpi-3.70.00.12/exports/coresdk_cc13xx_cc26xx_3_70_00_12/kernel/nortos/startup/startup_cc13xx_cc26xx_ccs.c" Locate the file or edit the source lookup path to include its location.
Hi Ki,
I try one another PC and that time it is working well, i'm able to start and put breakpoints and it works well (I test with 2 breakpoints);
I didn't made any différences between the setups (i think).
To fix the problem, can you tell me if we can run the program not from flash ? how can we do that ? is it a CCS tuning ?
I also try to search to put SW breakpoints ? what is the différences between HW breakpoints and SW breakpoints ?
I try one another PC and that time it is working well, i'm able to start and put breakpoints and it works well (I test with 2 breakpoints); I didn't made any différences between the setups (i think).
Interesting. Try using a brand new workspace folder and a new target configuration file.
Samuel CREGUT said:
To fix the problem, can you tell me if we can run the program not from flash ? how can we do that ? is it a CCS tuning ?
The answer can vary. There are several things that may need to be done. One would be to modify your linker command file to allocate your code to non-flash memory. There may be other configurations needed.
Samuel CREGUT said:
I also try to search to put SW breakpoints ? what is the différences between HW breakpoints and SW breakpoints ?
Hi Ki,
I finally succeed to fix my problem; i solve by downloading a new SDK on the PC with trouble as i found it wasn't the same between the 2 PCs,
The good one is :
simplelink_cc13x2_26x2_sdk_2_40_00_81
and i was working with:
simplelink_cc26x2_sdk_2_30_00_34
or
simplelink_cc2652rb_ble_stack_sdk_3_10
so idon't fully understand why these 2 SDK were not working ...
But perhaps you know ?
Interesting. Thanks for the update and glad to hear it is working.
I do know that there are various revisions of the CC26x2 and CC13x2 and your need to use the right SDK version depending on your device/board revision. As for what exactly these dependencies are, I don't know (the device experts in the device forum would know). But that is likely the issue.
