You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically this is saying that if the child's (current node) max offset (the size of the child basically) is bigger than the current offset (the current position in the addrmap) a padding will be added to match the maximum of the child.
It's fun because if I include a bunch of registers as a regfile, the child.raw_address_offset is bigger than if I add the registers to the regmap "manually" (this means not using a regfile). In that last case each register will be processed manually, where the child.raw_address_offset is always smaller than the current_offset so no padding is needed.
Hi, first of all, thank you very much for the work. It is very useful and professional.
Now, the "issue" I had is the following. Maybe I'm doing something wrong but, I don't know why I have this padding created on the .h file.
The RDL is a simple file:
And I run
peakrdl
with:peakrdl c-header test2_regmap.rdl -o out.h
I'm getting the
.h
:I don't know why there is a reserved array of chars. I think it is aligned to 32bits.
Do you know what may be happening? Any recommendations appreciated.
The text was updated successfully, but these errors were encountered: