AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

I recently upgraded my CCS for 6xxx from version 1.2 to version 2.12. I am having all kinds of difficulties and am hoping someone here has seen these issues before and know how to overcome them. 1) if I open my existing CCS1.2 mak file project, CCS2.1 properly converts this to the new format .pjt file. 2) next, I try to open the cdb file and CCS2.1 says this is an old file type, convert or open as read only? If I open as read only, the file looks OK but a build cannot complete because CCS recognizes its an 'old' format. If I tell it to convert the file... it essentially locks up my PC and I have to re-boot to get anything to run again. An added feature here is that in the process, it destroys the original file. 3) since the CCS conversion didn't work, I tried creating a new cdb file from scratch. I now get: undefined first referenced symbol in file --------- ---------------- _CLK_TIMERNUM C:/ti/c6000/bios/lib/bios.a62 >> warning: output file main.out not executable Build Complete, 0 Errors, 1 Warnings, 0 Remarks I have clk manager disabled in the cdb file and have no idea where/why this function is being called. I am certain that it is a result of the cdb file though. When creating the cdb file from scratch, many items in the original cdb file that I tried to put in, CCS rejected saying something to the effect that this configuration was not an option and would clash with other options. I am primarily concerned with the error when I try to make the Global Settings match for L2 Mode. On the original 1.2 cdb file it says 2 way cache. If I try to select this in the new file, it says "segment will overlap another memory segment or cache configuration"--but it doesn't say where and as far as I can tell, all other mem settings match the v1.2 cdb file. Can anyone help? I have emailed TI regarding this, but as usual the support from them is lacking... Thanks, Paul

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Paul, As to number 2 below. We recently found a defect in CDB Update during development of the next CCS. Analysis has shown this problem existed in CCS 2.12 however very few machines in our test set actually exhibit the problem - looks like you're encountering the problem. I will send separately a zip of the dll that contains the fix. If you could please forward the email you sent to support I'd like to follow up as using TI's support should have resulted in prompt action. Thanks, Thom of the DSP/BIOS team -----Original Message----- From: Calvert, Paul [mailto:] Sent: Tuesday, September 24, 2002 10:20 AM To: Subject: [c6x] CCS 1.2 to CCS2.1 upgrade I recently upgraded my CCS for 6xxx from version 1.2 to version 2.12. I am having all kinds of difficulties and am hoping someone here has seen these issues before and know how to overcome them. 1) if I open my existing CCS1.2 mak file project, CCS2.1 properly converts this to the new format .pjt file. 2) next, I try to open the cdb file and CCS2.1 says this is an old file type, convert or open as read only? If I open as read only, the file looks OK but a build cannot complete because CCS recognizes its an 'old' format. If I tell it to convert the file... it essentially locks up my PC and I have to re-boot to get anything to run again. An added feature here is that in the process, it destroys the original file. 3) since the CCS conversion didn't work, I tried creating a new cdb file from scratch. I now get: undefined first referenced symbol in file --------- ---------------- _CLK_TIMERNUM C:/ti/c6000/bios/lib/bios.a62 >> warning: output file main.out not executable Build Complete, 0 Errors, 1 Warnings, 0 Remarks I have clk manager disabled in the cdb file and have no idea where/why this function is being called. I am certain that it is a result of the cdb file though. When creating the cdb file from scratch, many items in the original cdb file that I tried to put in, CCS rejected saying something to the effect that this configuration was not an option and would clash with other options. I am primarily concerned with the error when I try to make the Global Settings match for L2 Mode. On the original 1.2 cdb file it says 2 way cache. If I try to select this in the new file, it says "segment will overlap another memory segment or cache configuration"--but it doesn't say where and as far as I can tell, all other mem settings match the v1.2 cdb file. Can anyone help? I have emailed TI regarding this, but as usual the support from them is lacking... Thanks, Paul _____________________________________

