Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • in reply to: Kernel vanilla #7356
    hchenji
    Participant

    Can you share your .config for linux-arm and also uboot printenv output if possible? I cannot figure out why my build doesn’t boot.

    in reply to: Kernel vanilla #7354
    hchenji
    Participant

    I cannot boot linux-arm mcbin branch. Any idea what’s wrong??

    
    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 [PRIME], eth1: mvpp2-3, eth2: mvpp2-4, eth3: mvpp2-5
    Hit any key to stop autoboot:  0 
    switch to partitions #0, OK
    mmc1 is current device
    14383616 bytes read in 13932 ms (1007.8 KiB/s)
    32173 bytes read in 9 ms (3.4 MiB/s)
    ## Flattened Device Tree blob at 06f00000
       Booting using the fdt blob at 0x6f00000
       Using Device Tree in place at 0000000006f00000, end 0000000006f0adac
    
    Starting kernel ...
    
    
    in reply to: Kernel vanilla #7353
    hchenji
    Participant

    Have you tried with mcbin branch of Russell King’s linux-arm repo? Lots of changes in the last week: http://git.armlinux.org.uk/cgit/linux-arm.git/log/?h=mcbin

    in reply to: Kernel vanilla #7351
    hchenji
    Participant

    I don’t think you should pay them anything to get the SFP+ to work. Since the board was advertised as having 2 SFP+ ports, it is expected that they supply customers with correct working BSP that lets them use the SFP+ ports in all modes.

    Unless they are paying you to solve the problem by writing code, do not pay them anything!

    in reply to: Kernel vanilla #7348
    hchenji
    Participant

    Looks like @alpha_one_x86 has tried: https://bugzilla.kernel.org/show_bug.cgi?id=201563 .

    Are Solidrun/Marvell even attempting to get this figured out???

    in reply to: cannot boot linux-4.14.22-armada-18.09 #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??

    in reply to: Compatible SFP #6851
    hchenji
    Participant

    That’s very promising. Could I know what version/branch of the marvell kernel you used? Could you post the .config? What version of u-boot did you use? Is this a double shot or a single shot board?

    in reply to: Kernel vanilla #6843
    hchenji
    Participant

    Can you please send me your .config if you got it to boot?

    Also, try the latest .18-RC5, it has SFP cage support. marvell linux just hardcodes the phy bit rate.

    https://patchwork.kernel.org/patch/10380619/

    in reply to: Compatible SFP #6842
    hchenji
    Participant

    eth3 port seems to be hardcoded at 2.5Gbps in the dts/dtb. overall, SFP support isn’t even present (drivers/net/phy/sfp.c doesn’t exit) in this marvell-linux kernel. Ports are fixed at some rate. Things now depend on how the transceiver is implemented, whether it uses SGMII or some other bus.

    At this rate, might as well ditch marvell-linux and move to mainline. DTS file has support for sfp: https://patchwork.kernel.org/patch/10380619/

    emac3_1: mac3 {
    phy-mode = “1000base-x”; /* lane-5 */
    phy-speed = <2500>;
    phys = <&comphy1 5 COMPHY_HS_SGMII2>;
    phy-names = “comphy”;
    };

    in reply to: Compatible SFP #6841
    hchenji
    Participant

    No luck with fs.com BiDi and even CWDM and multi mode SFPs in the 1G slot.

    I suspect the problem is similar to what we had with Clearfog units – there’s a particular kernel version that works fine, others do not. The Armbian distro has some SFP related patches for 4.4 kernels, and this made the clearfogs accept a ton of SFPs. Unfortunately there’s no armbian for clearcloud yet, though the kernel/DTBs should still be available.

    Will try custom kernels and ubuntu on my units.

    in reply to: Compatible SFP #6838
    hchenji
    Participant

    What brand modules are you using? I am unable to get fs.com DWDM 10Gbe SFP+ ones to work, the link keeps flapping between up and down.

    We have some 1G SFPs, will try those and let you know.

Viewing 11 posts - 1 through 11 (of 11 total)

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