Øyvind Harboe wrote:
>> target state: halted
>> target halted in ARM state due to debug-request, current mode: Supervisor
>> cpsr: 0x000000d3 pc: 0x00000000
>>
>>> flash protect 0 0 2 off
>>>
>> memory read caused data abort (address: 0x00010000, size: 0x1, count: 0x1)
>> memory read caused data abort (address: 0x00020000, size: 0x1, count: 0x1)
>> cleared protection for sectors 0 through 2 on flash bank 0
>>
>
>
> You'll have to figure out why you can't access that memory region.
>
>
> Why are you using "reset halt" instead of "reset init"?
>
No reason except not knowing. (Where can I find up-to-date documentation?)
> "reset init" will run the reset init script which will make the memory
> accessible...
>
Ok.
> reset init
RCLK not supported
jtag_khz: 16
JTAG device found: 0x04570041 (Manufacturer: 0x020, Part: 0x4570,
Version: 0x0)
JTAG device found: 0x25966041 (Manufacturer: 0x020, Part: 0x5966,
Version: 0x2)
JTAG device found: 0x2457f041 (Manufacturer: 0x020, Part: 0x457f,
Version: 0x2)
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0x00000000
RCLK not supported
jtag_khz: 3000
cleared protection for sectors 0 through 7 on flash bank 0
> flash info 0
#0: str9x at 0x00000000, size 0x00080000, buswidth 0, chipwidth 0
#0: 0x00000000 (0x10000 64kB) protected
#1: 0x00010000 (0x10000 64kB) protected
#2: 0x00020000 (0x10000 64kB) protected
#3: 0x00030000 (0x10000 64kB) protected
#4: 0x00040000 (0x10000 64kB) protected
#5: 0x00050000 (0x10000 64kB) protected
#6: 0x00060000 (0x10000 64kB) protected
#7: 0x00070000 (0x10000 64kB) protected
str9x flash driver info
> flash info 1
#1: str9x at 0x00080000, size 0x00008000, buswidth 0, chipwidth 0
#0: 0x00000000 (0x2000 8kB) protected
#1: 0x00002000 (0x2000 8kB) protected
#2: 0x00004000 (0x2000 8kB) protected
#3: 0x00006000 (0x2000 8kB) protected
str9x flash driver info
> flash protect 0 0 2 off
cleared protection for sectors 0 through 2 on flash bank 0
> flash info 0
#0: str9x at 0x00000000, size 0x00080000, buswidth 0, chipwidth 0
#0: 0x00000000 (0x10000 64kB) protected
#1: 0x00010000 (0x10000 64kB) protected
#2: 0x00020000 (0x10000 64kB) protected
#3: 0x00030000 (0x10000 64kB) protected
#4: 0x00040000 (0x10000 64kB) protected
#5: 0x00050000 (0x10000 64kB) protected
#6: 0x00060000 (0x10000 64kB) protected
#7: 0x00070000 (0x10000 64kB) protected
str9x flash driver info
> flash info 1
#1: str9x at 0x00080000, size 0x00008000, buswidth 0, chipwidth 0
#0: 0x00000000 (0x2000 8kB) protected
#1: 0x00002000 (0x2000 8kB) protected
#2: 0x00004000 (0x2000 8kB) protected
#3: 0x00006000 (0x2000 8kB) protected
str9x flash driver info
> flash erase_address 0x00000000 0x00008000
erased address 0x00000000 length 32768 in 1.126030s
> flash erase_address 0x00000000 0x00010000
erased address 0x00000000 length 65536 in 1.111105s
> flash erase_address 0x00000000 0x00020000
erased address 0x00000000 length 131072 in 2.254089s
> flash erase_address 0x00000000 0x00030000
erased address 0x00000000 length 196608 in 3.317857s
> flash erase_address 0x00000000 0x00040000
erased address 0x00000000 length 262144 in 4.461253s
> flash erase_address 0x00000000 0x00080000
erased address 0x00000000 length 524288 in 6.558052s
Wonderful?!
>
> I would expect this to fail too:
>
> mdw 0x10000
>
> mdw 0x10000
0x00010000: ffffffff
((With "reset halt": yes it does fail. As does:
> mdw 0x8000
memory read caused data abort (address: 0x00008000, size: 0x4, count: 0x1)
Runtime error, file "?", line 1:
> mdw 0x00000
0x00000000: ffffffff
> mdw 0x7ffc
0x00007ffc: ffffffff
> flash info 1
#1: str9x at 0x00080000, size 0x00008000, buswidth 0, chipwidth 0
...
> mdw 0x00080000
memory read caused data abort (address: 0x00080000, size: 0x4, count: 0x1)
Runtime error, file "?", line 1:
Now I don't understand what the "at 0x..." addresses given by "flash
info" mean.
))
But now it seems all the reason was I needed "reset init".
Wondering: why does "flash info" still say the memory is protected?
Christian.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
