Hi
There is an option ("-bfield_gap_limit") that is controlling which is the maximum number of gap bits allowed in the bit-field allocation. The bit-field allocation is done "byte" wise, unless the padding required for "byte" allocation exceeds the gap.
By default, the gap is "0" which means that "byte" allocation is used all the time.
The Processor Expert generated header files ("IO_Map.h") the gap limit is set to "-1" (by using "pragma bfield_gap_limit -1"). The gap set to "-1" automaticaly forces the bit-field allocation to "word" (2-byte). thus all the bit structures under this line are grouped together in a "word" instead of staying grouped in "byte" units.
I don't suggest you remove this line. If your application requires"byte" allocation, you should set the gap limit to 0 after the inclusion of the "IO_Map.h" file, by using:
#pragma bfield_gap_limit 0
example:
1. bfield_gap_limit = 0 (set in panel)
- #include "derivative.h" will set the "bfield_gap_limit" to -1
- all following bfield data structures (from included headers) will consider the "bfield_gap_limit" as -1 and will behave accordingly
2. bfield_gap_limit = 255 (set in panel)
- #include "derivative.h" will set the "bfield_gap_limit" to -1
- this results in the same behavior as before
Have a great day,
TIC
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
