[Openocd-development] post 0.4 merging

2010-02-13 Thread Øyvind Harboe
Post 0.4 release, I'd like to see patches being merged in ascending order of disruptiveness. Of course it isn't possible to measure disruptiveness, but I think about two things: cherry pickability and impact on design and direction of openocd. This makes patches more cherry pickable(create some

[Openocd-development] dsp56371 crash

2010-02-13 Thread Austin, Alex
Version in use: v0.4.0-rc1-194-gf7a6e62 Configuration: ./configure --enable-maintainer-mode --enable-jlink --enable-ft2232_libftdi --enable-usb_blaster_libftdi --enable-amtjtagaccel CFLAGS=-O0\ -g3 Config file: source [find interface/axm0432.cfg] set CPUTAPID 0x01c0001d source [find

Re: [Openocd-development] post 0.4 merging

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, Øyvind Harboe wrote: Post 0.4 release, I'd like to see patches being merged in ascending order of disruptiveness. Of course it isn't possible to measure disruptiveness, but I think about two things: cherry pickability and impact on design and direction of

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, Austin, Alex wrote: openocd segfaults upon connecting to it. I've tracked it down to target_get_gdb_reg_list being called when target-type-get_gdb_reg_list is null. Tracing back to where the target-type comes from, it never gets set in dsp563xx.c, so is null. Why

Re: [Openocd-development] [PATCH 1/2] arm11: allow minidrivers to implement inner loop of memory writes

2010-02-13 Thread David Brownell
On Tuesday 09 February 2010, Øyvind Harboe wrote: This allows minidrivers to e.g. hardware accelerate memory writes. Same trick as is used for arm7/9 dcc writes. Added error propagation for memory transfer failures in code rearrangement. These would be a *lot* better as method pointers

Re: [Openocd-development] Support for AVR: AT90CAN128

2010-02-13 Thread David Brownell
On Thursday 11 February 2010, hp...@space.aau.dk wrote: Yes. Here is the patch and the new cfg used to test (almost just a   copy of the one for mega128) Thanks ... we'll hold this until the 0.5 merge window opens, since the 0.4 series has been feature-frozen for some time now. - Dave

[Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread CeDeROM
Hello world! :-) I finally got for better testing if 0.4.0-RC1, there are no big issues as for now, however I have some remarks: -It is better to name package openocd-0.4.0rc1.tar.gz than openocd-0.4.0-rc1.tar.gz, as there are some other system conventions that forbids using - and _ mark after

[Openocd-development] OpenOCD v0.4.0-rc2 is out ...

2010-02-13 Thread David Brownell
Git has an RC2 tag, and when you autoreconfig it comes out as RC2. Source archives are downloadable from SourceForge, and its news has a brief blurb. https://sourceforge.net/projects/openocd/ Berlios downloads are in the works. (They take forever to do, since Berlios uses such an

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, CeDeROM wrote: Hello world! :-) I finally got for better testing if 0.4.0-RC1, there are no big issues as for now, however I have some remarks: Good ... can you let us know if RC2 has any significant deltas from this list? -It is better to name package

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread CeDeROM
Hello David! On Sun, Feb 14, 2010 at 12:11 AM, David Brownell davi...@pacbell.net wrote: I finally got for better testing if 0.4.0-RC1, there are no big issues as for now, however I have some remarks: Good ... can you let us know if RC2 has any significant deltas from this list? Sure thing!

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 8:11 AM, David Brownell davi...@pacbell.net wrote: FreeBSD does have parport support though, right?  Is the issuse that it doesn't work at all with OpenOCD?  Or instead, that it can work given some changes? Yes but the API is different from Linux. xBSD uses ppbus.

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread CeDeROM
Hello Xiao! :-) On Sun, Feb 14, 2010 at 12:41 AM, Xiaofan Chen xiaof...@gmail.com wrote: (...) But I have not used FreeBSD for a while. It did not boot on my desktop PC (Nvidia 620i/Geforce 7050 integrated chipset) when I wanted to try it last time. It also had quite bad USB support last

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, CeDeROM wrote: Hello Xiao! :-) On Sun, Feb 14, 2010 at 12:41 AM, Xiaofan Chen xiaof...@gmail.com wrote: (...) But I have not used FreeBSD for a while. It did not boot on my desktop PC (Nvidia 620i/Geforce 7050 integrated chipset) when I wanted to try it

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 9:04 AM, David Brownell davi...@pacbell.net wrote: So Xiaofan, I encourage you to give it a try! :-) Probably I will try it later, maybe with a Live CD first to see if it boots. Last time I spent sometime to get USB things working under FreeBSD.

[Openocd-development] OpenOCD 0.4.0-RC2 Fedora RPM

2010-02-13 Thread Dean Glazeski
Hey all, I've posted the source RPM and builds for Fedora 11 and 12 for OpenOCD 0.4.0-RC2 on my Fedora people page. (http://dnglaze.fedoraproject.org). Give the RPMs a spin if you are running Fedora. I'll post my own results a bit later this evening. -- // Dean Glazeski

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread Austin, Alex
The GDB in question is the gdb56300.exe provided by freescale, running under WINE. I had the source for it at one time, but I've somehow managed to misplace it. From: David Brownell [davi...@pacbell.net] Sent: Saturday, February 13, 2010 5:52 AM To:

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-13 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 9:26 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Feb 14, 2010 at 9:04 AM, David Brownell davi...@pacbell.net wrote: So Xiaofan, I encourage you to give it a try! :-) Probably I will try it later, maybe with a Live CD first to see if it boots. Last time I spent

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, Austin, Alex wrote: The GDB in question is the gdb56300.exe provided by freescale, running under WINE. I had the source for it at one time, but I've somehow managed to misplace it. Yeah, that's what you'd want to have OpenOCD work with. If it's not