Peter LaDow a écrit : > This may not directly be an OpenOCD issue, but I am trying to debug my > design. Since this list is well populated with ARM users, perhaps > somebody has some insight. > > I've received the parts and assembled my first LPC2148 based design. > I've also purchased the Olimex ARM-USB-TINY module to use for > programming/debuging, and planned to use Yagarto along with OpenOCD. > However, I am running into issues with the JTAG. At first, it was an > OpenOCD configuration issue, but I resolved that one (failed to find > my wiggler, but I've fixed the config file). > > Now, it indicates there is a problem with the JTAG chain. I've probed > around quite a bit trying to determine issues. I copied the JTAG > header design from the Olimex LPC-2148 schematic, and I have the same > pullups/pulldowns. I probed the JTAG header and I appear to have the > proper voltages. I do not have the jumper on RTCK as I always want > JTAG enabled (the pulldown is there). I do have 3V3 on pins 1 and 2. > > Here's what I tried: > > 1. I verified the VCC and GND pins on the JTAG header. > 2. I probed the VCC connections on the LPC2148 to verify it has power. > 3. I grounded NRST (/RESET on the LPC2148) to force reset and to > recognize the 0 on P1.31 in case it wasn't recognized. > > Unfortunately I don't have a digital o-scope, so I can't capture JTAG > traces. When I use my analog scope, I do see some activity on the JTAG > lines, but I can't capture it. > > Is there a tool/utility to debug the JTAG connection using the FT2xx > based wigglers? Is there anything else I can check? > > Attached is a link with a PDF of the schematic, and the Eagle > schematic and board files. You can find them here: > http://cid-3e6aa75359e23754.skydrive.live.com/self.aspx/USB2IEC > > Also, I've posted the OpenOCD output below (at the end of the post) > with debugging turned up to level 3. Here is my arm-usb-ocd.cfg file: > > #interface > interface ft2232 > #ft2232_device_desc "Olimex OpenOCD JTAG A" > ft2232_device_desc "Olimex OpenOCD JTAG TINY A" > ft2232_layout "olimex-jtag" > ft2232_vid_pid 0x15BA 0x0004 > > Thanks, > Pete > >
Here is one like the one that I use and it works like a champ. That is on Fedora 9 though. I use a 2138 which is similar to a 2148. The difference in mine is that I edited lpc2148.cfg so it doesn't give me error messages. I think the problem you have is the garbage in the device description and your configuration is incomplete. Look into the lpc2148.cfg the /usr/lib/openocd/target directory # REFERENCE: http://www.olimex.com/dev/arm-usb-tiny.html interface ft2232 ft2232_device_desc "Olimex OpenOCD JTAG TINY" ft2232_layout olimex-jtag ft2232_vid_pid 0x15BA 0x0004 jtag_speed 20 # Change the default telnet port... telnet_port 4444 # GDB connects here gdb_port 3333 # GDB can also flash my flash! gdb_memory_map enable gdb_flash_program enable source [find target/lpc2148.cfg] Michel -- Tired of Microsoft's rebootive multitasking? then it's time to upgrade to Linux. http://home.comcast.net/~mcatudal _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
