| 01:15.17 | flyback | try #sparkfun, #electronics #avr |
| 02:06.33 | *** join/#openjtag _julian (n=quassel@dslc-082-083-135-030.pools.arcor-ip.net) |
| 06:21.16 | *** join/#openjtag _julian (n=quassel@dslc-082-083-135-030.pools.arcor-ip.net) |
| 08:27.58 | the-moog | having problems building openocd under linux/Ubuntu, anybody care to lend a hand? Config script says that the libftdi compile test fails. I have tried libftdi-dev package and compiling/installing libftdi from source. |
| 08:50.18 | PaulFertser | the-moog: have you tried looking at config.log? |
| 08:50.28 | PaulFertser | the-moog: the reason for the script failing should be pretty obvious from that |
| 08:56.24 | the-moog | yes, it says it can't find libftdi.so.1, this path is in /usr/local/lib which is listed ld.so.conf |
| 09:58.48 | PaulFertser | the-moog: who says? the linker? |
| 09:58.54 | PaulFertser | the-moog: can you pastebin the log? |
| 09:59.23 | PaulFertser | the-moog: are you sure to have done "ldconfig" after you installed libftdi from source? |
| 10:17.49 | the-moog | I would have thought make instal did ldconfig? But I will give it a go anyway.... |
| 10:20.10 | the-moog | yep, you were right, libftdi did not do the ldconfig - thanks |
| 10:31.42 | PaulFertser | the-moog: welcome |
| 10:38.34 | the-moog | ok, it builds but report "Command handler execution filed", seems like a log way of saying "something happened" |
| 10:39.28 | the-moog | *failed = filed |
| 10:42.30 | the-moog | interesting, it works with a shipped config file, but not with mine, even though the binary / windows one does. |
| 10:46.16 | zoobab | hi |
| 10:46.27 | zoobab | does anybody owns an Amontec JTAG adaptor? |
| 10:46.34 | zoobab | JTAG tiny |
| 10:47.58 | the-moog | I've got the JTAGkey (not the tiny) |
| 10:51.27 | zoobab | I think the non-tiny is more sensitive |
| 10:51.35 | zoobab | supports more voltages |
| 11:26.42 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 11:27.21 | *** part/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 11:53.27 | *** join/#openjtag methril|work (n=methril@127.Red-80-38-102.staticIP.rima-tde.net) |
| 11:58.13 | PaulFertser | the-moog: i'm trying to debug a weird stack (?) corruption here on windows that doesn't occur with GNU/Linux... Shows its ugly face when i use flash write_bank command... So who knows what other bugs are still hiding there. Better use a decent os for development, this way you can easily debug openocd itself. |
| 13:03.10 | *** join/#openjtag Weaselweb (n=quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 13:50.49 | the-moog | PaulFertser: That is what I am having to do. Up to now I've always used windows openocd - because it just works, has done for years. But now I need to use SVF and that dies with a stupid error. Though't I'd build it on Linux to find why its dying only to find building it is not as straight forward as all that..... |
| 13:52.59 | the-moog | Sorry,I don't think I help with the windows stack problems either, I usually program ARMs. |
| 13:53.55 | PaulFertser | the-moog: building on GNU/Linux is really straight forward. In fact cross-compiling with mingw is straight-forward too. |
| 13:54.13 | PaulFertser | the-moog: i was just unfortunate enough to hit a 2-year old bug still not fixed in debian :( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452977 |
| 13:54.37 | PaulFertser | the-moog: so did you finally build it, what is your issue now? |
| 13:58.41 | the-moog | <the-moog> ok, it builds but report "Command handler execution filed", seems like a log way of saying "something happened" |
| 13:59.03 | the-moog | I then try a as-shipped config file for JTAGkey and it works. |
| 14:00.05 | PaulFertser | the-moog: so the build doesn't seem to be a problem, right? Or do you suspect it uses some wrong libusb/ftdi version? |
| 14:00.20 | the-moog | My config file works with the windows binary, obviously a bug but no time to look into it right now (unless it acually affects me) |
| 14:00.52 | PaulFertser | the-moog: can it be that's due to the version difference? |
| 14:03.13 | the-moog | I'm using 3.1 source code so unless the git tree is wrong or perhaps the binary maintainer fixed bugs without submitting - dunno |
| 14:04.30 | PaulFertser | the-moog: i'm sorry but i can't help much without more specifics, debugging information and such. |
| 14:06.51 | the-moog | Now I see another problem. I think the source is not clean. If I put reset_config in the config file it says it must be called after jtag init, but if I put jtag init in the config file it says it is already called. |
| 14:07.04 | the-moog | Goning to try the 4.0 rc1 code |
| 14:09.00 | the-moog | I've seen this lots with openOCD the parsing code is a heap of poo, both command line and config files. |
| 14:09.21 | the-moog | I'm expecing it is the same problem with the svf parser. |
| 14:09.27 | the-moog | *expecting |
| 14:10.59 | the-moog | same :( |
| 14:34.33 | the-moog | Thought so, the code for svf.c has a stupid error, check out this line: |
| 14:34.35 | the-moog | if ((num_of_argu > 10) || (num_of_argu % 2)) |
| 14:34.35 | the-moog | { |
| 14:34.35 | the-moog | LOG_ERROR("invalid parameter of %s", argus[0]); |
| 14:34.35 | the-moog | return ERROR_FAIL; |
| 14:34.36 | the-moog | } |
| 14:35.17 | the-moog | num_of_argu is always odd (1,3,5,7,9, etc) so num_if_argu % 2 is always 1 which means it always fails. |
| 14:35.39 | the-moog | Now: How to build under windows........? |
| 15:01.27 | the-moog | Hm, the problem is more fundamental, the person who write it did not read the spec properly and assumed that a space is always the delimieter between the signal and its value, e.g. TDI<sp>(123) when it can be TDI(123) |
| 15:02.04 | the-moog | I'll raise a bug and write a parser to fixup the SVF files, it will be quicker. |
| 15:13.37 | *** join/#openjtag zoobab_ (i=zoobab@vic.ffii.org) |
| 15:14.23 | *** join/#openjtag _julian (n=quassel@dslc-082-083-135-030.pools.arcor-ip.net) |
| 17:27.24 | *** join/#openjtag toi (n=toi@d54C2A96D.access.telenet.be) |
| 21:14.21 | *** join/#openjtag key2 (n=key2@gob75-7-82-247-113-230.fbx.proxad.net) |
| 22:04.53 | *** join/#openjtag the-moog (n=the-moog@static-195-248-121-199.adsl.hotchilli.net) |
| 22:06.26 | the-moog | Still having problems with SVF in OpenJTAG, this time its lower level, perhaps some sort of buffer overrun or lockup in the libftdi driver - no idea how to debug it though. |
| 22:06.29 | the-moog | ftdi_write_data: usb bulk write failed |
| 22:06.30 | the-moog | couldn't write MPSSE commands to FT2232 |
| 22:06.54 | the-moog | Short SVF files <1000 odd lines are fine, longer ones screw up. |
| 22:10.13 | roxfan | maybe it tries to send too much |
| 22:11.17 | roxfan | try putting around the place of error a printf with number of bytes |
| 22:23.14 | the-moog | the word 'bulk' does not occur in the OpenOCD code, so it must be in the libftdi driver. |
| 22:26.23 | the-moog | ....which it is. |
| 22:27.22 | the-moog | I guess this means it could be a bug in the firmware of the ftdi device. |
| 22:47.27 | roxfan | look for ftdi_write_data |
| 22:47.41 | roxfan | the error message is looked up |
| 23:01.17 | roxfan | <PROTECTED> |
| 23:01.17 | roxfan | <PROTECTED> |
| 23:01.17 | roxfan | <PROTECTED> |
| 23:01.17 | roxfan | <PROTECTED> |
| 23:01.18 | roxfan | <PROTECTED> |
| 23:01.20 | roxfan | <PROTECTED> |
| 23:05.57 | the-moog | indeed, but that message comes from the driver so I don't think its the openocd that is going wrong, more like the driver or even the firmware. |
| 23:06.38 | the-moog | I'm going to implement internal programming, I think this will be easier. |
| 23:53.33 | roxfan | just add a printf before the message, so you can at least know which size triggers it |