• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 253 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:

CC1352P: Help using internal NVM

CC1352P: CCS unexpected and wrong errors after good compiling results

Roberto Nucera
Intellectual 265 points
Part Number: CC1352P


Hello!

Can anyone tell me why I get many errors after a good compile result on a project, just moving on some file of the project itself?

Recompiling gets no errors again, then surfing through the project files, normally errors appear again. 

Thanks

Regards

Luigi

  • 0
    TI__Guru**** 220227 points

    Hi Luigi,

    The issue is with uint8_t, a standard variable type.  This is an error I would expect if the correct standard C library includes were missing from the file:

    #include <stdlib.h>
#include <unistd.h>

    Or directories are missing from the Arm Compiler search path: Project Properties -> CCS Build -> Arm Compiler -> Include Options.

    ${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/source
${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/kernel/tirtos7/packages
${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/source/ti/posix/ticlang

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 265 points

    Hi Ryan, I have two projects, the one that gives these errors is derived from the original, that surfing along the project does not show these errors:

    Please consider that these errors do not arise after a compile session. They arise when I open the project and then open a .C file....

    Is this a "pre processor like" running at edit time?

    I inserted the two lines you suggest, on the top of a C file:

    #include <stdlib.h>
    #include <unistd.h>

    but it does not resolve..... (the original prj does not include these two lines, and it does not give these errors)

    I've compared the two "Project Properties -> CCS Build -> Arm Compiler -> Include Options"  and they seem to be equal....

    ---------------------------

    Besides this argument, I'd like you gave me a tip in order to put somwhere a "delay(unint16 delay)" funcion somwhere on the project, before ZigBee stack starts:

    the reason is that in some cases (e.g. global power on from mains)  Many devices would start joining Coordinator at the same time! Placing a delay() whose period is determined by device MAC address, I would avoid an intense radio traffic....

    Many thanks

    Luigi

  • 0 in reply to Roberto Nucera
    TI__Guru**** 220227 points

    I recommend that you post to the Code Composer Studio E2E Forum for questions concerning the CCS environment and TI Compilers.  For staggering device joining, you can start a timer (see the UtilTimer_* APIs in util_timer.c) at the end of zclSample*_Init, upon the expiry of which will set a flag that can be serviced during zclSample*_process_loop to call Zstackapi_bdbStartCommissioningReq.  You may also find OsalPort_rand to be useful for random delay values.

    Regards,
    Ryan