Zq01-v1.3

[Vinnie Frevert]

audio kees Perhaps you can install armbian in eMMC and libreelec from sdcard/USB stick. It will work because armbian bootloader is capable of booting from several devices; altough it is quite strange libreelec bricks your board.

@audio kees

for me too is strange libreelec is bricking your board. Sure this don't happen on emmc and old nand with legacy kernel , but you have ecmp so maybe devil is in details.

On this same thread and on libreelec forum there is a man @ilmich .

He is the libreelec' s MASTER (lol), he is a friend and always prone to answer and find solutions.

Let's ear directly from him his opinion. So I find usefull now you move on libreelec forum since here is more specific to armbian, linux and hardware problems related, all problems that seems to be solved

Anyway I guess it should boot and work smoothless even libreelec on this ecmp , but I'm not the one that can answer

@audio kees if your need is just play video at 4k you probably won't go with armbian but rather with libreelec; if your goal is playing music you'd probably want to go with volumio either. Armbian is suited mostly for linux desktop replacement and server-like tasks.

Much better if you go with properly supported Single Board Computer (SBC) and, as said, you'd better take a look to what libreelec suggests as preferred hardware (probably Raspberry Pi) if you want/need an out-of-the-box working system.

@audio kees You really need to take your questions elsewhere. You are off topic for this thread. Please take your libreelec questions to to their support channels. If you want to talk armbian on raspberry pi then open a new thread in the proper location in these forums.

Tv box mxq pro 4k 5g, pcb zq01-v1.3 rk3228a and kingston 08emcp08-el3cv100, wifi esp8265.

Multitool boots properly but after a minute the box turns off(Libreelec has same behavior).

This minute is enough to erase emms but not enough to flash img on board and bricks the device.

Rkdeveloptool works great in maskrom mode and I managed to burn loader and image.

I tried Armbian_21.02.1_Rk322x-box_buster_legacy_4.4.194.img , Armbian_23.08.0-trunk_Rk322x-box_buster_edge_6.5.5_minimal, Armbian_23.11.1_Rk322x-box_jammy_current_6.1.63_minimal and self compiled Armbian-unofficial_24.2.0-trunk_Rk322x-box_bookworm_edge_6.7.5_minimal on emmc and sd card with no success.

Every time booting process stops and every time on different point despite of so many reboots, and after a minute the box turns off.

I noticed with fresh written on emmc Armbian_21.02.1 , Multitool works properly (libreelec too). So I decided to try Armbian-unofficial_24.2.0-trunk on sd card and after more than 20 reboots I managed to set root password and Armbian works fine on sd card. Multutool , Armbian and Libreelec works from sd card on this strange decice only if there is partitision with filesystem on emms, othervice it turns off after a minute.

I tried to install Armbian from sd card to emmc with armbian-config with no luck, box does not boot from emmc and from sd card again turns off after 1 minute.

Any suggestions how to install Armbian on internal flash?

Why Armbian needs so many reboots to reach finish point?

It is not power or thermal issue, if there is partition with filesystem on emmc, Multitool Armbian and Libreelec works from sd card flawlessly.

I have resolved problem running Armbian on sd card, I still can't install Armbian on internal emmc.

I tried different overlays: cpu-stability, emmc, emmc-hs200, ddr3 and other with no success.

Probably that is wrong settings of emmc, I will check internal flash with mmc-utils.

The issues regarding the automatic shutdown after 1 minute are probably related to a piece of closed source blob (the "Trust OS"). Most of the time it never causes issues, but on some systems it looks like it triggers this automatic shutdown or suspend state for unknown reasons.

Normally you don't need to do all this hassle to install armbian, neither there is the necessity for any reboot. It is the combination of the Trust OS and your board that triggers this unexpected behaviour.

So if I understand correctly, you flashed a piece of Armbian 21.02.1 on the eMMC, then you were able to boot armbian 24.2.0 from sdcard and it tooks 20 reboots to finally reach the user creation phase and login, but once you get there, it finally works for and indefinite time and does not reboot/turn off?

