Jump to content

maka

Members
  • Posts

    136
  • Joined

  • Last visited

Posts posted by maka

  1. I have a T9 2017 rk3328 box running Ubuntu xcfe many hours for downloading. There are not problems but xcfe displays lunchs himself many times and i have to close 20 or more instances of this application when checking the progress. Box is not crashed by this funny clonning. is it  possible to avoid this?

     

    p.d. la test trunk

  2. I see this on your dts:

     

    ethernet-phy@1 {
                                     compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";
                    

    But I think should be:

     

    ethernet-phy@1 {

                                   compatible = "ethernet-phy-ieee802.3-c22";

                                    reg = <0x01>; 

     

    And try to use the generic driver for ethernet.

  3. All you need is in this thread

    CSC Armbian for RK3318/RK3328 TV box boards

    And the special uboot is there.

     

    Quote

    The Multitool does not boot / How to burn image directly on eMMC:

     

    Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one.

    Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard.

     

    In such case, burning images directly on eMMC is the only way to have a working Armbian installation.

    You can follow these instructions by @fabiobassa to burn images directly on eMMC:

     

    https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453

     

     

    You have a chance to brick you device so if you don't understand something don't go ahead.

  4. I think your driver is already in armbian, but your chip is not identified. To get it working you can identify it in the ethernet node this way:

     

    mdio {
                compatible = "snps,dwmac-mdio";
                #address-cells = < 0x01 >;
                #size-cells = < 0x00 >;

                ethernet-phy@1 {
                    compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";

  5. Yes but is ICPLUS chip

     

    You can try this, maybe the chip is awaked

     

    mdio {
                compatible = "snps,dwmac-mdio";
                #address-cells = < 0x01 >;
                #size-cells = < 0x00 >;

                ethernet-phy@1 {
                    compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id001c.c916", "ethernet-phy-ieee802.3-c22";

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines