e2f07cbcd1
connect and disconnect functions public
2020-01-02 14:01:21 +01:00
831a01e79e
recvBuffer and recvSize initialized
2020-01-01 17:31:17 +01:00
c73cb90c36
receiveTc function adapted
2020-01-01 16:54:05 +01:00
a762c159fe
pool raw access helper info output commented out
2019-12-30 01:13:33 +01:00
2425685e44
Pool Raw Access Helper serialization of vectors implemented
2019-12-29 01:59:02 +01:00
666341d03d
new bool datatype for possible pool entries
2019-12-27 22:43:09 +01:00
79e7fee807
comment deleted
2019-12-26 22:15:19 +01:00
a38a2f4b3a
tmtc bridge bugfix: tm data deleted when overwriting old data
2019-12-26 22:07:17 +01:00
33a7c033a2
doc extended, instructions for sendTm and receiveTc
2019-12-26 20:38:15 +01:00
19e257a90a
tmtc bridge debug output corrected
2019-12-26 20:35:11 +01:00
8397f5b2b1
tmtc bridge bugfix
2019-12-26 20:17:21 +01:00
0066a6b788
Generic TMTC Bridge added
2019-12-26 19:47:46 +01:00
29b4480fc4
include adapted
2019-12-26 18:55:31 +01:00
e24f9b89e4
Pool Raw Access Helper tested, appesrs to work. SerializeAdapter doc
...
changes, tm packet stored debug output if not enough
storage available
2019-12-26 16:44:50 +01:00
1f1831c4a1
pool raw access init
2019-12-24 22:15:39 +01:00
f6b9b23287
pool raw access init
2019-12-24 01:41:04 +01:00
89f490ac36
assembly constructor formatting
2019-12-20 23:09:35 +01:00
Maximilian Luz
d17146d847
Check object existence before adding it to the PST
...
Currently, adding new objects/components to the FixedSlotSequence PST is
not being checked, meaning that it is possible to add NULL objects here
without any warning. This causes NULL-pointer errors when non-existent
components are added, which can be hard to debug.
To solve this, add a check for the object existence before adding it to
PST and emit an error message.
Signed-off-by: Maximilian Luz <luzmaximilian@gmail.com>
2019-12-20 18:10:39 +01:00
fa6cbe7e0c
pool raw access changed reverted
2019-12-11 23:18:28 +01:00
625f3dc79c
local pool modify data doc modifided
2019-12-11 23:15:34 +01:00
9382eb03e6
function to serialize pool ID buffers into dataset created
2019-12-11 22:50:08 +01:00
29a15e8154
commented out functions which will propably not
...
be needed and removed
2019-12-11 13:03:51 +01:00
138cac98d1
experimenting with recursive constructor and dataset call
2019-12-11 01:57:36 +01:00
f7d8f0c161
Reverted changed pool raw access commit
2019-12-10 23:26:48 +01:00
6abb3cc525
Merge remote-tracking branch 'origin/feature_EndianSwapper_UINT32_BUFFER_PoolRawAccess_Modification_For_Vectors' into mueller_framework
2019-12-10 14:54:32 +01:00
f33949ba4b
doc adapted, merging
2019-12-10 14:54:17 +01:00
356d1d35dc
experimenting with recursive constructor to enable
...
automatic vector registering
2019-12-10 13:29:16 +01:00
e765f8c99b
pool raw access modified so vectors are properly serialized now
...
Endian swapper can swap the entries of a uint16,uint32 buffers now.
Some documentation for functions added. setter function for serial buffer
adapter written but does not appear to compile, commented out
2019-12-09 12:27:14 +01:00
8168885dd9
Serialization documentation update
2019-12-08 22:57:03 +01:00
3159ccbc40
fixed map and local pool doc
2019-12-08 22:26:42 +01:00
d99ed47150
fixed map bugfix (fist instead of first), new access functions for fixed maP
...
(first(), second()), some documentation, raw pool access read() call public
because call is necessary before using public serialize function.
maybe integrate read() call into serialize function?
2019-12-08 19:04:53 +01:00
950a48078c
some documentation, question about HasParametersIF,
...
variable in ParameterHelper intialized (compiler warning)
2019-12-05 12:21:06 +01:00
9c3a9323b7
some doc change proposals while
...
writing hk service.
Added Type.h in PoolRawAccess.h, compiler error
when not doing that
2019-12-03 19:30:37 +01:00
37a70df244
SerialBufferAdapter can process uint32_t * buffers now
2019-12-01 17:48:05 +01:00
10c24e39a3
new returnvalue for scanForReply to ignore full packet
2019-11-29 19:56:05 +01:00
2039aa5665
Service Interface Stream buffer size higher to print long buffers (like nav data)
2019-11-25 00:14:39 +01:00
2f14fd5d4d
Cant reach mode reason getter function added
2019-11-11 22:45:53 +01:00
2b44e1c9c4
CCSDS sscanf function adapted for atmel stdio.c (see comments)
2019-11-10 13:08:02 +01:00
b8af3b5e3d
debugInterface extended
2019-11-09 18:15:45 +01:00
537e2ceb18
Getter method for logicalAddress
2019-11-09 13:29:12 +01:00
ee765eafc7
ioBoardAddress renamed to logicalAddress
2019-11-09 13:17:54 +01:00
801bd4d7eb
debug interface for dhb created.
...
This is useful to track states or values
in child handler. some documentation added.
New doxygen group for interfaced added.
2019-11-09 13:07:26 +01:00
bf7bc342ff
Revert "documentation for DHB init function, ioBoard addres has default value 0 now, order in ctor changed (not used in source)"
...
This reverts commit c6e34cada6
2019-11-05 19:30:02 +01:00
af4e9db9e3
Merge branch 'mueller_framework' of https://egit.irs.uni-stuttgart.de/KSat/fsfw into mueller_framework
2019-11-05 19:25:27 +01:00
b594bc2a97
removed obsolete comment
2019-11-05 19:25:00 +01:00
8a93a873a8
Merge branch 'mueller_framework' of https://egit.irs.uni-stuttgart.de/KSat/fsfw into mueller_framework
2019-11-04 11:07:02 +01:00
e7f7625adf
removed wrong include
2019-11-04 11:06:59 +01:00
cb919ada2a
assuming that a default value of 0 for expectedReplies is needed, I introduced a new variable into DeviceCommandInfo, which stores another number of replies expected. this value is assigned in enableReplyInReplyMap. That way, the initial value of 0 remains the same (if it was needed), and is only set to another desired value if a write was sent
2019-11-04 01:55:40 +01:00
12f51575eb
removed a flag by accident, fixed now
2019-11-04 00:53:05 +01:00
8eb1a5b13e
proposal 1: expectedReplies parameter is set in insertInCommandAndReplyMap, default value stays one. overriding enableReplyInReplyMap is not necessary anymore.second proposal: the commander id is supplied in the interpretDeviceReply function, so we don't have to look for it in the DeviceCommandMap. was it removed at some point because it is listed in the documentation?
2019-11-04 00:47:46 +01:00
