Disabling assertions broke the build; fix.
--- a/src/jtag/drivers/driver.c
+++ b/src/jtag/drivers/driver.c
@@ -215,7 +215,10 @@ int interface_jtag_add_dr_scan(int in_num_fields, const
struct scan_field *in_fi
if (!tap->bypass)
{
- struct sca
Starting the daemon with with just a bare "openocd" I saw:
Can't find openocd.cfg
That's not an error; don't treat it as if it were. There may
be an error later -- like, "no interface set up" -- but let
messages only report real errors, not fake ones.
---
I committed this, but suspect t
Also, could you split your configuration file in three files:
- interface
- target
- board
I would like to see all three contributed to the openocd target library.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScal
On Tuesday 05 January 2010, Robert Jenssen wrote:
> I build on FreeBSD with:
>
> ./configure \
> CFLAGS="-I/usr/local/include -D__DARWIN__" LDFLAGS="-L/usr/local/lib" \
> --enable-dummy --enable-jlink
That /usr/local/... stuff suggests the config issue isn't
generic enough to belong in a "configu
On Tuesday 05 January 2010, Øyvind Harboe wrote:
> This regression was introduced in ... v0.4.0-rc1-32-gb3bf1d1
Sorry.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Tuesday 05 January 2010, richard vegh wrote:
> #0 0xb805a416 in __kernel_vsyscall ()
> No symbol table info available.
This trace isn't helpful if you haven't included
the symbol table in your OpenOCD build.
The most immediately useful thing you can do is
send along a backtrace which includes
On Tuesday 05 January 2010, Spencer Oliver wrote:
> David Brownell wrote:
> > On Tuesday 05 January 2010, you wrote:
> >> Hi,
> >>
> >> I have been looking into the mips/pic32 programming and as most of you
> >> are aware it is very slow.
> >
> > Thinking of this for 0.4? I understand it's slow
Another thing would be to step through the nand write code
using GDB to try to get to the crash from that end. The backtrace
wasn't very helpful.
Also trying git master head would be good.
If this is a memory corruption, then the crash could be *after* the bug.
Another way to bisect is then to d
Can you make it crash using the dummy driver?
configure --enable-dumy
openocd ... -f interface/dummy.cfg ...
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
__
Øyvind Harboe wrote:
> Give David a chance to comment first. He's running the release process.
>
>
he sent me an email earlier, looks like it never made it to the list for
some reason.
Cheers
Spen
___
Openocd-development mailing list
Openocd-developm
Give David a chance to comment first. He's running the release process.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
O
Øyvind Harboe wrote:
> This could be committed to 0.4 under the assumption that we treat
> the MIPS target as work in progress that really isn't part of the release
> cycle before 0.5...
>
> Do you feel that these changes should go into 0.4?
they might as well, as you say most of the mips stuff i
This regression was introduced in b3bf1d12b2fdfba1c1cbee3e1afbfbb27cbd1a26,
i.e. v0.4.0-rc1-32-gb3bf1d1
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_
This could be committed to 0.4 under the assumption that we treat
the MIPS target as work in progress that really isn't part of the release
cycle before 0.5...
Do you feel that these changes should go into 0.4?
Having immature targets/interfaces under git is advantageous in terms
of getting testi
From: Øyvind Harboe
The gdb_port command can be invoked during normal execution
to report the port used for gdb, whereas it was listed as
CONFIG stage only, which caused an error when excuting
it to return the reported error.
Also in line with the grander goal of making more commands
available d
Hi,
I have been looking into the mips/pic32 programming and as most of you
are aware it is very slow.
The following series of patches increase the pic32 programming speed by
approx 35%.
Most of this increase is due to fastdata patch by David N. Claffey.
I am also looking into other areas to
I build on FreeBSD with:
./configure \
CFLAGS="-I/usr/local/include -D__DARWIN__" LDFLAGS="-L/usr/local/lib" \
--enable-dummy --enable-jlink
Regards,
Robert Jenssen
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists
On Monday 04 January 2010, Johannes Stezenbach wrote:
> Dec 8 17:06:23 worf udevd[425]: BUS= will be removed in a future udev
> version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to
> match a parent device, in /lib/udev/rules.d/60-openocd.rules:1
> Dec 8 17:06:23 worf udev
18 matches
Mail list logo
