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


Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | TMS320C6x | TMS320C6000 McBSP: IOM-2 interface

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

  

Post a new Thread

TMS320C6000 McBSP: IOM-2 interface - faty najmeddine - Aug 9 8:04:00 2002

Hi, I am newer to c6000 and I'm trying to use the
TMS320C6000 McBSP to interface to an IOM-2 compliant
device .I am working on a 6711DSK using CCS version
2.10. I followed the application report document
(SPRA569A) for TI. After build the program, I have
several errors, especially:

undefined first referenced
symbol in file
--------- ----------------
_vectors
C:\ti\myprojects\IOM-2\Debug\iom2.obj
>> error: symbol referencing errors - iom2.out not
built

To build the program, it seems necessary to give a
value different of 0x000000 to the symbol _vectors.
Not having a value recommended in TI documentations, I
have arbitrarily chosen the value of 0x000001. this
allowed to build correctly the program.

However, when I tried running the program, I obtain
the list of following errors: "Can't Set Breakpoint: Cannot set/verify breakpoint at
0xDAE8
Breakpoint Manager: An error was encountered
attempting to set a breakpoint used
for end of program detection.
Trouble Halting Target CPU : Timeout on Target
Processor Please check cabling or multi-processor
configuration It is recommended to RESET EMULATOR.
This will disconnect each target, perform an
emulation reset, and then reconnect each target. The
target should then be power cycled or hard reset.
Trouble Reading Target CPU memory: Processor accessing
not ready memory at 0xF8B4"

Any idea what could be the cause?

Thank you in advance for your help,






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