SysConfig Pin Abstraction Code

Kier

Other Parts Discussed in Thread: SYSCONFIG

Hello,

I would have expected that one of the more useful outputs of SysConfig generated code would be an abstraction of the pin function from the pin number.

For example I have configured GPIO91 to be a HW_FLT_LATCH in the SysConfig tool. I had hoped the code generated would have the following macro defined somewhere.

#define HW_FLT_LATCH 91U

My application now just needs to refer to HW_FLT_LATCH and it does not need to be modified if/when we change the pin allocation.

Am I missing a button click somewhere to produce this mapping or does SysConfig simply not do this?

Thank you.

over 3 years ago

0 JohnS over 3 years ago

TI__Guru**** 162875 points

Can you let me know which device you are using?

Regards,

John

0 Kier over 3 years ago in reply to JohnS

Mastermind 9470 points

Yes, it's TMS320F2837xD. Apologies I hadn't anticipated this would be pertinent to my question.

0 JohnS over 3 years ago in reply to Kier

TI__Guru**** 162875 points

Kier,

Thank you for providing the device. The device matters as the code generation templates are owned by the respective device teams. I will send this over to the C2000 team to comment. Personally, I think the request is reasonable and for some other device families this is done today.

Regards,

John

0 Kier over 3 years ago in reply to JohnS

Mastermind 9470 points

Many thanks John!

0 Nima Eskandari over 3 years ago in reply to Kier

TI__Guru 52040 points

Kier, very interesting, why do you need the #define HW_FLT_LATCH GPIO_91_GPIO91

Are you planning on changing the pinmux later?

0 Kier over 3 years ago in reply to Nima Eskandari

Mastermind 9470 points

Not the pin mux but rather the pin selection. At the moment I'm using the controlCARD for prototyping but later we'll be using our own control board so there's a always a chance we might need to use a different input pin. In this scenario it makes sense (to me) to manage that centrally in the SysConfig file without change to the application code.

0 Santosh Jha over 3 years ago in reply to Kier

TI__Guru 50611 points

Kier,

Due to US holiday please expect response by tomorrow.

0 Kier over 3 years ago in reply to Nima Eskandari

Mastermind 9470 points

Nima,

Apologies. I can see why you asked the question now. My code sample in the OP was wrong since it mapped HW_FLT_LATCH to the pin mux value. I meant to map it to the pin number, i.e. 91U as shown in this example. Nonetheless the request still holds.

pin_state = GPIO_readPin( HW_FLT_LATCH );

0 Vince over 3 years ago in reply to Kier

TI__Mastermind 19795 points

Hi Kier,

We actually have that built into Sysconfig, so you should be okay to use as you have mentioned! A mapping from "myGPIO0" (or whatever you name it) gets generated in board.h. See below, where I created a GPIO called "HW_FLT_LATCH" and changed it from GPIO0 to GPIO91 as you mentioned:

You can then use this "HW_FLT_LATCH" as you mentioned. Let me know if any questions!

Regards,

Vince

0 Kier over 3 years ago in reply to Vince

Mastermind 9470 points

Hi Vince,

Thank you. That's very encouraging but I think my problem now is that there's no sign of board.h being produced. I only get the following files produced:

...

Do I need to push a button somewhere?

0 Vince over 3 years ago in reply to Kier

TI__Mastermind 19795 points

Hi Kier,

Typically the board.h and board.c files don't show up until the project is built, could you try building the project?

Regards,
Vince

0 Kier over 3 years ago in reply to Vince

Mastermind 9470 points

Hi Vince,

Thanks but I have the built the project already. There's never been files called board.c and board.h generated for my F2837xD based project. Here is the generated file list:

From this, it looks unlikely that I will get board.h. Is it possible to add this file to the list?

Kier.

0 Kier over 3 years ago in reply to Kier

Mastermind 9470 points

Hi Vince,

Please find attached my file. Can you generate board.h with this please?

Kier.Portpin.zip

+1 Nima Eskandari over 3 years ago in reply to Kier

TI__Guru 52040 points

I think this is an issue with your project setup. Did you start from an example or did you add sysconfig to the project yourself? I am assuming the SW product is not added correctly.

e2e.ti.com/.../faq-how-do-i-add-sysconfig-support-pinmux-and-peripheral-initialization-to-an-existing-driverlib-project

Take a look at:

https://www.ti.com/lit/spracx3

0 Kier over 3 years ago in reply to Nima Eskandari

Mastermind 9470 points

Thanks Nima for the info.

The syscfg file was given to me by my Hardware Team about 6 months ago. They used the standalone SysConfig tool...

https://www.ti.com/tool/SYSCONFIG

...and created a brand new configuration for F2837xD_337ZWT (BGA) then filled in the pin allocation accordingly. They then gave me the syscfg file to begin the software. The code always generated just fine but board.c/board.h were never generation options, only pinmux.c and pinmux.h.

Further to your comment "SW product is not added correctly" I tried creating a new project in the standalone tool and could repeat the missing board.c/.h using the following settings:

In these circumstances, board.c and board.h are not generated.

However selecting Software Product...

Means that that board.c and board.h are generation options.

So to anybody reading this, to cut a long story short, if sysconfig generates pinmux.c/pinmux.h but not board.c/board.h it means you have chosen, rightly or wrongly, a "bare metal PinMux project".....whatever that is.

Code Composer Studio™︎

Code Composer Studio forum

SysConfig Pin Abstraction Code