Sign in

username:

password:



Not a member?

Search c6x



Search tips

Subscribe to c6x



c6x by Keywords

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

Ads

Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | TMS320C6x | Problem with TMS320CC416 DSP Test Evaluation Board - and the SOLUTION

Technical discussions about the TI C6000 DSPs (including the c62x, c64x and c67x DSPs).

  

Post a new Thread

Problem with TMS320CC416 DSP Test Evaluation Board - and the SOLUTION - matdude247 - Jan 21 12:34:00 2002

Hi,
Thanks to everyone who pitched in to help me out. (I am the guy who
posted the message "Problem with TMS320CC416 DSP Test Evaluation
Board")
My problem is solved and my code is running perfectly well on the
TEB. However, the problem was quite different from the explanations
that were offered by various people. Essentially what happened was
that I forgot to change the linker command file (which of course is
target specific - the command file being used for running the code on
the Simulator will most probably need to be changed when migrating to
a board-based set-up.) I figured this out when I tried running
some "example code" that came with the IDK installation CD.
I am writing this reply so that anyone who is planning to use a
board may not make the same mistake that I did and waste a quite a
bit of time and effort.






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