How to install kernel image into T2080RDB Board (SD card)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to install kernel image into T2080RDB Board (SD card)

609 Views
julencruchaga
Contributor II

Hi, I need to install new kernel images into my SD card (T2080RDB Board) and run the board from a SD card for testing. I've followed QorIQ-SDK-2.0-IC-Rev0.pdf manual (4.4.15.9.4 chapter) . 

-I've download QorIQ Linux SDK v2.0 PPC64E6500 IMAGE.iso, mount it, and I've copied uImage and uImage.dtb from t2080rdb-64b/ directory (5..7) into my SD card. Previously I've created two partitions into my SD card (1..3).

-After that I've plug in the SD card and power on the board with this switch setting (Default Switch Settings) 

SW1 : 00010011

SW2 : 10111111

SW3 : 11100001

-Into u-boot terminal I've  configured bootcmd command (4.4.15.9.4 SD Deployment)

 setenv bootcmd 'setenv bootargs root=/dev/mmcblk0p2 rw rootdelay=5 console=$consoledev,$baudrate; mmcinfo; ext2load mmc 0:2 $loadaddr /boot/$bootfile; ext2load mmc 0:2 $fdtaddr /boot/$fdtfile;bootm $loadaddr - $fdtaddr'

-After that I've executed run bootcmd (before to execute save command) in order to check if everything is correct, but the board doesn't startup correctly, here that's the serial port output:

...

...
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
ata1: No Device OR PHYRDY change,Hstatus = 0xa0000000
ata1: SATA link down (SStatus 10 SControl 300)
ata2: No Device OR PHYRDY change,Hstatus = 0xa0000000
fsl-ehci fsl-ehci.1: irq 45, io mem 0xffe211000
ata2: SATA link down (SStatus 10 SControl 300)
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
i2c /dev entries driver
mpc-i2c ffe118000.i2c: timeout 1000000 us
rtc-ds1307 0-0068: SET TIME!
rtc-ds1307 0-0068: rtc core: registered ds1339 as rtc0
mpc-i2c ffe118100.i2c: timeout 1000000 us
mpc-i2c ffe119000.i2c: timeout 1000000 us
mpc-i2c ffe119100.i2c: timeout 1000000 us
i2c i2c-1: Added multiplexed i2c bus 4
i2c i2c-1: Added multiplexed i2c bus 5
i2c i2c-1: Added multiplexed i2c bus 6
i2c i2c-1: Added multiplexed i2c bus 7
pca954x 1-0077: registered 4 multiplexed busses for I2C switch pca9546
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Freescale(R) MPC85xx EDAC driver, (C) 2006 Montavista Software
EDAC MC0: Giving out device to module MPC85xx_edac controller mpc85xx_mc_err: DEV mpc85xx_mc_err (INTERRUPT)
MPC85xx_edac acquired irq 490 for MC
MPC85xx_edac MC err registered
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-esdhc ffe114000.sdhc: No vmmc regulator found
sdhci-esdhc ffe114000.sdhc: No vqmmc regulator found
mmc0: SDHCI controller on ffe114000.sdhc [ffe114000.sdhc] using ADMA 64-bit
platform caam_qi.0: Linux CAAM Queue I/F driver initialised
caam ffe300000.crypto: Instantiated RNG4 SH1
caam ffe300000.crypto: device ID = 0x0a13020000000000 (Era 6)
caam ffe300000.crypto: job rings = 4, qi = 1
caam algorithms registered in /proc/crypto
platform caam_qi.0: fsl,sec-v5.2 algorithms registered in /proc/crypto
caam_jr ffe301000.jr: registering rng-caam
caam ffe300000.crypto: fsl,sec-v5.2 algorithms registered in /proc/crypto
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Freescale USDPAA process driver
fsl-usdpaa: no region found
Freescale USDPAA process IRQ driver
dce_sys_init done!
fsl-dce ffe312000.dce: Device /soc@ffe000000/dce@312000 initialized ver: 0x0af00101

fsl-pme ffe316000.pme: ver: 0x00100201
Freescale pme2 db driver
Freescale pme2 scan driver
fsl-pme2-scan: device pme_scan registered
Freescale hypervisor management driver
fsl-hv: no hypervisor found
ipip: IPv4 over IPv4 tunneling driver
Initializing XFRM netlink socket
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
fsl_generic: FSL DPAA Generic Ethernet driver
rtc-ds1307 0-0068: setting system clock to 2000-01-01 01:19:16 UTC (946689556)
mmc0: new SDHC card at address 0001
mmcblk0: mmc0:0001 ASTC 7.51 GiB
mmcblk0: p1 p2
Waiting 5 sec before mounting root device...
md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
EXT2-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 179:2.
devtmpfs: error mounting -2
Freeing unused kernel memory: 364K (c000000000a9b000 - c000000000af6000)
Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
CPU: 7 PID: 1 Comm: swapper/0 Not tainted 4.1.8-rt8+gbd51baf #1
Call Trace:
[c0000000f1083c90] [c0000000007a34fc] .dump_stack+0x8c/0xb8 (unreliable)
[c0000000f1083d10] [c0000000007a0e34] .panic+0xf0/0x270
[c0000000f1083db0] [c0000000000022d8] .kernel_init+0x10c/0xe34
[c0000000f1083e30] [c000000000000998] .ret_from_kernel_thread+0x58/0xc0
Rebooting in 180 seconds..

How I can restart my board from the SD Card? Have I followed all the steps correctly?

Regards,

Julen.

0 Kudos
1 Reply

445 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Julen Cruchaga,

Please deploy rootfs filesystem in the host PC as the following.

# mkdir  /temp

# mount  /dev/sdb2  /temp

# cd /temp

# cp QorIQ_SDK_V2.0_PPC64E6500_20160527_ROOTFS_Image.tar.gz .

# tar -xzvf QorIQ_SDK_V2.0_PPC64E6500_20160527_ROOTFS_Image.tar.gz

# rm QorIQ_SDK_V2.0_PPC64E6500_20160527_ROOTFS_Image.tar.gz

Please deploy uImage and the dtb to the /boot folder.

# cp uImage boot

# cp  uImage-t2080rdb.dtb boot

Set the environment in uboot for SD boot.

=>setenv bootfile uImage

=> setenv fdtfile uImage-t2080rdb.dtb

=> setenv bootcmd 'setenv bootargs root=/dev/mmcblk0p2 rw rootdelay=5 console=$consoledev,$baudrate;mmcinfo;ext2load mmc 0:2 $loadaddr /boot/$bootfile;ext2load mmc 0:2 $fdtaddr /boot/$fdtfile;bootm $loadaddr - $fdtaddr'

Please refer to other u-boot parameters.

=> pri consoledev

consoledev=ttyS0

=> pri baudrate

baudrate=115200

=> pri loadaddr

loadaddr=1000000

=> pri fdtaddr

fdtaddr=c00000

 Boot up Linux

=> boot


Have a great day,
TIC

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

0 Kudos