Forum Discussion
47 Replies
- JonWay_altera
Frequent Contributor
Hi @Wgith,
Sure, keep me posted. Signaltaps would be helpful. Just a note, the SDM can only process 1 IP at a time. So you have to make sure both IPs is back at cmd_ready, and only assert cmd_valid for one of the the IPs (not both together). Hope this helps.
- WGith
Occasional Contributor
Hi,
Still having issues. I made sure to one enable one of the IP blocks at a time. I also have added very large waits between accesses. I have attached a zip file with my simple vhdl state machine that access the voltage and temperature IPs. I also included 4 signaltap screenshots which shows how I enable the voltage and temperature requests and how it shows the IP responding as expected, and then 2 screenshots which shows for the voltage IP it responds with 4 and not 5 requests and also the 2 requests that actually respond with data that is not zero is formatted in a way that is for temperature readings, not voltage readings. And then for the temperature IP response, I do get two responses, but the second response valid as you can see is 2 clock cycles too late for the second valid data response.
So, the temperature IP is almost working as expected, but the voltage IP is completely responding in a manner that makes no sense.
Note that I am running the IP blocks at 100 Mhz.
- JonWay_altera
Frequent Contributor
Hi @WGith ,
Let me take a look at the STP, and I will get back to you.
It would be great if you could share with the me the simple design QAR.
Could I confirm with you that these IPs were working correctly individually?
- JonWay_altera
Frequent Contributor
Hi @WGith
I took a look at the STP, for voltage sensor, i see you set to read channel 2,3,4,6,9
The results came back for 2,3,4,6...9 is missing. Is that what you meant by "Voltage IP is responding in a manner that makes no sense"? If not, please elaborate.
Btw, what device PN are you using?
Could you share with me the simple design QAR.
- WGith
Occasional Contributor
JwChin, There are a couple things to note. 1. Yes the Voltage IP only responded with 4 out of 5 requests. 2. The results it did send back are completely incorrect. Channel 2 responded with a voltage of zero, Channel 3 responded with a voltage I can’t read from the signaltap, but I know it was incorrect. Channel 4 responded with 0x1D00 which in voltage conversion equals 0.113 volts, but in temperature conversion equal 29C, which makes sense. The last channel read 6 equals zero as well. There is no way I could be reading from the FPGA, if these were the actual voltages. It seems like the two blocks (temperature / voltage) get confused and the temperature data somehow outputs on the voltage request. We are using the following part: 1SG280HU2F50E2VGS1 It is a ES sample on the H-tile Intel Eval board. Is there an errata regarding this? I do not have a small QAR project at the moment, just our full design. I will try and find time to optimize everything out and send you a smaller version to test with. Thank you, --Will - JonWay_altera
Frequent Contributor
@WGith,
There is no errata regarding this.
When you have a simple design, send it over, i can help to check further.
- JonWay_altera
Frequent Contributor
Hi @WGith
I modified the youtube design example to make it simpler. Upgraded the IP to 18.1, recompiled. Attached file. can you test it?
In System Console, run the below scripts:
# Setting up ISSP
set issp_index 0
set issp [lindex [get_service_paths issp] 0]
set claimed_issp [claim_service issp $issp mylib]
#{cmd_valid, reset, cmd_data [6:0]}
issp_write_source_data $claimed_issp 0x17F
#0x80 TSinactive
#0x17F active
set issp_index 1
set isspVS [lindex [get_service_paths issp] 1]
set claimed_isspVS [claim_service issp $isspVS mylib1]
#{cmd_validVS, reset_VS, cmd_dataVS [15:0]}
issp_write_source_data $claimed_isspVS 0x2025C
#0x10000 VSinactive
#0x2025C VSactive
- JonWay_altera
Frequent Contributor
- WGith
Occasional Contributor
I haven't had a chance to look at your new example yet. It maybe a while, but here is an archived project of mine. In this design, teh voltage IP appears to work, but the temperature IP is not.
- WGith
Occasional Contributor