• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1555 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

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/CC2642R: Not booting after power cycle

Matthias Arndt
Prodigy 45 points
Part Number: CC2642R
Other Parts Discussed in Thread: CC2650, CC2640

Tool/software: Code Composer Studio

Hello,

we are developing an application based on the ble5_simple_peripheral_oad_offchip_cc26x2r1lp example project. It works fine, if loaded with the debugger, but it won't restart after a power cycle.

I'm loading the BIM first and afterwards the app. With first test on a CC2650 this procedure worked. But for the CC2642, I'm probably missing one small but important step. In the build settings, the TI CC2652 is selected. Selecting the correct chip results in the same compiler errors as already experienced by Joshua Meyer in https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/657834?CC2642R-Problems-with-XDC-Configuro . Deriving from https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/404236 Question "What is the difference between CC2650 & CC2640? How do I move from CC2650 to CC2640 or different package sizes?", this should not be an issue (at least for the CC26X0 series).

I hope someone can give me a hint, where to take a deeper look.

Best regards
Matthias

Code Composer Studio Version: 8.0.0.00016
Simplelink cc26x2_sdk_2_10_00_44
Compiler TI v16.9.3.LTS

  • 0
    TI__Mastermind 39650 points
    Matthias,

    Noticed that you are using Compiler TI v16.9.3.LTS. CC26x2 SDK v2.10.00.44 in the release notes says it is dependent on 18.1.1.LTS. If you change to this compiler do you still see the same issue?

    Compiler download if you need it: www.ti.com/.../18.1.1.LTS
  • 0 in reply to Evan W
    TI__Mastermind 39650 points

    Matthias,

    Did you make any adjustments to the BIM? This also could be an issue with your vector table/linker command file as well. Maybe if you provided a memory map image as well that would be helpful to see how you are allocating your memory.

    Helpful document to keep in mind when adding OAD features to a project:

    http://software-dl.ti.com/lprf/simplelink_cc26x2_latest/docs/ble5stack/ble_user_guide/html/ble-stack-oad/add-ble-oad-to-proj.html

  • 0 in reply to Evan W
    Prodigy 45 points

    Dear Evan,

    thank you for your inspiring thoughts. Changing the compiler to 18.1.1.LTS will prevent the App from being built:

    configuring ble_release.xem4 from package/cfg/ble_release_pem4.cfg ...
generating custom ROM library makefile ... 
TOOLS/subdir_rules.mk:12: recipe for target 'build-1339487297-inproc' failed
js: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/cfg/Main.xs", line 48: XDC runtime error: can't find the library 'lib/boot.aem4' specified by package ti.targets.arm.rtsarm.  It wasn't found along the path 'C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_10_00_44/source;C:/ti/simplelink_cc26x2_sdk_2_10_00_44/kernel/tirtos/packages;C:/ti/simplelink_cc26x2_sdk_2_10_00_44/source/ti/ble5stack;C:/ti/xdctools_3_50_05_12_core/packages;..;'.
xdctools_3_50_05_12_core\gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Error 1
xdctools_3_50_05_12_core\gmake.exe: *** Deleting file `package/cfg/ble_release_pem4.xdl'
xdctools_3_50_05_12_core\gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.h'
xdctools_3_50_05_12_core\gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.c'
js: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-1339487297-inproc] Error 1
gmake: *** [build-1339487297] Error 2
TOOLS/subdir_rules.mk:9: recipe for target 'build-1339487297' failed
gmake: Target 'all' not remade because of errors.

    The BIM is the original as loaded with the example project. The command file is the bim_cc26x2_cc13x2.cmd. I hope that the memory map is helpful.

  • 0 in reply to Matthias Arndt
    TI__Mastermind 39650 points
    Hi Matthias,

    Thanks for the extra info, it actually seems like during your porting process, something got changed int he projectspec file and/or the SDK has been modified such as the RTOS config file. We generally recommend that you start with a base project from the SDK and add code to your new project from you previous project.

    For the project properties, make also sure CC2642R1F is selected as the Variant and not "Generic M4 Device". Your missing ble_release_pem4.h should be "ble_release_pem4f.h", for example.

    I suggest reverting to a clean SDK install and build the default simpel_peripheral project to confirm the build is correct. Then, add your changes one-by-one.

    Here is a few threads with similar issues.
    e2e.ti.com/.../2416656
    e2e.ti.com/.../587448
  • 0 in reply to Evan W
    TI__Mastermind 39650 points
    Hi,

    I'm going to close this post due to inactivity. To reopen this thread, just post a follow up question. Otherwise, after 30-days of inactivity from this post, this thread will lock.
  • 0 in reply to Evan W
    Prodigy 45 points
    Thank you Evan for your help. After several iterations of wiping off all CCS and SDK related files from the hard disc and reinstalling, I finally managed the BIM to work properly with the sample project. I don't know what is different to the attemps before. Changing neither the compiler version nor the device from the sample project. Once the sample project was able to restart after a power cycle, integrating our custom code was a quick task and our application is running smoothly.

    I think we have to preserve this combination of CSS, SDK and compiler and carefully test each change of one of these components carefully on a test machine before migrating the project.

    Best regards,
    Matthias