Hi Aaron,

On 27/01/2011 6.53, Aaron Carroll wrote:
Hi Luca,

On 26 January 2011 00:13, luca ellero<lro...@gmail.com>  wrote:
With your patch it seems to work. Anyway after issuing "halt" instruction, I
always get the following message:

target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x60000173 pc: 0x0002dc92
MMU: disabled, D-Cache: disabled, I-Cache: enabled

I would point out that I'm using PandaBoard without any SD inserted, so only
ROM code is executed.

It seems quite strange that the target state is always Thumb and not ARM.
Even pc value is strange, I would expect someting in the range
0x40028000-0x40033FFF (which is where the ROM boot code is mapped, right?).

I think this is fine: it makes sense that the ROM is thumb to minimise
code size.  The addresses are also fine: see section 27.4.2.1 of the
OMAP4430 TRM.

What I'm confused about is that you can't read the ROM through the
debugger.  Dumping the exception vectors from the debugger gives:

mdw 0x28000 8
0x00028000: 40014000 40034002 40054004 40074006 40094008 400b400a
400d400c 400f400e

which makes no sense to me (note the weird pattern).  However, if you
run to u-boot and do the same:

Panda # md.l 0x28000 8
00028000: ea000242 e59ff018 e59ff018 e59ff018
00028010: e59ff018 e59ff018 e59ff018 e59ff018

it looks correct.

Regarding x-loader issue, I also noticed this problem. After a little
investigation I found that the problem is related to clocking (as you
correctly presume).
[snip]

I think I've got an x-loader fix for this... I'm trying to test it now
with Linux.  Stay tuned.


I think it could be useful reporting here an opeonocd session with Mistral EVM3530 (OMAP 3530), _without_ an SD, so we are in an similar environment (3530 has boot ROM mapped at 0x14000, see OMAP 3530 TRM 25.4.2.1).

Open On-Chip Debugger
> reset halt
RCLK not supported - fallback to 500 kHz
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)
JTAG tap: omap3530.dap enabled
omap3530.cpu: ran after reset and before halt ...
target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x80000173 pc: 0x0001687c
MMU: disabled, D-Cache: disabled, I-Cache: enabled
> mdw 0x14000
0x00014000: a001a000
> mdw 0x14000 10
0x00014000: a001a000 a003a002 a005a004 a007a006 a009a008 a00ba00a a00da00c a00fa00e
0x00014020: a011a010 a013a012
> mdw 0x40014000 10
0x40014000: ea00022e e59ff018 e59ff018 e59ff018 e59ff018 e59ff018 e59ff018 e59ff018
0x40014020: 288f48f7 4020ffc8
> arm disassemble 0x40014000
0x40014000      0xea00022e      B 0x400148c0
>

As you can see "mdw 0x14000" reports the weird pattern similar to yours on 4430, but "mdw 0x40014000" report something which, I think, can be the real ROM code. What do you think?

PS. regarding x-loader, I will try your patch as soon as possible, and report it here.
regards
luca


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

Reply via email to