(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

DSPers, Just change your IRAM from 0x0 to higher location (how much, I am not sure), I used to do it. Peace, TR. > When creating the cdb file from scratch, many items > in the original cdb file > that I tried to put in, CCS rejected saying > something to the effect that > this configuration was not an option and would clash > with other options. I > am primarily concerned with the error when I try to > make the Global Settings > match for L2 Mode. On the original 1.2 cdb file it > says 2 way cache. If I > try to select this in the new file, it says "segment > will overlap another > memory segment or cache configuration"--but it > doesn't say where and as far > as I can tell, all other mem settings match the v1.2 > cdb file. > > Can anyone help? > > I have emailed TI regarding this, but as usual the > support from them is > lacking... > > Thanks, > > Paul > _____________________________________ > > _____________________________________ __________________________________________________

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

I recently upgraded my CCS for 6211 from version 1.2 to version 2.12. I have had/am having all kinds of difficulties and am hoping someone here has seen these issues before and knows how to overcome them. I have finally managed to get the conversion/build process to complete without errors. Now I am having a run-time issue that makes no sense whatsoever.. In my cdb file I specify timer 0 to run on HWI 8. HWI 12 is unused and disabled. Now, I load my code and it runs as expected--until the line that enables HWI 8, timer 0. The enable occurs and immediately my code jumps to the .s62 file at HWI 12. At this point, all bets are off and the code is forever hung at this line: HWI_Obj1, HWI_INT12, 12, _Function, _monitor, _addr, _dataType.... other parameters. I did a QuickWatch on all of these items--all of which say "Unknown Object". I verified the timer 0 interrupt is somehow magically causing this to happen by breaking just before the enable, and modifying the PC to skip the enable instruction. When I do this, the breakpoint I have set in my IDL function occurs and I have no reason not to believe that at this point everything would run fine. (except perhaps the other interrupts I am using may have similar issues, but they are not occuring because they are externallly generated HW interrupts?). So far, TI support has been unable to tell me what is causing this. I double checked the cdb file and everything seems to be as expected. Note, this code built with CCS v1.2 runs fine. It is my understanding that from v1.2 to v2.x the BIOS changed considerably. Can this be a BIOS issue/bug? Any input greatly appreciated... Regards, Paul

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Allthough I have not seen the specific probles you describe, the cdb file is _very_ different between 1.2 and 2.0 and indeed from 2.0 to 2.1. We found impoting the old cdb gave us a lot of bizarreness and when we made the cdb file from the beginning (setting exactly the same settings) the problems dissapeared. I have also seen somewhere an admission that there was a bug in the 2.0 to 2.1 upgrade from TI, which made me feel better. Try creating the cdb file from one of the templates in 2.1 rather than importing it. If that doesn't help, or you have tried it already I'm out of ideas. Pete Warnes Technical director HUNT ENGINEERING (U.K.) Ltd email URL http://www.hunteng.co.uk or http://www.hunt-dsp.com phone +44 (0)1278 760188 direct +44 (0)1278 760966 GSM +44 (0)7711 190099 Fax +44 (0)1278 760199 > -----Original Message----- > From: Calvert, Paul [mailto:] > Sent: Thursday, October 03, 2002 2:36 PM > To: > Subject: [c6x] CCS 1.2 to CCS2.1 upgrade > I recently upgraded my CCS for 6211 from version 1.2 to > version 2.12. I have > had/am having all kinds of difficulties and am hoping someone > here has seen > these issues before and knows how to overcome them. I have > finally managed > to get the conversion/build process to complete without > errors. Now I am > having a run-time issue that makes no sense whatsoever.. > > In my cdb file I specify timer 0 to run on HWI 8. HWI 12 is unused and > disabled. > > Now, I load my code and it runs as expected--until the line > that enables HWI > 8, timer 0. The enable occurs and immediately my code jumps > to the .s62 file > at HWI 12. At this point, all bets are off and the code is > forever hung at > this line: > > HWI_Obj1, HWI_INT12, 12, _Function, _monitor, _addr, > _dataType.... other > parameters. > > I did a QuickWatch on all of these items--all of which say > "Unknown Object". > > I verified the timer 0 interrupt is somehow magically causing > this to happen > by breaking just before the enable, and modifying the PC to > skip the enable > instruction. When I do this, the breakpoint I have set in my > IDL function > occurs and I have no reason not to believe that at this point > everything > would run fine. (except perhaps the other interrupts I am > using may have > similar issues, but they are not occuring because they are externallly > generated HW interrupts?). > > So far, TI support has been unable to tell me what is causing > this. I double > checked the cdb file and everything seems to be as expected. > Note, this code > built with CCS v1.2 runs fine. It is my understanding that > from v1.2 to v2.x > the BIOS changed considerably. Can this be a BIOS issue/bug? > > Any input greatly appreciated... > > Regards, > > Paul > > _____________________________________

______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )