CSC Armbian for RK322x TV box boards

[Virgilio Junior]

Quote

 

Now I run MultiTool, select "Jump Start," and shut down the rk322x.
I burn my Armbian .img to the USB stick with: sudo dd if=/root/Armbian_24.2.5_Rk322x-box_bookworm_current_6.6.22_minimal.img of=/dev/sdb conv=fsync bs=4M status=progress

But when I turn on the power, the blue LED shows init (the same as with MultiTool), but the video doesn't appear again 

 

hahahha  I took my pendrive out of the OTG port and put it in the normal USB, surprise:

Tkys Team ❤️

[Igor]

22 hours ago, jock said:

I see users.armbian.com is serving the certificate for stpete-mirror.armbian.com

 

I had to rebuild server and this was not fixed yet. Temporally location https://stpete-mirror.armbian.com/users.armbian.com/

[jock]

1 hour ago, Igor said:

I had to rebuild server and this was not fixed yet. Temporally location https://stpete-mirror.armbian.com/users.armbian.com/

 

Thanks!

 

For @Victor Picinin the temporary working URl is https://stpete-mirror.armbian.com/users.armbian.com/jock/web/rk322x/armbian/beta/Armbian-unofficial_24.11.0-trunk_Rk322x-box_noble_current_6.6.56_xfce_desktop.img.xz

[Aroldo Bossoni]

Is the repository https://users.armbian.com/jock/web/rk322x/ also offline for you?

No need to authorize this post, I've already found the answer, thank you!

Edited Thursday at 02:27 AM by Aroldo Bossoni

[Aroldo Bossoni]

Hello everyone!
 

I'm willing to develop a script that automates firmware, u-boot, and ROM compatibility testing with the boards via OTG.
 

I've thought of a workflow something like this:

1. Download a list of files by type from several different sources.
2. Extract files from pre-built images, ROM, loader, u-boot.
3. Check for duplicate files by size and checksum.
4. Apply and test in stages: ROM, loader, u-boot, kernel, rootfs, network, video.
5. Log what worked and what went wrong.
6. Since this process can take hours, emit a beep when user interaction is needed.
 

What I need help with from you:
Is this idea feasible?
Will it produce results and facilitate the implementation process on rk322X boards?
Can it be reused and adapted for other boards?
 

I have little experience with ROMs and ARM firmware, but if it's feasible, I intend to create a public repository for the community to help me with the development.

Thank you for your attention!

[Alex83]

I would love to get this or support with the devices I own.

 

I think we should continue developing Mini-AndroidTV-PCs as easy as possible and give that junk devices a sensful feasible life.😃

[jock]

@Aroldo Bossoni

 

The optimal would be understanding the reason why the watchdog triggers, but could be a difficult task without a hint because of the closed source proprietary trust os.

 

The easiest thing is to provide armbian images with the opensource trust os rather than the proprietary, which is totally feasible because it just requires to swap a file in the armbian build scripts. That would blow the issue away, but unfortunately the proprietary trust os provided DDR scaling and virtual poweroff. The latter is a seldom used feature, but the DDR scaling provided a dramatic improvement in performance and it is hard to give up on that.

 

Swapping the things at runtime is not savvy: when u-boot updates, the proprietary trust os will be reinstalled overwriting whatever you put in there.

 

I would be happy with opensource Trust OS and no runtime DDR scaling, but stil having it at a fixed decent rate (660MHz, instead of the default 330MHz), but some boards do not boot at all when they are instructed to boot at 660MHz.

[Aroldo Bossoni]

@jock

I didn't know the problem could be the watchdog, nor did I know about the existence of the open-source Trust OS.

Do you think it's feasible to include the open-source Trust OS in this testing process, or does the open-source Trust OS solve all these problems?

My idea wasn't to change it at runtime; my idea is to flash, reboot, test, save the result, repeatedly until all possible combinations are exhausted.

[Mateus Lima]

Hello, idk if this the right place to ask, but, I'm really struggling to get a working driver for the sv6256p, I can't find a repository that compiles on kernel 6.X. My question is, where is the driver source that builds for the rk322x uses? I want to compile it on my installation. I already tried moving the driver files from a rk322x build to my installation, but it didn't work.

[LoSpo]

I found a TX box X96 Mini with rk3228 chip and I try to boot with multitool but it is stuck with a red ligh.

I try multitool and multitool2, with no success, can someone tell me what I am doing wrong ?

Thank you

The multitool i used are from here

i used balena etcher to burn the image

I also try to short pins on eMMc (around 45 times...) but nothing works from me.

Now i order a male-male cable on amazon.

 

edit: added front/left photos

Edited yesterday at 03:11 PM by Francesco Spossati
attach board photo/added details

[NiTr0]

I've checked performance of my old rk322x-based box (H2O with 1.5G RAM/4G ROM) and compared it with fresh, h618-based. sysbench shows that rk322x is ~20x times slower in CPU (rk322x - 39 events, h618 - 700 events) and 6x times slower in RAM operations (216MB/s vs 1333 MB/s). in threads test rk3222x is just less than 2x times slower (4317 events vs 7563 events).

are these values OK? or maybe something is mistuned?