Jovan 0 Posted February 18 (edited) During the production, we create the master image (based on Debian 11, v3.0.20) on one tinkerBoard 2S, and then clone it on other boards. That worked for some time, until recently it stopped working, meaning that restoring the same image does not end up in working/bootable TinkerBoard 2S device. Only thing we found is that new boards are TinkerBoard 2S R1.03, but the master image was created on TinkerBoard 2S R1.02. @tooz Is there a way to make the image work on all hardware revisions? Please check the photos below for revision info: Edited February 18 by Jovan Share this post Link to post Share on other sites
tooz 54 Posted February 18 hello @Jovan, what have you added in your master image? is there anything related to /proc/boardinfo ? Share this post Link to post Share on other sites
Jovan 0 Posted February 18 @tooz We've: * installed software from official debian repository * updated default network netplan configuration * copied our binaries Nothing that would affect boardinfo. btw, /proc/boardinfo content on both boards is: Tinker Board 2S - 16GB however, /proc/boardid on "master" board is "1", but on new board is "3". Just to mention, restoring "master" image to TInkerBoard R1.02 still works properly. Share this post Link to post Share on other sites
tooz 54 Posted February 19 hello @Jovan, On 2/18/2025 at 6:23 PM, Jovan said: the same image does not end up in working/bootable TinkerBoard 2S device 1. do you have idea which stage it boots to on tinker board r1.03? (u-boot, system ... etc) 2. is it possible to collect the uart logs for us to investigate? (please see the post embedded for the how-to on using serial dongle) 3. have you tried using the os from the official website and if so does the same issue happen? (it's worth noting that there's a cap on the board that keeps the board in maskrom mode if not removed) Share this post Link to post Share on other sites
