**** BEGIN LOGGING AT Thu Apr 08 02:59:56 2010 Apr 08 06:59:52 hello, i'd like to build an jtag programmer - planning on experimenting with STM32 chips in the future. if it could also work with AVRs, it would be great. i'd also like some altera support, but i'm not hoping for any. Apr 08 07:00:54 i've got soldering experience, can make pcbs at home (and i don't want to fab them at a pcbhouse), i have a working avr programmer + various avrs, i also have a ft2232 chip, a serial and a parallel port. using windows Apr 08 07:01:32 the openocd hardware lists several versions, i'm not really sure what to pick. Apr 08 08:25:02 there is really no one who like to respond, I guess posting on a forum is a better option... Apr 08 14:41:13 hello world Apr 08 14:42:07 I am banging my head in the walls with a FT2232H + STM32 setup Apr 08 14:42:12 does Apr 08 14:42:14 Info : 272 9447 core.c:917 jtag_examine_chain_display(): JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Apr 08 14:42:44 this message mean openocd actually managed to talk to the MCU ? Apr 08 14:52:38 poine: I'm pretty sure, yes. One of the ST documents shows what TAP identification numbers should be, so you can verify it there. I think its the reference manual Apr 08 14:55:47 thanx penguinece - I'm very unfamiliar with JTAG in general - what I find very weird is that I have a very similar setup on a breadboard that works - the difference are pullups on the breadboard and a different stm32 chip Apr 08 14:57:23 i have had to hack openocd to use channel B of the ft2232 and now i have no idea wether the problem is hardware or software - could be hardware cause those QFN are a pain to solder by hand Apr 08 15:00:18 poine: they are indeed. using a stencil, solder paste, and a toaster oven makes it wayyyyy easier. If you're getting device found, connect to the openocd server with gdb or telnet and see if the chip is listening to you. Apr 08 15:01:01 do you know if there is one of the JTAG signals that is not used in the "jtag_examine_chain" thingy but used in the next step that fails ( "jtag_validate_ircapture" ) Apr 08 15:05:39 instruction register capture, hm. I'm not sure. It is worth checking whether your TRST and RST are shorted together. There is a parameter passed to openocd (via a config file) that specifies whether or not htey are tied together. Apr 08 15:09:58 Bummer :) that web chat kicked me out Apr 08 15:10:15 poine: instruction register capture, hm. I'm not sure. It is worth checking whether your TRST and RST are shorted together. There is a parameter passed to openocd (via a config file) that specifies whether or not htey are tied together. Apr 08 15:10:17 I figured Apr 08 15:11:17 checking that - on my design they are supposed to be separate - ohmetring now :) Apr 08 15:15:23 http://openocd.berlios.de/doc/html/Reset-Configuration.html#Reset-Configuration -- Read the section on command: reset_config closely. Apr 08 15:16:10 Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Apr 08 15:16:11 Info : JTAG tap: stm32.bs tap/device found: 0x06418041 (mfg: 0x020, part: 0x6418, ver: 0x0) Apr 08 15:16:18 ^ that's what I get on startup Apr 08 15:17:15 I'm using target/stm32.cfg and interface/olimex-arm-usb-ocd.cfg within my own .cfg that defines my reset line configuration Apr 08 15:17:51 fwiw, using a stm32f105rct6 (qfp 64) Apr 08 15:18:40 so - they are not tied together Apr 08 15:20:43 so you should have "reset_config trst_and_srst separate" Apr 08 15:20:52 and whatever your trst_type and srst_type are Apr 08 15:21:10 I'm using a STM32F103RET6 Apr 08 15:23:01 I'm using "usbjtag" layout without sepecifying reset_config trst_and_srst Apr 08 15:24:13 what strikes me is that it works on my dev board - and the only difference is the STM chip ( RBT6 vs RET6 ) and pullups on the jtag lines Apr 08 15:24:49 you specify your trst_type and srst_type correctly? Apr 08 15:32:07 I have not specified anything. I am using something adapted from interface/openocd-usb.cfg Apr 08 15:46:28 which one should I use, push_pull or open-drain ? Apr 08 16:07:29 poine: I can't remember. try both. Apr 08 16:10:30 penguinece - I did - everything seems to work on my dev board and fail on my prod board Apr 08 16:11:13 poine: sounds like you'll have to check your soldering then. or put together another board. Apr 08 16:11:50 you're using a custom pcb? Apr 08 16:12:49 penguin - I'm about to coil wire in some vias to check signals - as it works on the dev board I did not make the prob board very accessable :) Apr 08 16:12:59 yep - I'm using a custom PCB Apr 08 16:13:53 plus I'm not 100% sure what those signal are supposed to look like - but I can at least check if they are different than on the dev board Apr 08 16:14:06 poine: I've put together 3 of my custom PCB so far. All three act differently :(. Apr 08 16:14:20 I'm starting to worry that I may have over-baked some of the chips Apr 08 16:14:30 QFN soldering ? Apr 08 16:14:55 I am using a stencil, solder paste, and a toaster oven Apr 08 16:17:04 i don't have a stencil, but I have paste and a reflow oven Apr 08 16:17:20 pololu.com Apr 08 16:17:24 they're cheap and the ship quickly Apr 08 16:18:13 you might inspect your soldering under a microscope Apr 08 16:19:07 I've had good luck fixing shorted qfp pins by putting a dab of flux on top of pins that were shorted, then applying a soldering iron, slowly moving the iron towards the end of the pins. Apr 08 16:19:52 thanx Apr 08 16:31:30 penguinece: how far you got? Apr 08 16:32:05 i've been checking openocd programmers but i'm not sure which one to make for jtag progging the same stm32 Apr 08 16:33:11 i have had no problem with the ftdi dev module Apr 08 16:33:30 you can get it from the FTDI website Apr 08 16:33:43 ft2232h dev module Apr 08 17:04:45 what can you use a ftdi2232 based programmer for, except ARMs? **** ENDING LOGGING AT Fri Apr 09 02:59:56 2010