TMS320F28379D: TMS320F28379D DSP board damaged

how to find the required schematic files from c2000ware i have it but i am getting
"Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.0.27.9)"

this error when i try to dump a code and also LD1 , LD2 and LD2 are not ON when i switch on the board

Lakshmi.

Which specific board are you using, the Launchpad or controlCard? The board files are in "c2000ware<version>/boards" directory.

That error can indicate damage to the board or a JTAG connection issue. try walking through the procedures outlined here: http://www.ti.com/lit/spracf0

If the debug guide does not yield results, it is likely going to be a hardware problem. You need to get your hands on at least a multimeter an oscilloscope is helpful as well. To repair, you need to identify the failing component and replace it.

-Mark

i am using controlcard, i have c200ware but what to do with that i am not using JTAG i am using USB ports

Lakshmi,

The schematic will help you as you probe different points of the circuit so you know what you are looking at. As mentioned in the previously linked threads, you need to start stepping through various circuits and checking which ones do not appear to be operating properly. Check the power supplies on the board at the embedded test points, labeled as "TPx" or "A:TPx" on the PCB and in the schematic. Ensure that they are at the proper voltages. You mentioned that LD1, LD2, and (i'm guessing) LD3 are not on anymore. That tells me that there likely is not 3.3 on the MCU side. Specifically look at USB_5V0 and MCU_3V3 nets to see if they are correct.

The USB connector A:J1 is in fact connected to the on-board XDS100v2 JTAG debugger. JTAG is your primary interface to the MCU on this board. The error message you pasted is a JTAG error and indicates that there is likely something wrong with your board or your JTAG setup. Follow the JTAG debug guide previously linked, and ensure that all the steps are followed.

-Mark