On Mon, Apr 14, 2014 at 3:25 AM, rh_ <richard_hubb...@lavabit.com> wrote: > On Sun, 13 Apr 2014 19:07:00 -0400 > Jason Kridner <jkrid...@beagleboard.org> wrote: > > --8<-- > >> To provide the best experience of using Debian on BeagleBone Black, we >> are connecting the switch-over to an increase in the on-board eMMC >> flash storage from 2GB to 4GB, leaving more free room in which you can >> work. The eMMC is faster and more reliable than micro-SD cards, so >> this is adding a lot of value---and a little bit of cost. >> >> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C >> and they will likely cost a bit more at most distributors. This extra >> money is helping CircuitCo pay for the additional expense of the eMMC, >> but also to cover costs for ramping production to higher-than-ever >> rates. >> >> With the additional capacity CircuitCo is bringing on, we expect to be >> able to fill all end-user back-orders for the Rev B boards by early >> May and shift all production to Rev C. With around 150,000 boards on >> *distributor* back-orders, we'll be working with distributors to >> quickly accept board shipments such that CircuitCo isn't sitting on >> any units. >> > > So no more 2GB eMMC models ever? What about one with no eMMC > at all? I know there are more than a few people here that boot from > network, sdcard or usb.
Never say never, but we are unlikely to make any more 2GB eMMC models. I've been kicking around the idea of doing a kickstarter for a no-eMMC model, but I'd like to wait a month or two to see how the Rev C and Element14 boards are doing out there. > > Another thought occurred, has beagle or circuitco done any long duration > eMMC testing? How graceful will the BBB handle a failed eMMC part? > Failed as-in worn out from use not a defect. I think some people are > concerned with eMMC failures and so they don't use it or don't rely > on it. The only data we have is from the manufacturer and the community. After a year, we aren't seeing wear-out issues. The ext4 file system if fairly robust, but if writes start failing, end-user failures can occur in odd ways. If you are creating a mission-critical app that must stay deployed for many years without the ability to perform replacements, I'd encourage you to alter the eMMC contents to read-only, except for your critical data acquisition. > > -- > 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 beagleboard+unsubscr...@googlegroups.com. > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
