By default there will be a working OS on the internal memory.
Most likely the same step as the Pandora.At what stage in the manufacturing process will the OS image get written?
I doubt they would bother with this even with bigger clients. The Pandora it's done by a Global Components employee during the testing phase, they install the OS to the NAND memory (eMMC in the Pyra's case) along with test everything out.I'm sure that the memory manufacturers will be happy to do it if you order a few million chips - but how does it work for smaller projects?
Flashing from SD card is typically how it's done... It doesn't care if the OS is working on it or not...Wasn't it possible to boot (or flash NAND at least) from SD card on Pandora even without working OS in the NAND? (ie. unbrickable feature) I think it's done by holding a different button combination during start up. I'm guessing Pyra should be similar.
There's also this
How good are you at shell scripting? Honestly aTc has been wanting someone to make a better First Start Wizard. Disk Encryption is likely complicated on a device that uses u-boot for boot management.Also, how easy to make your own taste of the installer?
Well, I know it works on the Internet Cube and it is also an ARM platform booting from a micro-SD card, so I guess it should be possible. Maybe someone who feels at ease with shell (i.e. not me, sorry) could have a look at the repository.Disk Encryption is likely complicated on a device that uses u-boot for boot management.
Debian dont have any "default" all it knows is : update-alternativesIs there some "default" for debian?
Disk encryption should just work, getting an encrypted disk to boot from u-boot is what is somewhat challenging.Well, I know it works on the Internet Cube and it is also an ARM platform booting from a micro-SD card, so I guess it should be possible. Maybe someone who feels at ease with shell (i.e. not me, sorry) could have a look at the repository.
AH! I'm going to delete this, thanks for reminding meThere's also this
There is a U-boot directory in the repository so I thought it used uboot too (well I thought it did before I checked but the directory is actually there so I am quite confident it does)Disk encryption should just work, getting an encrypted disk to boot from u-boot is what is somewhat challenging.
It's not an issue that it can't, just not something that can easily be enabled in a First Start Wizard as all of that needs to be enabled even prior to the disk image to be written to the eMMC.There is a U-boot directory in the repository so I thought it used uboot too (well I thought it did before I checked but the directory is actually there so I am quite confident it does)
Oh I think I am starting to get your point (please tell me if I am wrong, I'd like to get this one although my skills regarding this domain are still at beginner stage, growing slowly) : the issue is because of the installer, while the InternetCube (or any RaspberryPi-like board as far as I know) boots directly on the SD, right ?It's not an issue that it can't, just not something that can easily be enabled in a First Start Wizard as all of that needs to be enabled even prior to the disk image to be written to the eMMC.