Contributor
Regular ContributorHi, could you check if the ir command is correct by using the show_equivalent_device_ir_dr_shift argument.
If it is correct, it could be your design issue.
Contributor@YuanLi_S_Intel is this what you would expect to see?
Info (262019): Equivalent device ir and dr shift commands
Info (262020): device_dr_shift -length 12 -dr_value 00B -value_in_hex
Info (262020): device_dr_shift -length 12 -dr_value 40C -value_in_hex
(3 second delay)
Info (262019): Equivalent device ir and dr shift commands
Info (262020): device_dr_shift -length 12 -dr_value 00B -value_in_hex
Info (262020): device_dr_shift -length 12 -dr_value 40B -value_in_hex
I'm assuming the 40C corresponds to my RESET_LO_CMD (12) and 40B corresponds to RESET_HI_CMD (11) ?
Contributor@YuanLi_S_Intel there must be something wrong with my design. I've been struggling with this for weeks now.
I expect to see LED8 toggle, followed by LED7 toggle (RESETLO, 3 seconds, RESETHI). But what I see is the opposite (LED7 toggle= RESETHI, 3 seconds, LED8 toggle=RESETLO)
Am I not using uir correctly?
The full project can be found here: https://github.com/SparkyNZ/FixReset
Contributor@YuanLi_S_Intel I hooked up the VJTAG pins to an external logic analyzer and I think I know what is wrong with the design.
My design assumed that the tck signal is a regular clock - but it isn't. It only oscillates when there is incoming data.
So.. my question is: What would be a typical frequency for tck when it is oscillating? I have a 2Mhz clock which I am using in my design - would this be too slow to service the tck/VJTAG signals??
