I am working on my first TI ARM project using CCSv5 and TI-RTOS. I am developing my software on the TM4C123G Launchpad until my real custom target board is ready to use. In this process, I am following a very helpful post:
http://processors.wiki.ti.com/index.php/Migrating_a_TI-RTOS_project_to_a_custom_development_board
The basic idea is that you start with a working example project, rename the files and make a bunch of changes to reassign the assets of the MCU to work with TI-RTOS. I have In this process it describes how one must manually edit the files to reflect how my custom board config files should be configured for use on the launchpad.
When I looked at the Pinmux C and H files produced the information was not even close to how the TI-RTOS config files use it. As I see it, it requires a serious cut and paste job to shoe-horn the information into the structure of the config files.
I thought that perhaps I could use the pinmux files as is and only put the TI-RTOS specific code in the original example config files.
Specifically: I took the UARTECHO example code and am converting the EK_TM4C123GXL. (h,c,cmd) files to reflect my target boards name and io configuration.
Will this approach work as long as I call the pinmux config function prior to the TI-RTOS functions?
Is there a better way to automatically merge the PinMux output files into the TI-RTOS config files? If not, might I suggest that this would be a good upgrade to the pinmux tool.
