On Tue, Dec 2, 2008 at 8:01 AM, Rick Altherr <[EMAIL PROTECTED]> wrote:
> What config file are you using when this happens? What host OS/architecture
> are you using?
amd64 with the given configuration
greetings
btw performing 7 times
irscan 0 7
drscan 0 8 0X89
also makes it go BOOM
>
> Rick
What config file are you using when this happens? What host OS/
architecture are you using?
Rick
On Dec 1, 2008, at 10:14 PM, Kees Jongenburger wrote:
Hi
I am trying the run a drscan 0 32 0xa3002048 and I am getting a
SIGSEGV. Just posting here so you know :p
Program received signal SIGS
I haven't attempted to reproduce but I thought I would mention a few
things for those investigating. buf_set_buf() died because the passed
in src was bogus. That means the arg was wrong when buf_set_buf() was
invoked by jtag_build_buffer() at jtag.c:1228.
Rick
On Dec 1, 2008, at 1:14 PM
Kees Jongenburger wrote:
> Hi
>
> I am trying the run a drscan 0 32 0xa3002048 and I am getting a
> SIGSEGV. Just posting here so you know :p
>
I don't see anything obvious :-(
FYI -you should be able to specify "drscan TAPNAME 32 0xa3002048"
instead of the hard coded 0 above.
That was the i
Hi
I am trying the run a drscan 0 32 0xa3002048 and I am getting a
SIGSEGV. Just posting here so you know :p
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f47fee1b6e0 (LWP 13122)]
0x0044dd1f in buf_set_buf (src=0xff00ff , src_start=0,
dst=0x70cfb0 "
