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.

MCU-PLUS-SDK-AM243X: LWIP TCP Server example (and more) not compatible with latest sysconfig V1.21.0

Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Sysconfig v1.21.0 throws the following error when importing opening enet_cpsw_tcpserver_am243x-lp_r5fss0-0_freertos_ti-arm-clang from mcu_plus_sdk_am243x_10_00_00_20

Perhaps a good idea to update the examples in the sdk to be compatible with the latest version of sysconfig?

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Setting up SysConfig...
Error loading C:\ti\mcu_plus_sdk_am243x_10_00_00_20\examples\networking\lwip\enet_cpsw_tcpserver\am243x-lp\r5fss0-0_freertos\example.syscfg
Would you like to re-try in compatibility mode?
Error: Exception occurred calling addInstance()
at Proxy.<anonymous> (webpack://sysconfig/src/pinmux/services/scripting/scriptingGuard.ts:46:10)
at scriptFunc (C:\ti\mcu_plus_sdk_am243x_10_00_00_20\examples\networking\lwip\enet_cpsw_tcpserver\am243x-lp\r5fss0-0_freertos\example.syscfg:44:35)
at cb (webpack://sysconfig/src/pinmux/services/scripting/runScript.ts:113:7)
at withDeprecatedAccess (webpack://sysconfig/src/pinmux/services/deprecatedAccessGuard.ts:14:10)
at runAsUserScript (webpack://sysconfig/src/pinmux/services/scripting/scriptingGuard.ts:61:3)
at iteratee (webpack://sysconfig/src/pinmux/services/scripting/runScript.ts:111:5)
at baseEach (webpack://sysconfig/node_modules/lodash/lodash.js:530:11)
at Function.each (webpack://sysconfig/node_modules/lodash/lodash.js:9409:52)
at iteratee (webpack://sysconfig/src/pinmux/services/scripting/runScript.ts:109:6)
at xt (webpack://sysconfig/node_modules/lodash/lodash.js:530:11)
Caused by: TypeError: Cannot read properties of undefined (reading 'interfacePins')
at Object.getPinConfigurables (C:\ti\mcu_plus_sdk_am243x_10_00_00_20\source\sysconfig\drivers\.meta\pinmux\pinmux_am243x.syscfg.js:35:57)
at Object.getPinRequirements (C:\ti\mcu_plus_sdk_am243x_10_00_00_20\source\sysconfig\drivers\.meta\pinmux\pinmux.syscfg.js:7:25)
at getPeripheralRequirements (C:\ti\mcu_plus_sdk_am243x_10_00_00_20\source\sysconfig\networking\.meta\enet_cpsw\am64x_am243x\enet_cpsw_am64x_am243x_pinmux.syscfg.js:189:30)
at Object.pinmuxRequirements (C:\ti\mcu_plus_sdk_am243x_10_00_00_20\source\sysconfig\networking\.meta\enet_cpsw\am64x_am243x\enet_cpsw_am64x_am243x_pinmux.syscfg.js:373:30)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Hello Toby,

    The TI software tools (CCS, SysConfig, etc) are developed by a central team, different from the software development team who works on the code for a specific processor. There is no good way to make sure that the latest version of these different software "products" are in lockstep across the hundreds of different devices that use the same software tools.

    However, we document the version of SysConfig and CCS that was used to develop that version of the SDK in the SDK's Getting Started notes:
    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/10_00_00_20/exports/docs/api_guide_am243x/SDK_DOWNLOAD_PAGE.html

    So you should always be able to tell which version of the tools is guaranteed to work with which version of the SDK.

    Regards,

    Nick