• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 2005 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.

CC2642R: Problems with XDC / Configuro

Joshua Meyer
Expert 1080 points
Part Number: CC2642R
Other Parts Discussed in Thread: CC2640R2F,

Hello,

I am trying to get a project up and running on a custom board with a CC2642. We already have things working on the same hardware with the CC2640R2F. 

I've started with the simple_peripheral project from the cc26x2_sdk_1_60_00_43 SDK version. For a while I was making progress I had it building and was working on debugging an exception. I tried to enable an exception handler and since then I haven't been able to get the project to build. Even after removing all the exception handler changes and rolling back to an old revision I know built I'm getting the same error. Perhaps I'm not versioning some files that I need to be? Here is the console output with the errors:

**** Build of configuration FlashROM_Release for project RC_App_2642 ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k -j 4 all -O

TOOLS/subdir_rules.mk:12: recipe for target 'build-1260596559-inproc' failed
js: "C:/ti/xdctools_3_50_04_43_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/ccsv7/ccs_base;C:/ti/simplelink_cc26x2_sdk_1_60_00_43/source;C:/ti/simplelink_cc26x2_sdk_1_60_00_43/kernel/tirtos/packages;C:/ti/simplelink_cc26x2_sdk_1_60_00_43/source/ti/ble5stack;C:/ti/xdctools_3_50_04_43_core/packages;..;'.
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Error 1
gmake.exe: *** Deleting file `package/cfg/ble_release_pem4.xdl'
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.h'
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.c'
js: "C:/ti/xdctools_3_50_04_43_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-1260596559-inproc] Error 1
gmake: *** [build-1260596559] Error 2
TOOLS/subdir_rules.mk:9: recipe for target 'build-1260596559' failed
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

  • 0
    Expert 1080 points

    Just caught this further up in the build as well, probably closer to the root cause:

    >> Compilation failure
    ICall/subdir_rules.mk:9: recipe for target 'ICall/icall.obj' failed
    "C:/ti/xdctools_3_50_04_43_core/packages/xdc/cfg/global.h", line 39: fatal error #1965: cannot open source file "C:/Project/Workspace/RC_App_2642/FlashROM_Release/configPkg/package/cfg/ble_release_pem4.h"
    1 catastrophic error detected in the compilation of "C:/ti/simplelink_cc26x2_sdk_1_60_00_43/source/ti/ble5stack/icall/src/icall.c".
    Compilation terminated.
    gmake: *** [ICall/icall.obj] Error 1


    Worth noting that I've imported the projects into a brand new workspace, and still have the same issue.

  • 0 in reply to Joshua Meyer
    TI__Guru** 105180 points
    Hello Joshua,

    It seems that something in your projectspec file and/or the SDK has been modified, such as the RTOS config file. 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.

    For the project properties, make 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.

    Best wishes
  • 0 in reply to JXS
    Expert 1080 points
    Yeah, I think I was being a little to aggressive with trying to share files between the new project and my R2F version. Something in our custom board files was causing the issue, I'm slowly pulling custom changes into the board files for the new project and it's going well so far.

    Thanks for the tip on the Variant, I'll take a look.

    -Josh
  • 0 in reply to Joshua Meyer
    TI__Guru** 105180 points
    Ok, looks like you're on the right track. Probably something got pulled in from the R2 SDK as you suspect.

    BTW, I think you have the honor of the first CC2642R support inquiry!

    Best wishes
  • 0 in reply to JXS
    Expert 1080 points
    Not sure how to feel about breaking new ground on the CC2642, not sure if I should be excited or terrified :)

    Anyways, I've run into the same issue with take 2 of my port attempt. I more slowly pulled changes into the project and things were going well until I tried to flip the target from CC2652 to the CC2642 in the *.ccxml file. When I switched it a new CC2642R1F.ccxml file was generated. I started getting the same build errrors as referenced above after I made the change.

    I reverted to my last working build in git, and still get the build errors. I am only versioning my project specific files, not the SDK. After the issues with the initial attempt I made my entire SDK install read-only to insure I didn't accidentally change anything in there. I also did a directory diff against a clean install of the SDK and there are no differences.

    This issue is somewhat baffling as I would expect rolling back in version control / doing a full rebuild to correct it. Unless I've found some strange bug in the SDK / CCS there has to be something driving these changes that I'm missing in version control...
  • 0 in reply to Joshua Meyer
    Expert 1080 points
    Where should I be checking the variant? In the Project Properties -> General -> Project it's set to CC2652R1F, same setting in the default *.ccxml file. These were the default settings for the simple_peripheral example.