SteeMan

You are not using Armbian.  You have downloaded software from a site that is a fork of Armbian and uses the Armbian name without permission.  They do not participate in Armbian development, nor do they participate in these forums.  We can't help you here as we don't produce the code you are running.  You need to log your question with those you downloaded your software from.

If your emmc is not working, I don't think you can.  My understanding is that these amlogic boxes basically are hard coded to look for uboot on emmc.  That is why the aml-s9xx-box builds use the emmc uboot to then chain load the distribution from sd/usb/etc.  It is always using the emmc uboot initially.  If your emmc is working, you should use recovery to reinstall the android uboot and then you could move on from there.  But in your case you have already tried that, and it didn't work (likely indicating that your emmc is not working).  Based on your comments, it sounds like you have previously reinstalled the android firmware, so you know that process used to work (the reason I am stating this, is that sometimes different boards/firmware combinations require specific versions of the amlogic burning tool)

Another factor is that at least as far as the armbian builds go, there is no uboot suitable for your box available.  It isn't feasible/possible to build uboots for the hundreds of different tv box hardware configurations out there (and the tv box manufacturers don't release their source for their android uboots), so the uboot on the armbian build sd card is basically just a place holder (generic uboot that 100% is guaranteed not to work for your box).  The whole armbian amlogic tv box strategy is to use the uboot that comes with the tv box on emmc.  So if you are trying to get something working from sd, it isn't going to be armbian unless you can get your emmc working again.

I would recommend that you first start with a pre-built image (https://www.armbian.com/orange-pi-pc) Then if you want use the armbian build system (https://docs.armbian.com/Developer-Guide_Build-Preparation/)
Then you might be able to track down why the Debos isn't working as you think it should. 

@chinhhut The site you posted a link to, is a fork of Armbian, but continues to use the Armbian name without permission.  This causes users to think they are using official Armbian when they are not, causing people to come here for support.

No, the only output is to the screen

The only suggestion I have on the usb burning tool is to try different versions.  I have found that with some older TV boxes, the latest version sometimes doesn't work, but an older one will.
One other point I will mention is to have the box disconnected from power when you are trying to connect to it with the burning tool (it should get power over the usb connection) and to try different usb ports on the box.

@jock @Igor I have been thinking along the same lines for the aml-s9xx-box builds.  While having the weekly builds is great, they are very unstable, being built on current master with edge kernel and the unstable debian and ubuntu userlands.  While that is all good for testing purposes, it is far from desirable for running anything in a production environment (yes there are crazy people like me that use TV boxes for production servers).  Now that current has moved to 6.1 for meson64 and I suspect rockchip current will try to get to 6.1 soon, it would be nice to have stable builds based on a stable master, current kernel and supported userspace (i.e. jammy currently for ubuntu) for the TV Box targets, IMHO.

I don't know what the problem is because as I said, you didn't capture the important part of the install-aml.sh script run.  But I also did say the following:
If you want a valid test of installing to emmc you need to restore the box to the original android firmware and start from there.  And it may still not work, but that is the starting state the script expects and the only thing that is tested.

They are inexpensive and a necessary tool to have around if you work with sbc's. I would recommend you own one.

You are typing the command wrong.  There is a space after sudo, but if you are already logged in a root, you don't need the sudo at all.  And in the case you did the command without sudo you didn't include the ./
 
Also note that you can't install on emmc if the box has an s905 cpu (you need an s905x or newer for emmc support).  There was a recent thread that talked about this in the forums.

These instructions are for Amlogic CPUs for TV Boxes. 
 
Note: If you have previously run other distributions on the box such as coreelec the below installation will not work.  You will need to restore the original android firmware before attempting the install.  coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
 
Download links:
    Weekly Community Rolling Builds:  https://www.armbian.com/amlogic-s9xx-tv-box/
    or build your own image using the Armbian build framework
 
Once you download your chosen build, you need to burn the image to an SD card.  Generally balenaEtcher is recommended as it does a verification of the burn.  Also be sure to use high quality SD cards.
 
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.  There will also be a extlinux.conf.template file to use as a reference.  You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box.  Place this line before the APPEND line as shown in the .template file.
 
Basically you need to have the correct dtb for your box.  You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware).  It is unlikely that there will be a matching dtb file for your TV box.  The idea is to find the one that works best for your box.  This may mean that you try booting with different dtb files until you fine one that works good enough for your needs.  By searching the forums you will find information about what dtbs other users have found work best for different boxes.  Because you are booting from an SD card, you can easily try different dtb files.  The dtd files are named by cpu family.  So for example dtb files for the s905x2 cpu are named meson-g12a-*.  Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case).
 
