Layerscape中的主题 How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tafthorne — Mon, 22 Aug 2016 13:07:37 GMT

I have recently received a LS1021ATWR module and downloaded the QorIQ SDK V2.0 Yocto image of 2016-05-27 from the support pages. I have installed the SDK and used it to generate an fsl-image-full for the ls1021atwr target. When I try to boot from an SD card using these binaries the system seems to halt or freeze after the 'Starting kernel ...' message is displayed. How should I be attempting to boot, using binaries generated from the SDK, loaded onto an SDHC card?

I can see a series of files (mostly symlinks) in my images directory:

~/QorIQ-SDK-V2.0-20160527-yocto/build_ls1021atwr$ ls tmp/deploy/images/ls1021atwr/

fsl-image-full-ls1021atwr-20160822111052.rootfs.manifest u-boot-sdcard-qspi-2016.01+fslgit-r0.bin

fsl-image-full-ls1021atwr-20160822111052.rootfs.tar.gz u-boot-sdcard-qspi.bin

fsl-image-full-ls1021atwr-20160822112706.rootfs.manifest u-boot-secure-boot-2016.01+fslgit-r0.bin

fsl-image-full-ls1021atwr-20160822112706.rootfs.tar.gz u-boot-secure-boot.bin

fsl-image-full-ls1021atwr.manifest uImage

fsl-image-full-ls1021atwr.tar.gz uImage--4.1-r0-ls1021atwr-20160815152334.bin

modules--4.1-r0-ls1021atwr-20160815152334.tgz uImage--4.1-r0-ls1021a-twr-20160815152334.dtb

modules--4.1-r0-ls1021atwr-20160818140007.tgz uImage--4.1-r0-ls1021atwr-20160818140007.bin

modules--4.1-r0-ls1021atwr-20160818142615.tgz uImage--4.1-r0-ls1021a-twr-20160818140007.dtb

modules--4.1-r0-ls1021atwr-20160818145023.tgz uImage--4.1-r0-ls1021atwr-20160818142615.bin

modules-ls1021atwr.tgz uImage--4.1-r0-ls1021a-twr-20160818142615.dtb

README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt uImage--4.1-r0-ls1021atwr-20160818145023.bin

u-boot.bin uImage--4.1-r0-ls1021a-twr-20160818145023.dtb

u-boot-lpuart-2016.01+fslgit-r0.bin uImage-ls1021atwr.bin

u-boot-lpuart.bin uImage-ls1021a-twr.dtb

u-boot-ls1021atwr.bin zImage

u-boot-nor-2016.01+fslgit-r0.bin zImage--4.1-r0-ls1021atwr-20160815152334.bin

u-boot-nor.bin zImage--4.1-r0-ls1021atwr-20160818140007.bin

u-boot-qspi-2016.01+fslgit-r0.bin zImage--4.1-r0-ls1021atwr-20160818142615.bin

u-boot-qspi.bin zImage--4.1-r0-ls1021atwr-20160818145023.bin

u-boot-sdcard-ifc-2016.01+fslgit-r0.bin zImage-ls1021atwr.bin

u-boot-sdcard-ifc.bin

Following the instructions found in the QorIQ SDK 2.0 Documentation - Software Deployment Guides > Boardss > LS1024TWRA > Deployment > SD Deployment section I; formatted an SD card, created two partitions on it, extracted the root filesystem onto it, coped the uImage-ls1021atwr.bin to /boot/uImage and the uImage-ls1021a-twr.dtb to /boot/uImage.dtb. Then I synch'ed and unmounted the SD card and placed it in the tower board.

I powered on the board and watched u-boot come up, interrupting it by pressing a key at the prompt. As per the previously mentioned instructions I then updated a series of environment variables for u-boot:

# setenv bootfile uImage

# setenv fdtfile uImage.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'

# save

To me they looked suitable for a two partition SD card. The names match what has been put in place. All should be as instructed.

Why then do I not get any further than the "Starting kernel ..." message when I boot? Are there any diagnostic steps I can undertake to try and work out where things have gone wonky?

The full boot message and environment variables follows:

Boot Output

U-Boot 2015.01+ls1+g3281947 (Jul 30 2015 - 20:01:52)

