• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 484 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/CC1310: Does not enter LPM when build the soure code on another computer.

Khoa Tran
Prodigy 220 points

Part Number: CC1310

Tool/software: Code Composer Studio

Hi , 
We have 3 PC with CCS installed on it.
When we build it on the PC1 , the CC1310 works normal , it can be enter LPM and exit the LPM.
But when we build on the PC2 and PC3 all the function is normal ,but now it does not enter LPM.
Now the PC1 have some problems so we have to re installed the Window , now it act like PC2 and PC3.
Do you have any solution about this problem, cause our sensor is worked from battery , so it have to enter the LPM.
Regards,
Khoa Tran.

  • 0
    TI__Guru** 101520 points

    Hi Khoa Tran,

    Can you specify which CCS version you are using? Can you also specify which compiler and which version of it you are using?

    Can you specify which SDK version and which example you are basing your project on?

    To finish, can you explain how you are measuring if the device is entering in Low Power Mode?

    Best regards,

  • 0 in reply to Clément
    Prodigy 220 points

    Hi Clément,
    PC1 was on Windows 7 32bit CCS 7.0 Compiler TIv16.9.0.LTS , SDK TI RTOS 2.21.0.06 => Build Ok , CC1310 enter LPM
    Then PC1 re install Windows 7 32 bit , we also installed CCS 7.0 Compiler TIv16.9.0.LTS , SDK TI RTOS 2.21.0.06 => but now CC1310 does not enter LPM.
    PC2 is on Windows 7 32 bit , CCS 9.0.1 Compiler TIv18.12.1.LTS , SDK TI RTOS 2.21.0.06 => CC1310 does not enter LPM.
    PC3 is on Windows 10 64 bit , CCS 9.0.1 Compiler TIv18.12.1.LTS , SDK TI RTOS 2.21.0.06 => CC1310 does not enter LPM , we also try CCS 10.1.0 on PC3 but the result is the same.
    The example we are using is "rfWsnNode"
    We use BK Precison 5491B to measure the current consumption of CC1310. The first 30s , the CC1310 is running as normal mode ,then after 30s it gonna enter the LPM.
    Normal case : the first 30s current consumption is 1.8mA => enter LPM the current consumption is 5uA.
    Which the error : after 30s => current consumption is 1.4mA.
    We use the same board to measure the current consumption , the only change is the firmware built on differrent computer.
    Regards,
    Khoa.

  • 0 in reply to Khoa Tran
    TI__Guru 58425 points

    Hi Khoa Tran,

    I would advice you try to attach to the target after the 30s period to see what state the device is in. 1.4 mA likely means the ARM core is in IDLE but there is some peripherals still running.

    I notice you say you base your work on TI-RTOS 2.21.0.06. This free-standing TI-RTOS install is not supported for the CC1310 today, you are expected to use the CC13x0 SDK which ships with a TI-RTOS kernel (and drivers) that is up to date for the device in question:

    https://www.ti.com/tool/SIMPLELINK-CC13X0-SDK

    As you are on the "TI-RTOS SDK" side here and not the actual device SDK, it is hard to give you good tips on how to debug this as most of them would apply to the newer SDKs but if you can attach to the device and try to read out the "PowerCC26XX_module" structure and share the content here we could see if we can spot anything preventing you from entering standby.

  • 0 in reply to IUsedToBeARealPerson (M-W)
    Prodigy 220 points

    Hi , M-W

    We noticed in the end of all the hex file which the CC1310 can enter LPM is 

    :20FFA800000080011000C8FFFDFF58003AFFFFF1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF74
    :20FFC800FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00FFFFFFFF00FFFFFFC500C5FFAA
    :18FFE800000000FF00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF12
    :00000001FF

    and  in the end of all the hex file which the CC1310 does not enter LPM is 

    :20FFA80000008001100088FFFDFF58003AFFBFF3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF2
    :20FFC800FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00FFFFFFFF00FFFFFFC500C5FFAA
    :18FFE800000000FF00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF12
    :00000001FF

    So we replace the end of the hex file which the CC1310 does not enter LPM with the end one of the hex file which the CC1310 can enter LPM.
    Then we flash this modified hex => the CC1310 now can enter LPM.
    Khoa.

  • 0 in reply to Khoa Tran
    TI__Guru 58425 points

    Hi Khao,

    Could you share the "ccfg.c" files you use on both computers?

    Part of the changes you list there are part of the CCFG section which is configured during build time. The default ccfg file is pulled in from the SDK so if the SDK is the same then so should the CCFG section be (assuming the same project). In your case it seems your CCFG region does not fully match for some reason. Could you also share how you program the device (options used) etc? 

    If you could provide the actual project this would be super helpful, you could do this in private by PMing me here in the forum if you can't share it in public.

    Are you using the same device when testing the two images or is it two separate devices?

  • 0 in reply to IUsedToBeARealPerson (M-W)
    Prodigy 220 points

    Hi M-W, 

    Thanks for your help. We think we can fix this on our own.
    The owner of PC1 , he made some change in "ccfg.c" and he almost forgot about it.
    So now we edit "ccfg.c" like him then we good.
    Best Regards,
    Khoa.