Next you need to copy the correct uboot for your box.  This is needed for how these builds boot on amlogic boxes.  There are four different u-boot files located in the /boot directory:  u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3
You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory
So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext
(See table below for more details on which u-boot to use for which cpu)
 
Once you have your SD card prepared you need to enable multiboot on the box.  There are different ways documented to do this, but the most common is the "toothpick" method.  The "toothpick" method means to hold the reset button while applying power to the box.  The reset button is often hidden and located at the back of the audio/video jack connector.  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 unplugged, 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.  Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card.
 
After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box.  Don't do this unless you feel you understand how to reinstall your box's android firmware)  You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported).  It is recommended that you make a backup of emmc first.  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device.  If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file.
 
 
Mapping from CPU to uboot and dtb:
 
u-boot-s905
s905 - gxbb
 
u-boot-s905x2-s912
S905X - gxl
S905W - gxl
S905D - gxl
S905L - gxl
S805X - gxl
S912 - gxm
A311D - gxm
 
u-boot-s905x2-s922
S905X2 - g12a
S922 - g12b
 
u-boot-s905x3
S905X3 - sm1
 
Not supported or not tested
S805 -
S905W2 -
S905X4 -
S805X2 - s4
A113D - axg
A113X - axg
 
 
 
Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions.  Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

By flash drive I'm assuming you mean a usb flash drive.  Yes that should work, but generally an sd card is recommended and more commonly used.

I understand. I cannot apply 😆 but will act accordingly. thx

These instructions are for Amlogic CPUs for TV Boxes. 
 
Note: If you have previously run other distributions on the box such as coreelec the below installation will not work.  You will need to restore the original android firmware before attempting the install.  coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
 
Download links:
    Weekly Community Rolling Builds:  https://www.armbian.com/amlogic-s9xx-tv-box/
    or build your own image using the Armbian build framework
 
Once you download your chosen build, you need to burn the image to an SD card.  Generally balenaEtcher is recommended as it does a verification of the burn.  Also be sure to use high quality SD cards.
 
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.  There will also be a extlinux.conf.template file to use as a reference.  You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box.  Place this line before the APPEND line as shown in the .template file.
 
Basically you need to have the correct dtb for your box.  You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware).  It is unlikely that there will be a matching dtb file for your TV box.  The idea is to find the one that works best for your box.  This may mean that you try booting with different dtb files until you fine one that works good enough for your needs.  By searching the forums you will find information about what dtbs other users have found work best for different boxes.  Because you are booting from an SD card, you can easily try different dtb files.  The dtd files are named by cpu family.  So for example dtb files for the s905x2 cpu are named meson-g12a-*.  Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case).
 
Next you need to copy the correct uboot for your box.  This is needed for how these builds boot on amlogic boxes.  There are four different u-boot files located in the /boot directory:  u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3
You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory
So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext
(See table below for more details on which u-boot to use for which cpu)
 
Once you have your SD card prepared you need to enable multiboot on the box.  There are different ways documented to do this, but the most common is the "toothpick" method.  The "toothpick" method means to hold the reset button while applying power to the box.  The reset button is often hidden and located at the back of the audio/video jack connector.  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 unplugged, 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.  Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card.
 
After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box.  Don't do this unless you feel you understand how to reinstall your box's android firmware)  You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported).  It is recommended that you make a backup of emmc first.  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device.  If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file.
 
 
Mapping from CPU to uboot and dtb:
 
u-boot-s905
s905 - gxbb
 