CPU: Freescale LayerScape LS1021E, Version: 2.0, (0x87081120)

Clock Configuration:

CPU0(ARMV7):1000 MHz,

Bus:300 MHz, DDR:800 MHz (1600 MT/s data rate),

Reset Configuration Word (RCW):

00000000: 0608000a 00000000 00000000 00000000

00000010: 70000000 00007900 e0025a00 21046000

00000020: 00000000 00000000 00000000 20000000

00000030: 00080000 881b7340 00000000 00000000

Board: LS1021ATWR

CPLD: V2.0

PCBA: V1.0

VBank: 0

I2C: ready

DRAM: 1 GiB

Using SERDES1 Protocol: 112 (0x70)

Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0

QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1

Flash: 128 MiB

MMC: FSL_SDHC: 0

EEPROM: NXID v1

PCIe1: Root Complex no link, regs @ 0x3400000

PCIe2: Root Complex no link, regs @ 0x3500000

In: serial

Out: serial

Err: serial

SEC0: RNG instantiated

SATA link 0 timeout.

AHCI 0001.0300 1 slots 1 ports ? Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc

scanning bus for devices...

Found 0 device(s).

SCSI: Net: eTSEC2 is in sgmii mode.

eTSEC1, eTSEC2, eTSEC3 [PRIME]

Hit any key to stop autoboot: 0

=> setenv bootfile uImage

=> setenv fdtfile uImage.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'

=> save

Saving Environment to Flash...

Un-Protected 1 sectors

Erasing Flash...

. done

Erased 1 sectors

Writing to Flash... 9....8....7....6....5....4....3....2....1....done

Protected 1 sectors

=> save

Saving Environment to Flash...

Un-Protected 1 sectors

Erasing Flash...

. done

Erased 1 sectors

Writing to Flash... 9....8....7....6....5....4....3....2....1....done

Protected 1 sectors

=> boot

Device: FSL_SDHC

Manufacturer ID: 89

OEM: 502

Name: NCard

Tran Speed: 50000000

Rd Block Len: 512

SD version 2.0

High Capacity: No

Capacity: 1.8 GiB

Bus Width: 4-bit

Erase Group Size: 512 Bytes

3511256 bytes read in 266 ms (12.6 MiB/s)

21610 bytes read in 99 ms (212.9 KiB/s)

## Booting kernel from Legacy Image at 82000000 ...

Image Name: Linux-4.1.8-rt8+gbd51baf

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 3511192 Bytes = 3.3 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

## Flattened Device Tree blob at 8f000000

Booting using the fdt blob at 0x8f000000

Loading Kernel Image ... OK

Loading Device Tree to bef1b000, end bef23469 ... OK

Starting kernel ...

Environment Variables

=> printenv

baudrate=115200

bootargs=root=/dev/mmcblk0p1 rw rootdelay=5 console=,115200

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

bootcmd_ori=cp.b 60300000 82000000 700000;cp.b 60a00000 88000000 2000000; cp.b 60200000 8f000000 10000;bootm 82000000 88000000 8f000000;

bootcmdsd=setenv bootargs root=/dev/mmcblk0p1 rw rootdelay=5 console=$consoledev,$baudrate;mmcinfo;ext2load mmc 0:1 $loadaddr /boot/$bootfile;ext2load mmc 0:1 $fdtaddr /boot/$fdtfile;bootm $loadaddr - $fdtaddr

bootdelay=3

bootfile=uImage

dnsip=10.192.130.201

eth1addr=00:04:9f:03:e1:26

eth2addr=00:04:9f:03:e1:27

ethact=eTSEC3

ethaddr=00:04:9f:03:e1:25

ethprime=eTSEC3

fdt_high=0xcfffffff

fdtaddr=8f000000

fdtfile=uImage.dtb

gatewayip=10.193.20.254

initrd_high=0xcfffffff

ipaddr=10.193.20.191

loadaddr=82000000

netmask=255.255.255.0

scsidevs=0

serverip=10.192.208.233

stderr=serial

stdin=serial

stdout=serial

Environment size: 1085/131068 bytes

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tafthorne — Tue, 23 Aug 2016 16:13:40 GMT

I tried the SDK above so I thought I would give a couple of other things a go.

