problems upgrading from CCSv2 BIOS 4.90.280 to CCSv5 BIOS 5.31.02

Lyn,

For the 2nd thing you tried:

a.  Why did you have to copy c28xx.cdb over the existing c28xx.cdb?
b.  Is that really the path for the c28xx.cdb?  Shouldn't it be something like:  c:/ti/bios_5_41_13_42/packages/ti/bios/config/cdb
c.  Can you post your tcf file here?  I think there's something in there that references GBL.PLLTYPE?

For the 3rd thing you tried:

a.  Your older linker probably does not understand the --diag_suppress=16002.  Codegen tools v6.1 or greater should understand this.
b.  Are the memory map for the two projects the same? If so, I don't see why it would give you a problem loading/running in CCS v3.3.  My guess is, the memory maps are probably different.  Posting memory maps of both executable builds here could be helpful too. 

Judah

Judah,

For 2a,b I didn't copy over a pre-existing file.  Instead, I created the entire path /ti/bios/config/cdb/c28xx.cdb per error messages when I compiled:

...

'Building file: ../pmc.tcf' 'Invoking: TConf' "C:/ti/xdctools_3_23_03_53/tconf" -b -Dconfig.importPath="C:/ti/bios_5_41_13_42/packages;" "../pmc.tcf"

js: "C:/ti/bios_5_41_13_42/packages/ti/bios/config/bios_2812.tci", line 57: Error: Can't find configuration seed: ti/bios/config/cdb/c28xx.cdb

gmake: *** [pmccfg.cmd] Error 1

...

The above problem and fix seemed to be covered in one of TI's online docs (don't recall which one), so it didn't seem an item of concern in my mind, just a step I had to go through. Yes, that is the path I used, because it was the path I found hardcoded in bios_2812.tci (I chose to create the desired path, not to edit bios_2812.tci to match the pre-existing path.)

For 2c, I'm attaching the tcf file and the original cdb files. Thanks for taking a look.

For the memory map, do you want the *.cmd files? Apologies, this is my first TI development project.

Thank you,

Lyn

3187.copy_of_cdb.txt5342.copy_of_tcf.txt

Sorry, some operator error there.  I misunderstood "Uploaded" to mean "attached", but it clearly doesn't.  -Lyn

Lyn

For 2a,b - Its actually not hard coded in bios_2812.tci because there is a relative path.   Tconf does look along a path for the seed.  Typically the path it looks along includes the BIOS install.  But for now, since what you did is working for you, its not a huge deal.

For 2c.  I wonder if the line params.regs.pllcr = 0xa; in your tcf is the culprit of the PLLTYPE error?  I didn't see anything else that looked like it would be the source.

.cmd files and .map files (map files are generated if you are able to link an executable).

Judah

Judah,

The *.cmd and *.map files are attached: CCSv2 are the original, CCSv33 seem to work (no extensive testing done), CCSv52 won't build.

Any idea on what is wrong with the pllcr setting?  I looked on the datasheet (SPRS174t, p 51), and 10 looks like a legitimate value.

thanks,

Lyn

4540.cmd_map_files.zip

Second, I tried jumping to CCSv5.2 with BIOS 5.41.13.42.  Here I had to put c28xx.cdb into c:/ti/bios/config/cdb/c28xx.cdb, but then I was unable to get rid of a build-time error "js:property 'PLLTYPE' doesn't exist for instance GBL".  I can't figure out where this error is coming from, so I have no idea how to attack it.  

The error is most likely coming from a file ti/bios/config/bios_2812.tci.  The thing is the c28xx.cdb should have a field called 'PLLTYPE'.  Can you grep the c28xx.cdb that it is using to see if you find the PLLTYPE in there?

So for CCS v3.3, you are able to build the program but you cannot load/run with CCS v3.3...is that correct?  Are you using the right gel files here?

I don't know if the pllcr setting is the culprit.  My suggestion would be to comment it out and see if you still get the error.  I'm sure its probably not the culprit.  I think its my first suggestion which you are seeing the error from.

Judah

Looks like I mangled the version numbers in my initial posting.  Here's a summary with correct (I think!) version numbers:

First, CCSv2 BIOS 4.90.280 works.  Upgrading to CCSv3.3, BIOS5.31.02 compiled and ran (I can no longer duplicate this success; will compile but will not connect to my XDS510 USB JTAG emulator.  The GEL menu says "Not loaded")

Second, CCSv2 BIOS 5.41.13.42 won't compile due to the PLL error.  As you suspect, commenting out the pll line in the tcf file does not clear the error.  There is no PLLTYPE in the c28xx.cdb (see attached). 7802.c28xx_cdb.txt

Third, CCSv3.3 BIOS 5.41.13.42 compiles, but won't connect to my XDS510 USB JTAG emulator.  The GEL menu says "Not loaded"

How do the GEL files get set inside CCS?  Under windows, I do see a file c:\CCStudio_v3.3\cc\gel\f2812.gel, but I don't see a way to specify it or load it into CCS?

-Lyn

I found the File->Load GEL, and tried loading c:\CCStudio_v3.3\cc\gel\f2812.gel, but can't connect.  I also tried loading the gel file that CCSv2 uses into CCSv3.3, but I still can't connect.  I always get the same error message (attached) -Lyn

5756.CCSv3.3_wont_connect.rtf

Judah,

I did a clean re-install of CCSv5.2.  This gave me c28xx.cdb in the place you suggested (ti\bios\config\cdb).  I no longer see the PLLTYPE issue, so I think that problem is fixed.  I'm not sure what I botched the first time, when that file did not exist, but it is solved with your help.

I will take the connection issue to another forum as you suggest.

I still cannot compile/link, but it will take some time for me to sort out the next hurdle.  I'll put in a new thread if I can't figure it out.

Thank you very much for your time!

-Lyn