Hi Øyvind,
Thanks for your previous message. Do you have any idea about the nature
of the following "runtime" error (I get it when I try to protect a
memory part for blob)?
> reset halt
JTAG tap: imote2.cpu tap/device found: 0x79265013 (mfg: 0x009, part:
0x9265, ver: 0x7)
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x580000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
(processor reset)
> flash protect 0 0 4 off
flash protect <bank> <first> <last> <on | off>
set protection of sectors
Runtime error, file "command.c", line 580:
flash protect <bank> <first> <last> <on | off>
set protection of sectors
The line 580 in the command.c is the following:
retcode = Jim_Eval_Named(interp, line, __THIS__FILE__, __LINE__);
Best Regards,
Andrey
Øyvind Harboe wrote:
> Hi Andrey,
>
>
>> Error: type 'xscale' is missing write_phys_memory
>> Error: type 'xscale' is missing read_phys_memory
>>
>
> Ignore these errors. They are only reminders to the developers
> to add this support to the xscale target.
>
> Try writing up a fresh bug report using these guidelines:
>
> http://openocd.berlios.de/doc/doxygen/bugs.html
>
>
>
> It is almost as if you have a trivial file not found problem
> w.r.t. the error below, but your report does not contain enough information.
>
>
>>> flash write_image blob-im2
>>>
>> couldn't open blob-im2
>>
>>
>
>
>
>
>
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
