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.

TMDS243EVM: Error recompiling sdk+mcu for AM234x

Part Number: TMDS243EVM
Other Parts Discussed in Thread: SYSCONFIG

Hi I'm trying to recompile the entire SDK and running into an issue.

Prerequisites:

  • Windows 10
  • mcu_plus_sdk_am243x_09_01_00_41
  • ti-cgt-armllvm_3.2.2.LTS
  • sysconfig_1.20.0
  • CCS 12.6
  • Everything installed in c:\ti

First of all, the following commands succeed without issues:

gmake -s libs PROFILE=release

gmake -s libs PROFILE=debug

gmake -s sbl PROFILE=release

gmake -s sbl PROFILE=debug

It is only when I try to rebuild the examples that I run into trouble.

Running "gmake -s examples PROFILE=release" results in a bunch of build commands that succeed until eventually I get the following error:


...
Boot image: am243x:r5fss0-0:freertos:ti-arm-clang C:/ti/mcu_plus_sdk_am243x_09_01_00_41/examples/drivers/epwm/epwm_duty_cycle/am243x-lp/r5fss0-0_freertos/ti-arm-clang/epwm_duty_cycle.release.appimage ...
Generating certificate for epwm_duty_cycle.release.appimage ...
Boot image: am243x:r5fss0-0:freertos:ti-arm-clang C:/ti/mcu_plus_sdk_am243x_09_01_00_41/examples/drivers/epwm/epwm_duty_cycle/am243x-lp/r5fss0-0_freertos/ti-arm-clang/epwm_duty_cycle.release.appimage.hs_fs Done !!!
.
Generating SysConfig files ...
Running script...
Error: Exception occurred calling addInstance()
at Proxy.<anonymous> (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\scripting\scriptingGuard.ts:46:10)
at scriptFunc (C:\ti\mcu_plus_sdk_am243x_09_01_00_41\examples\drivers\epwm\epwm_duty_cycle_sync\am243x-evm\r5fss0-0_nortos\example.syscfg:16:30)
at cb (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:113:7)
at withDeprecatedAccess (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\deprecatedAccessGuard.ts:14:10)
at runAsUserScript (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\scripting\scriptingGuard.ts:61:3)
at iteratee (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:111:5)
at baseEach (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11)
at Function.each (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:9409:52)
at iteratee (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:109:6)
at Mt (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11)
Caused by: TypeError: Cannot read properties of undefined (reading 'configurables')
at Object.getPinConfigurables (C:\ti\mcu_plus_sdk_am243x_09_01_00_41\source\drivers\.meta\pinmux\pinmux_am243x.syscfg.js:28:76)
at Object.getGpioPinRequirements (C:\ti\mcu_plus_sdk_am243x_09_01_00_41\source\drivers\.meta\pinmux\pinmux.syscfg.js:71:25)
at func (C:\ti\mcu_plus_sdk_am243x_09_01_00_41\source\drivers\.meta\gpio\v0\gpio_v0.syscfg.js:38:27)
at cb (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleRequirements\requirements.ts:26:6)
at guardCallbackAccess (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\moduleAccessGuard.ts:44:10)
at g.resolveRequirements (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleRequirements\requirements.ts:25:5)
at L.resolveRequirements (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:1214:23)
at L.initDynamicConfigurables (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:1058:8)
at Function.createInstanceImpl (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:155:11)
at Function.createInstance (C:\ti\sysconfig_1.20.0\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:1336:28)
makefile:229: recipe for target 'syscfg' failed
gmake[2]: *** [syscfg] Error 1
makefile.am243x:1717: recipe for target 'epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti-arm-clang' failed
gmake[1]: *** [epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti-arm-clang] Error 2
makefile:77: recipe for target 'examples' failed
gmake: *** [examples] Error 2


Any ideas?

Thanks

  • Hello ,

    I am looking at your query and you may expect reply by today.

    Regards,

    S.Anil.

  • Running "gmake -s examples PROFILE=release" results in a bunch of build commands that succeed until eventually I get the following error:

    Hello Emil Popov,

    I have compiled with the above command and I got below compilation errors.

    But I am failing at above project and this error is not same with the your error.

    Then , I tried to compile the same above project with the below command and then it does not throw an any error .

    PS C:\ti\mcu_plus_sdk_am243x_09_01_00_41> gmake -s -C .\examples\empty\am243x-lp\system_freertos

    I am still finding the Rootcasue for the above issue .

    makefile.am243x:1717: recipe for target 'epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti-arm-clang' failed
    gmake[1]: *** [epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti-arm-clang] Error 2

    Is is possible to you compile the above individual project with the command below and see if you have any issues .

    PS C:\ti\mcu_plus_sdk_am243x_09_01_00_41> gmake -s -C .\examples\drivers\epwm\epwm_duty_cycle\am243x-lp\r5fss0-0_freertos\ti-arm-clang

    Regards,

    S.Anil.

  • Hello Emil Popov,

    Can you please try with the new sdk and see still if you face any problems ?

    I assume that you have changed files in the SDK, which creates an issue.

    Since in my project I have also changed many things and I asked one more colleague to compile the entire project and see if he still has any errors.

    But in his setup there were no errors with the same SDK version.

    Regards,

    S. Anil.

  • Hi Swargam, I have not modified the example that fails, but I followed your advise.

    I reinstalled the MCU+SDK version 9.1.0.41 and tried again. The build failed in the same spot with the same error.

    Then, I decided to try different versions of the SysConfig tool and here are the results.


    SysConfig 1.18.0

    gmake -j -s scrub PROFILE=release --> SUCCESS

    gmake -s libs PROFILE=release --> SUCCESS

    gmake -s sbl PROFILE=release --> SUCCESS

    gmake -s examples PROFILE=release --> SUCCESS


    SysConfig 1.18.1

    gmake -j -s scrub PROFILE=release --> SUCCESS

    gmake -s libs PROFILE=release --> SUCCESS

    gmake -s sbl PROFILE=release --> SUCCESS

    gmake -s examples PROFILE=release --> SUCCESS


    SysConfig 1.19.0

    gmake -j -s scrub PROFILE=release --> SUCCESS

    gmake -s libs PROFILE=release --> SUCCESS

    gmake -s sbl PROFILE=release --> SUCCESS

    gmake -s examples PROFILE=release --> SUCCESS


    SysConfig 1.20.0

    gmake -j -s scrub PROFILE=release --> SUCCESS

    gmake -s libs PROFILE=release --> SUCCESS

    gmake -s sbl PROFILE=release --> SUCCESS

    gmake -s examples PROFILE=release --> FAILED ( with the same error as in the first post )

  • Hello Emil Popov,

    I can reproduce the issue at my side with new MCU+SDK and let you know status .

    Regards,

    S.Anil.

  • Swargam

    Can you please confirm that you have reproduced the issue and I should use version 19 of SysConfig until an official solution is found.

    If that is the case, I will close this issue.

  • Hello Emil Popov,

    I will provide reply by eod .Sorry for delayed responses.

    Regards,

    S.Anil.

  • Hello Emil Popov,

    I freshly downloaded the MCU+SDK and, as per the 9.1 MCU+SDK version recommendation to use the 1.18.0 System config.

    Then after compilation I did not get any errors with the above versions .

    So, please try to use the 1.18 version of the system config since at our side we have tested all examples with the same version only.

    Regards,

    Anil.

  • Hi Swargam,

    As I reported earlier, I do  not have issues when using SysConfig 1.18.1,  1.18.2, and  1.19.0

    Anyway, you are telling me stuff that I  already know. Have a nice day.