**** BEGIN LOGGING AT Wed Aug 26 02:59:57 2009
Aug 26 19:56:28 <florian> hi all
Aug 26 20:08:38 * russell_ just got an olimex arm-usb-ocd jtag interface, trying to get talking to an arm9 (micrel ks8695p) based board.  have lots of info about the chip and parts on the board.  not sure where to start with openocd.  help?
Aug 26 20:12:32 <florian> russell_: for yout jtag there is a confguration already
Aug 26 20:12:38 <florian> eh ypur
Aug 26 20:12:46 <russell_> yeah
Aug 26 20:12:53 <russell_> i got that far
Aug 26 20:12:56 <florian> hrm... i guess i should try to find a coffee
Aug 26 20:13:01 <russell_> heh
Aug 26 20:14:51 <russell_> i have what i think is the jtag pinout.  at least TDI, TCK, TDO and TRSTN and a decent guess at TMS.  i have a serial console on the board.
Aug 26 20:16:06 <russell_> (the pinouts were derived from tracing continuity back to the cpu chip ball grid array)
Aug 26 20:17:25 <russell_> neither the board or the cpu seem to have a canned config in openocd, at least not the version I have from debian (0.2.0+r2529-1)
Aug 26 20:18:41 <russell_> a couple years ago, someone was using openocd with a dev board for my cpu (micrel ks8695p) and was successful, but his config is obsolete for current openocd or something
Aug 26 20:21:10 <florian> yes looks like there is no support for this cpu in upstrem openocd
Aug 26 20:21:21 <florian> but it might be easy to port this information
Aug 26 20:21:42 <florian> that's an area i didn't touch so far
Aug 26 20:24:35 <florian> Currently I'm more interested in openocd architecture
Aug 26 20:25:57 <russell_> i guess i'm looking for help getting a minimal config that'll let me probe the flash chips
Aug 26 20:26:57 <russell_> the goal being to read/write the flash, as the current bootloader on this board is an obstacle
Aug 26 20:28:12 <florian> a config for a cpu with the same core would bea good start
Aug 26 20:31:39 <russell_> yeah, but ... the one i found has piles of inscrutable jibberish (stuff i don't yet comprehend)
Aug 27 00:28:57 <aSmig> Does anyone have openocd working on a mips32 target with a successful gdb connection?  I get "Remote 'g' packet reply is too long:..." error and disconnect "dropped 'gdb' connection - error -400"
**** ENDING LOGGING AT Thu Aug 27 02:59:57 2009