STAT reg
Closed this issue · 6 comments
We have a universal board which has several firmware types, so we need to have read-only register with FW_TYPE at defined address which is the same for all types of firmware.
We have used STAT reg inside CTRL type reg.
If we add more CTRL reg then address for STAT reg changes as they are created after CTRL regs.
Is it possible to modify firmware in such way that STAT registers are created first ?
Hi,
I assume that you are referring to the ipbus_ctrlreg_v entity that's defined within ipbus_ctrlreg_v.vhd. If that's not the case, please let me know
I do not believe that it would be possible at this stage to change the order of the STAT & CTRL register within ipbus_ctrlreg_v, as that would be a backward-incompatible change that would affect many other people.
Instead, given the fixed-address constraint on the firmware version/type register(s) in your case, I think that a more feasible solution would be for you to declare the CTRL and STAT register blocks as two separate components in place of the single ipbus_ctrlreg_v entity that you're currently instantiating.
Cheers,
Tom
I have added a new generic SWAP_ORDER to the ctrlreg_v block and its friend syncreg_v. Added to the dev branch for this issue.
I've also used this branch to fix a recently-discovered race condition in ipbus_syncreg_v. This caused a lock-up condition if a block of syncreg_v stat registers were read too quickly, due to a bug in the read handshake logic.
Any more work required on this or shall the branch merged back into the master?
Pull request made.