Forum Replies Created

Viewing 15 posts - 1 through 15 (of 55 total)
  • Author
    Posts
  • in reply to: Controlling PWM-fan #130319
    nanasi
    Participant
    in reply to: Controlling PWM-fan #127235
    nanasi
    Participant

    Hi,

    It’s my mod. 🙂
    I don’t claim any copyright on my changes.

    Another new patch is here.

    in reply to: How to enable eMMC Command queue #112218
    nanasi
    Participant

    Hi,
    Unfortunately, “Command Queuing” is optional.
    The extcsd from chip(8GME4R) is “Not-supported”.

    # mmc extcsd read /dev/mmcblk0 | grep CMDQ
    Command Queue Support [CMDQ_SUPPORT]: 0x00
    Command Queue Depth [CMDQ_DEPTH]: 1
    Command Enabled [CMDQ_MODE_EN]: 0x00
    # 
    in reply to: Kernel vanilla #8510
    nanasi
    Participant

    Hi,
    Are there any SATA problems other than the warning messages?
    Messages will be suppressed by the patch below.

    diff --git a/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtsi b/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtsi
    index 572e2610e..443e1ed52 100644
    --- a/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtsi
    +++ b/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtsi
    @@ -30,6 +30,22 @@
                    ethernet3 = &cp1_eth2;
            };
    
    +       /* Regulator labels for sata supply */
    +       v_sata_soc: regulator-sata-soc {
    +               compatible = "regulator-fixed";
    +               regulator-name = "regulator-sata-soc";
    +               regulator-always-on;
    +               status = "okay";
    +       };
    +
    +       /* Regulator labels for dummy sata target supply */
    +       v_sata_target: regulator-sata-target {
    +               compatible = "regulator-fixed";
    +               regulator-name = "regulator-sata-target";
    +               regulator-always-on;
    +               status = "okay";
    +       };
    +
            /* Regulator labels correspond with schematics */
            v_3_3: regulator-3-3v {
                    compatible = "regulator-fixed";
    @@ -239,10 +268,21 @@
     &cp0_sata0 {
            status = "okay";
    
    +       /* Dummy supply */
    +       ahci-supply = <&v_sata_soc>;
    +       phy-supply = <&v_sata_soc>;
    +
    +       /* Dummy port */
    +       sata-port@0 {
    +               phy-names = "dummy";
    +               target-supply = <&v_sata_target>;
    +       };
    +
            /* CPM Lane 5 - U29 */
            sata-port@1 {
                    phys = <&cp0_comphy5 1>;
                    phy-names = "cp0-sata0-1-phy";
    +               target-supply = <&v_sata_target>;
            };
     };
    
    @@ -329,16 +369,22 @@
     &cp1_sata0 {
            status = "okay";
    
    +       /* Dummy supply */
    +       ahci-supply = <&v_sata_soc>;
    +       phy-supply = <&v_sata_soc>;
    +
            /* CPS Lane 1 - U32 */
            sata-port@0 {
                    phys = <&cp1_comphy1 0>;
                    phy-names = "cp1-sata0-0-phy";
    +               target-supply = <&v_sata_target>;
            };
    
            /* CPS Lane 3 - U31 */
            sata-port@1 {
                    phys = <&cp1_comphy3 1>;
                    phy-names = "cp1-sata0-1-phy";
    +               target-supply = <&v_sata_target>;
            };
     };
    
    
    in reply to: Blank eMMC, failure in U-Boot after running from SD card #7955
    nanasi
    Participant

    In my case,
    when cold boot is starting,
    the following error messages are reported.

    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - wait_for_sd_interrupt: Error interrupt -  00008000
    SD - wait_for_sd_interrupt: Error interrupt status 00000120
    SD - read_buffer_pio: Failed - ret = 00000081
    SD - wait_for_sd_interrupt: Error interrupt -  00008000
    SD - wait_for_sd_interrupt: Error interrupt status 00000120
    SD - wait_transfer_complete: wait for transfer completion timeout.
    
    Error: failed reading from boot position 0x00000000
    Error: Failed boot attempt 01. error = 0x0C1
    
    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - wait_for_sd_interrupt: Error interrupt -  00008000
    SD - wait_for_sd_interrupt: Error interrupt status 00000120
    SD - read_buffer_pio: Failed - ret = 00000081
    SD - wait_for_sd_interrupt: Error interrupt -  00008000
    SD - wait_for_sd_interrupt: Error interrupt status 00000120
    SD - wait_transfer_complete: wait for transfer completion timeout.
    
    Error: failed reading from boot position 0x00000000
    Found valid image at boot postion 0x002
    lNOTICE:  Starting binary extension

    But no problems appear when accessing the SD card.

    The only malfunction is that
    a legacy (<=2GB) SD card is not usable for boot source.

    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - sd_init: Only Standard Capacity SD cards are supported.
    Error: Failed initializing interface
    Error: Failed boot attempt 01. error = 0x0C3
    
    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - sd_init: Only Standard Capacity SD cards are supported.
    Error: Failed initializing interface
    Error: Failed boot attempt 02. error = 0x0C3
    
    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - sd_init: Only Standard Capacity SD cards are supported.
    Error: Failed initializing interface
    Error: Failed boot attempt 03. error = 0x0C3
    
    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD - sd_init: Only Standard Capacity SD cards are supported.
    Error: Failed initializing interface
    Error: Failed boot attempt 04. error = 0x0C3
    
    Trying Uart..
    in reply to: Blank eMMC, failure in U-Boot after running from SD card #7938
    nanasi
    Participant

    Hi,
    You can configure jumpers and a microSD to load another bootloader from the microSD.

    – Boot Selection
    – Setup alternative boot sources
    or
    – Marvell ARMADA 8040 Dipswitch
    – Armada 8040 U-Boot and ATF

    in reply to: Failed to boot from eMMC #7936
    nanasi
    Participant

    Hi,
    I found a similar log.
    IRC log of channel #cubox on freenode
    But my mcbin(v1.2) does not report “Error interrupt” if eMMC is blank.

    If you have datasheet for 88F8040,
    you might want to check definitions of “SDIO Registers/Error Interrupt Status Register”
    and “Boot ROM routine and Error Code Register”.
    (Register names are my guess.)

    I suspect that it is a simple hardware defect.
    If your warranty is expired,
    is there an any reason why you do not use SPI-boot?

    in reply to: UART boot problem for marvell 7040 board #7809
    nanasi
    Participant

    SolidRun’s KB for 8040:
    Booting the board using UART xmodem

    in reply to: Loopback testing experience between two 10G SFP #7645
    nanasi
    Participant

    I have no info other than this HCL. Sorry.

    in reply to: 10G interfaces not working #7546
    nanasi
    Participant
    in reply to: mv_ddr armada-18.09 for ECC DIMM #7396
    nanasi
    Participant

    I got late.
    I tried the following combinations.
    Reference binary from maintainer
    Debian grub-efi-arm64 (2.02~beta3-5+deb9u1)
    – 16GB ECC
    There are similar symptoms.

    Shell> fs1:
    FS1:\> cd EFI\EFI\debian
    FS1:\EFI\EFI\debian\> ls
    Directory of: FS1:\EFI\EFI\debian\
    04/21/2019  21:46 <DIR>         2,048  .
    04/21/2019  21:46 <DIR>         2,048  ..
    04/21/2019  21:46             120,832  grubaa64.efi
              1 File(s)     120,832 bytes
              2 Dir(s)
    FS1:\EFI\EFI\debian\> grubaa64.efi
    error: no such partition.
    Entering rescue mode...
    grub rescue> 

    With modding to fake DRAM size.
    8GB: NG
    4GB: Good

    in reply to: ECC RAM #7373
    nanasi
    Participant

    Hi.
    If ECC is initialized correctly, the next message will appear.

    mv_ddr: scrubbing memory...
    mv_ddr: completed successfully

    There is no easy way to check whether ECC is working.
    Since there is no open source memory controller driver for A8k/A7k.(AFAIK)

    In addition, the memory width is hardcoded into UEFI source.
    From dmidecode manpage:

    BUGS
           More often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong.
    in reply to: DIMM Recomendation 2018/10 #7372
    nanasi
    Participant

    There is a report with Kingston’s EUDIMM.
    DDR training fails on ARMADA 8040 / MACCHIATObin with KVR24E17D8/16

    Latest mv_ddr code (mv_ddr-devel-18.12.0) has another fixes for A8K.

    mv_ddr: apn806: fix RX align shift process 
    mv_ddr: apn806: remove stage2 and fix Tx vref configuration error 
    mv_ddr: apn806 : remove decreasing 50mv of the CPU_CORE AVS before tr… 
    mv_ddr: apn806: fix write leveling suplementary algo
    in reply to: mv_ddr armada-18.09 for ECC DIMM #7371
    nanasi
    Participant

    decode-dimms output:

    $ decode-dimms
    # decode-dimms version $Revision$
    
    Memory Serial Presence Detect Decoder
    By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
    Jean Delvare, Trent Piepho and others
    
    Decoding EEPROM: /sys/bus/i2c/drivers/ee1004/0-0053
    Guessing DIMM is in                              bank 4
    
    ---=== SPD EEPROM Information ===---
    EEPROM CRC of bytes 0-125                        OK (0x7A64)
    # of bytes written to SDRAM EEPROM               384
    Total number of bytes in EEPROM                  512
    Fundamental Memory type                          DDR4 SDRAM
    SPD Revision                                     1.1
    Module Type                                      UDIMM
    EEPROM CRC of bytes 128-253                      OK (0x05F1)
    
    ---=== Memory Characteristics ===---
    Maximum module speed                             2400 MHz (PC4-19200)
    Size                                             16384 MB
    Banks x Rows x Columns x Bits                    16 x 16 x 10 x 64
    SDRAM Device Width                               8 bits
    Ranks                                            2
    Rank Mix                                         Symmetrical
    Bus Width Extension                              8 bits
    AA-RCD-RP-RAS (cycles)                           17-17-17-39
    Supported CAS Latencies                          21T, 20T, 19T, 18T, 17T, 16T, 15T, 14T, 13T, 12T, 11T, 10T
    
    ---=== Timings at Standard Speeds ===---
    AA-RCD-RP-RAS (cycles) as DDR4-2400              17-17-17-39
    AA-RCD-RP-RAS (cycles) as DDR4-2133              15-15-15-35
    AA-RCD-RP-RAS (cycles) as DDR4-1866              13-13-13-30
    AA-RCD-RP-RAS (cycles) as DDR4-1600              11-11-11-26
    
    ---=== Timing Parameters ===---
    Minimum Cycle Time (tCKmin)                      0.833 ns
    Maximum Cycle Time (tCKmax)                      1.600 ns
    Minimum CAS Latency Time (tAA)                   13.750 ns
    Minimum RAS to CAS Delay (tRCD)                  13.750 ns
    Minimum Row Precharge Delay (tRP)                13.750 ns
    Minimum Active to Precharge Delay (tRAS)         32.000 ns
    Minimum Active to Auto-Refresh Delay (tRC)       45.750 ns
    Minimum Recovery Delay (tRFC1)                   350.000 ns
    Minimum Recovery Delay (tRFC2)                   260.000 ns
    Minimum Recovery Delay (tRFC4)                   160.000 ns
    Minimum Four Activate Window Delay (tFAW)        21.000 ns
    Minimum Row Active to Row Active Delay (tRRD_S)  3.300 ns
    Minimum Row Active to Row Active Delay (tRRD_L)  4.900 ns
    Minimum CAS to CAS Delay (tCCD_L)                5.000 ns
    Minimum Write Recovery Time (tWR)                15.000 ns
    Minimum Write to Read Time (tWTR_S)              2.500 ns
    Minimum Write to Read Time (tWTR_L)              7.500 ns
    
    ---=== Other Information ===---
    Package Type                                     Monolithic
    Maximum Activate Count                           Unlimited
    Post Package Repair                              One row per bank group
    Soft PPR                                         Supported
    Module Nominal Voltage                           1.2 V
    Thermal Sensor                                   TSE2004 compliant
    
    ---=== Physical Characteristics ===---
    Module Height                                    19 mm
    Module Thickness                                 2 mm front, 2 mm back
    Module Reference Card                            ZZ
    
    ---=== Manufacturer Data ===---
    Module Manufacturer                              Micron Technology
    DRAM Manufacturer                                Micron Technology
    Manufacturing Location Code                      0x0F
    Manufacturing Date                               2018-W13
    Assembly Serial Number                           0x********
    Part Number                                      18ADF2G72AZ-2G3B1
    Revision Code                                    0x31
    
    Number of SDRAM DIMMs detected and decoded: 1
    
    in reply to: mv_ddr armada-18.09 for ECC DIMM #7370
    nanasi
    Participant

    I use a Crucial CT16G4XFD824A (Micron MTA18ADF2G72AZ-2G3B1).
    No problems in my environment with the fix above.

Viewing 15 posts - 1 through 15 (of 55 total)

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