fix: correct latching of manager motor control signals
All threads resolved!
All threads resolved!
- Moved latching for local motor control signals of manager module into TX part of m2s interface.
I thought that the M2S-TX-FSM is the best place to latch the section of motor control signals that the manager should use for its motors. If you agree, could you please cross-check the solution?
Merge request reports
Activity
requested review from @cagil.guemues
assigned to @michael.randall
- Resolved by Cagil Guemues
added 1 commit
- c69c5958 - fix: wrong output port assignment on the M2S Rx side
With the !35 (c69c5958) commit, I can now confirm that M2S path is working correctly now on simulations.
There is still a TODO: Do not rely on 100 MHz clock for S2M Clock failure detection logic.
mentioned in commit 96627f99
Please register or sign in to reply