| 00:00.16 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:01.16 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:01.46 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:02.16 | *** join/#openjtag MarkusBec (znc@ist.deswahnsinns.de) |
| 00:02.46 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:03.17 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:04.18 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:05.20 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:05.46 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:06.16 | *** join/#openjtag MarkusBec (znc@80.69.39.131) |
| 00:06.48 | *** join/#openjtag roxfan (dunno@91.180.53.65) |
| 01:23.16 | *** join/#openjtag _julian_ (~quassel@hmbg-4d06e562.pool.mediaWays.net) |
| 06:37.17 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 06:45.49 | *** join/#openjtag drath (~vmaster@178-27-180-11-dynip.superkabel.de) |
| 07:05.31 | *** join/#openjtag e-ndy (~e-jones@fantomas.bestit.cz) |
| 07:16.01 | *** join/#openjtag nattg225 (~andreas@c-c0f170d5.026-401-67626721.cust.bredbandsbolaget.se) |
| 09:19.58 | *** join/#openjtag Uhrheber (~Uhrheber@piratenpartei/rp/Uhrheber) |
| 11:21.09 | *** join/#openjtag Vikthor (~viktor@78-80-200-5.tmcz.cz) |
| 13:36.07 | Uhrheber | When I compile oocd under cygwin for ft2232 with libusb, do I also need the drivers from ftdichip.com? |
| 13:39.40 | *** join/#openjtag tc- (~tc@static-213-115-157-66.sme.bredbandsbolaget.se) |
| 13:40.47 | *** join/#openjtag _julian (~quassel@hmbg-5f76584a.pool.mediaWays.net) |
| 13:46.37 | tc- | Would it be possible go get some help hooking up a jtag programmer to a board(been trying for two days now)? |
| 13:47.15 | tc- | The Board has an at91sam9g20 and the programmer I'm using is an olimex arm-usb-ocd |
| 13:47.30 | tc- | I get the following errors: http://pastebin.com/1RxB5Thj |
| 13:48.46 | tc- | test.cfg only contains reset_config trst_and_srst and jtag_rclk 5 |
| 13:52.32 | tc- | I have been trying all the at91sam9 board configs as well |
| 13:53.31 | tc- | My guess is the wiring but I have checked and rechecked that as well |
| 13:57.27 | tc- | Any hints on where to start? |
| 14:07.43 | Uhrheber | Hi tc-. Looking into it. |
| 14:07.52 | Uhrheber | But I'm not an expert. |
| 14:08.19 | Uhrheber | Why are you using version 0.4.0? |
| 14:09.49 | Uhrheber | Is your interface detected? Try a lsusb. |
| 14:12.21 | Uhrheber | And could you please paste your test.cfg? |
| 14:12.43 | tc- | I tried hooking it up with an arm stm32F1007 and that worked perfectly |
| 14:13.14 | Uhrheber | ok, that rules this out |
| 14:13.37 | tc- | I could try to compile latest from source I guess |
| 14:13.54 | tc- | I just installed the one in the Ubuntu repository |
| 14:13.55 | Uhrheber | I don't know the at91sam9. Does it need the trst and srst? |
| 14:14.26 | tc- | I think it should be trst_push_pull |
| 14:14.37 | tc- | But that doesn't solve the problem |
| 14:15.12 | Uhrheber | Maybe you should try 0.5.0 or compile from the repository. The actual version contains a board file for an at91sam9 |
| 14:15.49 | tc- | Yeah, I will try that |
| 14:16.01 | Uhrheber | boardfile says: # At reset CPU runs at 32.768 kHz. |
| 14:16.02 | Uhrheber | <PROTECTED> |
| 14:16.02 | Uhrheber | <PROTECTED> |
| 14:16.02 | Uhrheber | <PROTECTED> |
| 14:16.35 | Uhrheber | Maybe that's your problem |
| 14:17.36 | Uhrheber | The board file contains a lot of memory writes, that enable the main oscillator and the pll |
| 14:17.39 | tc- | I set the jtag_rclk to 5... |
| 14:18.31 | tc- | The initialization should probably succeed if I stay at 5? |
| 14:19.00 | tc- | Even without setting up the oscillator? |
| 14:19.08 | Uhrheber | This is the board file form version 0.6.0: http://pastebin.com/jDPHWNbJ |
| 14:19.45 | tc- | halt wasn't supported in my version of openocd :) |
| 14:19.58 | tc- | invalid command |
| 14:20.17 | tc- | Working on building latest |
| 14:20.21 | Uhrheber | try to compile from repository. it's easy and described in the readme. |
| 14:21.11 | tc- | git://openocd.git.sourceforge.net/gitroot/openocd/openocd ? |
| 14:21.23 | Uhrheber | exactly |
| 14:21.58 | Uhrheber | you also need libusb and libftdi |
| 14:22.14 | Uhrheber | And automake, autoconf, gcc, etc. |
| 14:23.21 | Uhrheber | when you have anything, start ./bootstrap |
| 14:23.41 | Uhrheber | everything, I meant |
| 14:24.48 | tc- | Hmmm, compile error |
| 14:25.20 | Uhrheber | did you run ./configure after bootstrap? |
| 14:25.21 | tc- | http://pastebin.com/YE6gip5T |
| 14:25.26 | tc- | Yeah |
| 14:26.47 | tc- | Is that documentation? |
| 14:27.15 | Uhrheber | Hm. I don't know. I'm not a member of the development team. |
| 14:27.34 | Uhrheber | I compiled it yesterday and it worked. |
| 14:27.57 | tc- | .texi is texinfo |
| 14:28.06 | tc- | Must be a way to disable it |
| 14:28.15 | Uhrheber | The only reason why I'm hanging around here is that I'm trying to get some help with using oocd with a PIC32MX220 :-) |
| 14:30.04 | Uhrheber | configure command should be: ./configure --enable-maintainer-mode ----enable-ft2232_libftdi |
| 14:30.26 | tc- | Wish I could help you there :) |
| 14:31.15 | Uhrheber | Support for PIC32 (mips32) is pretty much experimental. Especially for the new small MX1/2 devices |
| 14:32.01 | Weaselweb | "# JTAG Frequency must be 6 times slower if RCLK is not supported." keep that in mind, if you reconfigure the pll settings |
| 14:33.18 | Uhrheber | Is it possible to do rclk with FT2232 anyway? |
| 14:34.10 | tc- | Good question :/ |
| 14:34.42 | Uhrheber | AFAIK you need at least an additional CPLD for that. |
| 14:35.33 | Uhrheber | That's the way Freescale/Spectrum Digital are doing it in their XDS100v2 |
| 14:36.49 | tc- | http://pastebin.com/YPwy2fMb |
| 14:36.58 | Weaselweb | well, I expected you have no RCLK, so beware of the 1/6 clock issue |
| 14:38.36 | tc- | Info : RCLK (adaptive clock speed) not supported - fallback to 5 kHz |
| 14:39.30 | Uhrheber | Hm. It doesn't read the id. TDI and TDO misplaced? |
| 14:39.56 | tc- | I could try swapping them I guess |
| 14:40.47 | tc- | soldering |
| 14:51.13 | tc- | http://pastebin.com/UYQwx8LF |
| 14:51.56 | tc- | Still can't read the ID |
| 14:52.44 | tc- | Error: JTAG scan chain interrogation failed: all ones <- All zeroes before |
| 14:53.59 | Uhrheber | Any capacitors/resistors connected to the jtag lines? |
| 14:54.40 | tc- | Not that I know of |
| 14:59.39 | tc- | Is it supposed to reset the board when I try to init? |
| 15:10.29 | Uhrheber | Depends on your jtagger |
| 15:10.38 | Uhrheber | And the target chip |
| 15:10.48 | Uhrheber | And the oocd version |
| 15:12.14 | tc- | If I look at the oscilloscope there is a lot of data on TDI but nothing on TDO |
| 15:12.26 | tc- | When initializing |
| 15:13.12 | Weaselweb | do you change JTAG_SEL? |
| 15:13.28 | tc- | No |
| 15:13.36 | Weaselweb | that's fine |
| 15:13.54 | tc- | I think it has internal pulldown |
| 15:14.54 | tc- | When I pull jtag sel up the board resets |
| 15:16.22 | Weaselweb | jtag_Sel needs to be set before power-on to switch between normal boot /jtag and boundary scan otherwise |
| 15:17.11 | Uhrheber | How does this work for processors that don't have a jtag_sel? |
| 15:17.32 | Weaselweb | i think this is specific to at91 |
| 15:17.40 | Uhrheber | ok |
| 15:20.19 | tc- | How does this jtag scan chain work? |
| 15:21.20 | tc- | Error: JTAG scan chain interrogation failed: all zeroes |
| 15:31.35 | Uhrheber | Do the other signals work? tck, tms? |
| 15:34.14 | tc- | The problem is I don't know how they are supposed to work :/ |
| 15:34.40 | tc- | There are signals on both tck and tms |
| 15:36.24 | Uhrheber | is the connection to the micro ok? |
| 15:36.46 | tc- | The jtag connection? |
| 15:36.51 | Uhrheber | yes |
| 15:37.02 | tc- | That's what I don't know :) |
| 15:37.08 | Uhrheber | BGA? |
| 15:37.16 | tc- | ? |
| 15:37.24 | Uhrheber | The micro housing |
| 15:37.31 | Uhrheber | tqfp or bga? |
| 15:39.12 | tc- | I'll have to google that :) |
| 15:39.32 | Uhrheber | does it have visible pins? |
| 15:39.37 | tc- | No |
| 15:39.46 | Uhrheber | The it's bga |
| 15:39.48 | tc- | They are under |
| 15:40.05 | Uhrheber | Not easy to measure the connection |
| 15:40.33 | Uhrheber | you could try to find the vias for the jtag signals, but that's a time consuming thing |
| 15:40.46 | Uhrheber | Did you buy the board? |
| 15:41.08 | tc- | But I don't think the problem is between the test points and the micro |
| 15:41.32 | tc- | Unless I burned something with the soldering |
| 15:41.54 | tc- | But I was very careful not to |
| 15:43.22 | tc- | I also have another board that I didn't solder, but glued instead, same problem |
| 15:45.36 | tc- | I have the testpoints that I solder the programmer to that I can measure on |
| 15:47.59 | Uhrheber | I don't know anything about the sam9, sorry. |
| 15:49.51 | tc- | Wish I knew more :) |
| 15:50.12 | tc- | Anyway, thanks for being very helpful :) |
| 15:50.36 | tc- | I have to take this up tomorrow :) |
| 15:51.14 | Uhrheber | That's always the same crap when you start with a new chip. You spend a long time till it works, and afterwards you don't even know what the problem was. |
| 15:51.34 | tc- | That sucks :) |
| 15:51.41 | Uhrheber | Yeah :-) |
| 15:51.50 | tc- | Anyway, have to run (literally) :) |
| 15:51.58 | Uhrheber | bye |
| 15:52.03 | tc- | Thanks! |
| 16:39.55 | *** part/#openjtag Uhrheber (~Uhrheber@piratenpartei/rp/Uhrheber) |
| 17:19.01 | *** join/#openjtag dmarion1 (~Adium@cpe-109-60-76-208.zg3.cable.xnet.hr) |