Sign in
Search c54x
Subscribe to c54x
c54x by Keywords
5409 | 5416 | AD5 | ADC | BIOS | Boot | Booting | Bootloader | C540 | C5402 | C5409 | C5416 | CCS | Codec | DMA | Dmad | DSK | DSKPlus | Dsplib | EVM | FFT | FIR | Flash | GPIO | HPI | Initialization | Interrupt | JTAG | LOG_printf | MCBSP | RFFT | RTDX | Sampling | STLM | UART | VC540
Discussion Groups
See Also
Discussion Groups | TMS320C54x | wierd behavior of CCS/Compiler
Technical discussions about the TI C54x DSPs (including the c5401, c5402, c5402a, c5404, c5407, c5409, c5409a, c5410, c5410a, c5416, c5420, c5421, c5441, c549, c5470 and c5471).
wierd behavior of CCS/Compiler - j_ouh - Aug 23 9:04:00 2002
|
Hi, group, I am using TMS320C5416 and CCS1.2/XDS-510. Currently, we are facing a wiered compiler problem that has been bothering us for a long time. I am hoping that if someone can give us a clue. Basically, this is what happen: when a program is running under the development environment (CCS1.2/XDS-510/Target Machine) the program executed as expected. However, the build is complete and .out was burned into the external ROM, sometimes an unexpected error execution will occur. Our current solution to this is changing the linker sequence and recompile several times. After few attemps, we might got a good executable (once it took as long as 5 days or hundreds of retries). J. Ouh. |
|
|
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )
Re: wierd behavior of CCS/Compiler - Benjamin Chan - Aug 23 11:34:00 2002
|
Do you use DSP/BIOS in your design? If the answer is yes, then you might want to remove all RTDX component and their association, including real-time analysis, Host channel manager that use RTDX for Host link and of course the RTDX module itself. Hope this help Ben --- j_ouh <> wrote: > Hi, group, > > I am using TMS320C5416 and CCS1.2/XDS-510. > Currently, we are facing > a wiered compiler problem that has been bothering us > for a long > time. I am hoping that if someone can give us a > clue. > > Basically, this is what happen: when a program is > running under the > development environment (CCS1.2/XDS-510/Target > Machine) the program > executed as expected. However, the build is complete > and .out was > burned into the external ROM, sometimes an > unexpected error > execution will occur. Our current solution to this > is changing the > linker sequence and recompile several times. After > few attemps, we > might got a good executable (once it took as long as > 5 days or > hundreds of retries). > > J. Ouh. > > > _____________________________________ __________________________________________________ |
|
|
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )
Re: wierd behavior of CCS/Compiler[Scanned] - James Ou - Aug 24 4:01:00 2002
|
Thank you very much for your help. I don't use the RTDX and all of its Component and all of what you stated as below. We use DSP/BIOS . Does there any other passable reason ? Again, Thanks a lot ! James --- Benjamin Chan <> ¼g¹D¡G> Do you use DSP/BIOS in your design? If the answer is > yes, then you might want to remove all RTDX > component > and their association, including real-time analysis, > Host channel manager that use RTDX for Host link and > of course the RTDX module itself. > > Hope this help > > Ben > --- j_ouh <> wrote: > > Hi, group, > > > > I am using TMS320C5416 and CCS1.2/XDS-510. > > Currently, we are facing > > a wiered compiler problem that has been bothering > us > > for a long > > time. I am hoping that if someone can give us a > > clue. > > > > Basically, this is what happen: when a program is > > running under the > > development environment (CCS1.2/XDS-510/Target > > Machine) the program > > executed as expected. However, the build is > complete > > and .out was > > burned into the external ROM, sometimes an > > unexpected error > > execution will occur. Our current solution to this > > is changing the > > linker sequence and recompile several times. After > > few attemps, we > > might got a good executable (once it took as long > as > > 5 days or > > hundreds of retries). > > > > J. Ouh. > > > > > > > > > > _____________________________________ > > > > > > > > > > > > __________________________________________________ > > _____________________________________ > _________________________________________________________ |
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )