Jump to content

flippy

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation Activity

  1. Like
    flippy got a reaction from Maxxim in Methods to fix x96 max plus(s905x3) gigabit ethernet problem   
    I found the correct method to fix the bug that the x96-max-plus(s905x3) gigabit ethernet  does not work:
    Up to now, only HK1Box/vontar x3 is the only s905x3 TV box that can be used perfectly in armbian.  So I extracted the bootloader of hk1box and wrote it into x96-max-plus, and it worked.
    This method is very simple, so it is recommended to everyone in need.
     
    Step 1:  upload three dtbs into /boot/dtb/amlogic :
        meson-sm1-x96-max-plus-100m.dtb
        meson-sm1-x96-max-plus.dtb
        meson-sm1-hk1box-vontar-x3.dtb  (Similar to meson-sm1-x96-max-plus.dtb, only the modal name is changed)
     
    Step 2:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus-100m.dtb,  restart the Armbian system
     
    Step 3:  upload hk1box-bootloader.img to /tmp
     
    Step 4:  Run these commands under the shell:
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=1 count=442
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=512 skip=1 seek=1
    sync
    reboot
     
    Step 5:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus.dtb, and restart again.
     
     
    meson-sm1-x96-max-plus.dtb meson-sm1-x96-max-plus.dts meson-sm1-hk1box-vontar-x3.dtb meson-sm1-hk1box-vontar-x3.dts hk1box-bootloader.img.xz meson-sm1-x96-max-plus-100m.dtb meson-sm1-x96-max-plus-100m.dts
    x96maxplus-orig-bootloader.img.xz
  2. Like
    flippy got a reaction from chinhhut in Methods to fix x96 max plus(s905x3) gigabit ethernet problem   
    I found the correct method to fix the bug that the x96-max-plus(s905x3) gigabit ethernet  does not work:
    Up to now, only HK1Box/vontar x3 is the only s905x3 TV box that can be used perfectly in armbian.  So I extracted the bootloader of hk1box and wrote it into x96-max-plus, and it worked.
    This method is very simple, so it is recommended to everyone in need.
     
    Step 1:  upload three dtbs into /boot/dtb/amlogic :
        meson-sm1-x96-max-plus-100m.dtb
        meson-sm1-x96-max-plus.dtb
        meson-sm1-hk1box-vontar-x3.dtb  (Similar to meson-sm1-x96-max-plus.dtb, only the modal name is changed)
     
    Step 2:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus-100m.dtb,  restart the Armbian system
     
    Step 3:  upload hk1box-bootloader.img to /tmp
     
    Step 4:  Run these commands under the shell:
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=1 count=442
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=512 skip=1 seek=1
    sync
    reboot
     
    Step 5:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus.dtb, and restart again.
     
     
    meson-sm1-x96-max-plus.dtb meson-sm1-x96-max-plus.dts meson-sm1-hk1box-vontar-x3.dtb meson-sm1-hk1box-vontar-x3.dts hk1box-bootloader.img.xz meson-sm1-x96-max-plus-100m.dtb meson-sm1-x96-max-plus-100m.dts
    x96maxplus-orig-bootloader.img.xz
  3. Like
    flippy got a reaction from cnxzp in Methods to fix x96 max plus(s905x3) gigabit ethernet problem   
    I found the correct method to fix the bug that the x96-max-plus(s905x3) gigabit ethernet  does not work:
    Up to now, only HK1Box/vontar x3 is the only s905x3 TV box that can be used perfectly in armbian.  So I extracted the bootloader of hk1box and wrote it into x96-max-plus, and it worked.
    This method is very simple, so it is recommended to everyone in need.
     
    Step 1:  upload three dtbs into /boot/dtb/amlogic :
        meson-sm1-x96-max-plus-100m.dtb
        meson-sm1-x96-max-plus.dtb
        meson-sm1-hk1box-vontar-x3.dtb  (Similar to meson-sm1-x96-max-plus.dtb, only the modal name is changed)
     
    Step 2:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus-100m.dtb,  restart the Armbian system
     
    Step 3:  upload hk1box-bootloader.img to /tmp
     
    Step 4:  Run these commands under the shell:
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=1 count=442
    dd if=/tmp/hk1box-bootloader.img of=/dev/mmcblk2 bs=512 skip=1 seek=1
    sync
    reboot
     
    Step 5:  modify /boot/uEnv.txt, replace dtb with meson-sm1-x96-max-plus.dtb, and restart again.
     
     
    meson-sm1-x96-max-plus.dtb meson-sm1-x96-max-plus.dts meson-sm1-hk1box-vontar-x3.dtb meson-sm1-hk1box-vontar-x3.dts hk1box-bootloader.img.xz meson-sm1-x96-max-plus-100m.dtb meson-sm1-x96-max-plus-100m.dts
    x96maxplus-orig-bootloader.img.xz
  4. Like
    flippy got a reaction from guidol in Fix dtb of aml s905d phicomm n1 box   
    I improved the dts of Phicomm N1 again.
    The reasons are:
    1. The Ethernet card of N1 is not very compatible with some switches. When the ethernet phy is activated, the flow control sometimes cannot be turned on, so  will get bad results during the speedtest.net . For this reason, I added a dts separately force_thresh_dma_mode, which is equivalent to flow control in software mode. But there are also side effects: tx performance is reduced. In addition, as auxiliary optimization items, set snps, aal; snps, txpbl = <0x8>; snps, rxpbl = <0x4>; their role is to improve the performance of the network card.
    2. The phy reset-delay-us value of N1 is sometimes not enough. When running openwrt, sometimes the ethernet phy cannot be enabled, so the reset-delay-us value is increased.
    Provide two dts files:
    meson-gxl-s905d-phicomm-n1.dts: This is the default dts, used in most occasions, when the flow control can be turned on normally, this is the best choice
    meson-gxl-s905d-phicomm-n1-thresh.dts: This is a dts with the force_thresh_dma_mode option enabled. It is applicable when flow control cannot be turned on. You can use force_thresh_dma_mode to control flow at the cost of a small amount of performance loss.
    meson-gxl-s905d-phicomm-n1.dts meson-gxl-s905d-phicomm-n1-thresh.dts
  5. Like
    flippy got a reaction from guidol in Fix dtb of aml s905d phicomm n1 box   
    In the mainline kernel, meson-gxl-s905d-phicomm-n1.dts has been around for a long time, but there has been a problem of high CPU load. I fixed it and it has been stable for several months, so it is shared for reference .
    I think the cause of the problem is that the IRQ is wrong. The original value is 29 and needs to be changed to 25.
    // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright (c) 2018 He Yangxuan */ /dts-v1/; #include "meson-gxl-s905d-p230.dts" / { compatible = "phicomm,n1", "amlogic,s905d", "amlogic,meson-gxl"; model = "Phicomm N1"; cvbs-connector { status = "disabled"; }; leds { compatible = "gpio-leds"; status { label = "n1:white:status"; gpios = <&gpio_ao GPIOAO_9 GPIO_ACTIVE_HIGH>; default-state = "on"; }; }; }; &cvbs_vdac_port { status = "disabled"; }; &external_phy { /delete-property/ reset-gpios; interrupts = <25 IRQ_TYPE_LEVEL_LOW>; };  
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines