p2020 doesn't boot from SDK 1.9

cancel
Showing results for 
Search instead for 
Did you mean: 

p2020 doesn't boot from SDK 1.9

444 Views
alex16
Contributor I

I have a custom board with schematics identical to p2020rdb. We used one with linux 2.6.30 SMP from 2013. Worked fine for us. I'd like to update one from NXP's Linux SDK 1.9, which has RTlinux 3.12. I download SDK, successfully build minimal image, tftp on the target but fail to boot. My u-boot listing is below. What did I miss? Do I need to update u-boot from my build as well? What commands could fix my problem? 

CPU0: P2020E
Core: E500
Clock Configuration:
CPU0:1200 MHz, CPU1:1200 MHz,
CCB:600 MHz,
DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:150 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: X-ES XPedite5500 PMC/XMC SBC
Rev B, Serial# 35150706, Cfg 90015165
I2C: ready
DRAM: 2 GiB (DDR3, 64-bit, CL=6, ECC on)
FLASH: Executed from FLASH1
POST memory PASSED
POST ecc PASSED
FLASH: 256 MiB
L2: 512 KB enabled
NAND: 4096 MiB
PCIE1: connected as Root Complex (x1, 2.5 GT/s)
01:00.0 - 10b5:8112 - Bridge device (x1, 2.5 GT/s)
PCIE1: Bus 00 - 02
PCIE2: disabled
PCIE3: disabled
In: serial
Out: serial
Err: serial
DTT: 48 C local / 68 C remote (adt7461@4c)
DTT: 49 C local (lm75@48)
Net: eTSEC1, eTSEC2, eTSEC3
POST i2c PASSED
POST ethernet PASSED
POST temp PASSED
POST eeprom PASSED
POST pcie PASSED
Hit any key to stop autoboot: 0
=> tftp 1000000 uImage--3.12-r0-p2020rdb-20180611235049.bin
eTSEC1: No link.
eTSEC2: No link.
Speed: 100, full duplex
Using eTSEC3 device
TFTP from server 192.168.1.105; our IP address is 192.168.1.218
Filename 'uImage--3.12-r0-p2020rdb-20180611235049.bin'.
Load address: 0x1000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
################################
done
Bytes transferred = 4275760 (413e30 hex)
=> tftp 2000000 fsl-image-minimal-p2020rdb.ext2.gz.u-boot
Speed: 100, full duplex
Using eTSEC3 device
TFTP from server 192.168.1.105; our IP address is 192.168.1.218
Filename 'fsl-image-minimal-p2020rdb.ext2.gz.u-boot'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
###################
done
Bytes transferred = 3141370 (2feefa hex)
=> tftp c00000 uImage--3.12-r0-p2020rdb-pc_32b-20180611235049.dtb
Speed: 100, full duplex
Using eTSEC3 device
TFTP from server 192.168.1.105; our IP address is 192.168.1.218
Filename 'uImage--3.12-r0-p2020rdb-pc_32b-20180611235049.dtb'.
Load address: 0xc00000
Loading: #
done
Bytes transferred = 13899 (364b hex)
=> bootm 1000000 2000000 c00000
WARNING: adjusting available memory to 30000000
## Current stack ends at 0x7fe57ce0
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-3.12.37-rt51+g43cecda
Created: 2018-06-12 0:19:01 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 4275696 Bytes = 4.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
Image Name: fsl-image-minimal-p2020rdb-20180
Created: 2018-06-12 0:52:59 UTC
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 3141306 Bytes = 3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 00c00000
Booting using the fdt blob at 0xc00000
Uncompressing Kernel Image ... OK
Loading Ramdisk to 2fd01000, end 2ffffeba ... OK
Loading Device Tree to 03ff9000, end 03fff64a ... OK
POST: Unable to find a node for POST result: fsl,mpc8548-pcie (reg ef00a000)
POST: Unable to find a node for POST result: fsl-i2c (reg 00000054)
POST: Unable to find a node for POST result: fsl-i2c (reg 00000048)
POST: Unable to find a node for POST result: fsl-i2c (reg 0000004c)
POST: Unable to find a node for POST result: fsl-i2c (reg 0000004c)
## Transferring control to Linux (at address 00000000) ...
Booting using OF flat tree...

0 Kudos
2 Replies

162 Views
alex16
Contributor I

Thanks Yiping for your writing tome. When I fail to boot my minimal image I found the prebuild image, you pointed to me, and I tried to boot from that. I used all components from the IMAGE ISO. Nothing had been used from my build. It fail with exactly same log as I provided. Looks like my build is identical to the prebuild IMAGE iso. Exactly same log. Have no idea what is the problem. I build kernel 2.6.35 minimal image for p2020 and that worked! I boot my board with linux 2.6.35. Looks like Konfig file made a good job for me. From NXP linux 3.12 I had build development tools. I cross compiled a HelloWorld app, copy executable on my target and that worked! So far, we can ship the board with linux 2.6.35 with development tools from 3.12 and customers could experiment on that by themself. I'd like to finish my linux 3.12 porting at mean time. Any idea how to go from working build 2.6.35 to port linux 3.12 build? I guess, 2.6.35 is not RTLinux, but 3.12 is RTLinux. Our customers will appreciate RTLinux options

Thanks,

Alex

0 Kudos

162 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello alex voytov,

According to the above log, u-boot has already passed control to Linux Kernel, Linux should be executed.

I suspect whether there is problem with your generated uImage with SDK 1.9.

Please download SDK 1.9 pre-built ISO "Image: QorIQ SDK V1.9 PPCE500V2 IMAGE" from https://www.nxp.com/support/developer-resources/run-time-software/linux-software-and-development-too... (previous version->previous). Please use uImage and dtb file provided in the pre-built image ISO to do verification in the current u-boot environment.

If this problem persists, please customize u-boot source in SDK 1.9 with the modification for your target board.


Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos