Hi Spen,
I was running ./boostrap, but the " --enable-maintainer-mode " was
missing in my last config.
With --enable-maintainer-mode, it works better !
Thanks.
Regards,
Laurent
http://www.amontec.com
Spencer Oliver wrote:
>> openocd.texi:12: @include `version.texi': No such file or directory.
Well...that is great and now everyone knows about your important
contributions to the project. Good for you!
On 9/1/09 5:12 PM, "Duane Ellis" wrote:
> I did *QUITE* a lot for the at91sam7 chips a when we first introduced
> TCL to openocd.
> I also did some more for the STM32 chip.
The old sam7 and stm32 tcl scripts I wrote last year are crusty and
where not fixed when the tcl code was re-arranged and moved around.
[this has already been committed]
-Duane.
du...@desk ~/test/openocd/tcl
$ svn diff
Index: chip/atmel/at91/at91sam7x128.tcl
Gary Carlson wrote:
> I can now see that I left off a critical detail! :)
>
> Yes, you most certainly can use a TCL set command to accomplish this. The
> only issue is you have to spend an inordinate amount of time entering the
> values by hand. That in itself is another source for errors -- esp
On Sun, 30 Aug 2009, David Brownell wrote:
> On Saturday 29 August 2009, Duane Ellis wrote:
>
> > Some screens are nice and wide, tiny fonts, mine is not - I have to have
> > larger fonts so I can see.
>
> Yeah, that too. Some peoples' eyes are born weak; other
> people have to age into eyes t
> openocd.texi:12: @include `version.texi': No such file or directory.
> openocd.texi:37: warning: undefined flag: VERSION.
> openocd.texi:38: warning: undefined flag: UPDATED.
> openocd.texi:58: warning: undefined flag: VERSION.
> openocd.texi:59: warning: undefined flag: UPDATED.
> makeinfo: Rem
The svn 2600 cannot finalize MAKE under windows cygwin.
Note: openocd.exe is compiled and is working for both Amontec JTAGkey
and Amontec JTAGkey-2
Here the result of the last line of make :
make[2]: Leaving directory
`/cygdrive/c/amontec/openocd_builder/svn/trunk/src'
Making all in doc
ma
On Monday 31 August 2009, Michael Schwingen wrote:
> > 3) One feature that I think may make sense to add at some point in the
> > future to the main software is support for label/value associations that
> > allow hexadecimal register values to be associated with more legible and
> > understandable
On 9/1/09, Alan Carvalho de Assis wrote:
> Still not working:
>
> (gdb) target remote :
> Remote debugging using :
> 0xd800 in ?? ()
> (gdb) monitor reg pc 0xd850
> pc (/32): 0xD850
> (gdb) si
> 0xd800 in ?? ()
> Infinite loop detected
> (gdb)
>
> (gdb) monitor reg pc 0xd80
michal smulski wrote:
> When I run this code:
>
> set CONFIG_SYS_HZ_CLOCK16500
> global CONFIG_SYS_HZ_CLOCK
>
> proc showAmbaPLL {} {
> global CONFIG_SYS_HZ_CLOCK
> puts [format "CONFIG_SYS_HZ_CLOCK %d" $CONFIG_SYS_HZ_CLOCK]
> }
>
> I get this message:
> Runtime error,
Hi Oyvind,
On 9/1/09, Øyvind Harboe wrote:
>
> Fixed in head of GDB?
>
> http://www.nabble.com/Patch-for-the-gdb-problem-%C2%ABValue-being-assigned--to-is-no-longer-active%C2%BB-td23615004.html
>
Thank you very much!
>> Is there any other way to setup the PC to right position?
>
> I've always u
On Tue, Sep 1, 2009 at 11:54 AM, Peter Zuidema wrote:
> The AT91SAM7X(C)512 contains 2 flash banks, each 256KB.
Yes, I know
> You have to change the sam7x512.cfg and add a flash-bank definition.
Are you sure?
> The doc/openocd.pdf has some information in chapter 13 "Flash programming".
>
> You co
Starting a new thread on a crazy idea I had to help alleviate
problems with coming up with the reset init sequence.
Lots of hardware out there have working .elf files that set up
the hardware.
What if a known working elf image could be used instead of
having to first succeed in writing a reset in
+++ Øyvind Harboe [2009-09-01 08:39 +0200]:
> 1614 introduces *lots* of changes. It could have been broken into half
> a dozen commits. :-)
>
> One thing to try:
>
> tms_sequence long
That was added in r1834, so is not present in r1614 where the issue
started. So presumably I'm using the old 'lo
Hello Massimiliano,
The AT91SAM7X(C)512 contains 2 flash banks, each 256KB.
You have to change the sam7x512.cfg and add a flash-bank definition.
The doc/openocd.pdf has some information in chapter 13 "Flash programming".
You could try this:
flash bank at91sam7 0 0 0 0 0
flash bank at91sam7 0 0 0
> Hm - yes, that might be useful. I have used objdump to extract the
> initialization tables from my board-init code to create BDI2000/OpenOCD
> init scripts.
Now, if we could do that in some *nice* way it would be quite
a powerful method. Most every PCB out there has some working
sample code
Øyvind Harboe wrote:
>> What advantage does that provide?
>> You need a disassembler to view the effective board-init sequence, you
>> need a cross-toolchain to modify the code, in comparison to just
>> changing a script file.
>>
>
> You can use the header files for the target file without hav
Harald Welte wrote:
> Hi Magnus,
>
> On Mon, Aug 31, 2009 at 05:36:11PM +0200, Magnus Lundin wrote:
>
>
>>> dap_ap_select(swjdp, 1);
>>> before the two lines
>>> dap_ap_read_reg_u32(swjdp, 0xFC, &idreg);
>>> dap_ap_read_reg_u32(swjdp, 0xF8, &romaddr);
>>> in ahbap_debugport_i
On Tue, Sep 1, 2009 at 10:24 AM, Michael
Schwingen wrote:
> Øyvind Harboe wrote:
>> Crazy idea:
>>
>> - write a small C app for the target that goes along with board config file
>> - this .elf file is loaded by OpenOCD
>> - use built-in ARM simulator to execute fn's in that .elf file
>>
> What adva
Hi Magnus,
On Mon, Aug 31, 2009 at 05:36:11PM +0200, Magnus Lundin wrote:
>> dap_ap_select(swjdp, 1);
>> before the two lines
>> dap_ap_read_reg_u32(swjdp, 0xFC, &idreg);
>> dap_ap_read_reg_u32(swjdp, 0xF8, &romaddr);
>> in ahbap_debugport_init()
>>
>>
> What happens when
Øyvind Harboe wrote:
> Crazy idea:
>
> - write a small C app for the target that goes along with board config file
> - this .elf file is loaded by OpenOCD
> - use built-in ARM simulator to execute fn's in that .elf file
>
What advantage does that provide?
You need a disassembler to view the effe
Crazy idea:
- write a small C app for the target that goes along with board config file
- this .elf file is loaded by OpenOCD
- use built-in ARM simulator to execute fn's in that .elf file
?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
_
On 9/1/09 12:04 AM, "Øyvind Harboe" wrote:
>> 2) One possible process improvement that I believe makes sense is to start
>> enforcing a rule that authors of new configuration files must include a
>> minimal comment header at the top of the file that specifies the exact
>> hardware/debugger co
I can now see that I left off a critical detail! :)
Yes, you most certainly can use a TCL set command to accomplish this. The
only issue is you have to spend an inordinate amount of time entering the
values by hand. That in itself is another source for errors -- especially
on processors with la
Some quick comments...
Why are you using "reset halt" and not "reset init"?
> last qestion:
> if i try the command line
> openocd -f jtagkey.cfg -f sam7x512.cfg -c "script flash.script"
> I have an error:
> Unknown command: reset halt
You need to set up OpenOCD after configuring it by running
th
>> 3) One feature that I think may make sense to add at some point in the
>> future to the main software is support for label/value associations that
>> allow hexadecimal register values to be associated with more legible and
>> understandable names. Looking at "mww 0x3ec2 0x2" in a configura
> 2) One possible process improvement that I believe makes sense is to start
> enforcing a rule that authors of new configuration files must include a
> minimal comment header at the top of the file that specifies the exact
> hardware/debugger combination used. The SAM-ICE (J-link) debugger I am
Gary Carlson wrote:
> 1) One of the features that the software currently allows is configuration
> setting inheritance from board to target to CPU. While I generally am a big
> advocate of extensibility in most software projects, I have been very leery
> of doing this for hardware-specific configu
28 matches
Mail list logo
