All, Thank you for the suggestions. I will definitely steer clear of constant writes to the eMMC. Thank you Telsa for learning the hard way for the rest of us!
In this case, I would opt to use an SD card to accomplish this. Would mmap or msync still be the best methods to do this? Bryan On Monday, November 18, 2019 at 8:56:53 AM UTC-7, Graham Haddock wrote: > > Hi Brian: > > It is the number of writes, not the reads that I was concerned about. > You used the phrase "send a streaming update to it as the motor moves" in > your initial email. > If you are continuously doing writes to the eMMC, then that is a long term > concern. > If this is just a short term demonstrator, then no problem. > If this is a real product, then there are anecdotal reports of users > killing the BeagleBone's eMMC after a few years of logging. > > For a real good example, (of eMMC wearout, not a BeagleBone issue) read: > https://insideevs.com/news/376037/tesla-mcu-emmc-memory-issue/ > > https://www.businessinsider.com/older-teslas-reportedly-having-issues-charging-screen-not-working-memory-2019-10 > > > If you need a small, almost unlimited write memory that remembers with the > power off, > try something like an FRAM. > > Example of a small development board: > https://www.adafruit.com/product/1897 > Spec sheet says good for a trillion write cycles. > > Beware buying a used Tesla. :-) > --- Graham > > == > > On Monday, November 18, 2019 at 8:23:55 AM UTC-6, [email protected] > wrote: >> >> Something that can be stored and called upon at boot time to be used in a >> main python function > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/804a3435-c1d4-492d-b351-f8df18f3bfa3%40googlegroups.com.
