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
Right now PI-related tests set the PI code through a signal that is not part of the JTAG debug interface. Once issue #62 is resolved they can be set directly through normal JTAG debug signals, which is a better representation of what we would actually be able to do in the lab.
The text was updated successfully, but these errors were encountered:
This still doesn't appear to be resolved in the following tests:
cpu_system_tests/pi
cpu_system_tests/pi_pm
The glitch test also has an unusual way of setting the PI control code, but I think that's what we want in that case, since it makes it easier to create different timing scenarios.
Right now PI-related tests set the PI code through a signal that is not part of the JTAG debug interface. Once issue #62 is resolved they can be set directly through normal JTAG debug signals, which is a better representation of what we would actually be able to do in the lab.
The text was updated successfully, but these errors were encountered: