SteeMan
-
Posts
1921 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
Moved your post to the Rockchip CPU Box forum. I do not work with rockchip based boxes myself, but there are a few people who do in this forum that may be able to provide you some guidance. The RK3188 is an older 32bit cpu. A lot of the effort recently around here is support for more recent 64 bit based cpus.
This post was originally posted to the mega thread: https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7
-
Moved your post to the Rockchip CPU Box forum. I do not work with rockchip based boxes myself, but there are a few people who do in this forum that may be able to provide you some guidance. The RK3188 is an older 32bit cpu. A lot of the effort recently around here is support for more recent 64 bit based cpus.
Having said that, I will point for reference to: https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7/page/6/?tab=comments#comment-117335 which appears to be the latest builds referencing the 3188. I am not aware of general instructions for using the balbes 32bit builds, but I haven't read the whole thread regarding them (https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7)
-
@Youness Bouamal welcome to the Armbian forums. First off I want to point you to the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
As you will see in that FAQ, wifi is not something that generally works on the TV boxes. And even if it does work, the cheap built in antennas don't provide good coverage. To get better wifi support you likely would need the more expensive TV boxes with external antennas. So while you might be able to get something to work, most likely using external usb wifi adapters, you probably would be better off buying a purpose built device that would likely cost less.
If your goal is to just experiment and see if it can be done, we would love to hear back on your findings for your specific box.
.
Finally you mention X96Q box. From what I know the X96Q uses the Allwinner H313 cpu not the Amlogic S905W. And those Allwinner chips (H313 and H616) are new chips that don't yet have armbian support, so that would be a non-starter. But the manufactuers are all the time reusing box names for different hardware, so you certainly could have something labeled X96Q that contains an amlogic cpu. (That is one of the problems supporting TV boxes with armbian is that two identical looking boxes can have completely different components).
-
@as400 I was going to point you to read the TV Box club FAQ entry on overall status (https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first)
Honestly you have more working than most users as wifi and ir are not something I would expect to be working for you. Since you are running Amlogic boxes, you should be aware that balbes150 stopped his support of that CPU back in October. While he is still involved in Armbian he has mostly gotten out of supporting end users of the TV boxes. You were actually fortunate to get a response from him directly as that is rare these days in the TV box forums.
I however have a question for you. Your original post didn't mention which boxes you have running. If you could take the time, it would be appreciated if you could post your results for others. I have recently started gathering information of working boxes in a consistent standardized format: https://forum.armbian.com/topic/16814-template-to-report-a-working-tv-box
-
To answer your questions, please go to the TV Boxes FAQ and read both:
Status of Armbian on TV Boxes - Please Read First
Installation Instructions for TV Boxes with Amlogic CPUs
-
Moved to correct forum
-
Please describe what steps you are performing. The log would indicate you are booting with dtb/amlogic/meson-g12b-odroid-n2.dtb, not the dtb you think you are.
-
@Joel Mercedes First I want to draw your attention to the following information so that your expectations are properly set: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
Second, what build did you install and where did you download it from? I am not aware of a build for amlogic TV boxes that has kernel 5.9.7 in it.
-
Moved post into its own thread as this is not related to the thread it was originally posted in.
-
Moved post to the correct forum. If you want help, please provide information on what exactly you have tried, what build you are working with, what dtb's you have tried, what installation steps you are following, etc. Also please read the following post to set proper expectations: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
-
Adding a link to the following thread that talks about hardware differences on some newer? x96 mini models that require changes to the dtb: https://forum.armbian.com/topic/15665-new-x96mini-hardware-upgraded-but-no-emmc-found
-
@robertoenr FYI, the information in this thread: https://forum.armbian.com/topic/8728-s905w-boot-process
is helpful in learning the boot process (see especially Jock's post). Jock maintains the builds for rk3228/rk3229 based TV boxes. His approach is more of a 'pure' armbian environment than the balbes approach of reusing the android boot loader, but his explanation of the process is good.
-
@robertoenr FYI. I just installed into emmc on my Tx3 mini and it boots fine using u-boot-s905x-s912 copied to u-boot.ext along with meson-s905w-tx3-mini.dtb
-
8 minutes ago, robertoenr said:
But since the "non-booting-black-screen" issue only happens once installed on eMMC, how can I test it by using SD/USB?
That wasn't at all clear from your posts that that was the case. So you have a working SD install, and when you run install-aml.sh to move that install to emmc, that is when you are seeing this issue?
-
@robertoenr Based on what you described you have done, you a doing a lot of work you don't need to.
First off, the Oct 14, 2021 Balbes images already have the u-boots from hexdump for the s905x (and therefore s905w) cpu. The one you downloaded and are trying is the same as what is already in the image. My comments above all talk about the s905x2 and s905x3 which don't have hexdumps u-boots in the balbes images.
.
My strong recommendation is to do all your testing on an SD card install, get that working the way you want, then copy the working environment from SD card to emmc using the install-aml.sh script. Experimenting with u-boots and kernels directly in the emmc environment is asking for a bricked box, as any number of simple mistakes can lead to the box not booting correctly. If you make those same mistakes on and SD card, you simply pop it into another machine and edit/undo what you did and try again.
.
-
-
4 hours ago, lgranie said:
If I want to boot from emmc, I have to rename it to u-boot.emmc?
No you don't need to do that, the script will do whats necessary to take the working SD environment and copy it to internal emmc. And that involves among other things creating a file called u-boot.emmc
-
4 hours ago, lcapriotti said:
tks! There are two possible candidates: install-aml-s905-emmc.sh and install-aml.sh, which one shall be used on our box?
The install-aml-s905-emmc.sh is for boxes running the s905 cpu
The install-aml.sh script is for boxes running all other s905?? cpus (s905x,s905w, s905x2, s905x3, etc)
I don't have any s905 based boxes so I have only ever used the install-aml.sh script for my s905w, s905x2 and s905x3 boxes.
-
@jbolanosg I haven't had time to test hexdump's u-boots much yet. But the general idea is that you replace the /boot/u-boot.ext file with the appropriate hexdump uboot (g12a-u-boot.bin (s905x2) or sm1-u-boot.bin (s905x3)). Once you verify that works with a 5.9 kernel, then you can attempt to use a 5.10+ kernel. The testing I have done in the past was all from SD card.
BTW, the ethernet issue I was seeing I believe is this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/amlogic?h=v5.11-rc7&id=19f6fe976a61f9afc289b062b7ef67f99b72e7b9 which was just fixed in 5.11.0-rc7, but hasn't yet been fixed in 5.10.y. I am in the middle of testing that this does or doesn't fix my ethernet issues under 5.10
-
@Janaboy What version of the kernel where you previously running? If you were running an old vendor legacy kernel, there are enough differences between the legacy kernels and mainline kernels that it could explain the dtd issues you are seeing. As for the dtb's the general idea is to try them all and use the one that works best for your hardware. In your case try all the meson-gxbb* dtbs.
-
10 hours ago, Janaboy said:
btw is that normal that aml_autoscript.zip size is 0?
yes that is normal
-
8 hours ago, lgranie said:
I did not manage to run a 5.10 packaged kernel on my x96max.
The chain loaded u-boots for s905x2/x3 in the balbes 10/14/2020 build do not support kernels greater than 5.9, due to the changes in the 5.10 kernel. Also there is a change in 5.10 that breaks ethernet on these cpus as well in some cases.
To fix the u-boot problem you should use the following u-boots from hexdump: g12a-u-boot.bin (s905x2) and sm1-u-boot.bin (s905x3) from https://github.com/hexdump0815/u-boot-misc/releases/tag/200926-01 (renamed to u-boot-ext).
If you run into the ethernet issue, that should be solved by reverting with this patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/amlogic?h=v5.11-rc7&id=19f6fe976a61f9afc289b062b7ef67f99b72e7b9 (This fix was just rolled into 5.11.0-rc7 this past week, it hasn't made it into 5.10.y yet)
I am in the process of testing all of the above to verify that I can get 5.10 and higher kernels working on my own s905x2 and s905x3 boxes. So the above may or may not be correct until it is verified.
-
On 2/8/2021 at 12:15 PM, Daniel Cagarrinho said:
Anyone can put the vfd working normally??
Mine was stuck with the message “boot”
it is possible to put the clock back working??
I'm not aware of anyone that has done this successfully.
-
@lcapriotti The process for installing a TV box image into emmc is to run the appropriate script in the /root directory.
Single Armbian image for RK + AML + AW (armhf ARMv7)
in General Chat
Posted
I am closing this thread. With balbes no longer working on a unified single kernel/build for all CPU architectures (rockchip, amlogic, allwinner) (especially with his no longer supporting amlogic cpus), further questions or issues would better be created in the cpu family specific subforums: Rockchip CPU Boxes, Amlogic CPU Boxes, or Allwinner CPU Boxes.