On Wed, 2009-07-08 at 14:43 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 2:22 PM, Thomas A. Moulton wrote:
> > On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
> >> I have an Aduc7024 here that I can test with.
> >>
> >> Could you provide instructions on how to reproduce the crash on
On Wed, Jul 8, 2009 at 2:22 PM, Thomas A. Moulton wrote:
> On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
>> I have an Aduc7024 here that I can test with.
>>
>> Could you provide instructions on how to reproduce the crash on
>> that target?
>>
>>
>
> It works without crashing now!
With or
On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
> I have an Aduc7024 here that I can test with.
>
> Could you provide instructions on how to reproduce the crash on
> that target?
>
>
It works without crashing now!
The elf file does have a problem.
I will send it to you.
I did not cha
I have an Aduc7024 here that I can test with.
Could you provide instructions on how to reproduce the crash on
that target?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Op
On Mon, 2009-07-06 at 21:23 +0200, Øyvind Harboe wrote:
> On Mon, Jul 6, 2009 at 8:52 PM, Thomas A. Moulton wrote:
> > On Mon, 2009-07-06 at 20:27 +0200, Øyvind Harboe wrote:
> >> Can you reproduce with:
> >>
> >> - dummy driver? (--enable-dummy + -f interface/dummy.cfg)
> >> - "help fill" => flash
On Mon, 2009-07-06 at 21:23 +0200, Øyvind Harboe wrote:
> On Mon, Jul 6, 2009 at 8:52 PM, Thomas A. Moulton wrote:
> > On Mon, 2009-07-06 at 20:27 +0200, Øyvind Harboe wrote:
> >> Can you reproduce with:
> >>
> >> - dummy driver? (--enable-dummy + -f interface/dummy.cfg)
> >> - "help fill" => flash
On Mon, Jul 6, 2009 at 8:52 PM, Thomas A. Moulton wrote:
> On Mon, 2009-07-06 at 20:27 +0200, Øyvind Harboe wrote:
>> Can you reproduce with:
>>
>> - dummy driver? (--enable-dummy + -f interface/dummy.cfg)
>> - "help fill" => flash fill
>>
>
> I built with
>
> ./configure --enable-maintainer-mode -
On Mon, 2009-07-06 at 20:27 +0200, Øyvind Harboe wrote:
> Can you reproduce with:
>
> - dummy driver? (--enable-dummy + -f interface/dummy.cfg)
> - "help fill" => flash fill
>
I built with
./configure --enable-maintainer-mode --enable-parport
--enable-ft2232_libftdi --enable-jlink --enable-dumm
Can you reproduce with:
- dummy driver? (--enable-dummy + -f interface/dummy.cfg)
- "help fill" => flash fill
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-devel
On Mon, 2009-07-06 at 19:01 +0200, Øyvind Harboe wrote:
> I'm guessing that this is an elf file parsing problem.
>
> Can you provide the elf file?
Here is the same crash with a BIN file
flash write file.bin 0x8 bin
Program received signal SIGSEGV, Segmentation fault.
target_buffer_get_u32
I'm guessing that this is an elf file parsing problem.
Can you provide the elf file?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
http
On Mon, 2009-07-06 at 18:14 +0200, Øyvind Harboe wrote:
> Hmm. here is a stab in the dark. Try the attached
> patch...
>
>
it is still dark...
Program received signal SIGSEGV, Segmentation fault.
target_buffer_get_u32 (target=0x82a2a20, buffer=0x82c8000 )
at ../../src/helper/types.h:80
Hmm. here is a stab in the dark. Try the attached
patch...
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
Index: C:/workspace/openocd/src/flash/flash.c
===
--- C:/workspace/openocd/src/f
On Mon, 2009-07-06 at 17:25 +0200, Øyvind Harboe wrote:
> Can you try again with svn head?
>
> The line #'s in the backtrace are off.
>
>
Sorry - I should have known better
Program received signal SIGSEGV, Segmentation fault.
target_buffer_get_u32 (target=0x82e6a20, buffer=0x830c000 )
at .
Can you try again with svn head?
The line #'s in the backtrace are off.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.be
When I try to burn flash on a ADuC7021 using the ADuC702x.cfg I get a a
crash. (traceback attached)
in aduc7021.cfg if I comment out the following line it works
$_TARGETNAME configure -work-area-phys 0x1 -work-area-size 0x2000
it just takes a LONG time - of course)
The lines below the HALT
On Fri, Jul 3, 2009 at 3:12 PM, Thomas A. Moulton wrote:
> I am also using an ADuC702x (7021)
>
> I was using the windows version (pre-built r1888 I think)
>
> And when I try to use the internal RAM for flash writes I get a SEGV
> If I do not give it a ram block it finishes (eventually)
Please pro
On Fri, Jul 3, 2009 at 9:12 PM, Thomas A. Moulton wrote:
> I am also using an ADuC702x (7021)
>
> I was using the windows version (pre-built r1888 I think)
>
> And when I try to use the internal RAM for flash writes I get a SEGV
> If I do not give it a ram block it finishes (eventually)
>
> I am ru
I am also using an ADuC702x (7021)
I was using the windows version (pre-built r1888 I think)
And when I try to use the internal RAM for flash writes I get a SEGV
If I do not give it a ram block it finishes (eventually)
I am running svn HEAD
This may not be a new problem, as the r1888 on windows
On Fri, Jul 3, 2009 at 1:47 AM, Øyvind Harboe wrote:
> Committed.
>
> Thanks!
>
> You're not running svn head, are you?
>
> If you can update to svn when testing then that would be *great*! :-)
>
I am running the latest svn version.
--
Xiaofan http://mcuee.blogspot.com
___
Committed.
Thanks!
You're not running svn head, are you?
If you can update to svn when testing then that would be *great*! :-)
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing l
On Thu, Jul 2, 2009 at 5:19 PM, Øyvind Harboe wrote:
>> The _CHIPNAME and _CPUTAPID do not look right at all.
>> Does OpenOCD support AduC70xx right now?
>
> Yes, but you need to plug in the right values into that
> script. Patches gladly accepted.
>
> I believe the bugs you've spotted are a resul
> The _CHIPNAME and _CPUTAPID do not look right at all.
> Does OpenOCD support AduC70xx right now?
Yes, but you need to plug in the right values into that
script. Patches gladly accepted.
I believe the bugs you've spotted are a result of wholesale
copy & paste of code into the target config scri
http://svn.berlios.de/svnroot/repos/openocd/trunk/tcl/target/aduc702x.cfg
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME s3c2410
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
# This config file was defaulting to big
24 matches
Mail list logo
