View Single Post
Old 02-27-2020, 08:44 AM   #5
ezdiy
Zealot
ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.ezdiy can grok the meaning of the universe.
 
Posts: 121
Karma: 156515
Join Date: Oct 2019
Device: KT, KPW4, PB740-2
The monitor app won't boot in qemu as it expects a lot of I/O specific to this board it assumes to be present. Moreoever, real system uses multiple partitions you need to expose as mmc layout correctly - best is to just give it full NAND dump and let qemu expose that as full emmc device. A good starting point is to look at what the running system actually does and try to replicate that.

And even after that, you'll have to then manually patch monitor.app to ignore all the missing ioctls. In summary, it's not usually worth it. Its usually far simpler AND more useful (able to trace actual kernel) on a running system directly, on the device. Like most allwinner boards, it's neigh impossible to truly brick your system, even if you do something exceptionally silly, like wipe out whole emmc. The brom is smart enough to fallback to secondary mmc.

Just make sure to do the important part: Have full dump of the stock emmc at hand, to have something you can restore. Official FW update files *cannot* really repair broken partitions on their own.
ezdiy is offline   Reply With Quote