u-boot-s905x2-s912
S905X - gxl
S905W - gxl
S905D - gxl
S905L - gxl
S805X - gxl
S912 - gxm
A311D - gxm
 
u-boot-s905x2-s922
S905X2 - g12a
S922 - g12b
 
u-boot-s905x3
S905X3 - sm1
 
Not supported or not tested
S805 -
S905W2 -
S905X4 -
S805X2 - s4
A113D - axg
A113X - axg
 
 
 
Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions.  Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box).  You can now build your own builds directly with the Armbian build system.
 
This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework.  If you are not familiar with the Armbian build system check out the Armbian developer documentation.  If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see.
 
I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well.  Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

These instructions are for Amlogic CPUs for TV Boxes. 
 
Note: If you have previously run other distributions on the box such as coreelec the below installation will not work.  You will need to restore the original android firmware before attempting the install.  coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
 
Download links:
    Weekly Community Rolling Builds:  https://www.armbian.com/amlogic-s9xx-tv-box/
    or build your own image using the Armbian build framework
 
Once you download your chosen build, you need to burn the image to an SD card.  Generally balenaEtcher is recommended as it does a verification of the burn.  Also be sure to use high quality SD cards.
 
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.  There will also be a extlinux.conf.template file to use as a reference.  You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box.  Place this line before the APPEND line as shown in the .template file.
 
Basically you need to have the correct dtb for your box.  You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware).  It is unlikely that there will be a matching dtb file for your TV box.  The idea is to find the one that works best for your box.  This may mean that you try booting with different dtb files until you fine one that works good enough for your needs.  By searching the forums you will find information about what dtbs other users have found work best for different boxes.  Because you are booting from an SD card, you can easily try different dtb files.  The dtd files are named by cpu family.  So for example dtb files for the s905x2 cpu are named meson-g12a-*.  Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case).
 
Next you need to copy the correct uboot for your box.  This is needed for how these builds boot on amlogic boxes.  There are four different u-boot files located in the /boot directory:  u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3
You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory
So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext
(See table below for more details on which u-boot to use for which cpu)
 
Once you have your SD card prepared you need to enable multiboot on the box.  There are different ways documented to do this, but the most common is the "toothpick" method.  The "toothpick" method means to hold the reset button while applying power to the box.  The reset button is often hidden and located at the back of the audio/video jack connector.  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 unplugged, 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.  Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card.
 
After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box.  Don't do this unless you feel you understand how to reinstall your box's android firmware)  You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported).  It is recommended that you make a backup of emmc first.  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device.  If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file.
 
 
Mapping from CPU to uboot and dtb:
 
u-boot-s905
s905 - gxbb
 
u-boot-s905x2-s912
S905X - gxl
S905W - gxl
S905D - gxl
S905L - gxl
S805X - gxl
S912 - gxm
A311D - gxm
 
u-boot-s905x2-s922
S905X2 - g12a
S922 - g12b
 
u-boot-s905x3
S905X3 - sm1
 
Not supported or not tested
S805 -
S905W2 -
S905X4 -
S805X2 - s4
A113D - axg
A113X - axg
 
 
 
Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions.  Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box).  You can now build your own builds directly with the Armbian build system.
 
This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework.  If you are not familiar with the Armbian build system check out the Armbian developer documentation.  If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see.
 
I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well.  Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

These instructions are for Amlogic CPUs for TV Boxes. 
 
Note: If you have previously run other distributions on the box such as coreelec the below installation will not work.  You will need to restore the original android firmware before attempting the install.  coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
 
Download links:
    Weekly Community Rolling Builds:  https://www.armbian.com/amlogic-s9xx-tv-box/
    or build your own image using the Armbian build framework
 
Once you download your chosen build, you need to burn the image to an SD card.  Generally balenaEtcher is recommended as it does a verification of the burn.  Also be sure to use high quality SD cards.
 
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.  There will also be a extlinux.conf.template file to use as a reference.  You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box.  Place this line before the APPEND line as shown in the .template file.
 
