Hồng Thất Công
Đả Cẩu Bổng Pháp
How do I make Pyra OS boot from a ext4 formatted SD card?
Can a devboard be used fully for a few years once the OS is fully stable or would that be unwise?
As to the exact method, not sure. aTc is the one that generates it.Could somebody tell us, how this image is generated at the moment? I asume this is kind of a manual process?
Personally on the move to buy a devboard or two (one to pass around locally) since this is cheaper than a standalone dev. Pyra, but wouldn't know where to start (resource wise, loading OS and whatnot) since I've no experience with such devices before. Pointers please?
Could somebody tell us, how this image is generated at the moment? I asume this is kind of a manual process?
Image building is done completely automated using multistrap.
Configuring is left to the package manager as much as possible, although some things have to be set up using external scripts (mostly stuff that normally gets done by the debian installer).
http://dev.pyra-handheld.com/index.php/p/pyraos-build/source/tree/master/multistrap
Which script do you mean.
There are a few, one that gets run right after multistrap has finished downloading and extracting the packages, which sets up a few things the next stage expects to be there.
The next one has to run on arm hardware to configure all the packages.
If the rootfs is beeing built on arm hardware, it uses a chroot (systemd-nspawn actually) to jump into the rootfs and configure everything.
If it's not beeing built on arm hardware, /sbin/init is replaced with a link to the config script (the init system doesn't fully work when all the packages are unconfigured anyway), which then runs when the rootfs is booted on the device for the first time. That script then resets sbin/init at the end.
That second method has the disadvantage that the first boot takes about 7 minutes longer, so I build everything on the devboard.
Everything in the rootfs is then ready for the first proper boot. It's now a fully installed debian system, except that there's only a root user account.
The pyra first-run-wizard is run using a normal systemd service, and takes care of adding users, configuring timezones/languages and other things like that.
http://dev.pyra-handheld.com/index....rce/tree/master/debian/pyra-first-run.service
Very nice, very clean Debian rootfs. Good job, guys! I wonder if it would be possible to start developing Pyra software for the system now? Probably something like a QEMU build that can somehow emulate most, if not all of the hardware on the Pyra would be a good idea, or maybe we can all still wait for the hardware. Ahahaha. I'm impatient, can't ya tell?
What would you run in QEMU out of curiosity?
I've always had this issue with it.I just fired up this OS on my Pandora given my devboard has ended up in the graveyard and have found the touch screen / nubs don't respond anymore
Well Wally has the IGEP OMAP5 board, not the Ti OMAP5 EVM board. If you're talking about my board, yeah it seems that way... I think Wally's issue seems to be related to the SDRAM, mine I don't get any kind of serial prompt to indicate what may be the issue. Using a scope I can see some clocks still running, I need to do some deep debug work on it.Your EVM is also kaput ?