Strontium wrote:
> Magnus Lundin wrote:
>> Magnus Lundin wrote:
>>
>>> When I do this for the Beagle i just use
>>>
>>> # set the current target, should not be nexessary with only one target
>>> configured
>>> targets omap3.cpu
>>> # call tcl functions without the extra target name
>>> mem2arr
Magnus Lundin wrote:
> Magnus Lundin wrote:
>
>> When I do this for the Beagle i just use
>>
>> # set the current target, should not be nexessary with only one target
>> configured
>> targets omap3.cpu
>> # call tcl functions without the extra target name
>> mem2array dataval 32 [expr "0x54011
Magnus Lundin wrote:
> When I do this for the Beagle i just use
>
> # set the current target, should not be nexessary with only one target
> configured
> targets omap3.cpu
> # call tcl functions without the extra target name
> mem2array dataval 32 [expr "0x54011000 + $reg_num * 4"] 1
>
>
And t
When I do this for the Beagle i just use
# set the current target, should not be nexessary with only one target
configured
targets omap3.cpu
# call tcl functions without the extra target name
mem2array dataval 32 [expr "0x54011000 + $reg_num * 4"] 1
Regards
Magnus
Strontium wrote:
> Hmm,
>
> S
Hmm,
So i looked into the code and it would appear to be a bug.
ocd_mem2array is implemented via jim_mem2array which eventually calls
target_mem2array. When this happens, I am pretty confident if
ocd_mem2array works, that argc will be 5.
BUT
if I use omap3.cpu mem2array, this is implemented
Howdy,
I have a script that goes:
proc omap3_ReadDebugRegister { reg_num } {
# read the value of the debug register reg_num at address reg_num << 2
omap3.cpu mem2array dataval 32 [expr "0x54011000 + $reg_num * 4"] 1
}
It errors and crashes openocd with the following message:
Runtime error,
