Hi Scott:
After enabling debugging option from kernel (2.6.29) , here is the log.
We do have an external debugger(BDI). But soon after the crash happens,
looks like the core freezes and hence reading from any location in memeory
gives "SAP: Read access failed" error.
I have disabled PCI.
--Than
Junita Ajith wrote:
Hi Scott:
I am still stuck at Linux kernel booting in MPC8343EA based board.
I have disabled "Ethernet, PCI, USB, dma engines " in the *.dts file and
also in the kernel config.
I am using MPC8349emitxgp.dts ; enabled MPC8349ITX support in kernel
config also. In fact, I tr
Hi Scott:
I am still stuck at Linux kernel booting in MPC8343EA based board.
I have disabled "Ethernet, PCI, USB, dma engines " in the *.dts file and
also in the kernel config.
I am using MPC8349emitxgp.dts ; enabled MPC8349ITX support in kernel config
also. In fact, I tried building MPC8349emIT
Eric,
1. I did try building with MDS configuration.
2. Removed BCSR section
3. Set u-boot environment variable.
The code boots up in the MPC8349 reference platform and not in the custom
board.
Also I am wondering why the cuImage would not give out any serial output
even, whereas I do see serial o
I would probably remove the bcsr region. this was some cpld I believe on a
reference board. with this dts it'll try to write to some hardware registers
that do not exist or are not mapped to the same area.
-Original Message-
From: linuxppc-dev-bounces+eric.lee=hp@lists.ozlabs.org
On Sun, Dec 06, 2009 at 10:41:25PM -0800, ajij...@gmail.com wrote:
> Hi
>
> We have an MPC8343EA based custom board.
>
> I am not able to get Linux up and running in this. No serial output to debug
> further.
> U-boot shows correct 'bdinfo' & 'clocks' output.
> inux hangs at machine_probe.
