T4240QDS Rev 1 fails boot with SDK V2.0 (works with SDK V1.4)

[juergenwittig]

Hi,

I have a T4240QDS Rev 1 that boots find with the pre-installed SDK V1.4 linux kernel.

U-Boot 2012.10 (Dec 08 2012 - 22:38:39)

 Image Name:   Linux-3.0.51-rt75

See attached file "t4240qds-bootlog-sdkv1.4.txt"

=> bootm e8020000 - e8800000
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at e8020000 ...
   Image Name:   Linux-3.0.51-rt75
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    4287063 Bytes = 4.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at e8800000
   Booting using the fdt blob at 0xe8800000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 03fdc000, end 03fff43f ... OK
Using T4240 QDS machine description
MMU: Supported page sizes

....

But when I download the SDK V2.0 kernel and FDT, u-Boot seems to hang and does not start the kernel

Any help welcome

See attached file

=> bootm 1000000 - 5000000
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-4.1.8-rt8+gbd51baf
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    5099858 Bytes = 4.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 05000000
   Booting using the fdt blob at 0x05000000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 03fdc000, end 03fff5c4 ... OK

Best Regards

Juergen

[Pavel]

Test your board using RAM disk image instead of NFS. See the Section 4.4.19.9.1 Ramdisk Deployment from TFTP of NXP SDK 2.0-1703 documentation:

https://www.nxp.com/docs/en/supporting-information/QORIQ-SDK-2.0-IC-REV0.pdf

Have a great day,
Pavel Chubakov

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

[juergenwittig]

Thank you for your proposal. Unfortunately it still results in the same behaviour.

=> bootm 1000000 5000000 2000000
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-4.1.8-rt8+gbd51baf
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    5099858 Bytes = 4.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 05000000 ...
   Image Name:   fsl-image-core-t4240qds-20160515
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    31801204 Bytes = 30.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Uncompressing Kernel Image ... OK
   Loading Ramdisk to 2e1ac000, end 2fffff74 ... OK
   Loading Device Tree to 03fdc000, end 03fff5c4 ... OK

[juergenwittig]

So I programmed the U-Boot and the fman uode from SDK v2.0 into the altbank. Makes no difference

=> qixis altbanký

U-Boot 2016.012.0+ga9b437f (May 15 2016 - 12:11:12 +0800)

CPU0:  T4240E, Version: 1.0, (0x82480010)
Core:  e6500, Version: 1.0, (0x80400010)
Clock Configuration:
       CPU0:1666.667 MHz, CPU1:1666.667 MHz, CPU2:1666.667 MHz, CPU3:1666.667 MHz,
       CPU4:1666.667 MHz, CPU5:1666.667 MHz, CPU6:1666.667 MHz, CPU7:1666.667 MHz,
       CPU8:1666.667 MHz, CPU9:1666.667 MHz, CPU10:1666.667 MHz, CPU11:1666.667 MHz,
       CCB:666.667 MHz,
       DDR:800  MHz (1600 MT/s data rate) (Asynchronous), IFC:166.667 MHz
       FMAN1: 444.444 MHz
       FMAN2: 333.333 MHz
       QMAN:  333.333 MHz
       PME:   333.333 MHz
L1:    D-cache 32 KiB enabled
       I-cache 32 KiB enabled
Reset Configuration Word (RCW):
       00000000: 14180019 0c101914 00000000 00000000
       00000010: 04383063 30548c00 1c020000 1d000000
       00000020: 00000000 ee0000ee 00000000 000307fc
       00000030: 00000000 00000000 00000000 00000020
I2C:   ready
Board: T4240QDS, Sys ID: 0x1e, Sys Ver: 0x26, vBank: 4
FPGA: v3 (T4240QDS_2012_1113_1114), build 438 on Tue Nov 13 17:14:23 2012
SERDES Reference Clocks: SERDES1=125MHz SERDES2=125MHz SERDES3=100MHz SERDES4=100MHz
SPI:   ready
DRAM:  Initializing....using SPD
Detected UDIMM 9JSF25672AZ-2G1KZ
Detected UDIMM 9JSF25672AZ-2G1KZ
Detected UDIMM 9JSF25672AZ-2G1KZ
4 GiB left unmapped
6 GiB (DDR3, 64-bit, CL=11, ECC on)
       DDR Controller Interleaving Mode: 3-way 4KB
Flash: 128 MiB
L2:    2 MiB enabled
enable l2 for cluster 1 fec60000
enable l2 for cluster 2 feca0000
Corenet Platform Cache: 1.5 MiB enabled
Using SERDES1 Protocol: 1 (0x1)
Using SERDES2 Protocol: 28 (0x1c)
Using SERDES3 Protocol: 6 (0x6)
Using SERDES4 Protocol: 12 (0xc)
SRIO1: enabled
SRIO2: disabled
SEC0: RNG instantiated
NAND:  512 MiB
MMC:   FSL_SDHC: 0
EEPROM: CRC mismatch (3a04a057 != d2dd410b)
PCIe1: Root Complex, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: disabled
PCIe3: Root Complex, no link, regs @ 0xfe260000
PCIe3: Bus 01 - 01
PCIe4: disabled
In:    serial
Out:   serial
Err:   serial
Net:   Fman1: Uploading microcode version 108.4.5
Fman2: Uploading microcode version 108.4.5
FM1@DTSEC5 [PRIME], FM2@DTSEC5
Error: FM2@DTSEC5 address not set.

Hit any key to stop autoboot:  0
=> tftp 1000000 uImage-t4240qds.bin
Using FM1@DTSEC5 device
TFTP from server xxx; our IP address is xxx
Filename 'uImage-t4240qds.bin'.
Load address: 0x1000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################
         2.8 MiB/s
done
Bytes transferred = 5099922 (4dd192 hex)
=> tftp 5000000 uImage-t4240qds.dtb
Using FM1@DTSEC5 device
TFTP from server xxx; our IP address is xxx
Filename 'uImage-t4240qds.dtb'.
Load address: 0x5000000
Loading: ##############
         1.1 MiB/s
done
Bytes transferred = 67013 (105c5 hex)
=> bootm 1000000 - 5000000
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-4.1.8-rt8+gbd51baf
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    5099858 Bytes = 4.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 05000000
   Booting using the fdt blob at 0x5000000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 03fdc000, end 03fff5c4 ... OK

[Pavel]

Replace u-boot on your boar to u-boot from SDK 2.0. Usually similar behavior happens if kernel from different SDK is used.

Have a great day,
Pavel Chubakov

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