4 Device Features
4.1 LED Indication
The demo application does not actively control the LED indication.
The table below shows the LED indication controlled by the bord controller MCU. The LED indicator stats can be overwritten by the application. The MCU ether restores the previous indication state after signaling an action (e.g. modem reset) or triggers a reset (reboot) of the whole device.
Board Controller LED indication:
Mode / LED | LED1 | LED2 | LED3 | LED4 |
---|---|---|---|---|
Device Active (initial state) | Green blinking | / | / |
/ |
Modem reset ongoing | Red blinking | / | / |
/ |
Reset button pressed | Red blinking | / | / |
/ |
Undervoltage detected (ERROR) | Red blinking | / | / |
/ |
IMX8 heart beat reset | Red single flash | / | / |
/ |
Device in Sleep Mode | Yellow blinking | / | / |
/ |
4.2 Device and User Data Memory
Beside the eMMC memory on the CPU module and the pluggable SD memory card, the device has dedicated persistent storage for configuration and user data. Those memory section are further described further in this chapter.
Device Data
Factory preprogrammed device data are stored in one of the two I2C EEPROM memories.
This memory section must not be used for user application data, see therefore the user data memory.
The memory can be accessed by the I2C Bus interface, see 6.3 EERPOM Script as example.
EEPROM Device:
Type: | 24AA025E48T-I/OT |
Manufacturer | Microchip |
Size: | 256 Byte |
Organization | 2 Blocks a 128 Bytes |
I2C address: | 0x51 |
Memory Map:
Address [in HEX] | Description | Size [Byte] | Format | ||
---|---|---|---|---|---|
0x00 | Reserved | 250 | TBD | ||
0xFA | Device MAC and identification number | 6 |
|
4.2.2 User Data
The RAR4000 series devices provide a dedicated EEPROM memory for storing user applications configuration parameters persistently. This memory section is under full control of the user application. For advanced network device configuration the preprogrammed globally unique MAC address can be used.
If the user application desires more persistent configuration data memory, see section 4.2.3 Extended User Data (optional).
The memory can be accessed by the I2C Bus interface, see 6.3 EERPOM Script as example.
EEPROM Device:
Type: | 24AA025E48T-I/OT |
Manufacturer | Microchip |
Size: | 256 Byte |
Organization | 2 Blocks a 128 Bytes |
I2C address: | 0x50 |
Memory Map:
Address [in HEX] | Description | Size [Byte] | Format | ||
---|---|---|---|---|---|
0x00 | User Configuration Data | 250 | To be defined by the user application | ||
0xFA | Device MAC and identification number | 6 |
0xFA 0xFF |
4.2.3 Extended User Data (optional)
The RAR4000 series devices can be assembled on request with an FRAM memory device to extend user configuration data capacity to up to 32k Byte and very short read and write cycles.
EEPROM Device:
Type: | FRAM |
Size: |
32k Byte |
Organization |
32768 x 8 Bit with different write protection levels |
SPI CS: |
See 2.2.3 Main CPU Module GPIOs |
For more information please contact us.
4.3 RTC Backup Battery
A replaceable clock backup battery can be inserted to maintain the calendar time if the device is unpowered or offline. The current battery voltage level can be measured and read out by the board controller (see 5.3 Board Controller API).
Battery type: 3V Lithium Coin Cell, CR2032
Assembly step resalt

- The battery holder is located in the service port.
- Place the battery with the plus-pole (+) pointing downwards into the battery holder.
