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.

RTOS/SIMPLELINK-MSP432-SDK: TIRTOS examples give build warning - package/cfg/debug_pem4f.c statement is unreachable

Part Number: SIMPLELINK-MSP432-SDK

Tool/software: TI-RTOS

Hi Guys

I've set up a project based off the MSP432 Wifi SDK plug in (1.40.00.02) "power measurement" example using TIRTOS in MSP432P4 SDK 1.50.00.12 and XDC Tools 3.50.3.33_core.

Using either the Debug or Release build configurations I get the same build warnings as part of the linked TIRTOS project:

Looking at the generated file debug_pem4f.c, the offending functions/line all looks similar to this one:

I also get these warnings when I drop a .cfg into the main project instead of link in the RTOS.

Although the program appears to work correctly I'd like to get rid of these warnings. Any help?
Stewart

  • It seems my pictures didn't show up. The generated code has the warning on the last return line.

    /* Object__get__S */
    xdc_Ptr ti_sysbios_hal_Hwi_Object__get__S(xdc_Ptr oa, xdc_Int i)
    {
        if (oa) {
            return ((ti_sysbios_hal_Hwi_Object__ *)oa) + i;
        }
    
        if (ti_sysbios_hal_Hwi_Object__count__C == 0) {
            return NULL;
        }
    
        /* the bogus 'const' in the cast suppresses Klocwork MISRA complaints */
        return ((ti_sysbios_hal_Hwi_Object__ * const)ti_sysbios_hal_Hwi_Object__table__C) + i;
    }

  • Stewart,

    Let me look into this for you and I’ll get back to you soon.
  • If you need any further details on reproducing it, just let me know.
  • Stewart,

    My apologies for the delay. I'm currently trying to reproduce, but running the WiFi plugin 1.40.00.02 with SDK (v1.50.00.07) with XDS Tools 3.50.3.33_core and I'm not getting any warnings. I'm installing 1.50.00.12 to see if this changes anything. Can you please give me the exact warning message you are receiving?
  • Stewart,

    Seems to work with no warnings on 1.50.00.12 SDK as well. Have you tried starting from the example 'power_measurement' without changing anything and see if it produces that warning you are receiving on your setup?
  • I imported power_measurement fresh using Resource Explorer (TI-RTOS, CCS). The warning doesn't seem to show up in the "problems" window, but it's definitely there for me in the Build Console of project tirtos_builds_MSP_EXP432P401R_release_ccs - just need to scroll up a page:

    `C:/tiworkspace_v7/tirtos_builds_MSP_EXP432P401R_release_ccs/src/sysbios'
    Build of libraries done.
    clem4f package/cfg/release_pem4f.c ...
    "package/cfg/release_pem4f.c", line 9721: warning: statement is unreachable
    "package/cfg/release_pem4f.c", line 10490: warning: statement is unreachable
    "package/cfg/release_pem4f.c", line 10853: warning: statement is unreachable
    "package/cfg/release_pem4f.c", line 11135: warning: statement is unreachable
    "package/cfg/release_pem4f.c", line 11396: warning: statement is unreachable
    "package/cfg/release_pem4f.c", line 11639: warning: statement is unreachable
    'Finished building: ../release.cfg'
    ' '
    gmake[1]: Leaving directory 'C:/tiworkspace_v7/tirtos_builds_MSP_EXP432P401R_release_ccs/Debug'
            1 file(s) copied.
    making ../src/sysbios/sysbios.aem4f ...
    gmake[1]: Nothing to be done for 'all'.
    gmake[1]: Nothing to be done for 'configPkg/linker.cmd'.
    making ../src/sysbios/sysbios.aem4f ...
    gmake[2]: Nothing to be done for 'all'.
    
    **** Build Finished ****

    XDCtools 3.50.2.20 or 3.50.3.33 doesn't matter.

    SimpleLink MSP423P4 SDK 1.50.0.12

    The WiFi plug in is not enabled on the separate RTOS project so I don't think it's having an effect.

  • I forgot to add compiler is TI v17.9.0.STS.
  • Stewart,

    Can you go to TI v16.9.4.LTS? I've gotten word that we haven't verified the SDK and it's components to work on TI V17.x compilers and won't be until 1Q18. Can you also inform me how you managed to get TI v17.9.0.STS?
  • Going to v16.9.4.LTS fixed it. Importing from Resource Explorer had the compiler default to v17.9.0.STS.

    Is there a compatibility matrix of compilers, SDKs etc anywhere? The MSP432P4 SDK release notes state:
    TI Code Generation Tools
    ARM version 16.9.3.LTS or later

    It is likely v17.9 came from a general CCS update, but I'm not sure. I'm also working with ccXX00 BTLE/sub1Ghz range of parts too.
  • Stewart,

    Thanks for the feedback actually. I'm going to pursue this to try and fix this with the appropriate teams! I imagine it came from the general CCS update as well but still, good feedback for the teams to make sure everyone stays on the same page. V17 should be good for the SDK in 1Q18.
  • Thanks Evan. Good to see a keen interest from TI!

**Attention** This is a public forum