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.

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!

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!