Group Actions
Engagement
  • Author Author: ralphjy
  • Date Created: Date Created
  • Views 7019 views
  • Likes 3 likes
  • Comments 30 comments
Related
Recommended

PYNQ v2.6 on Ultra96v2

ralphjy

Last week I saw an announcement that PYNQ v2.6 is available for the Ultra96v1 and Ultra96v2 https://discuss.pynq.io/t/pynq-v2-6-is-avialable-for-ultra96-v1-and-v2/1951 .

 

PYNQ v2.6 is compatible with Xilinx tools version 2020.1.  DPU-PYNQ for v2.6 isn't available yet but because a pre-built image for the Ultra96v2 is available for PYNQ v2.6, I thought that I'd see what has changed from v2.5.

 

The first thing that I noticed is that there are 3 new notebooks in the Common directory

  1. display_port_introduction.ipynb
  2. programming_pybind11.ipynb
  3. ultra96_pmbus.ipynb

 

image

 

The pmbus notebook caught my eye because I had attended the PMBus webinar that Chris Ammann   had presented back in July PMBus and Power Supply Telemetry .

Chris had mentioned to me that the next BSP release will include the capability to update the PMICs on the Ultra96v2 and the UltraZed-EV and I expect will also include the sensors program that will display the PMIC settings.

 

I hoped that this pmbus notebook might provide the same information as that sensors program provided, i.e. the voltage and current measurements and settings for the all the PMICs.

 

The slide from the webinar shows the 3 PMICs and the 11 voltages that they control on the Ultra96v2 (I am not sure about the configuration of the Ultra96v1).

image

 

Running the pynq.get_rails() function almost works.  It provides the voltage, current and power information for the 2 IRPS5401 parts.  Unfortunately it lists the 10 voltages in alphabetical order by name rather than by IC position.  I can fix that easily enough but I don't understand why IR38060 (5V) isn't listed.  I also don't understand all the garbled stuff at the end.

 

image

 

I looked at the ultra96.conf file in /etc/sensors.d/ directory and the entry for the IR38060 at the end looks incorrect but I'm not quite sure what it should be.

I think it should be :

chip "*-i2c-6-45"

        label in1 "5V"

        label curr1 "5V"

        label power1 "5V"

 

I'll try that tomorrow.

 

ultra96.conf

bus "i2c-6" "i2c-0-mux (chan_id 4)"


chip "*-i2c-6-43"
        ignore in1
        ignore power1
        ignore curr1
        label in2 "AUX"
        label in3 "1V2"
        label in4 "PSDDR"
        label in5 "INT"
        label in6 "3V3_D"
        label power2 "AUX"
        label power3 "1V2"
        label power4 "PSDDR"
        label power5 "INT"
        label power6 "3V3_D"
        label curr2 "AUX"
        label curr3 "1V2"
        label curr4 "PSDDR"
        label curr5 "INT"
        label curr6 "3V3_D"

chip "*-i2c-6-44"
        ignore in1
        ignore power1
        ignore curr1
        label in2 "PSAUX"
        label in3 "PSINT_LP"
        label in4 "3V3"
        label in5 "PSINT_FP"
        label in6 "PSPLL"
        label power2 "PSAUX"
        label power3 "PSINT_LP"
        label power4 "3V3"
        label power5 "PSINT_FP"
        label power6 "PSPLL"
        label curr2 "PSAUX"
        label curr3 "PSINT_LP"
        label curr4 "3V3"
        label curr5 "PSINT_FP"
        label curr6 "PSPLL"

chip "*-i2c-6-45"
        #ignore power1
        label in1 "VIN"
        label curr1 "5V"
        label power1 "5V"
        label in2 "5V"
        compute in2 @/256,@*256

 

 

Anyway, I'll play with this some more.  The notebook also includes a DataRecorder class that allows you to record/plot the sensor measurements while running tests.  Here's a link to the PYNQ library documentation https://pynq.readthedocs.io/en/v2.6.1/pynq_libraries/pmbus.html .

 

Hope the updated DPU-PYNQ is available soon and also the new BSP release so I can update the current limit for running the DPU.

  • in reply to albertabeef

    Mario,

    Looks good.  Hopefully, someone will have a fix for the plt.show() issue.

    I'll give it a try tomorrow.  I also need to update my Ultra96 tomorrow.

    I think I ran into a problem installing pysensors but I can't recall.  I'll have to fix that tomorrow too.

     

    Ralph

  • in reply to ralphjy

    Ralph,

    I have a python script that displays the power/current values as bar plots on this hackster.io project:

    http://avnet.me/pmbus-power-monitoring-py

    It is not yet published, as it is in progress.

    Regards,

    Mario.

  • in reply to ctammann

    Thanks Chris,

     

    I'll give it a try later this week and give you feedback via PM.

     

    Ralph

  • in reply to ralphjy

    Hey Ralph,

    I haven't done the PMIC update using PYNQ. Because I don't want to hold you up, I've sent you a PM with an alternative method. Please let me know if you have any issues.

    Thanks

    Chris

  • in reply to albertabeef

    Hi Mario,

     

    My plan was to use the DataRecorder in the PYNQ PMBus library to do the plots.  The example PMBus notebook has an example of that.  Of course, I can't do that for the DPU tests since the DPU upgrade isn't available yet for PYNQ v2.6 (haven't tried to see if the PMBus library works on v2.5.1).  I also need to get the PL supply current limit updated on my Ultra96v2.  I realized that I've been running all of your Vitis-AI tutorials on my UltraZed-EV so maybe the problem I'm having on the Ultra96v2 is not new.  I'm not sure why I don't get the EDID and other errors when I'm running PYNQ.  I tried running with a DisplayPort input on the monitor (vs HDMI with active adapter) but I still get the errors.  Using the DisplayPort input the display comes up cleanly on boot (with HDMI it does not) so that may not be a real problem.  I noticed that I get reboots when I try to run the Vitis-AI examples but that could be because of the current limit.

     

    Anyway, I'm running the Vitis-AI 1.2 examples on the UltraZed-EV.  I had hoped that you would get your python plotting working image.  I'm busy for the next week or so, otherwise I'd give it a try now.

     

    Ralph