VCC Glitch Mosfet Control Update #444
Conversation
|
A big chunk of changes in ChipWhispererExtra.py is because I moved CWExtraSettings above GPIOSettings so I could access the CWExtraSettings class globals from GPIOSettings globals. I would test the CWLITE VCC glitch demos but I think a long time ago, I burned out my mosfets cuz I can't hit glitches anymore :( I bought some replacement mosfets, but I have to find time to do the soldering work on the board. I do have a HUSKY, but I haven't had time to set it up. I do plan on playing around with it soon and use that as my new testing/development platform. |
DJShepherd
force-pushed
the
DJShepherd/fast_glitcht
branch
3 times, most recently
from
1e2b700
to
707ea7c
Compare
|
To see more of the direction I'm proposing for the CONSTS/API interface that I created in this PR, I'm currently working on the same interface for the TIO/GPIO API as seen here: |
DJShepherd
force-pushed
the
DJShepherd/fast_glitcht
branch
5 times, most recently
from
c4d7112
to
991fb73
Compare
DJShepherd
force-pushed
the
DJShepherd/fast_glitcht
branch
from
991fb73
to
efd9e87
Compare
DJShepherd
force-pushed
the
DJShepherd/fast_glitcht
branch
from
efd9e87
to
a2f409a
Compare
|
Any progress on getting this validated and merged in? I've been keeping it updated and making sure nothing breaks in terms of the workflow I have been testing with. |
|
Sorry about the delays with this. I've been working on stuff related to an upcoming training, so I don't want to make too many big changes before that. |
Understandable, thanks for the update, was just curious! :) I'll just keep working on the other changes slowly, I've been busy as of late, too. |
| self.clock.reset_dcms() | ||
| if count > 10: | ||
| raise OSError("Could not lock PLL. Try rerunning this function or calling scope.pll.reset(): {}".format(self)) | ||
| if not self.clock.try_wait_clkgen_locked(10): |
There was a problem hiding this comment.
This needs a Husky version as well (cwhardware/ChipWhispererHuskyClock.py)
There was a problem hiding this comment.
This is common logic so for now, in order to not duplicate/copy-paste code, I just moved it to be an OpenADC method with a note to move it into a base/common clock class if refactoring ever happens.
| @@ -452,6 +553,9 @@ def lo_gain_errors_disabled(self): | |||
| else: | |||
| return False | |||
|
|
|||
| def disable_clip_and_lo_gain_errors(self, disabled): | |||
There was a problem hiding this comment.
This needs to be in scope.errors instead of scope.adc.
There was a problem hiding this comment.
Whoops, this is just in the wrong class in this file (needs to be in TriggerSettings)
|
Will run this on a few more scope/target setups, but should be good once the fixes above are implemented |
|
I've been a bit busy so I haven't gotten to it, but it's on my radar and I'm hoping to tackle it this weekend! |
…etup/disable API; Added message utilities; Added optimized data copy; Added API utilities and tests
DJShepherd
force-pushed
the
DJShepherd/fast_glitcht
branch
from
a2f409a
to
5bd2af4
Compare
|
Can confirm the latest update works. Will merge in now. |
Passed tests/api_test.py, validated glitch_hp/lp value assignment and readback.