Forum > Embedded
RaspberryPi Zero2W
dbannon:
I find that depressing. No wear leveling for eMMC "laptops" ? These thing dominate the small laptop market. I still have little 10 year old Netbook, I have replaced the screen (I stood on it), the hard disk (with a standard SSD) and memory. Its no power house but its my 32bit test platform ! I'd buy a new version of it if available but would not touch a eMMC driven box.
I guess I'd think the same way with a RasPi clone but it is a different price point .....
EDIT: No, I think I might be a bit too critical.
NAND flash storage is not a simple read/write data medium. For reliable use, several algorithms should be implemented: NAND block management, garbage collection, error control and wear levelling. Modern NAND flash is managed, with algorithms on the storage device, not implemented in the host processor.
https://www.kingston.com/en/blog/embedded-and-industrial/emmc-lifecycle
Davo
Mark20:
Seems a problem with no way out... at least for solid long last solution...
May be we have to change the way we program, bringing all possible in Ram, and commit to flash only when really necessary...
MarkMLl:
--- Quote from: Mark20 on December 29, 2023, 09:24:53 am ---Seems a problem with no way out... at least for solid long last solution...
May be we have to change the way we program, bringing all possible in Ram, and commit to flash only when really necessary...
--- End quote ---
Which doesn't really help if the RAM isn't protected by ECC bits.
However I repeat my earlier position: eMMC is supposedly protected by at least some internal "intelligence", but that didn't help the Tesla owners.
MarkMLl
dbannon:
--- Quote from: Mark20 on December 29, 2023, 09:24:53 am ---Seems a problem with no way out... at least for solid long last solution...
May be we have to change the way we program, bringing all possible in Ram, and commit to flash only when really necessary...
--- End quote ---
Mark20, if you are doing a small project that, once done will just run in the background, you will probably be alright. Just keep in mind its better to write dribbling data to somewhere other that the sdcard, even a USB key.
If you are using the Pi as an on going development platform, then you are taking more significant risks. Its up to you to work out the impact, on you, of those risks. Note -
[x] Almost all risks are mitigated if you mount some external disk and use that for both swap and compiling.
[x] You will probably find compiling a great deal quicker using a (reasonable) external disk for the i/o intensive stuff anyway.
[x] If your Pi has 4g ram, it probably will not go into swap anyway.
[x] If you keep good backups, SDcards are cheap, maybe you are willing to risk it ?
Davo
Mark20:
Yes Davo,
for me it worth study a proper configuration and best practice to minimize risks.
I see room to work on this.
If I have to deal with projects where an ATmega32 is not enough, I want to switch on PiZero.
Also because other "micro" as ESP32 are complex too; it's not easy to get a real and full control of such devices.
At least with Rpi and Lazarus I have a full software ecosystem which I can rely on.
Navigation
[0] Message Index
[#] Next page
[*] Previous page