I tried basing things off of Yocto Krogoth v2.0 and adding the fsl layer. Same result.
I tried basing things off of Yocto Fido v1.8 and adding the fsl layer. Same results.
I tried firing up a VM image that Avnet had given us training on, taking the files from their and using those. Almost the same result, I had an extra line about Uncompressing kernel after the "Starting kernel ..." one but it never gets any further.

I must be doing something wrong at a basic level. I wondered if my SD card reader/writer was iffy but I have just setup booting over NFS using the krogoth files and have seen the same result.

Is there something I need to modify after getting the SDK or Yocto files?

Are there multiple revisions on the Tower board that need slightly different images?

Just to keep the record complete, here are the variables from my NFS booting:

=> printenv

baudrate=115200

bootargs=root=/dev/nfs rw nfsroot=192.168.0.10:/nfsroot console=,115200

bootcmd_ori=cp.b 60300000 82000000 700000;cp.b 60a00000 88000000 2000000; cp.b 60200000 8f000000 10000;bootm 82000000 88000000 8f000000;

bootdelay=3

bootfile=uImage

dnsip=10.192.130.201

eth1addr=00:04:9f:03:e1:26

eth2addr=00:04:9f:03:e1:27

ethact=eTSEC3

ethaddr=00:04:9f:03:e1:25

ethprime=eTSEC3

fdt_addr=8f000000

fdt_file=uImage-ls1021a-twr.dtb

fdt_file e=uImage-ls1021a-twr.dtb

fdt_high=0xcfffffff

fdtaddr=8f000000

fdtfile=uImage.dtb

fileaddr=8f000000

filesize=5206

gatewayip=192.168.0.10

image=uImage-ls1021atwr.bin

initrd_high=0xcfffffff

ip_dyn=no

ipaddr=192.168.0.100

loadaddr=82000000

netargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${nfsroot} ip=${ipaddr}:${serveripaddr}:${gatewayip}:${netmask}:fred:eth0:off console=$consoledev,$baudrate $othbootargs

netboot=run netargs;tftp ${loadaddr} ${image};tftp ${fdtaddr} ${fdt_file};bootm ${loadaddr} - ${fdtaddr}

netmask=255.255.255.0

nfsroot=/nfsroot

scsidevs=0

serverip=192.168.0.10

stderr=serial

stdin=serial

stdout=serial

Environment size: 1572/131068 bytes

My serial output from power on to netbooting with an NFS root filesystem is:

U-Boot 2015.01+ls1+g3281947 (Jul 30 2015 - 20:01:52)

CPU: Freescale LayerScape LS1021E, Version: 2.0, (0x87081120)

Clock Configuration:

CPU0(ARMV7):1000 MHz,

Bus:300 MHz, DDR:800 MHz (1600 MT/s data rate),

Reset Configuration Word (RCW):

00000000: 0608000a 00000000 00000000 00000000

00000010: 70000000 00007900 e0025a00 21046000

00000020: 00000000 00000000 00000000 20000000

00000030: 00080000 881b7340 00000000 00000000

Board: LS1021ATWR

CPLD: V2.0

PCBA: V1.0

VBank: 0

I2C: ready

DRAM: 1 GiB

Using SERDES1 Protocol: 112 (0x70)

Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0

QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1

Flash: 128 MiB

MMC: FSL_SDHC: 0

EEPROM: NXID v1

PCIe1: Root Complex no link, regs @ 0x3400000

PCIe2: Root Complex no link, regs @ 0x3500000

In: serial

Out: serial

Err: serial

SEC0: RNG instantiated

SATA link 0 timeout.

AHCI 0001.0300 1 slots 1 ports ? Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc

scanning bus for devices...

Found 0 device(s).

SCSI: Net: eTSEC2 is in sgmii mode.

eTSEC1, eTSEC2, eTSEC3 [PRIME]

Hit any key to stop autoboot: 0

=> run netboot

Speed: 1000, full duplex

Using eTSEC3 device

TFTP from server 192.168.0.10; our IP address is 192.168.0.100

Filename 'uImage-ls1021atwr.bin'.

Load address: 0x82000000

Loading: T #################################################################

#################################################################

###############

541 KiB/s

done

Bytes transferred = 3082104 (2f0778 hex)

