• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 320 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.

Original question:

RTOS/CC1310: ERROR #10234-D unresolved symbols remain and ERROR #10010 error encountered during linking

CC1352P: Unresolved PINCC26XX_hwAttrs symbol from some library file.... what now?

radar
Expert 3550 points
Part Number: CC1352P
Other Parts Discussed in Thread: SYSCONFIG

Champs,

I am using the latest 6.10SDK and a fresh CCS install.  The ULTIMATE goal was to try to get a DMM application running with wsnnode + BLE.  For reference, I have done this more than 30 times using the CC1352P2 project from your SDK; but I've run int oa snag where I think I MAY need a little more output power, so I was trying to move this over to a CC1352P1 for testing.  The problem.... NONE of the CC1352P1 DMM projects build... I am trying:

/ti/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/examples/rtos/CC1352P1_LAUNCHXL/dmm/dmm_wsnnode_ble_sp_app

and I get this wonderful error that I have no idea how to fix.

gmake: *** No rule to make target 'build-1064950911', needed by 'configPkg/compiler.opt'.  (repeated ~50X)

So this happens on BOTH my Mac and PC downloads of the SDK using CCS 11.2... it's like the CC1352P1 DMM projects just don't work out of the box.  So if you could tell me how to fix those, that would be preferred; but since I tried something different and it was related to this other three that I never truly saw a resolution to; I figured I'd throw this into the mix.  So because I can't get ANY CC1352P1 DMM project to build at all; I decided to try using just the

/ti/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/examples/rtos/CC1352P1_LAUNCHXL/easylink/rfWsnNode

project under the premise that... I really don't need the BLE except to config the sub-1GHz so I COULD just hardcode it for testing in the interim to figuring out the dmm piece, and the example uses the same EasyLink stack that the dmm used so my code should port over pretty cleanly.  SO I thought.

So yes I have made some modifications; insomuch as I copied over my version of the NodeRadioTask.c/.h and what not, commented out what few dependancies io had on BLE... but when I link I get this error:

PINCC26XX_hwAttrs /Applications/ti/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/source/ti/drivers/lib/ccs/m4f/drivers_cc13x2.a<PINCC26XX.oem4f>

which is seemingly telling me that something in a library I didn't write isn't found...so I'm not sure what to do there either.  Notice in both paths I took I get to the same conclusion....something buried in code I didn't write is broken...send help!!!  Again, the real goal is to get a CC1352P1 DMM project running; and if that's easier than debugging this issue with the rfWsnNode project I'm fine with just skipping that (because in fairness, the rfWsnNode project DID BUILD CORRECTLY out of the box; it's something I added/referenced or more likely somethting that had magically worked in the past because the PIN stuff got linked from the BLE side of the code that is no longer there.  

But sub-1GHz Easylink at +20dBm  + BLE DMM is what I'm ultimately trying to get to.  

  • 0
    TI__Mastermind 25395 points

    Hi,

    I just tried to build dmm_wsnnode_ble_sp_app for the CC1352P1, using CCS 12 and the simplelink_cc13xx_cc26xx_sdk_6_10_00_29 , and it worked out of the box using the Gettings Started->Browse and Import examples.

    Could you try updating to CCS12?

    Regards,

    Arthur

  • +1
    TI__Expert 3550 points

    So.... sort of.  I was able to get it to build on CCS12; so my first comment would be.... the release notes for the SDK cite CCSv11.2 which is why I used that.  But it does seem to at least build with vb12; so it's a solution.  Now I would further state that this still did NOT build on MacOSX with CCSv12; so I think there's still a bug/problem there; same issue in that I get this:

    gmake: *** No rule to make target 'build-1064950911', needed by 'configPkg/compiler.opt'.  (repeated ~50X)

    Beyond that; there are some issues with the SDK; insomuch as there are typos in your config files it would seem;  Here are the warnings I get even on a successful build with CCSv12:

    Description Resource Path Location Type
    Invalid project path: Include path not found (C:\ti\simplelink_cc13xx_cc26xx_sdk_6_10_00_29\.;C::\ti\ccs1200\xdctools_3_62_01_16_core\packages). dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs pathentry Path Entry Problem
    Invalid project path: Include path not found (C:\ti\simplelink_cc13xx_cc26xx_sdk_6_10_00_29\source\ti\dmm\apps\dmm_wsnnode_ble_sp\source\wsn_node). dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs pathentry Path Entry Problem
    The selected TX Power requires Force VDDR in /ti/devices/CCFG forceVddr to be disabled, otherwise the output power may be wrong and the current draw too high. dmm_wsnnode_ble_sp.syscfg /dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs /ti/easylink/easylink radioConfigEasylinkPhyCustom.txPower SysConfig Problem
    XDCpath repository 'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/.;C:/ti/ccs1200/xdctools_3_62_01_16_core/packages' cannot be found! Visit project's 'Properties > General > Products' tab to adjust the XDCpath. dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs Problem

    So the two items in yellow; the first one is just wrong.  Thete's an extra '. at the end of the first path (which might be okay, not sure what the tool does with that actually; but the second one is wrong; has two ':' in it which will not work.  Again, it did build so maybe it doesn't need any of these; but it's wrong.

    And then the item in 'green'... okay, I get what to fix, but if the project is going to default to +20dBm (which it does) then it should default to clear that bit too; out of the box whouldn't have warnings.

    So in the end I have a fix, though not clear this works with MacOSX yet.  I'm going to try once again with a fresh install of both the SDK and CCS on my Mac to see if it works.

  • 0 in reply to radar
    TI__Expert 3550 points

    So definitely not working in MacOSX; not sure what to do there.

  • 0 in reply to radar
    TI__Expert 3550 points

    Guys, this is still broken on Windows too.  So this error is still there:

    <Linking>

    undefined first referenced
    symbol in file
    --------- ----------------
    PINCC26XX_hwAttrs C:/ti/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/source/ti/drivers/lib/ccs/m4f/drivers_cc13x2.a<PINCC26XX.oem4f>

    error #10234-D: unresolved symbols remain
    error #10010: errors encountered during linking; "dmm_wsnnode_ble_sp_app_CC1352P1_LAUNCHXL_tirtos_ccs.out" not built

    The symbol PINCC26XX_hwAttrs USED to be define in ti_drivers_config.c (in the v5.20 of the SDK); WHICH IS A DERIVED FILE!!!  What did you change it to in this new 6.x SDK, and whatever you changed it to, it was a terrible idea if the M4F driver library code didn't match.  I don't know how to fix this because I can't just add the symbol in there.