TMS320VC5510A: Migrating CCS 2.30 project into CCS 3.3 baseline

Let me add additional info. Since this was converted from CCS 2.3 project into 3.3. There's one additional source file called "appCfg_csl.c" that provides DMA related object initialization such as "hDmaXmt".  Below source lines are from "appCfg_csl.c" file,  where it creates, initializes the hDmaXmt:

DMA_Handle hDmaXmt;
MCBSP_Handle C55XX_CONTROLHANDLE_hMcbsp;
MCBSP_Handle C55XX_DMA_MCBSP_hMcbsp;
/* ======== cslCfgInit() ===== */

void cslCfgInit()  { ... },  In spite of this, it still results in a hDmaXmt undefined, I wonder why, order?   FYI, I imported this same 2.3 project into 3.1, it builds successfully. 3.3 departs quite a bit.

For the GPIO error #2 ,  error: identifier "GPIO_GPIO" is also undefined, below info is what I can see in my build environment FYI.

IDECL void GPIO_pinDirection(GPIO_Handle hGpio, Uint32 pinMask, Uint16 direction);

// where IDECL is #define IDECL CSLAPI

Hi Shao,

Our expert for this topic is out of office and will return by Nov27, please expect a response early that week.

Best Regards,

Sahana

Hello Shao,

I am asking around about this possibility but it may not be an area we can support. CCS 3.3 is an extremely old version of CCS. I've never used it - the earliest CCS version I've touched was a 5.x revision.

Best Regards,

Ralph Jacobi

Hi Ralph,

I believe the actual difference between CCS 2.x to 3.3 is not by that much, but the key is where to look. I suspect one area is from BIOS 4.9 (CCS 2.x) to BIOS 5.33 (3.3). My goal is to make sure the runtime binary is identically behaved, etc.  The surprise is how easily CCS 3.3 build was broken after such a simple project conversion. Does TI keep any such conversation archived so you can dig up? I bet there would be similar cases just like this. 

Best Regards,

Shao

Hi Ralph, I also found from Ki's identical topics with another customer (long time ago) with some document links which are now broken, can you please check if I can access them:

http://www-k.ext.ti.com/SRVS/CGI-BIN/WEBCGI.EXE/,/?St=27,E=0000000000006654954,K=7392,Sxi=8,Case=obj%2852425%29

and

http://tiexpressdsp.com/index.php/Migrating_from_BIOS_4.9_to_BIOS_5.x

Hi Shao,

I'm not certain about that first link, but the second was one that I could track down: /cfs-file/__key/communityserver-discussions-components-files/791/Migrating-from-BIOS-4.9-to-BIOS-5.x.pdf

I'm still trying to see if I can find that knowledge base article as well, but haven't had any luck there so far.

Best Regards,

Ralph Jacobi

Thanks Ralph. The link you given above seemed to point at a useful document but turns out, the content doesn't live up to the title, it is not yet helpful to address my issues. If you go back to the start of my description, it was all about "CSL" as root cause when failing hDMAXmt, GPIO during build in CCS 3.3, otherwise I don't have any other error. This first step of converting from 2.3 to 3.3 didn't detect any build issue - how come? so it maybe serving as a clue for you. What about adding a "clsdata" section in the linker cmd file due to the change of BIOS change from 4.9x to 5.33?     

I appreciate any of your help, thanks in advance!

Best,

Shao

Hi Shao,

I'll continue to see if there is anyone who can help speak to this issue but I personally have no background whatsoever with that kind of build error so I'll need to rely on others who might have worked with these products back in those days to be able to comment on this. I'll also check with the team that put together that document in the event this is not specific to the device our team owns, but the error reads to me as something that is device specific.

Best Regards,

Ralph Jacobi