AM2432: SDK 9.0 patch required for the SYSCONFIG crash issue when many GPIOs are added

Hi Michael,

Thank you for your query.

I am checking the above details internally. Please allow some time to revert back.

Regards,

Tushar

Hello Tushar, 

We use MCU+SDK v09.00.00.35 and Sysconfig version 1.17. 

I don't understand above you refer to "Please note you will need to use the Sysconfig version 1.20 as there are changes done in the device data also.".

Do you suggest that we should use the patch you provided for GPIO on SDK 09.00.00.35 and use the Sysconfig version 1.20?

We have seen some compatibility issues using SDK 09.00.00.35 with Sysconfig version 1.20. Do you in case know how this can be resolved?  


Thanks, 

Hong  

Hello Tushar, 

The issue is that we could not build our FW project with SDK 09.00.00.35 with Sysconfig v1.20.  It failed with the following error as below. 



Thanks,
Hong 

Hi Hong,

The sysconfig changes are backward compatible and will still work with old.syscfg. How your firmware project is build?

Is it build using Pinmux(i.e. without selecting product in sysconfig)?

Can you try reconfiguring the GPIO related setting manually as suggested below?

Please refer Soc driver for more details.

Please refer below screenshot.

Regards,

Tushar

Unlocking the thread for follow up discussion.

Regards

Karan

Hello Karan, 

Thanks for unlocking this thread. 

Our FW project failed to run with SYSCONFIG 1.20, see the following error:

I will try the re-adding GPIO solutions that was suggested above. 

Hong 

Hi Hong,

The error message is not complete enough.

Please send the full error logs with screenshot.

Regards,

Tushar

Hello Tushar, 

Please see the more detailed log and screenshot. 

Error: Exception occurred calling addInstance()
Hide Details...

at Proxy.<anonymous> (webpack://sysconfig/src/pinmux/services/scripting/scriptingGuard.ts:46:10) at scriptFunc (C:\Users\Hong\git\ti\firmware\projects\bootloader_am243\example.syscfg:16:26) 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 _t (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_00_00_35\source\drivers\.meta\pinmux\pinmux_am243x.syscfg.js:28:76) at Object.getGpioPinRequirements (C:\ti\mcu_plus_sdk_am243x_09_00_00_35\source\drivers\.meta\pinmux\pinmux.syscfg.js:72:25) at func (C:\ti\mcu_plus_sdk_am243x_09_00_00_35\source\drivers\.meta\gpio\v0\gpio_v0.syscfg.js:38:27) at cb (webpack://sysconfig/src/pinmux/services/objectManagers/moduleRequirements/requirements.ts:26:6) at guardCallbackAccess (webpack://sysconfig/src/pinmux/services/moduleAccessGuard.ts:44:10) at g.resolveRequirements (webpack://sysconfig/src/pinmux/services/objectManagers/moduleRequirements/requirements.ts:25:5) at j.resolveRequirements (webpack://sysconfig/src/pinmux/services/objectManagers/moduleInstance.ts:1214:23) at j.initDynamicConfigurables (webpack://sysconfig/src/pinmux/services/objectManagers/moduleInstance.ts:1058:8) at Function.createInstanceImpl (webpack://sysconfig/src/pinmux/services/objectManagers/moduleInstance.ts:155:11) at Function.createInstance (webpack://sysconfig/src/pinmux/services/objectManagers/moduleInstance.ts:1336:28)

Would you like to re-try in compatibility mode?

Hong 

Hello TI team,

After reviewing the scope of the patch change, the change in the patch is not trivial. At this moment that we are focus on release testing, we don't plan to take this patch for current release.

After our current release, our plan is to move to SDK 10 or latest.   

Thanks a lot for the effort here, we would like to drop this request. 


Thanks,
Hong