Demo project details

    In the demo project, the in main.c is the entry function. This function is divided into two sections, which initialize a KVDB and TSDB objects respectively, and then execute the corresponding example functions. The general content is as follows:

    Set lock and unlock

    Before initializing KVDB and TSDB, it is usually necessary to set the lock callback and unlock callback through the control function:

    • KVDB：
      • fdb_kvdb_control(&kvdb, FDB_KVDB_CTRL_SET_LOCK, lock);
    • TSDB：
      • fdb_tsdb_control(&tsdb, FDB_TSDB_CTRL_SET_LOCK, lock);
      • fdb_tsdb_control(&tsdb, FDB_TSDB_CTRL_SET_UNLOCK, unlock);

    For bare metal platforms, the lock and unlock callbacks are usually set to close interrupt and open interrupt functions. The RTOS platform generally uses mutex mutex lock or binary semaphore take and release actions as locking and unlocking methods.

    timestamp simulation

    Therefore, the time stamp simulated by this method does not have the meaning of real-time time, just to make the time stamp inserted in each record not repeated.

    Example

    This article mainly explains initialization related code functions. For more detailed explanations of example functions, please read the corresponding detailed explanations of the examples.

    The log will be explained in sections below.

    1. [D/FAL] (fal_flash_init:65) Flash device |             stm32_onchip | addr: 0x08000000 | len: 0x00040000 | blk_size: 0x00000800 |initialized finish.
    2. [I/FAL] ==================== FAL partition table ====================
    4. [I/FAL] -------------------------------------------------------------
    5. [I/FAL] | fdb_tsdb1 | stm32_onchip | 0x0001a000 | 0x00002000 |
    6. [I/FAL] | fdb_kvdb1 | stm32_onchip | 0x0001c000 | 0x00004000 |
    7. [I/FAL] =============================================================
    8. [I/FAL] Flash Abstraction Layer (V0.5.0) initialize success.

    Each time KVDB is initialized, it will check whether the sector header information is correct (some attribute information is stored in the sector header). If it is not correct, the sector will be formatted automatically.

    When the Flash is used for the first time, it usually needs to be formatted, so the log at the first initialization will contain formatted information. After the format is successful, there is no need to format it again for each subsequent initialization.

    Similar to KVDB, when TSDB is initialized for the first time, it will automatically perform formatting.

    1. [FlashDB][tsl][log] Sector (0x00000000) header info is incorrect.
    2. [FlashDB][tsl][log] All sector format finished.

    Here we mainly look at the initialization logs of KVDB and TSDB. Compared with the first initialization, it can be found that the initialization logs at the second startup will be relatively small, and the formatting process is mainly missing.

    1. [D/FAL] (fal_flash_init:65) Flash device |             stm32_onchip | addr: 0x08000000 | len: 0x00040000 | blk_size: 0x00000800 |initialized finish.
    2. [I/FAL] ==================== FAL partition table ====================
    4. [I/FAL] -------------------------------------------------------------
    5. [I/FAL] | fdb_tsdb1 | stm32_onchip | 0x0001a000 | 0x00002000 |
    6. [I/FAL] | fdb_kvdb1 | stm32_onchip | 0x0001c000 | 0x00004000 |
    7. [I/FAL] =============================================================
    8. [I/FAL] Flash Abstraction Layer (V0.5.0) initialize success.
    9. [FlashDB][kv][env] (D:/Program/STM32/FlashDB/src/fdb_kvdb.c:1599) KVDB in partition fdb_kvdb1, size is 16384 bytes.
    10. [FlashDB] FlashDB V1.0.0 beta is initialize success.
    11. [FlashDB] You can get the latest version on https://github.com/armink/FlashDB .
    12. Omit the sample run log...
    13. [FlashDB][tsl][log] (D:/Program/STM32/FlashDB/src/fdb_tsdb.c:759) TSDB (log) oldest sectors is 0x00000000, current using sector is 0x00000000.