On 03/12/2011 02:15 PM, Anatolij Gustschin wrote:
The reason for using wrsr register is that when reading this register,
we can also recognize the software reset cause (SWFT, bit 0 is set).
In our use case we have this requirement.
Ok, understood.
I do not think printing the reset cause
On Thu, 10 Mar 2011 16:07:49 +0100
Stefano Babic sba...@denx.de wrote:
On 03/10/2011 11:53 AM, Anatolij Gustschin wrote:
Add output of the WRSR register content while booting so that
we can see the source of the last reset.
Signed-off-by: Anatolij Gustschin ag...@denx.de
Hi Antolij,
Add output of the WRSR register content while booting so that
we can see the source of the last reset.
Signed-off-by: Anatolij Gustschin ag...@denx.de
---
arch/arm/cpu/arm1136/mx31/generic.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git
Hi Anatolij,
--- On Thu, 3/10/11, Anatolij Gustschin ag...@denx.de wrote:
mx31_get_mcu_main_clk() / 100);
+ struct wdog_regs *wdog = (struct wdog_regs *)WDOG_BASE;
+
+ printf(CPU: Freescale i.MX31 at %d MHz (WRSR=0x%04x)\n,
+
mx31_get_mcu_main_clk() / 100,
4 matches
Mail list logo