Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
Hi, Please, refrain from top-posting. On Tue, Sep 10, 2013 at 03:44:41PM +0200, Nicolas Produit wrote: > Error: tdo check error at line 76 > Error: read = 0x2F9FF, want = 0x3, mask = 0x3 This means the device answered something that it's not expected to. I guess that if it went so far, i

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Nicolas Produit
Hi, thanks a lot!!! with this patch opencd don't crash anymore on this. And I confirm it eat happily window created files with \r\n But I still cannot recycle my window machine... I am now able to run raspberry native (after finding configure needs a --enable-bcm2835gpio) But unfortunatley now I ge

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
On Tue, Sep 10, 2013 at 01:51:14PM +0200, Nicolas Produit wrote: > I checked that file do contain \r\n. > File was created on windows... > Perhaps mailer attachment changed that? I have a feeling that it's your MUA :) Anyway, the parser handles \r just fine, I've checked it already. Please try the

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Nicolas Produit
Hi, I checked that file do contain \r\n. File was created on windows... if I do a od -c I get: 000 ! # A C T I O N V E R I 020 F Y _ A R R A Y ; \r \n ! # P R O Perhaps mailer attachment changed that? Cheers On 09/10/

[OpenOCD-devel] [PATCH]: 4d246bd sysfsgpio: fix a typo in the informational output

2013-09-10 Thread gerrit
This is an automated email from Gerrit. Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1616 -- gerrit commit 4d246bd31d1e89793e65df502d94de923ead2eba Author: Paul Fertser Date: Tue Sep 10 15:27:11 2013 +0400 sys

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
On Tue, Sep 10, 2013 at 06:40:33PM +0800, 徐光晓 wrote: > I did not post a bug report, because I did not check the real reason of this > bug. The new line character reason is only from my suspection. Imagine the current position is 0. We're going to write the character itself, an (optional) space and

[OpenOCD-devel] [PATCH]: d9e0c9c svf: off-by-one error; do not access after the allocated memory

2013-09-10 Thread gerrit
This is an automated email from Gerrit. Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1615 -- gerrit commit d9e0c9cfcaab62d31303ffd6dabfbe9b29a5d4bc Author: Paul Fertser Date: Tue Sep 10 15:14:56 2013 +0400 svf

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
On Tue, Sep 10, 2013 at 06:40:33PM +0800, 徐光晓 wrote: > I did not post a bug report, because I did not check the real reason of this > bug. The new line character reason is only from my suspection. I think this shows some decent info: valgrind ./src/openocd -c \ "interface dummy; adapter_

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Peter Stuge
Hello, 徐光晓 wrote: > I did not post a bug report, because I did not check the real > reason of this bug. The new line character reason is only from > my suspection. It sounds likely to me. > Please somebody in charge of this module consider about this > modification and update it in new version.

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
Hi, On Tue, Sep 10, 2013 at 06:40:33PM +0800, 徐光晓 wrote: > It seemed that I've been in this bug before. > The reason cause this bug I guess is from the new line characters are much > different between linux (\n) and windows(\r\n). The file in question has no 0x0d's, only 0x0a's, so that's probabl

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread ??????
Hi guys, It seemed that I've been in this bug before. The reason cause this bug I guess is from the new line characters are much different between linux (\n) and windows(\r\n). When you generate your svf file in windows, the new line is one more character than linux. This cause the OpenOCD co

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
Hi, On Tue, Sep 10, 2013 at 12:06:45PM +0200, Nicolas Produit wrote: > thanks a lot. Very fast reaction on this list! The openocd web site > suggest forum for bug report... I hope one of the devs will fix it soon, thanks for reporting. > Native raspberry driver? How do I do that? another -f inte

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Nicolas Produit
Hi, thanks a lot. Very fast reaction on this list! The openocd web site suggest forum for bug report... I attach here start of the svf file (if mail attachment work on this mailing list...) Native raspberry driver? How do I do that? another -f interface? By the way there is a typo in the SysfsGP

Re: [OpenOCD-devel] bug in svf

2013-09-10 Thread Paul Fertser
Hi, On Tue, Sep 10, 2013 at 11:11:43AM +0200, Nicolas Produit wrote: > this is my first mail to this list so sorry if I do something wrong. > I posted a bug report on sparkfun openocd forum but did not get a lot of > answers there... > https://forum.sparkfun.com/viewtopic.php?f=18&t=36484&e=0 Heh

[OpenOCD-devel] bug in svf

2013-09-10 Thread Nicolas Produit
Hi, this is my first mail to this list so sorry if I do something wrong. I posted a bug report on sparkfun openocd forum but did not get a lot of answers there... https://forum.sparkfun.com/viewtopic.php?f=18&t=36484&e=0 I think it is a clear memory corruption problem in openocd. I find reallocate