Øyvind Harboe wrote:
>> So this *does* work :)
>>
>> Looks like a Cortex configuration/environment issue then.
> 
> Strange indeed.
> 
> Can you reproduce it w/your target and the dummy driver?

openocd -s lib/openocd/ -f interface/dummy.cfg -f board/ti_beagleboard.cfg

 > version
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-20:48) svn:1801
 > target create omap3.cpu cortex_m3 -endian little -chain-position 
omap3.cpu
 > targets
     CmdName    Type       Endian     AbsChainPos Name          State
--  ---------- ---------- ---------- ----------- ------------- ----------
  0: omap3.cpu  cortex_m3  little              0      omap3.cpu unknown
 > ocd_mem2array dataval 32 [expr "0x54011000 + 0 * 4"] 1
invalid command name "ocd_mem2array_dataval"
called at file "command.c", line 453
called at file "embedded:startup.tcl", line 89
called at file "embedded:startup.tcl", line 93
 >

For your reference: ti_beagleboard.cfg is in svn: 
./src/target/board/ti_beagleboard.cfg

Best regards

Dirk




_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to