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
Hi,
Thanks for your work on ORDT. It is very impressive and usefull tool.
I'm trying to define holding registers in RDL, and I'm not sure how to do that.
Holding registers basically keep the value written by software in a holding register until a specified update register bit is triggered, then all the holding registers make their value visible to the hardware side. For example, if I have 128 bit control bus for some analog block that I map to registers. It would be mapped to 4 32-bit holding registers that would be written by software one at a time then updated to present the full 128 bit value to the analog. The main objective is to avoid the analog seeing any unwanted intermediate values as the registers are being written.
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for your work on ORDT. It is very impressive and usefull tool.
I'm trying to define holding registers in RDL, and I'm not sure how to do that.
Holding registers basically keep the value written by software in a holding register until a specified update register bit is triggered, then all the holding registers make their value visible to the hardware side. For example, if I have 128 bit control bus for some analog block that I map to registers. It would be mapped to 4 32-bit holding registers that would be written by software one at a time then updated to present the full 128 bit value to the analog. The main objective is to avoid the analog seeing any unwanted intermediate values as the registers are being written.
Thanks
The text was updated successfully, but these errors were encountered: