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!

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!

@Vinicius Guastala I agree with @fabiobassa, thanks for the very detailed post of your board and broad description of the behaviour.
I would suggest you to erase the internal flash and try to boot from sdcard with this armbian image. It is an "experimental" image with opensource Trust OS; many recent boards are having issues with proprietary trust os, possibly yours has similar issues, so you could give a shot to this. By the way, the serial log output would be indeed very handy if you have the chance to find the serial port.
 
Beware also that armbian (and multitool) use 115200bps baud rate for the serial, while proprietary software uses 1.5Mbps baud rate!