Hi I had a simmilar Problem when I built my Jtag clone for the AVR. The Problem was I forgot to power up the processor. I your case somethin simmilar must be the problem, since the Jtag link is recogniced. Triple check all your power connections to the processor. Cheers Michael >From: "Simon Ansley" <simon@...> >Reply-To: lpc2000@yahoogroups.com >To: lpc2000@yahoogroups.com >Subject: [lpc2000] Newbie problem : Connecting LPC2214 to Segger J-Link >Date: Sat, 15 Oct 2005 17:39:35 -0000 > >Hello, > >I'm trying to get a new PCB up and running using an LPC2214, but >cannot get the chip to talk to the JTAG port. I'm fairly new to both >the processor, and ARM in general, so sorry if this is a really dumb >problem. > >I'm using a Segger J-Link (IAR rebadged) and Rowley compiler. > >I have connected to and run test code on the Olimex LPC2214 >development board, so I know the J-Link is OK. > >I have checked and double checked the JTAG connection against the >Olimex schematic. > >I have the BSL (P0.14) connected to a pullup. Boot0 and Boot1 are >open circuit (high through internal pullups). RTCK is pulled low by >10K. > >The processor oscillator is running. > >I've scoped the levels on the JTAG interface with the J-Link >unplugged, and they are identical on my and the Olimex board, with >the exception of TCK, which is at 0V on my board and approx 0.4V on >the Olimex board > >Whenever I try to connect from the Rowley IDE I get "Too few devices >on the JTAG bus. Selected Device :0, No. of Devices 0". I guess this >means the JLink simply can't see the processor for whatever reason. > >The board and chip are new, and have not have any code downloaded >into them. Do I need to download code using the Flash Loader utility >from the Phillips website, or should I be able to connect straight >away through the J-Link? > >Does everything else sound OK, or could I have got a duff processor? > > >Thanks > >Simon Ansley > > >
Message
RE: [lpc2000] Newbie problem : Connecting LPC2214 to Segger J-Link
2005-10-15 by Michael Rubitschka
Attachments
- No local attachments were found for this message.