Home Forum Software discussion cannot boot linux-4.14.22-armada-18.09

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #7345
    hchenji
    Participant

    Using a double shot board, booting from sd card. Using 18.09 for uboot, marvell-binaries, atf-marvell etc. What is wrong??

    
    Found valid image at boot postion 0x000
    lNOTICE:  Starting binary extension
    NOTICE:  SVC: DEV ID: 8040, FREQ Mode: 0xd
    NOTICE:  SVC: AVS work point changed from 0x28 to 0x28
    mv_ddr: mv_ddr-armada-17.10.5-gf537e1d (Apr 25 2018 - 19:11:27)
    mv_ddr: completed successfully
    NOTICE:  Cold boot
    Error: image checksum verification failed
    Found valid image at boot postion 0x002
    lNOTICE:  Starting binary extension
    NOTICE:  SVC: DEV ID: 8040, FREQ Mode: 0xd
    NOTICE:  SVC: AVS work point changed from 0x28 to 0x28
    mv_ddr: mv_ddr-devel-18.12.0-g618dadd (Jan 22 2019 - 17:13:58)
    mv_ddr: completed successfully
    NOTICE:  Cold boot
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
    NOTICE:  BL1: Built : 17:37:51, Jan 22 2019
    NOTICE:  BL1: Booting BL2
    NOTICE:  BL2: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
    NOTICE:  BL2: Built : 17:37:53, Jan 22 2019
    BL2: Initiating SCP_BL2 transfer to SCP
    NOTICE:  SCP_BL2 contains 2 concatenated images
    NOTICE:  Load image to CP1 MSS AP0
    NOTICE:  Loading MSS image from addr. 0x4023020 Size 0x135c to MSS at 0xf4280000
    NOTICE:  Done
    NOTICE:  Load image to AP0 MSS
    NOTICE:  Loading MSS image from addr. 0x402437c Size 0x1f6c to MSS at 0xf0580000
    N
    
    FreeRTOS 7.3.0 - Marvell cm3 - A8K release armada-18.05.1
    
    OTICE:  Done
    NOTICE:  SCP Image doesn't contain PM firmware
    NOTICE:  BL1: Booting BL31
    lNOTICE:  MSS PM is not supported in this build
    NOTICE:  BL31: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
    NOTICE:  BL31: Built : 17:37:55, Jan 22 2019
    
    U-Boot 2018.03-armada-18.09.1-g8fe4031 (Jan 22 2019 - 17:32:28 -0500)
    
    Model: Marvell Armada 8040 MACCHIATOBin
    SoC: Armada8040-A2; AP806-A1; 2xCP110-A2
    Clock:  CPU     1600 [MHz]
            DDR     1050 [MHz]
            FABRIC  1050 [MHz]
            MSS     200  [MHz]
    LLC Enabled (Exclusive Mode)
    DRAM:  4 GiB
    Comphy chip #0:
    Comphy-0: PEX0
    Comphy-1: PEX0
    Comphy-2: PEX0
    Comphy-3: PEX0
    Comphy-4: SFI0          10.3125 Gbps
    Comphy-5: SATA1
    Comphy chip #1:
    Comphy-0: SGMII1        1.25 Gbps
    Comphy-1: SATA0
    Comphy-2: USB3_HOST0
    Comphy-3: SATA1
    Comphy-4: SFI0          10.3125 Gbps
    Comphy-5: SGMII2        3.125 Gbps
    UTMI PHY 0 initialized to USB Host0
    SATA link 0 timeout.
    SATA link 1 timeout.
    AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
    flags: 64bit ncq led only pmp fbss pio slum part sxs
    PCIE-0: Link down
    MMC:   sdhci@6e0000: 0, sdhci@780000: 1
    Loading Environment from SPI Flash... Bus spi@700680 CS0 configured for direct access 00000000f9000000:0x1000000
    SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB
    OK
    Model: Marvell Armada 8040 MACCHIATOBin
    Net:   eth0: mvpp2-0, eth1: mvpp2-3, eth2: mvpp2-4 [PRIME], eth3: mvpp2-5
    Hit any key to stop autoboot:  0
    switch to partitions #0, OK
    mmc1 is current device
    "Synchronous Abort" handler, esr 0x96000046
    
            Attempt to access RT service or TEE region (addr: 0x5000000, el2)
            Do not use address range 0x4000000-0x5400000
    
    elr: 0000000000029958 lr : 00000000000297d0 (reloc)
    elr: 000000007ff66958 lr : 000000007ff667d0
    x0 : 0000000000000000 x1 : 0000000091005a4d
    x2 : 00000000000f4227 x3 : 0000000005000000
    x4 : 0000000000000001 x5 : 000000000000000d
    x6 : 000000007ffbfca8 x7 : 0000000000000000
    x8 : 000000007ffbfca8 x9 : 0000000000000008
    x10: 000000007f7b8220 x11: 0000000000000001
    x12: 000000007f7b8220 x13: 00000000000626f8
    x14: 000000007f7270b0 x15: 0000000000000002
    x16: 000000007ffbc6c5 x17: 000000007ffab299
    x18: 000000007f72cdd0 x19: 000000007f7b2030
    x20: 0000000000000020 x21: 000000007f726518
    x22: 0000000000000001 x23: 0000000000000000
    x24: 0000000000000000 x25: 0000000000000030
    x26: 00000000000f4227 x27: 000000007ffb4000
    x28: 0000000000000009 x29: 000000007f726450
    
    Resetting CPU ...
    
    resetting ...
    ing from SD 0 (0x29)
    
    #7346
    nanasi
    Participant

    It says:

    
    Do not use address range 0x4000000-0x5400000
    

    My inference:

    Marvell>> printenv kernel_addr_r
    kernel_addr_r=0x5000000
    #7347
    hchenji
    Participant

    That’s right, $kernel_addr was 0x5000000 and $fdt_addr was 0x4f00000 which is within the TEE range. What should be the right values for these variables??

    #7349
    nanasi
    Participant

    Default values are defined in “$UBOOTSRC/include/configs/mvebu_armada-common.h”

    kernel_addr_r=0x7000000
    initrd_addr=0xa00000
    initrd_size=0x2000000
    fdt_addr_r=0x6f00000
    loadaddr=0x6000000
    ramdisk_addr_r=0x8000000

    It is recommended to do “env default -a” after u-boot update.

    Update the Bootloader
    Please under the new U-Boot version, do env default -a to reset all the environment variables, then setup the desired variables again, and do env save to write them to the non-volatile storage.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Technical specification tables can not be displayed on mobile. Please view on desktop