p1010 localbus hardconnet such as:cs1--norflash ;cs2--nandflash; cs3--cpld
I find cpu dead when I operation of three peripherals at the same time in diffrent task (in linux), I want to know if the driver needs mutual protection? but norflash nandflash are linux itself drvier.
I wonder if there's a design flaws with localbus ?
Which NXP SDK is used?
it seems like QorIQ-SDK-V1.4 (linux2.6.35)
Please provide U-Boot booting log as text attachment.
U-Boot 2010.12 (May 12 2016 - 21:40:36) V1.01
CPU: P1010, Version: 2.0, (0x80f10020)
Core: E500, Version: 5.2, (0x80212152)
Clock Configuration:
CPU0:800 MHz,
CCB:400 MHz,
DDR:400 MHz (800 MT/s data rate) (Asynchronous), IFC:100 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: P1010ACCE
I2C: ready
SPI: ready
DRAM: Configuring DDR for 667 MT/s data rate
DDR: 1 GiB (DDR3, 32-bit, CL=6, ECC off)
FLASH: 32 MiB
L2: 256 KB enabled
NAND: NAND device: Manufacturer ID: 0xef, Chip ID: 0xd3 (Unknown NAND 1GiB 3,3V 8-bit)
1024 MiB
PCIe1: Root Complex of mini PCIe Slot, no link, regs @ 0xffe0a000
PCIe1: Bus 00 - 00
PCIe2: Root Complex of PCIe Slot, no link, regs @ 0xffe09000
PCIe2: Bus 01 - 01
In: serial
Out: serial
Err: serial
Net: eTSEC1: Not support
eTSEC2: No support for PHY id ffffffff; assuming generic
eTSEC3: No support for PHY id ffffffff; assuming generic
eTSEC1, eTSEC2, eTSEC3
................................................................
According to the log the SDK being used is very old.
In the SDK v1.9 the U-Boot is:
U-Boot 2015.01+SDKv1.9+geb3d4fc (Dec 03 2015 - 21:18:10)
It is recommended to use the latest SDK v1.9.
Is there localbus problem in old sdk ? uboot or linux driver has problem ? Please describe more in detail at this problem. update sdk is huge job, i want to reslove this problem quickly!