what's behind JTAG/ICE break-in action
From: alan tsai (tsai_anan_at_yahoo.com)
Date: 01/23/05
- Next message: Simon Paradis: "Re: Memory mapped hardware registers"
- Previous message: Michael Schnell: "Re: Memory mapped hardware registers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 23 Jan 2005 14:17:15 -0800
Dear all,
In my board with Samsung S3C2410, I found something strage and suspect
there should be something have been done after using ICE to stop the
system but I cannot figure out what it is. I wonder whether it is the
JTAG or the debugger(ARM AxD/MSFT Platform Builder), or timing issue
make the difference. Can anyone give me some hint?
Case 1:
One system fail when boot and free run, while it will work if I
intendedly leave a infinite loop after bootloader copy all image from
flash to RAM, instead of setting program counter to starting of the
image in RAM, I use debugger to break in and set program counter to
starting of the image in RAM, then it works. I cannot figure out why?
Case 2:
Use MSFT platform builder to read register is OK, while write fail.
But if I use JTAG/ICE to write, then it will be no problem. Why?
I really appreciate any input.
Alan Tsai
- Next message: Simon Paradis: "Re: Memory mapped hardware registers"
- Previous message: Michael Schnell: "Re: Memory mapped hardware registers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