Basically you need to have the correct dtb for your box.  You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware).  It is unlikely that there will be a matching dtb file for your TV box.  The idea is to find the one that works best for your box.  This may mean that you try booting with different dtb files until you fine one that works good enough for your needs.  By searching the forums you will find information about what dtbs other users have found work best for different boxes.  Because you are booting from an SD card, you can easily try different dtb files.  The dtd files are named by cpu family.  So for example dtb files for the s905x2 cpu are named meson-g12a-*.  Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case).
 
Next you need to copy the correct uboot for your box.  This is needed for how these builds boot on amlogic boxes.  There are four different u-boot files located in the /boot directory:  u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3
You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory
So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext
(See table below for more details on which u-boot to use for which cpu)
 
Once you have your SD card prepared you need to enable multiboot on the box.  There are different ways documented to do this, but the most common is the "toothpick" method.  The "toothpick" method means to hold the reset button while applying power to the box.  The reset button is often hidden and located at the back of the audio/video jack connector.  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 unplugged, 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.  Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card.
 
After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box.  Don't do this unless you feel you understand how to reinstall your box's android firmware)  You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported).  It is recommended that you make a backup of emmc first.  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device.  If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file.
 
 
Mapping from CPU to uboot and dtb:
 
u-boot-s905
s905 - gxbb
 
u-boot-s905x2-s912
S905X - gxl
S905W - gxl
S905D - gxl
S905L - gxl
S805X - gxl
S912 - gxm
A311D - gxm
 
u-boot-s905x2-s922
S905X2 - g12a
S922 - g12b
 
u-boot-s905x3
S905X3 - sm1
 
Not supported or not tested
S805 -
S905W2 -
S905X4 -
S805X2 - s4
A113D - axg
A113X - axg
 
 
 
Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions.  Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

After a fix committed this past week, these builds now work on all the amlogic based boxes I have:
TX3mini (s905w)
X96mini (s905w)
H96MaxX2 (s905x2)
TX3 (s905x3)

After a fix committed this past week, these builds now work on all the amlogic based boxes I have:
TX3mini (s905w)
X96mini (s905w)
H96MaxX2 (s905x2)
TX3 (s905x3)

@jiapei100  I think you are confusing cpu support and board support.  While the rk3229 cpu has good support in modern linux kernels (good but not perfect yet) there is no support for your specific board.  It is very different work to support the cpu than support a specific board using that cpu.  It can take months of development effort to get a board to work well after the kernel supports the cpu.  Board support entails support for all the other hardware on the board (memory chips, networking/wifi and whatever else may be on the board).  That involves both making sure that the proper drivers are available for the hardware (often since there is generally no help from the board manufacturer, it is a guessing game to reverse engineer the hardware and try to find source code for the hardware componentes) and that the dtb file is created for that specific hardware.  The dtb is the mapping between the hardware and the linux kernel.  Generally to work well you will need a dtb specific to your board.  And then finally all of this work also needs to be done with the u-boot code to again get the hardware mapped correctly so the device can boot.
 
As jock stated you should read the armbian development documentation to understand what armbian is.  For example your final question about which config file to use, doesn't make sense if you understand the armbian build system.  'current', 'edge' and 'legacy' are labels for specific kernel versions - legacy generally is the original 4.x kernel released by the manufacturer, current is the current stable version (i.e. 5.15), and edge is the bleeding edge development kernel (i.e 6.x).

What are you trying to accomplish?  Are you looking for help porting Armbian to support this device?  I ask because TV Boxes are not supported by Armbian (see https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first)  and the RK3588 cpu is a very new chip that is only partially working on mainline linux currently.  While there are people working on base support for the CPU, the significant additional work to support a specific box (with all its specific hardware) would still need to be done.
 

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box).  You can now build your own builds directly with the Armbian build system.
 
This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework.  If you are not familiar with the Armbian build system check out the Armbian developer documentation.  If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see.
 
I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well.  Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box).  You can now build your own builds directly with the Armbian build system.
 
This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework.  If you are not familiar with the Armbian build system check out the Armbian developer documentation.  If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see.
 
I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well.  Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.