Topic : Error reported by the DTC (Data Transfer Component)

Forum : ARM

Original Post
Post Information Post
May 7, 2010 - 12:42am
Guest

Hello,

I've been working on an NXP LPC1768, and this afternoon I started getting an error "Error reported by the DTC (Data Transfer Component)". The program in question is just blinking LEDs and seems to be working fine.

I'm using;
Ride7: 7.26.09.0351
RKit-ARM for Ride7: 1.24.10.0050

So I suspect that I may have inadvertantly put something in the code that is making the chip not work with the RLinkPro. I'm not sure but I don't think I'm doing anything strange to the debug port. I am however mucking around with the oscillator and power up configuration.

I was able to program the chip and at some point the RLink started giving me this error. We pulled the chip and put on a fresh LPC1768, I was able to load code into it (and the code is running). As soon as I loaded the code into the fresh chip, the RLink started giving the error, and I could no longer talk to the chip.

I'm also unable to talk to the chip using RFlasher (Pressing "Reset and Run", gives the same error message).

I have no idea what this error is, or how to resolve this problem. What is a DTC error? What causes it? How do I resolve it? Is there a JTAG script I need to set up or something?

Here's the clock config code I loaded;
#define CLOCK_SETUP 1
#define SCS_Val 0x00000020 // main OSC is 1-20Mhz, Main OSC is enabled
#define CLKSRCSEL_Val 0x00000001 // main oscillator is source
#define PLL0_SETUP 1
#define PLL0CFG_Val 0x0000000B // 2*12*8/1 = 192Mhz
//#define PLL0CFG_Val 0x00000011 // 2*18*8/1 = 288Mhz
#define PLL1_SETUP 0
#define PLL1CFG_Val 0x00000000 // not enabled... only feeds the USB interface
#define CCLKCFG_Val 0x00000001 // 192Mhz/2 = 96Mhz
//#define CCLKCFG_Val 0x00000002 // 288Mhz/3 = 96Mhz
#define USBCLKCFG_Val 0x00000000
#define PCLKSEL0_Val 0x00000040
#define PCLKSEL1_Val 0x00000000
#define PERIPHERAL_ENABLE 1 // configure peripherals
#define PCON_Val 0x0000001C // This is what is in the mbed
#define PCONP_Val 0x04A887DE // This is what is in the mbed

Replies
Post Information Post
+1
0
-1
May 10, 2010 - 9:34am
Raisonance Support Team

Hi,

The Data Transfer Component (DTC) is the part of the RLink that accesses the IOs in order to communicate with the target device. (LPC17 in your case) "Error reported by the DTC" means that the target device returned inconsistent patterns or nothing at all, but there is no way to know more precisely what or why. These errors usually happen when there are bad connections, clocks or powers.

However, if all connections are correct, nothing loaded in the flash should be able to prevent JTAG or SWD communication to start. It could prevent debugging, but not erasing. Please make sure that the RST and TRST signals are both connected from the RLink to the LPC17, and that they are not connected to each other. Please also make sure that no other component interferes on these lines. What you observe (connection working with some flash contents but not others) usually results from problems on the reset lines.

If you are not sure please send us your board's schematic and your example application. (complete project with headers and everything) Send it to 'support@raisonance.com'

Best Regards,

Vincent