Speed: 1000, full duplex

Using eTSEC3 device

TFTP from server 192.168.0.10; our IP address is 192.168.0.100

Filename 'uImage-ls1021a-twr.dtb'.

Load address: 0x8f000000

Loading: ##

4 MiB/s

done

Bytes transferred = 20998 (5206 hex)

## Booting kernel from Legacy Image at 82000000 ...

Image Name: Linux-3.12.37-rt51+ls1+gf488de6

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 3082040 Bytes = 2.9 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

## Flattened Device Tree blob at 8f000000

Booting using the fdt blob at 0x8f000000

Loading Kernel Image ... OK

Loading Device Tree to bef1b000, end bef23205 ... OK

Starting kernel ...

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tony_f123 — Fri, 26 Aug 2016 02:46:07 GMT

Hi Thomas,

Looks like you don't have a "console" bootarg set, which would be one reason why you are not seeing any Linux kernel boot messages.

According to your U-Boot env dump, by running 'run netboot' in U-Boot, the first thing this does is 'run netargs', and netargs blows away your current bootargs and is not setting a console bootarg (and your SD boot isn't correctly setting the console bootarg either). To fix network boot, you'll want to add a console= bootarg to the 'netargs' env variable, eg, in U-Boot, 'setenv netargs $netargs console=ttyS0,115200; saveenv'. Then try running 'run netboot' again.

Also, in case you didn't know, you can change the 'bootcmd' env variable to 'run netboot' so you don't need to stop U-Boot during the countdown timer every time you want to boot.

-Tony

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tafthorne — Fri, 26 Aug 2016 07:48:35 GMT

Thank you Tony. That solved my issue! I knew I had to be missing something to be getting such a consistent result.

I did "setenv consoledev ttyS0" and that got things to come up with Linux boot output. It did all fall over again a short while later but at least I have Liunx starting and some output to work with.

Once again thank you for your help.

Here is the boot message I finally got:

=> run netboot
Speed: 1000, full duplex
Using eTSEC3 device
TFTP from server 192.168.0.10; our IP address is 192.168.0.100
Filename 'uImage-ls1021atwr.bin'.
Load address: 0x82000000
Loading: #################################################################
#################################################################
#################################################################
###################################################
3.7 MiB/s
done
Bytes transferred = 3604656 (3700b0 hex)
Speed: 1000, full duplex
Using eTSEC3 device
TFTP from server 192.168.0.10; our IP address is 192.168.0.100
Filename 'uImage-ls1021a-twr.dtb'.
Load address: 0x8f000000
Loading: ##
1.9 MiB/s
done
Bytes transferred = 21873 (5571 hex)
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.12.37-rt51+ls1+gaaa395f
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3604592 Bytes = 3.4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 8f000000
Booting using the fdt blob at 0x8f000000
Loading Kernel Image ... OK
Loading Device Tree to bef1b000, end bef23570 ... OK

Starting kernel ...

Booting Linux on physical CPU 0xf00
Linux version 3.12.37-rt51+ls1+gaaa395f (legend@mcore0) (gcc version 4.8.3 20140401 (prerelease) (Linaro GCC 4.8-2014.04) ) #5 SMP Thu Aug 13 14:14:22 CST 2015
CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=70c73c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale LS1021A, model: LS1021A TWR Board
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 8 pages/cpu @80e44000 s8640 r8192 d15936 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096
Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.10:/nfsroot ip=192.168.0.100::192.168.0.10:255.255.255.0:fred:eth0:off console=ttyS0,115200
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1033076K/1048576K available (3780K kernel code, 278K rwdata, 1868K rodata, 188K init, 198K bss, 15500K reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xc0800000 - 0xff000000 (1000 MB)
lowmem : 0x80000000 - 0xc0000000 (1024 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f800000 - 0x7fe00000 ( 6 MB)
.text : 0x80008000 - 0x8058c384 (5649 kB)
.init : 0x8058d000 - 0x805bc1c0 ( 189 kB)
.data : 0x805be000 - 0x806038b8 ( 279 kB)
.bss : 0x806038c0 - 0x806354b4 ( 199 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
NR_IRQS:16 nr_irqs:16 16
Architected cp15 timer(s) running at 12.50MHz (phys).
Switching to timer-based delay loop
sched_clock: ARM arch timer >56 bits at 12500kHz, resolution 80ns
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 25.00 BogoMIPS (lpj=125000)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: update cpu_power 1024
CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
Setting up static identity map for 0x8038a298 - 0x8038a2fc
CPU1: Booted secondary processor
CPU1: update cpu_power 1024
CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
Brought up 2 CPUs
SMP: Total of 2 processors activated (50.00 BogoMIPS).
CPU: All CPU(s) started in HYP mode.
CPU: Virtualization extensions available.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
syscon 1570000.scfg: regmap [mem 0x01570000-0x0157ffff] registered
irq: no irq domain found for /soc/uqe@2400000/qeic@80 !
irq: no irq domain found for /soc/uqe@2400000/qeic@80 !
hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 8 bytes.
bio: create slab <bio-0> at 0
3P3V: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c i2c-0: IMX I2C adapter registered
i2c i2c-1: IMX I2C adapter registered
i2c i2c-2: of_i2c: modalias failure on /soc/i2c@21a0000/ltc2945@67
i2c i2c-2: IMX I2C adapter registered
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
fsl-ifc 1530000.ifc: Freescale Integrated Flash Controller
Advanced Linux Sound Architecture Driver Initialized.
Switched to clocksource arch_sys_counter
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A7 PMU driver, 5 counters available
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 2017
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
layerscape-pcie 3400000.pcie: phy link never came up
layerscape-pcie 3400000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x1000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x4040000000-0x407fffffff] (bus address [0x40000000-0x7fffffff])
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:00.0: BAR 1: assigned [mem 0x4040000000-0x4043ffffff]
pci 0000:00:00.0: BAR 0: assigned [mem 0x4044000000-0x4044ffffff]
pci 0000:00:00.0: BAR 6: assigned [mem 0x4045000000-0x4045ffffff pref]
pci 0000:00:00.0: PCI bridge to [bus 01]
layerscape-pcie 3500000.pcie: phy link never came up
layerscape-pcie 3500000.pcie: PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [io 0x10000-0x1ffff] (bus address [0x0000-0xffff])
pci_bus 0001:00: root bus resource [mem 0x4840000000-0x487fffffff] (bus address [0x40000000-0x7fffffff])
pci_bus 0001:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0001:00:00.0: BAR 1: assigned [mem 0x4840000000-0x4843ffffff]
pci 0001:00:00.0: BAR 0: assigned [mem 0x4844000000-0x4844ffffff]
pci 0001:00:00.0: BAR 6: assigned [mem 0x4845000000-0x4845ffffff pref]
pci 0001:00:00.0: PCI bridge to [bus 01]
sii902x: probe of 1-0039 failed with error -1
syscon 1570000.scfg: Failed to create debugfs directory
Console: switching to colour frame buffer device 60x34
fb0: fb device registered successfully.
fb1: fb device registered successfully.
fb2: fb device registered successfully.
fb3: fb device registered successfully.
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
21c0500.serial: ttyS0 at MMIO 0x21c0500 (irq = 118, base_baud = 9375000) is a 16550A_FSL64
console [ttyS0] enabled
21c0600.serial: ttyS1 at MMIO 0x21c0600 (irq = 118, base_baud = 9375000) is a 16550A_FSL64
of_serial 2402200.ucc: clk or clock-frequency not defined
of_serial: probe of 2402200.ucc failed with error -2
serial: Freescale lpuart driver
2950000.serial: ttyLP0 at MMIO 0x2950000 (irq = 112, base_baud = 6250000) is a FSL_LPUART
brd: module loaded
loop: module loaded
ahci 3200000.sata: AHCI 0001.0300 1 slots 1 ports ? Gbps 0x1 impl platform mode
ahci 3200000.sata: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc
ahci 3200000.sata: port 0 is not capable of FBS
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x03200000-0x0320ffff] port 0x100 irq 133
60000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00227e
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
10 ofpart partitions found on MTD device 60000000.nor
Creating 10 MTD partitions on "60000000.nor":
0x000000000000-0x000000020000 : "NOR bank0 RCW Image"
0x000000100000-0x000000200000 : "NOR bank0 u-boot Image"
0x000000200000-0x000000300000 : "NOR bank0 DTB Image"
0x000000300000-0x000000a00000 : "NOR bank0 Linux Kernel Image"
0x000000a00000-0x000004000000 : "NOR bank0 Ramdisk Root File System Image"
0x000004000000-0x000004020000 : "NOR bank4 RCW Image"
0x000004100000-0x000004200000 : "NOR bank4 u-boot Image"
0x000004200000-0x000004300000 : "NOR bank4 DTB Image"
0x000004300000-0x000004a00000 : "NOR bank4 Linux Kernel Image"
0x000004a00000-0x000008000000 : "NOR bank4 Ramdisk Root File System Image"
m25p80 spi0.0: found mr25h256, expected m25p80
m25p80 spi0.0: mr25h256 (32 Kbytes)
6Freescale DSPI master initialized
CAN device driver interface
flexcan 2a70000.can: device registered (reg_base=c0836000, irq=158)
flexcan 2a80000.can: device registered (reg_base=c0838000, irq=159)
libphy: Freescale PowerQUICC MII Bus: probed
fsl-gianfar ethernet.4: enabled errata workarounds, flags: 0x4
fsl-gianfar ethernet.4 eth0: mac: 00:04:9f:03:e1:25
fsl-gianfar ethernet.4 eth0: Running with NAPI enabled
fsl-gianfar ethernet.4 eth0: RX BD ring size for Q[0]: 256
fsl-gianfar ethernet.4 eth0: RX BD ring size for Q[1]: 256
fsl-gianfar ethernet.4 eth0: TX BD ring size for Q[0]: 256
fsl-gianfar ethernet.4 eth0: TX BD ring size for Q[1]: 256
fsl-gianfar ethernet.5: enabled errata workarounds, flags: 0x4
fsl-gianfar ethernet.5 eth1: mac: 00:04:9f:03:e1:26
fsl-gianfar ethernet.5 eth1: Running with NAPI enabled
fsl-gianfar ethernet.5 eth1: RX BD ring size for Q[0]: 256
fsl-gianfar ethernet.5 eth1: RX BD ring size for Q[1]: 256
fsl-gianfar ethernet.5 eth1: TX BD ring size for Q[0]: 256
fsl-gianfar ethernet.5 eth1: TX BD ring size for Q[1]: 256
fsl-gianfar ethernet.6: enabled errata workarounds, flags: 0x4
fsl-gianfar ethernet.6 eth2: mac: 00:04:9f:03:e1:27
fsl-gianfar ethernet.6 eth2: Running with NAPI enabled
fsl-gianfar ethernet.6 eth2: RX BD ring size for Q[0]: 256
fsl-gianfar ethernet.6 eth2: RX BD ring size for Q[1]: 256
fsl-gianfar ethernet.6 eth2: TX BD ring size for Q[0]: 256
fsl-gianfar ethernet.6 eth2: TX BD ring size for Q[1]: 256
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
ata1: SATA link down (SStatus 0 SControl 300)
xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
xhci-hcd xhci-hcd.0.auto: irq 125, io mem 0x03100000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
ina2xx 0-0040: power monitor ina220 (Rshunt = 1000 uOhm)
ina2xx 0-0041: power monitor ina220 (Rshunt = 1000 uOhm)
imx2-wdt 2ad0000.wdog: timeout 60 sec (nowayout=0)
qoriq_cpufreq: Freescale PowerPC qoriq CPU frequency scaling driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: no vqmmc regulator found
mmc0: no vmmc regulator found
mmc0: SDHCI controller on 1560000.esdhc [1560000.esdhc] using ADMA
caam 1700000.crypto: Instantiated RNG4 SH1
caam 1700000.crypto: device ID = 0x0a14030000000000 (Era 7)
caam 1700000.crypto: job rings = 4, qi = 0
caam algorithms registered in /proc/crypto
caam_jr 1710000.jr: registering rng-caam
caam 1700000.crypto: fsl,sec-v5.3 algorithms registered in /proc/crypto
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sgtl5000 1-000a: sgtl5000 revision 0x11
sgtl5000 1-000a: Failed to get supply 'VDDD': -19
1-000a: 1200 mV normal
sgtl5000 1-000a: Using internal LDO instead of VDDD
vf610-sgtl5000 sound.9: sgtl5000 <-> 2b50000.sai mapping ok
oprofile: using timer interrupt.
nf_conntrack version 0.5.0 (16141 buckets, 64564 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Bridge firewalling registered
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
regulator-dummy: disabling
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
usb 1-1: new high-speed USB device number 2 using xhci-hcd
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
usb 2-1: Parent hub missing LPM exit latency info. Power management will be impacted.
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
Waiting up to 110 more seconds for network.
Waiting up to 100 more seconds for network.
Waiting up to 90 more seconds for network.
Waiting up to 80 more seconds for network.
Waiting up to 70 more seconds for network.
Waiting up to 60 more seconds for network.
Waiting up to 50 more seconds for network.
Waiting up to 40 more seconds for network.
Waiting up to 30 more seconds for network.
Waiting up to 20 more seconds for network.
Waiting up to 10 more seconds for network.
Waiting up to 0 more seconds for network.
IP-Config: Complete:
device=eth0, hwaddr=00:04:9f:03:e1:25, ipaddr=192.168.0.100, mask=255.255.255.0, gw=192.168.0.10
host=fred, domain=, nis-domain=(none)
bootserver=255.255.255.255, rootserver=192.168.0.10, rootpath=
ALSA device list:
#0: FSL-VF610-TWR-BOARD
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
1f00 128 mtdblock0 (driver?)
1f01 1024 mtdblock1 (driver?)
1f02 1024 mtdblock2 (driver?)
1f03 7168 mtdblock3 (driver?)
1f04 55296 mtdblock4 (driver?)
1f05 128 mtdblock5 (driver?)
1f06 1024 mtdblock6 (driver?)
1f07 1024 mtdblock7 (driver?)
1f08 7168 mtdblock8 (driver?)
1f09 55296 mtdblock9 (driver?)
1f0a 32 mtdblock10 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.37-rt51+ls1+gaaa395f #5
[<800107c9>] (unwind_backtrace+0x1/0x88) from [<8000e4e7>] (show_stack+0xb/0xc)
[<8000e4e7>] (show_stack+0xb/0xc) from [<8038397d>] (dump_stack+0x4d/0x60)
[<8038397d>] (dump_stack+0x4d/0x60) from [<80381405>] (panic+0x55/0x144)
[<80381405>] (panic+0x55/0x144) from [<8058dbfb>] (mount_block_root+0x12b/0x168)
[<8058dbfb>] (mount_block_root+0x12b/0x168) from [<8058dd63>] (mount_root+0x87/0xa8)
[<8058dd63>] (mount_root+0x87/0xa8) from [<8058de45>] (prepare_namespace+0xc1/0x114)
[<8058de45>] (prepare_namespace+0xc1/0x114) from [<8058d979>] (kernel_init_freeable+0x109/0x150)
[<8058d979>] (kernel_init_freeable+0x109/0x150) from [<8037f617>] (kernel_init+0x7/0x90)
[<8037f617>] (kernel_init+0x7/0x90) from [<8000c1f9>] (ret_from_fork+0x11/0x38)
CPU1: stopping
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.12.37-rt51+ls1+gaaa395f #5
[<800107c9>] (unwind_backtrace+0x1/0x88) from [<8000e4e7>] (show_stack+0xb/0xc)
[<8000e4e7>] (show_stack+0xb/0xc) from [<8038397d>] (dump_stack+0x4d/0x60)
[<8038397d>] (dump_stack+0x4d/0x60) from [<8000fec3>] (handle_IPI+0x7f/0xd0)
[<8000fec3>] (handle_IPI+0x7f/0xd0) from [<800083ef>] (gic_handle_irq+0x3b/0x44)
[<800083ef>] (gic_handle_irq+0x3b/0x44) from [<8038795b>] (__irq_svc+0x3b/0x5c)
Exception stack(0xbf89bfa0 to 0xbf89bfe8)
bfa0: ffffffed 00000000 00892000 00000000 bf89a000 bf89a010 80000000 80603bd4
bfc0: 80003010 410fc075 00000000 00000000 00000008 bf89bfe8 8000cc01 8000cc02
bfe0: 60000133 ffffffff
[<8038795b>] (__irq_svc+0x3b/0x5c) from [<8000cc02>] (arch_cpu_idle+0x1a/0x20)
[<8000cc02>] (arch_cpu_idle+0x1a/0x20) from [<8003b765>] (cpu_startup_entry+0x7d/0xc4)
[<8003b765>] (cpu_startup_entry+0x7d/0xc4) from [<80008485>] (__enable_mmu+0x1/0x1c)

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tafthorne — Fri, 26 Aug 2016 07:59:00 GMT

I would also like to thank Zhenhua Luo for replying to my question on the meta-freescale yoctoproject mailing list last night with a similar suggestion. (I guess this may be the same person as zhenhualuo‌ )
https://lists.yoctoproject.org/pipermail/meta-freescale/2016-August/018995.html

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tony_f123 — Tue, 30 Aug 2016 22:33:41 GMT

Hey Thomas,

Glad to hear that worked.

The next error you are seeing is another common one - the Linux kernel is unable the mount the root filesystem. There's either a networking error or an issue between nfs client/server communication, because it looks like the target obtains an IP, but is unable the mount the NFS. Instead of setting a static IP and an nfsroot in the kernel commandline, I usually set ip=dhcp and no nfsroot (this info can be obtained from the DHCP server instead) for NFS boot. You could also try SD boot if that is available to you (set 'root=/dev/mmcblk0pX rw rootwait' in your bootargs, change X to the correct partition number).

-Tony

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

tafthorne — Wed, 31 Aug 2016 15:44:55 GMT

I am pleased to report that using the latest community BSP I have been able to get an LS1021A-TWR-PB to boot and provide a login prompt.

Poky (Yocto Project Reference Distro) 2.1.1 ls1021atwr /dev/ttyS0

ls1021atwr login: root

root@ls1021atwr:~#

root@ls1021atwr:~# uname -a

Linux ls1021atwr 3.12.37-rt51+ls1+gf488de6 #1 SMP Wed Aug 31 13:13:11 BST 2016 armv7l armv7l armv7l GNU/Linux

My original problem was an issue with the command I had saves as an environment variable in u-boot. Once that was corrected things started to work much better. My next hiccup was trying to do an NFS boot when the kernel does not seem to like starting with a static IP address. Now I am up and rolling using an SD card for the root filesystem, the IP stack is at least working for a local loopback ping.

Re: How do I boot a LS1021A-TWR from an SD card using the binaries generated by the 2.0 SDK?

muhammadumairkh — Thu, 16 Mar 2017 05:41:08 GMT

Hi Tony,

I have a similar issue. I mistakenly executed following commands on U-boot prompt.

=> setenv video-mode "fslfb:640x480-32@60,monitor=hdmi"
=> save
=> reset

After the save command was executed, following messages appeared:

Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... 9....8....7....6....5....4....3....2....1....done
Protected 1 sectors

Now, the U-boot prompt has disappeared and default output mode has switched to VGA. Following are U-boot boot messages now:

U-Boot 2015.01+ls1+g6ba8eed (Dec 31 2015 - 13:06:21)

CPU: Freescale LayerScape LS1021E, Version: 1.0, (0x87081110)
Clock Configuration:
CPU0(ARMV7):1000 MHz,
Bus:300 MHz, DDR:800 MHz (1600 MT/s data rate),
Reset Configuration Word (RCW):
00000000: 0608000a 00000000 00000000 00000000
00000010: 70000000 00007900 e0025a00 21046000
00000020: 00000000 00000000 00000000 00038000
00000030: 00080000 48007340 00000000 00000000
Board: LS1021ATWR
CPLD: V2.3
PCBA: V4.0
VBank: 0
I2C: ready
DRAM: 1 GiB
Using SERDES1 Protocol: 112 (0x70)
Not a microcode
Flash: 128 MiB
MMC: FSL_SDHC: 0
EEPROM: CRC mismatch (4cb0a600 != ffffffff)
PCIe1: Root Complex no link, regs @ 0x3400000
PCIe2: Root Complex no link, regs @ 0x3500000
DCU: Switching to HDMI monitor @ 640x480
In: serial
Out: vga
Err: vga

Is there any command to set output view to console again?

Thanks in advance,

Umair