11-22-2018 10:04 AM
Hi,
I try to use the ZCU102 - Board User Interface (BoardUI.exe) to get currents on all power rails.
I follow xtp433 tutorial, I updated board firmware successfully with the 5th July 2017 version.
However in "Power" tab, I can't read any power/voltage or current. It works for the "voltages" tab and "system monitor" tab and others.
I get this error when I try to get the power on PSINTFP for example :
Running sysc func: <interpINA226:0>
Error while running sysc function
Traceback (most recent call last):
File "testthread.py", line 537, in sysc
File "config.py", line 563, in interpINA226
ZeroDivisionError: float division by zero
This is the same error for all powers for PS side and PL side in tab "Use Default Calibration".
Thank you for your answer,
Best regards
01-10-2019 02:01 PM
I have the same problem. I am able to control clocks, read voltage, but unable to read power information and unable to read FMC HPC0 EEPROM Data.
01-10-2019 03:47 PM
06-14-2019 11:02 AM
I am seeing the same problem with Vivado 2018.3, try to read Power - Use Default Calibration - PS Side
Running sysc func: <interpINA226:0>
Error while running sysc function
Traceback (most recent call last):
File "testthread.py", line 537, in sysc
File "config.py", line 563, in interpINA226
ZeroDivisionError: float division by zero
06-14-2019 12:27 PM
Hi Chris,
That problem was fixed on the latest version of the BIT.
On the folder \zcu102_bit\BoardUI\tests\ZCU102, there's a SC.yaml
The first line has this comment:
# Version 1.1 08-14-18 Bradw Fix interpINA226 calls: need shunt resistor value. Passing 0 in most places got divide by 0 error.
Let me know if yours is different.
Thanks,
Andres
06-14-2019 12:42 PM
Hi Andres,
I downloaded rdf0382-zcu102-system-controller-c-2018-3.zip from https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html#documentation. I assummed that is the latest. I found SC.yaml in a different path than what you have shown, I found it at \rdf0382-zcu102-system-controller-c-2018-3\zcu102_scui\tests\ZCU102. Opened SC.yaml and I don't see the comment that you had mentioned.
Thanks
Chris
06-14-2019 01:39 PM
Hi Chris,
Try with rdf0377-zcu102-bit-c-2018-3.zip from the same documentation page and run BoardUI.exe. That one should have the right .yaml file.
Thanks,
Andres
06-14-2019 01:56 PM
Hi Andres,
Power Read worked fine with rdf0377-zcu102-bit-c-2018-3.zip but System Monitor is still having the same issue. See attached screen capture.
Thanks
Chris
06-14-2019 02:12 PM
06-14-2019 02:17 PM
Sorry, sent you the wrong file. See attached
Chris
06-17-2019 06:22 PM
Hi Chris,
That fails for me, too. I'll ask around, but it might take a few days to get a fix.
Thanks,
Andres
09-10-2019 07:53 AM
Hi Andres,
Did you finished to fix it?
Thanks.
Medhi
09-10-2019 05:29 PM
Hello khoja.medhi@gmail.com
I suggest trying it on Vivado 2019.1 because it has worked for me.
I have attached a screenshot of my results working on my machine using Vivado 2019.1
---------------------------------------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
---------------------------------------------------------------------------------------------------------
06-15-2020 02:56 AM
did it worked for power readings too? Your screenshot shows temperature readings only.
I noticed that at
where I would expect latest and greatest versions, there are at least two wersions of GUI:
rdf0382-zcu102-system-controller-c-2019-1.zip with incorrect SC.yaml file and
rdf0377-zcu102-bit-c-2019-1.zip with the corrected one.
I noticed this inconsistency thanks to @andresb comment earlier in this thread.
Unfortunately the one clearly refering to system controller is the buggy one which cost me some time to figure out. Can you have it fixed somehow?
Best regards
Marek
06-15-2020 09:19 AM
Hi Marek,
Usually, the place where to find the latest and greatest versions is the landing page for the board, not the Design Hub:
https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html#documentation
I'm sorry that this issue has cost you time. There's a Change Request to get it fixed (CR-1047802) but files haven't been updated yet.
Thanks,
Andres
06-16-2020 03:42 AM
Thanks @andresb ,
good to know. As design hubs are integrated into docnav(which is tool I really apreciate) I considered it somowhat prefered way.
Archives referenced in the design hub and from the landing page for the board are identical, and so both buggy.
Regards
Marek