• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 413 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.

MCU-PLUS-SDK-AM243X: SysConfig not compatible anymore with newer SDKs

Felix Heil
Expert 1265 points

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

Hello,

We are experiencing an issue with SysConfig (1.10 and 1.11) and the newer SDK versions. (we are using a 08.00.02.13 SDK-Version)

when we are trying to generate the files via the cli (/dist/cli.js) of the SysConfig we are getting an error:


Error: cannot set 'intrEnable' to false: Type mismatch, expected = string, actual = boolean
    at Object.set (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\objectManagers\proxyHandlers\managedObjectProxyHandler.ts:60:11)
    at scriptFunc (X:\X\X\XX\X\X-produce\X\X.syscfg:161:32)
    at cb (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:94:27)
    at Object.withDeprecatedAccess (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\deprecatedAccessGuard.ts:14:10)
    at Object.runAsUserScript (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\scriptingGuard.ts:49:3)
    at iteratee (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:94:5)
    at baseEach (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:530:11)
    at Function.each (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:9409:52)
    at iteratee (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:92:6)
    at at (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:530:11)

this relates to the mcspi-setting when interrupts are not enabled. In our case:
mcspi1.intrEnable                  = false;

SysConfig GUI does not show any problems.

We can't use the current SDK. Is there a workaround?

Best regards,

Felix

  • 0
    Expert 1265 points

    My first investigation shows that in the js-files of the SDK the intrEnable was changed from boolean to string. Seems that's not the case in SysConfig.

  • 0 in reply to Felix Heil
    TI__Mastermind 25593 points

    Hey Felix,

    Thanks for digging in here. I will file a bug report for SysConfig to make sure this is aligned.

    I also would recommend always using the latest release of the MCU+ SDK. SysConfig dev and related code will be forward compatible so no need to re-develop. The latest version is 8.02.00.31

    https://dr-download.ti.com/secure/software-development/software-development-kit-sdk/MD-ouHbHEm1PK/08.02.00.31/mcu_plus_sdk_am243x_08_02_00_31-windows-x64-installer.exe

    A new version of the SysConfig tool (1.12) will also be available mid-April and should resolve any compatibility issues.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Expert 1265 points

    Hey Zack, thanks for the response.
    Yes I know there is a new version but we are using the 0.13 because of another vendor which works for TI who uses this package.
    I also noticed another field that is not available for the mcspi via cli:

    TypeError: unknown property: dataSize
    at Object.set (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\objectManagers\proxyHandlers\managedObjectProxyHandler.ts:75:9)
    at scriptFunc (X.syscfg:111:36)
    at cb (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:94:27)
    at Object.withDeprecatedAccess (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\deprecatedAccessGuard.ts:14:10)
    at Object.runAsUserScript (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\scriptingGuard.ts:49:3)
    at iteratee (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:94:5)
    at baseEach (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:530:11)
    at Function.each (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:9409:52)
    at iteratee (C:\ti\sysconfig_1.11.0\dist\webpack:\src\pinmux\services\scripting\runScript.ts:92:6)
    at at (C:\ti\sysconfig_1.11.0\dist\webpack:\node_modules\lodash\lodash.js:530:11)

    This happens at the field
    mcspi2.mcspiChannel[2].dataSize    = 32;

    which is set if you enter a value different to 8 for the dataSize.

    I guess this will make our current setup unuseable with the newer SDK-Versions.

    best regards

    Felix

  • +1 in reply to Felix Heil
    TI__Mastermind 25593 points

    Hello Felix,

    Felix Heil said:
    I guess this will make our current setup unuseable with the newer SDK-Versions.

    I don't think this statement is correct. Once you've resolved to the latest SDK-Version and associated SysConfig Tool release, we will have the ability to directly address any translation/migration errors that may be experienced if any at all. We have dedicated internal validation tests and backwards compatible sanity checks that are run nightly on both current production branch and future development branch code databases. Questions and insight like yours help us to make these better!

    In the meantime, I will close this ticket and we should create new threads for future issues.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Expert 1265 points

    Hey Zack,

    we found out the problem: The MCSPI was redesigned and our driver needed different access to the TI-Driver than before. That related to the new DMA-functionality in SysConfig and the dataSize which was not set in SysConfig anymore but directly at the driver-interface. A fix at our side resolved this problem at the end, but we were a bit surprised about that.

    So yes, we can watch this topic as resolved.