Occasional Contributor
Regular ContributorHello,
We do not characterized that. May I know why do you want to know that? You cannot change the PIN behavior from output to input in user mode. This only can be done at Quartus and need compile. Please provide us more details about your inquiries.
Thank you.
Occasional ContributorHi AminT_Intel,
assign PINMAP_3B[22] = (PWRON && ~IO_MUX[0]) ? 1'bZ : vector_out[14];
Based on the statement above, we drive vector_out[14] into PINMAP_3B[22] when PWRON = 1 and IO_MUX = 1
Since PINMAP_3B[22] is externally loopback to PINMAP_3B[25]
We then capture back the pattern in PINMAP_3B[25] using the statement below.
assign CAPTURE_GRP03[0] = PINMAP_3B[25] ;
We initially thought that once IO_MUX is toggle, we would see the capture pattern at the same time in PINMAP_3B[25].
But on the contrary, what we saw was roughly a 3.75nm delay from the time IO_MUX is toggle to the time we capture the pattern at PINMAP_3B[25].
below are the signal tap we capture with sampling clock of 400Mhz. The pattern we drove in is 1010010110100101.
Regular ContributorHello,
Thank you for the detailed explanation. As mentioned in last post, you cannot change the PIN behavior from output to input in user mode. This only can be done at Quartus and need compile.
Thank you
Regular ContributorWe do not receive any response from you to the previous question/reply/answer that I have provided. This thread will be transitioned to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.
