Home Forum Software discussion Kernel vanilla

Viewing 5 posts - 46 through 50 (of 50 total)
  • Author
    Posts
  • #8511
    alpha_one_x86
    Participant

    It was due to u boot. u boot vanilla updated, working

    #8512
    nova_robotics
    Participant

    Nice. I’m having the exact same problem. What version u-boot are you on? I just tried updating, but I’m still at 17.10.1.

    #8513
    alpha_one_x86
    Participant

    kernel after correct config:

    make -j4
    make -j4 modules_install
    cp arch/arm64/boot/Image /boot/Image
    cp arch/arm64/boot/dts/marvell/armada-8040-mcbin-singleshot.dtb /boot/armada-8040-mcbin.dtb
    # SFP
    CONFIG_MDIO_I2C
    CONFIG_I2C_MUX
    CONFIG_I2C_MUX_PCA954x
    # Network
    CONFIG_MARVELL_PHY
    CONFIG_MARVELL_10G_PHY
    CONFIG_MVMDIO
    CONFIG_OF_MDIO
    CONFIG_PHY_MVEBU_CP110_COMPHY
    CONFIG_MVPP2
    CONFIG_MVPP2X
    CONFIG_SFP
    CONFIG_MARVELL_10G
    # SATA
    CONFIG_SATA_MV
    #8514
    alpha_one_x86
    Participant

    Armada 8040 U-Boot and ATF


    U-Boot v2020.01
    boot.txt:

    setenv bootargs "root=/dev/mmcblk1p2 rootwait rw no_console_suspend fsck.repair=yes net.ifnames=0"
    setenv loadaddr "0x12000000"
    setenv dtb_loadaddr "0x2000000"
    ext2load mmc 1:2 ${loadaddr} boot/Image
    ext2load mmc 1:2 ${dtb_loadaddr} boot/armada-8040-mcbin.dtb
    fdt addr ${dtb_loadaddr}
    booti ${loadaddr} - ${dtb_loadaddr}

    And few tweek:
    mkimage -A arm64 -T script -O linux -d boot.txt boot.scr
    parted /dev/sdX set 2 boot on

    #180807
    Torxed
    Participant

    First of all, thank you alpha one for taking your time to fix this.
    This was oddly confusing and to some extent very undocumented.

    I’ve even e-mailed MacchiatoBin and SolidRun to verify that the card I was buying was supported by the kernel.
    Which I guess, it *kinda* is to some extent, but no one ever mentioned that you’d have to have a custom kernel/device tree to get this to work.

    For what it’s worth, Arch Linux ARM users who end up here using MACCHIATObin Single Shot:
    There is a single-shot driver shipped with the OS, all you need to do is..

    Rename /boot/dtbs/marvel/armada-8040-mcbin-singleshot.dtb to /boot/dtbs/marvel/armada-8040-mcbin.dtb and reboot.

    Without this change in dtb driver, you will get:

    mvpp2 f4000000.ethernet eth0: could not attach PHY (-19)
    RTNETLINK answers: No such device

    Whenever you try to access or administrate the interfaces.

Viewing 5 posts - 46 through 50 (of 50 total)
  • You must be logged in to reply to this topic.

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