Øyvind Harboe wrote:
> On Sun, May 17, 2009 at 8:02 PM, Dirk Behme <dirk.be...@googlemail.com> wrote:
>> Ųyvind Harboe wrote:
>>> Strange indeed. Parsing works here...
>> Yes, I believe this ;)
>>
>> The big question is what might be different for me.
>>
>> From your last mail, you use 'at91eb40a' CPU configuration? Maybe the init
>> scripts for this do some magic which is missing for me? What scripts do you
>> source for this, just to have a loo
>
> Try the command line below to replicate my setup:
>
> openocd -f interface/dummy.cfg -f target/at91eb40a.cfg
>
>
> (using configure --enable-dummy to build the dummy driver...)
Done:
> version
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-20:48) svn:1801
> targets
CmdName Type Endian AbsChainPos Name State
-- ---------- ---------- ---------- ----------- ------------- ----------
0: at91eb40a.cpu arm7tdmi little 0 at91eb40a.cpu unknown
> ocd_mem2array dataval 32 [expr "0x54011000 + 0 * 4"] 1
Target not examined yet
mem2array: Read @ 0x54011000, w=4, cnt=1, failed
>
So this *does* work :)
Looks like a Cortex configuration/environment issue then.
Thanks
Dirk
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
