Re: Disabled LocalPlus Controller (LPC) clock on MPC512x

From: Alexander Popov
Date: Tue Feb 10 2015 - 05:36:08 EST


Hello Matteo,
sorry for such a long delay in replying, now I have my board back again.

19.12.2014 12:38, Matteo Facchinetti ÐÐÑÐÑ:
On 16/12/2014 13:00, Alexander Popov wrote:
In fact clk_ignore_unused bootparam helps to avoid disabling NFC clock.
The board crash is reproduced again if I perform the following steps:
1. disable NFC clock in uboot by clearing NFC_EN bit in SCCR1 register,
2. boot Linux with clk_ignore_unused,
3. touch any LPB address.

Could you see the Reset Status Register (RSR) after board crash?
When boad reset, you may stop uboot in console and then print the value
of this register.

This could be help to see what happen internally to the microcontroller.

I've reproduced TWR-MPC5125 crash without Linux only in uboot.
This is the annotated procedure:

=> md.l 0x80000e10 /* Reset Status Register */
80000e10: 60000000 /* All flags are cleared (just powered on) */

=> md.l 0x80000f04 /* System Clock Control Register 1 */
80000f04: e404b600 /* NFC clock is enabled */

=> md.l 0xfff00000 /* Reading from MRAM living at LPB CS0 */
fff00000: cafea134 /* Works fine */

=> mw.l 0x80000f04 0xc404b600 1 /* Disable NFC clock */

=> md.l 0x80000f04
80000f04: c404b600 /* NFC clock is disabled now */

=> md.l 0xfff00000 /* Reading from MRAM again */
fff00000:

/* The board has just reset */

U-Boot 2009.03-00004-gd37ab38 (Apr 14 2010 - 10:48:22) MPC512X
CPU: MPC5125 rev. 1.0, Core e300c4 at 393.216 MHz, CSB at 196.608 MHz
...

=> md.l 0x80000e10 /* Read RSR */
80000e10: 60000040 /* Only external HRESET1 event has occurred */

But rising of EXT1HRS flag is not special for this crash.
EXT1HRS is similarly set if I execute 'reset' command in uboot
or call 'reboot' from Linux.

Thanks.

Best regards,
Alexander

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/