So if I understand correctly, you flashed a piece of Armbian 21.02.1 on the eMMC, then you were able to boot armbian 24.2.0 from sdcard and it tooks 20 reboots to finally reach the user creation phase and login

That's right.

I use multitool only to erase internal flash and then use rkdeveloptool to flash loader and image as it is described in first page.

The device boots from sdcard in both cases, blank or flashed emmc but if there is a proper partition on internal flash Armbian works right, otherwise turns off(I heve tried to erase emmc and create partition with fdisk tool in Armbian, and OS works properly ). Armbian boots from internal flash too.

I think booting issue and turning off after minute are two different cases. Turning off probably is some kind of interaction between RAM and EMMC into EMCP chip itself(kingston 08emcp08-el3cv100).

This is dumped android firmware:

-KCvGS47SAO8tY1YDvCHDv6YWIWRP/view?usp=sharing

I took a look to the device tree and found something that could be somehow intersting. I'm not absolutely sure it may be related to your issue, but there the device tree contains this gpio switch which is not usual:

it maps to gpio3 bank and pin 17 (PC1, in the rockchip documentation). That string says that the pin is active low, it means that when it is 0, the poweroff is active; when it is 1 the poweroff is inactive.

With this command (to be run as root), you can see how the pins is configured. In my case, the pin is set to output at 0 level, but since it is not wired on my board it just does not do anything. Could you please execute the same command on your board?

Now you can also do another test: erase the emmc and verify you still have the shutdown issue. If that is the case, it may be interesting to see what is the pin state in that condition and if switching its condition causes the weird behaviour to stop or does not change anything.

Nothing happens when I change direction and value.

When I do software reboot the direction and value remain the same but if I do power reboot the direction and value return to their original state.The issue remains, system still switching off.

But I noticed that deleting the flash partition, the system works normally. I used to think that the system was working because it founds a correct partition in the flash, but when mmcblk2p0 is no longer there,

remains only that part of the armbian image before the root file system, which is before sector 8192. Blank emmc or flashed with newer armbian image cause problem but flashed with armbian 21.02.1 the OS works.

The more I read the more I think it is related with the trust os: when you leave the first 8192 sectors from armbian 21.02.1 on the eMMC, you actually leave all the boot pieces there. The boot process is made of 4 pieces: ddrbin, u-boot SPL, Trust Os and u-boot.

My best guess for your problem is that armbian 21.02.1 bootloader still had OPTEE opensource Trust OS I was using in the past (see here for source code); it is the same base that also rockchip uses for its Trust OS, but rockchip proprietary trust os has some closed-source code that is added on top for added features like DDR clock scaling and virtual poweroff and who knows what else... Nowadays I use the rockchip proprietary optee for those added features, but very seldom it causes issues like yours and it is impossible to debug because it is closed source.

@jock

I do agree with you, this is another case of " frankenstein needed! : some pieces from one, other pieces from others ..

Not very clean solution but in might work

Since those days when we starting case study of 322x shutdown and reboot issues were quite always, if not alaways , related to TRUSTOS so using the " legacy-proprietary" trustos and uboot for booting and then pass control to main kernel and rootfs could ipothetically work

Now when the box does not turns off I was able to add overlays in armbianEnv.txt ( emmc-hs200 and ddr3-800) and armbian booted at first time.

Now I have armbian on internal flash and can install octoprint server.

When we now see thats is a moreover need part maybe it is also a good idea to integrate a point in Multitool where a this 2MB part is flash to emmc or nand to replace the bootloader from normal Armbian image

I can reinstate the opensource optee as Trust OS, which seems to be more compatible, but we lose DDR clock scaling - that increases a lot the general performances - and virtual poweroff from the closed source rockchip Trust OS. Which one to choose?

3a8082e126