Jump to content

Ngo Thang

Members
  • Posts

    22
  • Joined

  • Last visited

Posts posted by Ngo Thang

  1. I have an X96 Air (version with chip wifi RTL8822CS). I installed Amrbian (via flash to SD Card) and run some months, next I install Armbian from SD Card to eMMC and run next some months.
    But in a day, it bricked, nothing in screen. And I have to flash stock rom (X96AIR_Q100_20210126-1140.img) via USB Burning Tool. Then my X96 is survive again, I can use it as a TVBox.
    But I try to plug SD Card with many images/versions of Armbian and with/without press reset, it can not boot from SD Card, it still boots to Android TVBox GUI. I try to flash Amrbian to USB stick, try each of three usb ports, it's still impossible boot to Armbian.

    So how I have to do now ?

  2. Hi all

    I try again 2 commands

    sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
    sudo ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt

    And now my TX3 Mini has wifi, good news !

     

    my TX3 Mini uses S905W, not S905X3 and uses SP6330 - X, not SP6330, my dtb is "/dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb"

    Now it has wifi but no bluetooth and I still really want it have bluetooth. Does anyone here try to get bluetooth in TX3 mini with same chipsets as mine ?

     

    Thanks

     

     

     

     

  3. I buy a TV Box Mxq pro 4k 5G, Soc Rk3229. I chose model 4GB Ram and 32GB Rom (emmc).

    First time I turn on it and run Android OS, I install Cpu-z tool in this Android and check, it's correct that it has 4GB Ram and 32GB Rom

    But after I install Armbian OS in emmc, and login in Armbian screen, it shows system has only 1GB Ram and 8GB Rom. So why are they (ram and rom) are difference like that?
    Tks and Best regards

  4. On 4/9/2021 at 10:00 PM, Daniel Cagarrinho said:

    I boot using a USB stick, then I used the two commands :

     

    ```
    sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
    sudo ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt
    ```

    after that I entered in the armbian-config and managed to connect to a wifi network, then restarted the box and no longer be able to boot armbian!

    Conclusion this two commands turn possible the usage of wifi, but somehow causes a problem removing the ability to boot the system after the change!!!

     

     

     

    Ps: I just can post 1 time a day here!

     

    I run 2 commands as yours and run armbian-config, come to network/wifi but I still can't see wifi list, just only "Wired"

     

     Wired              ↑ │ <Deactivate> │
                                              │ │ * Ifupdown (eth0)  ▒ │             

  5. On 4/9/2021 at 10:00 PM, Daniel Cagarrinho said:

    I boot using a USB stick, then I used the two commands :

     

    ```
    sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
    sudo ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt
    ```

    after that I entered in the armbian-config and managed to connect to a wifi network, then restarted the box and no longer be able to boot armbian!

    Conclusion this two commands turn possible the usage of wifi, but somehow causes a problem removing the ability to boot the system after the change!!!

     

     

     

    Ps: I just can post 1 time a day here!

    Could you please explain why do you use 6330 instead of 4330 ? And what is about your tvbox now, can you fix and boot again ?

     

    Tks

  6. back to Wifi issue, when I run command "ip a", I see this result

    # ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether xx:yy:1c:a0:ee:a2 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.XX/24 brd 192.168.1.255 scope global noprefixroute eth0
           valid_lft forever preferred_lft forever
        inet6 fe80::dfd8:619:439b:4bf2/64 scope link noprefixroute
           valid_lft forever preferred_lft forever
    3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
        link/ether e0:76:d0:14:76:d3 brd ff:ff:ff:ff:ff:ff
    
    

     

    So wlan0 still get its MAC address even wifi card is down, so I still hope there is any way to set and up wlan0, but I don't know how to do

  7. On 12/24/2020 at 9:21 PM, SteeMan said:

    I'm glad you were able to get armbian running.  You should not however expect that you will be able to get the analog audio jack to work.  Along with wifi/bluetooth it is highly unlikely that anything other than audio over hdmi is going to work on a TV box like this.  If you haven't already, please read the "Please Read First" post to familiarize yourself with what you can hope will work.

     

     

    It's a clear explaination. Thank you very much

  8. Hi robertoenr

     

    It's simple like that. Follow guide of SteeMan, but NO NEED to hold Reset while booting, DO NOT PRESS OR HOLD ANYTHING while booting and DO NOT plug USB Keyboard while booting, you can plug USB Keyboard later, after see login screen

     

    On 11/23/2020 at 10:26 PM, SteeMan said:

    Given that you do have general linux knowledge and rpi familiarity, here are my comments on your requests.

    I have 4 TX3 mini's three of which I run armbian on and one that I use the original android on.  I will mention that just because a box is labeled TX3 mini, doesn't mean the internals are the same.  The manufactures put identical external branding on boards that may be significantly different.  For example all TX3 minis claim they have emmc storage in them.  But only two of my TX3 minis have emmc storage, the other two come with nand storage (cheaper to manufacture that way).  Since mainline linux doesn't support nand I can only install armbian on internal storage on two of my boxes.

     

    From the above linked post you need to download an image file from any of the download locations.  The file you are looking for is the arm-64 version from October 14th 2020.  These are the last versions from balbes150 to support Amlogic cpus.  So be warned that when and if you get this running on your TX3 mini box, there is currently no path to get anything newer than this Oct 14 build with 5.9.0 kernel.  You will get updates from your chosen distribution (debian or ubuntu) just no kernel updates, unless someone else in the community picks up the ball and begins building/maintaining amlogic kernels.

     

    In the downloads directory you will find builds for debian (buster and bullseye) and ubuntu (bionic and focal), along with both a desktop and non-desktop version of each.

     

    Once you download your chosen build (for example  https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz - ubuntu focal non-desktop build)

    You need to burn the image to an SD card.  Generally balenaEtcher is recommended (however I have only ever used dd on linux to create my sd cards, so I have no familiarity with that tool)

     

    Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card.  In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. (In earlier builds this was done in the /boot/uEnv.txt file, so a lot of comments in these threads talk about that file, but in the latest builds it was changed to the extlinux.conf file)

     

    Your extlinux.conf file should look like:

    LABEL Armbian
    LINUX /zImage
    INITRD /uInitrd

    # aml s9xxx
    #FDT /dtb/amlogic/meson-gxbb-p200.dtb
    FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb
    #FDT /dtb/amlogic/meson-gxm-q200.dtb
    #FDT /dtb/amlogic/meson-g12a-x96-max.dtb
    #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb
    APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
     

    Basically you need to have the correct dtb for your box and the correct boot command for your box, along with the top three environment variables set.  *Everything* else needs to either be deleted or commented out.  This is a common mistake where people uncomment out what they need, but leave other lines in the file not uncommented and thus they fail to boot.  The extlinux.conf file above is directly from my TX3 mini box.  Note that if you were using a different box than a TX3 mini, you would attempt to use different dtb files until you found the one that works the best for you boxes hardware (there are a bunch of dtb files in /boot/dtb/... to try depending on your cpu architecture and hardward).

     

    Next you need to copy the correct uboot for your box.  This is needed for amlogic cpus (other cpus have different uboot stuff to do).  For your TX3mini you need to copy u-boot-s905x-s912 to u-boot.ext (note I say copy not move).

     

    Once you have your SD card prepared, on an Amlogic box you need to enable multiboot.  There are different ways documented to do this, but for your TX3 mini box, you should use the toothpick method.  At the back of the audio/video jack connector is a hidden reset button.  By pressing that button with a toothpick or other such pointed device you can enable multiboot.  What you need to do is have the box unpluged, have your prepared sd card inserted, then press and hold the button while inserting the power connector.  Then after a bit of time you can release the button.  (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times).

     

    You should now be booting into armbian/linux.

     

    If you want at this point, you can copy the installation to emmc (assuming your box has emmc).  You do this by running the appropriate shell script in /root, which for your case is /root/install-aml.sh.  Note that it is recommended that you make a backup of emmc first (use the ddbr tool that should be installed on your sd card).  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the armbian firmware using the Amlogic USB Burning Tool to unbrick your device.  It is pretty easy to find TX3mini android firmwares on the internet and you can generally recover a bricked box using the Amlogic tool and an original firmware file.

     

    Finally, I have written this from memory and haven't been actually doing these steps as I am writing, so there might be something I forgot to say, so I make no promises that this is completely accurate, but I think it is.

     

    Also, don't expect that all parts of your TX3mini box will work.  You should have a working boot, working wired ethernet and working hdmi.  Don't expect things like wifi, bluetooth, infrared remote, box display to work.  The experimental armbian for these boxes is enough to get a basic server running and a light graphical display, but don't expect full functionality.

     

     

  9. Now I can boot into Armbian, I find out an interesting way.

    If I unplug USB keyboard, it can boot from SDCard or USB into Armbian without pressing reset button, after it comes to login screen, I plug USB keyboard and I can use it normally. But if I plug USB keyboard while booting, it shows error "Unexpected XHCI event TRB,..." and reboot forever

  10. It's stranger like that:

    If I boot into Android, I can read content in my SDCard and my USB that mean SDCard slot and USB slot are OK.

    I flash both my SDCard and my USB with file https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz

    I plug only SDCard and hold reset -> it shows recovery screen

    I plug only USB and hold reset -> it shows recovery screen

    I plug both SDCard and USB, even I hold reset or do nothing, it boots into text screen but after restarts and boots into text screen again and restarts again and again. Let see my video capture https://streamable.com/76pj97

     

    Tks very much

  11. Hi SteeMan

    Thank you for your very detail guideline. I follow but still get a problem

    I download image, flash to SDCard via balenaEtcher,  edit /boot/extlinux/extlinux.conf with correct DTB parameter

    I push SDCard into, hold reset and power on, but my TX3 mini always shows the screen as in picture https://ibb.co/12JtfJS, as far as I understand it is recovery screen

    It can't boot into armbian in SDCard

     

    Best regards

     

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines