-
Notifications
You must be signed in to change notification settings - Fork 0
/
forte_config.h.in
83 lines (64 loc) · 3.13 KB
/
forte_config.h.in
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
/*******************************************************************************
* Copyright (c) 2005 - 2014 ACIN, Profactor GmbH, fortiss GmbH
* This program and the accompanying materials are made available under the
* terms of the Eclipse Public License 2.0 which is available at
* http://www.eclipse.org/legal/epl-2.0.
*
* SPDX-License-Identifier: EPL-2.0
*
* Contributors:
* Alois Zoitl, Martin Melik Merkumians, Ingo Hegny, Michael Hofmann
* - initial API and implementation and/or initial documentation
*******************************************************************************/
#ifndef _CONFIG_H_
#define _CONFIG_H_
#include <datatype.h>
/*!Define the number of times the CTimerHandler will be called per second.
*
* FORTE will use this information to calculate time values.
*/
const TForteUInt32 cg_nForteTicksPerSecond = ${FORTE_TicksPerSecond};
/*! \brief Defines the time base in units per second that will be used in the TIME data type
*
* The default value will be 1 000 000 000, which means that the time bas is 1 ns.
* For Smaller devices which do not use 64 bit datatypes a time base of 1000 (i.e., 1ms)
* or 1000000 (i.e., 1micro s) may be suitable.
*/
const uint_fast64_t cgForteTimeBaseUnitsPerSecond = ${FORTE_TimeBaseUnitsPerSecond};
/*! Define the initial size of the event chain list used in the event chain execution thread.
*
*/
const unsigned int cg_nEventChainEventListSize = ${FORTE_EventChainEventListSize};
/*! Define the initial size of the event chain's external event list.
*/
const unsigned int cg_nEventChainExternalEventListSize = ${FORTE_EventChainExternalEventListSize};
/*! Defines the number of pending communication messages can be handled by a communication function block
*
*/
const unsigned int cg_unCommunicationInterruptQueueSize = ${FORTE_CommunicationInterruptQueueSize};
/*! Buffer size in bytes to be used by the ip layer as receive buffer.
*
*/
const unsigned int cg_unIPLayerRecvBufferSize = ${FORTE_IPLayerRecvBufferSize};
/*! \brief Define the management encapsulation protocol
*
* Currently two protocols are supported:
* # DEV_MGR for FBDK compliant XML encoded commands
* # WBXML_DEV_MGR for WAP Binary XML encoded commands
*/
#define FORTE_MGM_COMMAND_PROTOCOL ${FORTE_MGMCOMM-ANDPROTOCOL}
//! Max supported hierarchy that can be provided in a management commands
#define FORTE_MGM_MAX_SUPPORTED_NAME_HIERARCHY ${FORTE_MGM_MAX_SUPPORTED_NAME_HIERACHY}
/*! \brief FORTE string dict's initial string buffer size
*
* Depending on the FORTE_STRING_DICT_FIXED_MEMORY flag the string dict will reallocate if necessary.
*/
const TForteUInt32 cg_unStringDictInitialStringBufSize = ${FORTE_STRINGDICTINITIALSTRINGBUFSIZE};
/*! \brief FORTE string dict's initial max nr of strings
*
* Depending on the FORTE_STRING_DICT_FIXED_MEMORY flag the string dict will reallocate if necessary.
*/
const TForteUInt32 cg_unStringDictInitialMaxNrOfStrings = ${FORTE_STRINGDICTINITIALMAXNROFSTRINGS};
const TForteUInt32 cg_unNumberOfHandlers = ${FORTE_NUMBER_OF_HANDLERS};
${FORTE_CUSTOM_CONFIGURATIONS}
#endif