Hi,
the OpenOCD contains support for some controllers with NAND interfaces, but
the AT91SAM9260 isn't currently supported. I looked into this once, but
SAM-BA is so easy to use, I didn't bother working on OpenOCD support for the
SAM9s.
There's a Linux version of SAM-BA (I never used the Window
Hello,
> Looks like you had the internal SRAM mapped to 0x0 at that point. Check the
> processors user's manual for information about its internal memories and
> mappings.
I had a closer look at the at91sam9260 datasheet.
On my board the code at the beginning of the NAND flash is loaded (thus
>
> so here's a first patch that adds the jim-eventloop
> functionality to openocd. Seems to work stably so far, but
> unfortunately openocd has some bugs/regressions that make it
> impossible to continously service the watchdog while halted:
>
> Most of the 'target_script' functionality seem
Committed.
> Most of the 'target_script' functionality seems to be unavailable in SVN
> head. The only target script that is actually called in the sources is
> 'pre_resume'. Neither 'post_halt' nor 'reset' seem supported.
Please explain?
post/pre_reset are used. See target/lpc2148.cfg as an e
Hello,
I am working with a patched OpenOCD on an ARM7 SoC, I have made some
modifications to support flash download and flash software breakpoints
and it works decently with an Olimex ARM-USB-OCD.
I am trying to get the same setup working with a JLink but I have some
problems, namely :
Debug:
Hi,
so here's a first patch that adds the jim-eventloop functionality to
openocd. Seems to work stably so far, but unfortunately openocd has
some bugs/regressions that make it impossible to continously service the
watchdog while halted:
Most of the 'target_script' functionality seems to be unava
This patch has three versions of lpc2148 config files:
- 2MHz
- RCLK
- no jtag speed defined
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
Index: C:/workspace/openocd/src/target/event/lpc2148_reset.script
On Thursday 07 Aug 2008 4:57:02 pm Christian Jaeger wrote:
> Duane Ellis wrote:
> > duane> I believe this would be a better solution.
> >
> > [snip]
> >
> > dominic>We would end up with quite a few config files.
> >
> > Ugh - that would be nasty.
> >
> > Then why not change openocd - w/ an #if WIND
On Thu, Aug 7, 2008 at 2:24 PM, Stefan Schoenleitner
<[EMAIL PROTECTED]> wrote:
> Hello Dominic,
>
> thanks for your fast answer.
>
> Dominic Rath wrote:
>> Hello Stefan,
>> > [...]
>>
>> The WIKI is completely outdated, but unfortunately none of the pages can be
>> edited.
>
> Is there some more
Hello Dominic,
thanks for your fast answer.
Dominic Rath wrote:
> Hello Stefan,
> > [...]
>
> The WIKI is completely outdated, but unfortunately none of the pages can be
> edited.
Is there some more recent documentation available somewhere ?
>> * How can I program the boot memory of my AT91S
Hello Stefan,
Original-Nachricht
> Datum: Thu, 07 Aug 2008 13:46:20 +0200
> Von: Stefan Schoenleitner <[EMAIL PROTECTED]>
> An: openocd-development@lists.berlios.de
> Betreff: [Openocd-development] programming AT91SAM9260 with openocd
> Hi,
>
> I read the (rather outdated) open
Hi,
I read the (rather outdated) openocd documentation at
http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger
more than once.
Unfortunately, I still can't program anything with it.
* How can I program the boot memory of my AT91SAM9260 at address 0x0 ?
Until now I tried the
Duane Ellis wrote:
> duane> I believe this would be a better solution.
>
> [snip]
>
> dominic>We would end up with quite a few config files.
>
> Ugh - that would be nasty.
>
> Then why not change openocd - w/ an #if WINDOWS - try the given DESC ,
> if that fails, quietly append " A" and try again.
duane> I believe this would be a better solution.
[snip]
dominic>We would end up with quite a few config files.
Ugh - that would be nasty.
Then why not change openocd - w/ an #if WINDOWS - try the given DESC ,
if that fails, quietly append " A" and try again.
-Duane.
_
Original-Nachricht
> I believe this would be a better solution.
>
> Why not
>
> (1) rename the orginal ".cfg" file I submitted to:
>
>olimex-jtag-tiny-windows-libftd2xxcfg
>
> (2) create another one - appropriately named...
> Not sure what that name might be bu
Christian> [the olimex jtag tiny cfg file is wrong, here is a patch]
Dominic> The problem is with the Windows version of the FTD2XX driver .
[snip]
Dominic> It's probably not much use fixing the config files, because
they're not really broken. A patch that adds some comments would be
highl
16 matches
Mail list logo
