AM2432: Some of the GPIO options are missing in SYSCFG tool

Hi Ramaiah,

I did the same selection as you "N20" it shows up OK, but GPIO0_4 instead of GPIO0_0. I am using the SysConfig 1.11.0 and the MCU+ SDK 08.01.00.36. It has the "Trigger Type":

Which SysConfig version and the MCU+ SDK version are you using?

Best regards,

Ming

I am using 

I am opening the SYSCFG toop start menu rather than from the SDK example. And selected the Device as Am243x_ALV_beta. part = ALV and package= ALV.

sorry for the typo error on the reply

I am opening the SYSCFG tool from the start menu rather than from the SDK example.

Device as Am243x_ALV_beta.

part = ALV and package= ALV.

Syscfg version: 1.11.0

SDK version: MCU+SDK for AM243x(08.01.00)

Hu Ramaiah,

You are seeing two different "views" of the SysConfig Tool.

Your first image is the MCU+SDK for AM243x SysConfig view.

Your second image is AM243x SysConfig-PinMux Tool view.

Both views are using the same AM243x deviceData source, however the MCU+SDK view expands upon the pinmux data by providing additional parameters and generating peripheral driver code.

Regards,

Zackary Fleenor

From above reply, my undersrtnding is "we can not set the trigger type by opening syscfg tool from start menu(pinmux view)". What are the different settings to do which allows me to replicate the  sdk syscfg tool view from start up memu.? My expectations/assumption is "syscfg is a tool which allows the user to configure most of the options per pin. Its not good to say here(sorry from my side), CUBEMX from ST is the tool which allows all the configs per pin.

Hi Ramaiahse,

The one screen capture which missing the "Trigger Type" is because you missed the "Software Product". If you select the MCU+ SDK 8.1.0 or 8.2.0. The trigger Type will appear, even you run the SysConfig from start menu.

Best regards,

Ming

Hi Thanks you verymuch for the quick responces.

My point was very clear on first reply. I.e if i work with "software product(sdk)" the "trigger type appears", otherwise(pinmux mode) it won't.

Thanks.

Hi Ramaiahse,

The SysConfig will generate the peripheral initialization/configuration code depending on the software environment (MCU+ SDK in AM243x case), so if there is not software environment is selected. The SysConfig will not work properly.

May I ask what are you trying to accomplish here to run SysConfig without MCU+ SDK?

Best regards,

Ming   

My intension is  to configure some of the pins (Am243x) and their properties as per my project requirement. Let's say i want the Pin A18 to be configured as GPIO input with property as trigger Input. Since i landed first with SDK in syscfg tool,i saw there is an option. But when i (un-intensionally) selected only the processor (without sdk) this option was not there. Then i tried to understand the behaviour / limitations of the syscfg tool by approching this forum. 

Basically i came from ST controllers as a work experience, where i use CUBEMX for most of the time which allows me to do alot on the pin configurations. I struck with that mindset and looking for same similarities in SysCFG tool.

we can close this topic as you already communicated what the SysCfg capable for.

I really appriciate your efforts(I am very happy with the speed of responce from TI team).

Thanks 

Ramaiah