TMS320F280041C: Micro selection in CCS

Hi Aleksandr,

Thanks for reaching out to the E2E.

Due to inclement weather in our region, many of our subject matter experts are without power and unable to provide support at this time.  An expert will get back to you as soon as possible but it likely will not be until next week.

Best Regards,

Marlyn

That wont matter. You dont do anything at the pin level for your micro in your SW developement . For example for your pinmux you select which GPIO has which functionality. Thats it. No matter which type of F28004x device you have, it will do the same thing.

Does that make sense?

Nima

The code is witten for F28004x family. You can do your pinmux based on the package but the SW is the same. It will never address pin numbers. It will only address pins by their name.

For you analog, non GPIO pins, they are placed on different pins in different packages, but in your code you reference them again by name ADCA CH1, A1, and not by their pin names. So you will have the same code for your different device variant in a specific family.

Nima

Thank you for the answer. You confirmed what I suspected. Then, what happens if I configure a pin that does not exist on a package and try to use it? Hard fault, any other fault or nothing?

Alex

Unbound GPIOs which dont exist on a package are incredibly useful. For loopback testing and other thing. They are fully functional just not connected outside.

Incredibly useful for TI guys - sure. But if I make a MISTAKE I will never find out why a design does not work. I mean the compiler won't tell me that I made a mistake. No need to reply. You can close this thread.

Thanks,

Alex

I recommend you use the C2000 SysConfig which has pinmux support and you can see which GPIO and pins are connected to each other and the code is auto-generated,

This will close your gap between hardware package and SW.

Nima

Code from SysConfig is not compatible with InstaSpin labs. TI needs a better coordination between divisions. Either make InstaSpin labs to have the same files that come out of SysConfig or make an optional button in SysConfig to produce the code that is inside void HAL_setupGPIOs(HAL_Handle handle) function.

Alex

Yes. As we roll out SysConfig, the system level content will be using it as well.

Nima

Aleksandr,

I am going to close this thread. Can you mark the post which best marks the ANSWER by clicking the verify answer?

Nima