“No Bugs” Bunny
Journaled Flash Storage – Emulating EEPROM over Flash, ACID Transactions, and More. Part II – Existing Implementations by Atmel, SiLabs, TI, STM, and Microchip
October 5, 2015 by • “No Bugs” Bunny
Quote:
Whenever a developer is using something named 'X Emulation over Y', she may expect that a faithful emulation exhibits the same properties as original (non-emulated) X.
Another Quote:
Unfortunately, as discussed in detail above, none of five implementations is a really faithful EEPROM emulation.
Filed under: On.ProgrammingEmbeddedOn.HardwareMCU
Read moreJournaled Flash Storage – Emulating EEPROM over Flash, ACID Transactions, and More. Part I – Flash vs EEPROM
September 28, 2015 by • “No Bugs” Bunny
Quote:
You cannot erase single byte of Flash, but need to erase the whole page
Another Quote:
First of all, we want to be sure that whatever-is-already-written to our persistent storage, stays there; this property is known as Durability.
Filed under: On.ProgrammingEmbeddedOn.HardwareMCU
Read moreModified Harvard Architecture: Clarifying Confusion
September 21, 2015 by • “No Bugs” Bunny
Abstract:
Definition of "Modified Harvard" architecture is confusing and overbroad. Proposed alternatives are "Almost-Harvard" and "Almost-von-Neumann
Quote:
"One thing nobody realised for a while is that the system with the least possible amount of chargebacks is the system which rejects all transactions outright
Filed under: On.ProgrammingEmbeddedOn.HardwareMCU
Read moreMulti-threading at Business-logic Level is Considered Harmful
September 7, 2015 by • “No Bugs” Bunny
Quote:
However, the window for triviality is very narrow: for example, even going into two interrelated mutexes instead of one, can easily make multi-threading non-trivial
Another Quote:
Technically you are able to jump to any point of your program, but the variables you see may (and if you have a multi-threaded bug – will) differ every time you jump there.
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingDebugging
Read more