This “exclusive” 8‑bit handling—ensuring that —is a fundamental discipline for reliable embedded programming. Flowcode 8 and earlier versions made this natural by using EEPROM.Read() and EEPROM.Write() as byte‑only operations. In Flowcode 10, however, those functions can handle both 8‑bit and 16‑bit reads/writes depending on context. To preserve the “exclusive 8‑bit” behaviour, developers now use EEPROM.ReadByte() and EEPROM.WriteByte() .
: Individual bytes are erased and reprogrammed electrically. While faster than older EPROM technology, each write operation typically takes several milliseconds (e.g., ~3.3ms) to complete. Flowcode Embedded Usage Comparison Standard EEPROM Component FlashEEPROM (Emulation) Storage Type Dedicated Non-volatile Memory Designated Page of Flash Memory Data Width Typically 8-bit (Byte-level) Often 16-bit values Primary Use High-cycle configuration data Large data storage on modern MCUs Availability Available on MCUs with internal EEPROM Used when no internal EEPROM exists For developers using
that emulates EEPROM functionality by using a specific page of Flash memory to store 16-bit values. Flowcode Embedded Technical Specifications and Constraints
If your Flowcode design utilizes hardware interrupts or RTOS tasks, a write operation to a multi-byte variable could be interrupted midway through execution. This results in a corrupted "half-written" state. flowcode eeprom exclusive
Set the property to match your target microcontroller specification (e.g., 256 bytes for a PIC16F1937, or 1024 bytes for an ATmega328P). Pre-loading Initial Data
This component is specifically designed for PIC24 and dsPIC series controllers and provides storage for up to 253 words of 16 bits. A key exclusive feature is its built-in , which significantly extends the emulated memory's lifespan by distributing write operations across two full 'erase' pages of Flash memory. However, a critical warning: because it uses Flash memory, data stored with this component will be lost when you reprogram the microcontroller.
This pattern exemplifies the “exclusive” discipline: every EEPROM write stores exactly one 8‑bit byte, and multi‑byte values are explicitly split and reassembled. 000 write cycles .
While the Flowcode component simplifies usage, effective implementation requires understanding its "exclusive" constraints: Write Endurance : Most microcontroller EEPROMs are rated for roughly 1,000,000 write cycles . Frequent writing in a fast loop can wear out the memory. Corruption Risks
: Data remains intact across power cycles and resets.
A critical design consideration for any EEPROM-based project is the hardware's limited lifespan. Most internal microcontroller EEPROMs are rated for approximately per cell. What is EEPROM? A Guide to Its Function and Operation 256 bytes for a PIC16F1937
Flowcode supports a wide range of microcontroller families, including PIC, AVR, ARM, and dsPIC, as well as platforms like Arduino and Raspberry Pi. This cross‑platform flexibility makes it an excellent choice for both educational settings and professional development.
: Data corruption often occurs if the power supply drops too low during a write operation. It is recommended to use "Brown-out Reset" (BOR) settings in Flowcode to prevent the CPU from executing incorrect instructions during low voltage. Target Dependencies
The answer is yes. With a loop and an index variable, you can implement a circular buffer that cycles through EEPROM addresses automatically. The following flowchart logic achieves this: