foxBMS - Unit Tests  1.2.0
The foxBMS Unit Tests API Documentation
database.c File Reference

Database module implementation. More...

#include "database.h"
#include "FreeRTOS.h"
#include "queue.h"
#include "ftask.h"
#include <string.h>
Include dependency graph for database.c:

Go to the source code of this file.

Data Structures

struct  DATA_BASE_HEADER
 

Macros

#define DATA_QUEUE_TIMEOUT_MS   ((TickType_t)10u)
 

Typedefs

typedef struct DATA_BASE_HEADER DATA_BASE_HEADER_s
 

Functions

STD_RETURN_TYPE_e DATA_Init (void)
 Initialization of database manager. More...
 
void DATA_Task (void)
 trigger of database manager More...
 
void DATA_DummyFunction (void)
 Dummy void function of the database module. More...
 
STD_RETURN_TYPE_e DATA_Read_1_DataBlock (void *pDataToReceiver0)
 Reads a datablock in database by value. More...
 
STD_RETURN_TYPE_e DATA_Read_2_DataBlocks (void *pDataToReceiver0, void *pDataToReceiver1)
 Reads a datablock in database by value. More...
 
STD_RETURN_TYPE_e DATA_Read_3_DataBlocks (void *pDataToReceiver0, void *pDataToReceiver1, void *pDataToReceiver2)
 Reads a datablock in database by value. More...
 
STD_RETURN_TYPE_e DATA_Read_4_DataBlocks (void *pDataToReceiver0, void *pDataToReceiver1, void *pDataToReceiver2, void *pDataToReceiver3)
 Reads a datablock in database by value. More...
 
STD_RETURN_TYPE_e DATA_Write_1_DataBlock (void *pDataFromSender0)
 Stores a datablock in database. More...
 
STD_RETURN_TYPE_e DATA_Write_2_DataBlocks (void *pDataFromSender0, void *pDataFromSender1)
 Stores a datablock in database. More...
 
STD_RETURN_TYPE_e DATA_Write_3_DataBlocks (void *pDataFromSender0, void *pDataFromSender1, void *pDataFromSender2)
 Stores a datablock in database. More...
 
STD_RETURN_TYPE_e DATA_Write_4_DataBlocks (void *pDataFromSender0, void *pDataFromSender1, void *pDataFromSender2, void *pDataFromSender3)
 Stores a datablock in database. More...
 
void DATA_ExecuteDataBIST (void)
 Executes a built-in self-test for the database module. More...
 

Variables

static const DATA_BASE_HEADER_s data_baseHeader
 device configuration of database More...
 
static uint16_t uniqueIdToDatabaseEntry [DATA_BLOCK_ID_MAX]
 uniqueId to respective database entry selector More...
 

Detailed Description

Database module implementation.

SPDX-License-Identifier: BSD-3-Clause

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

We kindly request you to use one or more of the following phrases to refer to foxBMS in your hardware, software, documentation or advertising materials:

  • ″This product uses parts of foxBMS®″
  • ″This product includes parts of foxBMS®″
  • ″This product is derived from foxBMS®″
Author
foxBMS Team
Date
2015-08-18 (date of creation)
Updated
2021-07-23 (date of last update)
Prefix
DATA

Implementation of database module

Definition in file database.c.

Macro Definition Documentation

◆ DATA_QUEUE_TIMEOUT_MS

#define DATA_QUEUE_TIMEOUT_MS   ((TickType_t)10u)

Maximum queue timeout time in milliseconds

Definition at line 69 of file database.c.

Typedef Documentation

◆ DATA_BASE_HEADER_s

configuration struct of database device

Function Documentation

◆ DATA_DummyFunction()

void DATA_DummyFunction ( void  )

Dummy void function of the database module.

This function is needed in the database module in order to implement the DATA_READ_DATA() and DATA_WRITE_DATA() in a ISO C99 standard compatible way. The invocation of a macro that accepts a variable number of arguments (and this is the case for DATA_READ_DATA() and DATA_WRITE_DATA()) needs more arguments in the invocation than there are parameters in the macro definition. For the most simple case, that DATA_READ_DATA() and DATA_WRITE_DATA() are only called with one argument, a violation of the standard would appear if the DATA_DummyFunction() would be omitted: GET_MACRO(databaseVaribale, DATA_Read_4_DataBlocks, DATA_Read_3_DataBlocks, DATA_Read_2_DataBlocks, DATA_Read_2_DataBlocks, DATA_Read_1_DataBlock)(databaseVaribale) So the macro invocation has six parameters, but it needs seven and an ISO C99 violation would appear. Adding the DATA_DummyFunction() fixes this violation. For details see 6.10.3 (paragraph 4) of the ISO C99 standard.

Definition at line 203 of file database.c.

◆ DATA_ExecuteDataBIST()

void DATA_ExecuteDataBIST ( void  )

Executes a built-in self-test for the database module.

This test writes and reads a database entry in order to check that the database module is working as expected. If the test fails, it will fail an assertion.

Definition at line 294 of file database.c.

◆ DATA_Init()

STD_RETURN_TYPE_e DATA_Init ( void  )

Initialization of database manager.

Returns
STD_OK if initialization successful, otherwise STD_NOT_OK

Definition at line 105 of file database.c.

◆ DATA_Read_1_DataBlock()

STD_RETURN_TYPE_e DATA_Read_1_DataBlock ( void *  pDataToReceiver0)

Reads a datablock in database by value.

This function reads data from database and copy this content in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[out]pDataToReceiver0(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 206 of file database.c.

Here is the call graph for this function:

◆ DATA_Read_2_DataBlocks()

STD_RETURN_TYPE_e DATA_Read_2_DataBlocks ( void *  pDataToReceiver0,
void *  pDataToReceiver1 
)

Reads a datablock in database by value.

This function reads data from database and copy this content in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[out]pDataToReceiver0(type: void *)
[out]pDataToReceiver1(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 211 of file database.c.

Here is the call graph for this function:

◆ DATA_Read_3_DataBlocks()

STD_RETURN_TYPE_e DATA_Read_3_DataBlocks ( void *  pDataToReceiver0,
void *  pDataToReceiver1,
void *  pDataToReceiver2 
)

Reads a datablock in database by value.

This function reads data from database and copy this content in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[out]pDataToReceiver0(type: void *)
[out]pDataToReceiver1(type: void *)
[out]pDataToReceiver2(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 216 of file database.c.

Here is the call graph for this function:

◆ DATA_Read_4_DataBlocks()

STD_RETURN_TYPE_e DATA_Read_4_DataBlocks ( void *  pDataToReceiver0,
void *  pDataToReceiver1,
void *  pDataToReceiver2,
void *  pDataToReceiver3 
)

Reads a datablock in database by value.

This function reads data from database and copy this content in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[out]pDataToReceiver0(type: void *)
[out]pDataToReceiver1(type: void *)
[out]pDataToReceiver2(type: void *)
[out]pDataToReceiver3(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 221 of file database.c.

◆ DATA_Task()

void DATA_Task ( void  )

trigger of database manager

TODO

Definition at line 155 of file database.c.

Here is the call graph for this function:

◆ DATA_Write_1_DataBlock()

STD_RETURN_TYPE_e DATA_Write_1_DataBlock ( void *  pDataFromSender0)

Stores a datablock in database.

This function stores passed data in database and updates timestamp and previous timestamp in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[in,out]pDataFromSender0(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 250 of file database.c.

Here is the call graph for this function:

◆ DATA_Write_2_DataBlocks()

STD_RETURN_TYPE_e DATA_Write_2_DataBlocks ( void *  pDataFromSender0,
void *  pDataFromSender1 
)

Stores a datablock in database.

This function stores passed data in database and updates timestamp and previous timestamp in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[in,out]pDataFromSender0(type: void *)
[in,out]pDataFromSender1(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 255 of file database.c.

Here is the call graph for this function:

◆ DATA_Write_3_DataBlocks()

STD_RETURN_TYPE_e DATA_Write_3_DataBlocks ( void *  pDataFromSender0,
void *  pDataFromSender1,
void *  pDataFromSender2 
)

Stores a datablock in database.

This function stores passed data in database and updates timestamp and previous timestamp in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[in,out]pDataFromSender0(type: void *)
[in,out]pDataFromSender1(type: void *)
[in,out]pDataFromSender2(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 260 of file database.c.

Here is the call graph for this function:

◆ DATA_Write_4_DataBlocks()

STD_RETURN_TYPE_e DATA_Write_4_DataBlocks ( void *  pDataFromSender0,
void *  pDataFromSender1,
void *  pDataFromSender2,
void *  pDataFromSender3 
)

Stores a datablock in database.

This function stores passed data in database and updates timestamp and previous timestamp in passed struct

Warning
Do not call this function from inside a critical section, as it is computationally complex.
Parameters
[in,out]pDataFromSender0(type: void *)
[in,out]pDataFromSender1(type: void *)
[in,out]pDataFromSender2(type: void *)
[in,out]pDataFromSender3(type: void *)
Returns
STD_OK if access was successful, otherwise STD_NOT_OK

Definition at line 265 of file database.c.

Variable Documentation

◆ data_baseHeader

const DATA_BASE_HEADER_s data_baseHeader
static
Initial value:
= {
.nrDatabaseEntries = sizeof(data_database) / sizeof(DATA_BASE_s),
.pDatabase = &data_database[0],
}
DATA_BASE_s data_database[]
channel configuration of database (data blocks)
Definition: database_cfg.c:176

device configuration of database

all attributes of device configuration are listed here (pointer to channel list, number of channels)

Definition at line 86 of file database.c.

◆ uniqueIdToDatabaseEntry

uint16_t uniqueIdToDatabaseEntry[DATA_BLOCK_ID_MAX]
static

uniqueId to respective database entry selector

This array is the link between the uniqueId of a database entry and the actual position of the database entry in data_database[]

Definition at line 96 of file database.c.