signal{encoder/decoder}: fix byte order & size calculation #206
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This PR might fix all possible encoding issues, these seem related:
#202
#200
The PDF that supposedly describes the DBC format got
the byte-order apparently wrong :)
The correct values are:
0 => big-endian, motorola
1 => little-endian, intel
Both encoder/decoder do bound checks before inserting the
bits into the raw signal. The bound checks need to take the
endianess into account because:
if the signal is little_endian / intel, start_bit describes
the LSB, so end_bit = start_bit + signal_size
if the signal is big_endian / motorola, start_bit describes
the MSB, so end_bit = start_bit - signal_size + 1
This I tested this PR together with #205
To test simply cherry-pick dfe3e90