SteeMan
-
Posts
1456 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
2 hours ago, xNiux said:
5s/10s or more (with armbian boot sdcard inserted) : The LED of box is blinking Red 1s, Blue 3s (No screen, I think it reset 1s every 3s).
This looks like you have successfully enabled multiboot. It is trying to now boot from the SD card. Apparently unsuccessfully. By enabling multiboot it will try to boot from the sd card if one is present.
Now that you can get it to try to boot from the SD card, you need to look at your setup on the sd card to get a successfull boot. From what you have stated above, it seems that you are doing the setup steps correctly according to the instructions in the FAQ (https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus). Now you just need to find a compatible dtb file for your box (if one exists). The general recommended approach is to try all the dtbs one by one for the same cpu as your box has (if you don't already know of one being compatible).
You mentioned that you tried meson-g12a-x96-max. Was this based on a successful report by some other user of your box?
-
Does the box correctly boot to android currently?
If so, when using the toothpick method, how long are you holding the reset button? You might try different lengths of time, from a few seconds up to 10 seconds. I find it takes about 5 seconds for the boxes I have. Don't hold it too long though or you end up in android recovery.
-
I don't think that is the update app that supports the multiboot method, given the error messages you are getting. I think that is an android update tool. You will need to use the "toothpick" method to enable multiboot. Most boxes hide the reset button at the back of the hole for the av plug, but others have a specific hole labeled for the reset button. (A few boxes don't have any reset button however)
-
What update menu? Be specific, don't make me try to guess.
-
3 hours ago, Voidbert said:
Getting the broken multitool link working again (https://users.armbian.com/jock/rk322x/multitool.img.xz -> https://users.armbian.com/jock/rk322x/multitool/multitool.img.xz) on the information page (https://www.armbian.com/rk322x-tv-box/).
I think this rk322x-tv-box page on the website is what should be removed. I'm not actually sure why that page exists. There generally aren't pages on the main website for specific tv boxs. There must be some historic reason this one exists that I don't know about. @jock would you be opposed to getting rid of that page, leaving the forums as the sole source of information?
-
On 6/5/2022 at 2:51 PM, xNiux said:
3- I start the stock system, update with the zip on the sd card. And after reboot, I have the error message ....
What do you mean by this step?
-
The only pointer I have on that tool is to try different versions. I have in the past found some firmwares that only load with specific versions of the amlogic tool
-
When you say 'flashing' what do you mean? What are you using/doing exactly.
-
14 minutes ago, ning said:
so the only solution is multiboot. and I will keep vendor OS in emmc, thus I can develop mainline components reference to it.
multiboot doesn't mean you can't still have your os in emmc. That is what the /root/install-aml.sh script does in the tv box builds from balbes150 (copies the install from sd to emmc while preserving the native vendor u-boot on emmc). The concept is to reuse the vendor u-boots which are device specific (dealing with memory, storage, etc) (since there are tens if not hundreds of different amlogic tv boxes creating uboots for each is impossible) while having only a few generic chainloaded u-boots that are cpu specific bridge to loading the kernel.
It is a bit tricky to preserve the vendor u-boot while overlaying the rest of the os into emmc, but generally balbes150's scripts work on most environments.
-
22 hours ago, ning said:
fatload mmc 0 0x01000000 u-boot.bin go 0x01000000 # use: mkimage -A arm64 -T script -O linux -d s905_autoscript.txt s905_autoscript.scrthis is chainload?
and before that, need store bootcmd to env
setenv bootfromnand 0 setenv bootcmd "run start_autoscript; run storeboot;" setenv start_autoscript "if mmcinfo; then run start_mmc_autoscript; fi; if usb start ; then run start_usb_autoscript; fi;" setenv start_mmc_autoscript "if fatload mmc 0 1020000 s905_autoscript; then setenv autoscript_source mmc; autoscr 1020000; fi;" setenv start_usb_autoscript "if fatload usb 0 1020000 s905_autoscript; then setenv autoscript_source usb; autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then setenv autoscript_source usb; autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then setenv autoscript_source usb; autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then setenv autoscript_source usb; autoscr 1020000; fi;" setenv upgrade_step "0" saveenv sleep 1 rebootI don't know what code you are referencing here. This is not the code that is part of the armbian TV box images that balbes150 produced and I try to support through these forums. If you are looking for input from an armbian forum, please be using armbian code. You can find the download links for the code that in the TV Box FAQ post: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
-
Nothing there actually says what CPU you have, "S905 series" doesn't mean anything specifically. But from what I do see, I would guess you have an s905x or s905w. The board type is p212 which is the reference board for the s905x. So I would recommend you first try using the u-boot-s905x-s912 uboot and the meson-gxl-s905x-p212.dtb
The best way to know what cpu you have is to remove the heatsink and look at the markings on the chip
-
Are you sure you know what CPU you have? You keep mentioning s905 but the dtb you mentioned is for a s905x CPU (gxl*).
-
If you ran coreelec from an SD you will need to reinstall android firmware. Resetting is not enough. The process of running either Armbian or coreelec changes the uboot environment on emmc in incompatible ways, that you need to get back to a fresh environment by reinstalling the original firmware before attempting to run Armbian.
-
Generally, you just need to try them one by one. I would focus on the glx* ones.
Note since you mention coreelec, if you have previously I stalled coreelec you will need to reinstall the android firmware, before attempting to install Armbian (as is described in the instructions I linked to above).
-
-
But with the multiboot strategy you are running a mainline uboot (chainloaded). I run mainline kernels on my amlogic based boxes (including upto the latest rc - I'm running right now 5.19.0-rc5 on one box).
-
I guess I would start by asking what is your goal with this TV Box? Are you looking to be able to build a full firmware (potentially using armbian build framework) for the box to install on multiple boxes of this type? or is this just a one-off box to experiment with and you want to get a modern kernel running on it?
If the latter, I would recommend going down the multiboot path that balbes150 created for these amlogic boxes (see this thread for some discussion on that: https://forum.armbian.com/topic/19004-trying-to-learn-more-about-u-boot-for-amlogic-devices)
This path leaves the vendor u-boot in place and chainloads a modern u-boot bypassing the risk of bricking the box by installing a non-working u-boot on emmc. In general this path also has you working from sdcard storage (although balbes150 had scripts to copy a working sdcard environment to emmc if you wanted to run from emmc).
The challenge as I understand it with amlogic tv boxes is that amlogic always boots from emmc if present which presents a risk of bricking when testing different u-boots.
-
I've moved this post to the TV Box club forum area.
Note that Armbian does not support TV Boxes.
Please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
Also note that I'm not aware of anyone working with hisilicon based boxes, all of the limited work is mostly on rockchip and amlogic cpus with some on allwinner.
-
@tripole I moved your original post to a new thread under the General Chat sub-forum. Then added a long explaination on why or why not your post may or may not be appropriate. Then another moderator hid the whole conversation. I have just unhid that for the time being so you can see the discussion about your content. I will however hide your repost here.
-
As far as jocks other points, I believe users are going to be confused wherever the tv box forum is located. But it isn't difficult as a mod to move a post to the correct location. I already do that for a good number of posts in the current format.
-
I forgot about the overview feature. That certainly would be missed. But I would think it should be possible to somehow recreate that functionality. If you don't know, the club overview feature is a simple search that shows the most recent posts in the entire club. Very useful for jock and myself to catch up on responding to posts in the tv box area.
While the forum has a similar feature that shows everything new for the entire forum I don't know of a way to restrict it to a subsection. Of the forum.
-
In general I think this is a good move.
Specifically I'm assuming your proposal is to replace the TV boxes link under "Unmaintained (CSC/EOL/TVB) / Other" with the content from the TV Boxes Club.
-
Does wired ethernet connection work?
Please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
Note: I have about 10 amlogic based tv boxes, including 4 tx3 minis and I don't have wifi working on any of those boxes. You should not expect wifi to be working. If you get it working you are lucky.
-
Please provide more information on what you have done. What build have you installed (exact file name), where did you download if from, what instructions have you followed to install.
what is this device???
in Amlogic CPU Boxes
Posted
What are you trying to accomplish? Saying you tried flashing different firmwares, doesn't tell us much about what you are trying to do. What is your goal for this box?