Thanks John. I've read the two articles. I have no idea of the endurance of my SD card, but it seems that I will be better off using it as the boot device in a development environment as it can be replaced when the time comes, where as the eMMC can't, and development involves a lot of file creation and deletion over time, at least the way I do it :-) Does that sound right to you?
I guess I need to design and build my software too so that it minimizes file I/O. Is that standard practice for linux programs that I might download with apt-get, or are there some that I should avoid for that reason? I don't know what The Deck is John, but I doubt if I'll ever need 12 GB. I just happened to have a 16 laying around from another project. Hard to imagine a 12GB app on a board this small :-) Thanks for the inputs/ On Friday, October 31, 2014 2:06:46 PM UTC-5, john3909 wrote: > > The answer is it depends on the SDCard you are using. Compare the number > of write cycles for your SDCard to that of the eMMC. If the number of write > cycles is the same for both devices, the eMMC will fail first because of > the smaller spare capacity given the use of wear leveling. To reduce the > possibility of write failure, increase the size of your storage. > > http://en.wikipedia.org/wiki/Flash_memory > http://en.wikipedia.org/wiki/Wear_leveling > > Regards, > John > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
