**** BEGIN LOGGING AT Thu Mar 15 02:59:58 2012
Mar 15 13:36:07 <Uhrheber> When I compile oocd under cygwin for ft2232 with libusb, do I also need the drivers from ftdichip.com?
Mar 15 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)?
Mar 15 13:47:15 <tc-> The Board has an at91sam9g20 and the programmer I'm using is an olimex arm-usb-ocd
Mar 15 13:47:30 <tc-> I get the following errors: http://pastebin.com/1RxB5Thj
Mar 15 13:48:46 <tc-> test.cfg only contains reset_config trst_and_srst and jtag_rclk 5
Mar 15 13:52:32 <tc-> I have been trying all the at91sam9 board configs as well
Mar 15 13:53:31 <tc-> My guess is the wiring but I have checked and rechecked that as well
Mar 15 13:57:27 <tc-> Any hints on where to start?
Mar 15 14:07:43 <Uhrheber> Hi tc-. Looking into it.
Mar 15 14:07:52 <Uhrheber> But I'm not an expert.
Mar 15 14:08:18 <Uhrheber> Why are you using version 0.4.0?
Mar 15 14:09:49 <Uhrheber> Is your interface detected? Try a lsusb.
Mar 15 14:12:21 <Uhrheber> And could you please paste your test.cfg?
Mar 15 14:12:43 <tc-> I tried hooking it up with an arm stm32F1007 and that worked perfectly
Mar 15 14:13:14 <Uhrheber> ok, that rules this out
Mar 15 14:13:37 <tc-> I could try to compile latest from source I guess
Mar 15 14:13:54 <tc-> I just installed the one in the Ubuntu repository
Mar 15 14:13:55 <Uhrheber> I don't know the at91sam9. Does it need the trst and srst?
Mar 15 14:14:26 <tc-> I think it should be trst_push_pull
Mar 15 14:14:37 <tc-> But that doesn't solve the problem
Mar 15 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
Mar 15 14:15:49 <tc-> Yeah, I will try that
Mar 15 14:16:01 <Uhrheber> boardfile says: # At reset CPU runs at 32.768 kHz.
Mar 15 14:16:02 <Uhrheber>         # JTAG Frequency must be 6 times slower if RCLK is not supported.
Mar 15 14:16:02 <Uhrheber>         jtag_rclk 5
Mar 15 14:16:02 <Uhrheber>         halt
Mar 15 14:16:25 <Uhrheber> Maybe that's your problem
Mar 15 14:17:36 <Uhrheber> The board file contains a lot of memory writes, that enable the main oscillator and the pll
Mar 15 14:17:39 <tc-> I set the jtag_rclk to 5...
Mar 15 14:18:31 <tc-> The initialization should probably succeed if I stay at 5?
Mar 15 14:19:00 <tc-> Even without setting up the oscillator?
Mar 15 14:19:08 <Uhrheber> This is the board file form version 0.6.0: http://pastebin.com/jDPHWNbJ
Mar 15 14:19:45 <tc-> halt wasn't supported in my version of openocd :)
Mar 15 14:19:58 <tc-> invalid command
Mar 15 14:20:17 <tc-> Working on building latest
Mar 15 14:20:21 <Uhrheber> try to compile from repository. it's easy and described in the readme.
Mar 15 14:21:11 <tc-> git://openocd.git.sourceforge.net/gitroot/openocd/openocd ?
Mar 15 14:21:23 <Uhrheber> exactly
Mar 15 14:21:57 <Uhrheber> you also need libusb and libftdi
Mar 15 14:22:14 <Uhrheber> And automake, autoconf, gcc, etc.
Mar 15 14:23:21 <Uhrheber> when you have anything, start ./bootstrap
Mar 15 14:23:41 <Uhrheber> everything, I meant
Mar 15 14:24:48 <tc-> Hmmm, compile error
Mar 15 14:25:20 <Uhrheber> did you run ./configure after bootstrap?
Mar 15 14:25:21 <tc-> http://pastebin.com/YE6gip5T
Mar 15 14:25:26 <tc-> Yeah
Mar 15 14:26:47 <tc-> Is that documentation?
Mar 15 14:27:15 <Uhrheber> Hm. I don't know. I'm not a member of the development team.
Mar 15 14:27:34 <Uhrheber> I compiled it yesterday and it worked.
Mar 15 14:27:57 <tc-> .texi is texinfo
Mar 15 14:28:06 <tc-> Must be a way to disable it
Mar 15 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 :-)
Mar 15 14:30:04 <Uhrheber> configure command should be: ./configure --enable-maintainer-mode ----enable-ft2232_libftdi
Mar 15 14:30:26 <tc-> Wish I could help you there :)
Mar 15 14:31:15 <Uhrheber> Support for PIC32 (mips32) is pretty much experimental. Especially for the new small MX1/2 devices
Mar 15 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
Mar 15 14:33:18 <Uhrheber> Is it possible to do rclk with FT2232 anyway?
Mar 15 14:34:10 <tc-> Good question :/
Mar 15 14:34:42 <Uhrheber> AFAIK you need at least an additional CPLD for that.
Mar 15 14:35:33 <Uhrheber> That's the way Freescale/Spectrum Digital are doing it in their XDS100v2
Mar 15 14:36:49 <tc-> http://pastebin.com/YPwy2fMb
Mar 15 14:36:58 <Weaselweb> well, I expected you have no RCLK, so beware of the 1/6 clock issue
Mar 15 14:38:36 <tc-> Info : RCLK (adaptive clock speed) not supported - fallback to 5 kHz
Mar 15 14:39:30 <Uhrheber> Hm. It doesn't read the id. TDI and TDO misplaced?
Mar 15 14:39:56 <tc-> I could try swapping them I guess
Mar 15 14:40:47 * tc- soldering
Mar 15 14:51:13 <tc-> http://pastebin.com/UYQwx8LF
Mar 15 14:51:56 <tc-> Still can't read the ID
Mar 15 14:52:44 <tc-> Error: JTAG scan chain interrogation failed: all ones <- All zeroes before
Mar 15 14:53:59 <Uhrheber> Any capacitors/resistors connected to the jtag lines?
Mar 15 14:54:40 <tc-> Not that I know of
Mar 15 14:59:39 <tc-> Is it supposed to reset the board when I try to init?
Mar 15 15:10:29 <Uhrheber> Depends on your jtagger
Mar 15 15:10:38 <Uhrheber> And the target chip
Mar 15 15:10:47 <Uhrheber> And the oocd version
Mar 15 15:12:14 <tc-> If I look at the oscilloscope there is a lot of data on TDI but nothing on TDO
Mar 15 15:12:26 <tc-> When initializing
Mar 15 15:13:12 <Weaselweb> do you change JTAG_SEL?
Mar 15 15:13:28 <tc-> No
Mar 15 15:13:36 <Weaselweb> that's fine
Mar 15 15:13:54 <tc-> I think it has internal pulldown
Mar 15 15:14:54 <tc-> When I pull jtag sel up the board resets
Mar 15 15:16:22 <Weaselweb> jtag_Sel needs to be set before power-on to switch between normal boot /jtag and boundary scan otherwise
Mar 15 15:17:11 <Uhrheber> How does this work for processors that don't have a jtag_sel?
Mar 15 15:17:32 <Weaselweb> i think this is specific to at91
Mar 15 15:17:40 <Uhrheber> ok
Mar 15 15:20:18 <tc-> How does this jtag scan chain work?
Mar 15 15:21:20 <tc-> Error: JTAG scan chain interrogation failed: all zeroes
Mar 15 15:31:35 <Uhrheber> Do the other signals work? tck, tms?
Mar 15 15:34:14 <tc-> The problem is I don't know how they are supposed to work :/
Mar 15 15:34:40 <tc-> There are signals on both tck and tms
Mar 15 15:36:24 <Uhrheber> is the connection to the micro ok? 
Mar 15 15:36:46 <tc-> The jtag connection?
Mar 15 15:36:51 <Uhrheber> yes
Mar 15 15:37:02 <tc-> That's what I don't know :)
Mar 15 15:37:08 <Uhrheber> BGA?
Mar 15 15:37:16 <tc-> ?
Mar 15 15:37:24 <Uhrheber> The micro housing
Mar 15 15:37:31 <Uhrheber> tqfp or bga?
Mar 15 15:39:12 <tc-> I'll have to google that :)
Mar 15 15:39:32 <Uhrheber> does it have visible pins?
Mar 15 15:39:37 <tc-> No
Mar 15 15:39:46 <Uhrheber> The it's bga
Mar 15 15:39:48 <tc-> They are under
Mar 15 15:40:05 <Uhrheber> Not easy to measure the connection
Mar 15 15:40:33 <Uhrheber> you could try to find the vias for the jtag signals, but that's a time consuming thing
Mar 15 15:40:46 <Uhrheber> Did you buy the board?
Mar 15 15:41:08 <tc-> But I don't think the problem is between the test points and the micro
Mar 15 15:41:32 <tc-> Unless I burned something with the soldering
Mar 15 15:41:54 <tc-> But I was very careful not to
Mar 15 15:43:22 <tc-> I also have another board that I didn't solder, but glued instead, same problem
Mar 15 15:45:36 <tc-> I have the testpoints that I solder the programmer to that I can measure on
Mar 15 15:47:59 <Uhrheber> I don't know anything about the sam9, sorry.
Mar 15 15:49:51 <tc-> Wish I knew more :)
Mar 15 15:50:12 <tc-> Anyway, thanks for being very helpful :)
Mar 15 15:50:36 <tc-> I have to take this up tomorrow :)
Mar 15 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.
Mar 15 15:51:34 <tc-> That sucks :)
Mar 15 15:51:41 <Uhrheber> Yeah :-)
Mar 15 15:51:50 <tc-> Anyway, have to run (literally) :)
Mar 15 15:51:58 <Uhrheber> bye
Mar 15 15:52:03 <tc-> Thanks!
Mar 15 19:47:59 <Uhrheber> ping
Mar 15 21:15:05 <Uhrheber> Hi. Anybody here that knows the PIC32/Mips4k routines?
Mar 15 21:36:37 <roxfan> routines?
Mar 15 22:04:46 <Uhrheber> I have some questions, like whether you use the PE or not, and how to connect the mclr pin of the PIC32
Mar 15 22:06:37 <Uhrheber> If I understand the PIC32MX Flash programming specification right, the mclr pin is needed to enter programming mode. But how do I connect it? To trst or srst?
**** ENDING LOGGING AT Fri Mar 16 02:59:58 2012