We are looking at the CC256x for a BT Dual mode application, using the Stellaris Bluetopia SDK. The installed sdk example projects for SPPLEDDemo - NoOS for Keil use a batch file to set up compiler paths and includes. However all batch file paths etc. are refering to the older Stellaris SDK not the Tiva C - also batch file runs for all compiler types, I suspect you need to comment out the other compile types ( ccs and IAR etc). - however paths etc are not for tiva c.
So in an attempt to get project to build, we added paths to tiva c sdk and also added the tiva c library file to the project and added the c99 option to compile. However we still have undefined constants - such as "GPIO_PA1_UOTX" in the HALCFG.c.
Also even tho the project build selected is EK-LM4F23 - the device type is not a TM4C123x but an LM3S9D96, with the Rom and Ram sizes bigger than contained in a TM4C123x
As the device selected is M3 (LM3S9D96) we would get M3 code - but if we change the selected device to the correct one (TM4C123x) - we would be compiling M4 code. Is this a problem for the Bluetopia libraries as the sdk release now says M3/M4
Does any one know what is needed to port the sample projects to use Tiva C processors, and Keil MDK -
The app notes say you should be able to use these boards - we are using the LSR TiWi ub2 EM boards with the TM4c123 dev kit.
Any help to get the sample projects compiling with these boards would be greatly appreciated.
Thanks Simon T