element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet & Tria Boards Community
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • More
  • Cancel
Avnet & Tria Boards Community
Avnet Boards Blog PYNQ v2.6 on Ultra96v2
  • Avnet Boards Blog
  • Forums
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet & Tria Boards Community to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: ralphjy
  • Date Created: 3 Nov 2020 6:19 AM Date Created
  • Views 7020 views
  • Likes 3 likes
  • Comments 30 comments
  • ultra96-v2
  • pmbus
  • pynq v2.6
Related
Recommended

PYNQ v2.6 on Ultra96v2

ralphjy
ralphjy
3 Nov 2020

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 ctammann  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.

  • Sign in to reply

Top Comments

  • ctammann
    ctammann over 5 years ago +1
    Hey Ralph, Thanks for your interest in this functionality. Let me follow up with my team specifically about the 38060. Without knowing the code, what you say above makes sense if the called out address…
  • ctammann
    ctammann over 5 years ago in reply to ralphjy +1
    Hey Ralph, So the PS vs PL only matters for the reporting from the UltraScale device. The regulator info should still be accessible the same way. I don't know that there is a config file for that, but…
  • ctammann
    ctammann over 5 years ago in reply to ralphjy +1
    Hey Ralph, Check out this dtsi on the UltraZed platform - https://github.com/Avnet/meta-avnet/blob/master/recipes-bsp/device-tree/files/uz7ev-evcc/system-bsp.dtsi specifically lines 48 - 86 where the I2C…
  • albertabeef
    albertabeef over 5 years ago in reply to ralphjy

    Ralph,

    Thank you for taking the time to research this.

    Your observation is very useful, and will certianly avoid a lot of head scratching.

     

    My conclusion:
    Before using a sensors.conf file, cross-validate with "sensors -u", just to be certain.

    Do you plan on attempting to display these values graphically ?

    Regards,Mario.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • ralphjy
    ralphjy over 5 years ago in reply to albertabeef

    Ok, I figured out what's going on with the labeling but I have no idea why.  Maybe Chris would know.

     

    I installed the lm-sensors package on PYNQ and it correlates with the notebook and gives me a sensible output. (I still don't have the ir38060 because I'm missing the kernel patch).  This is using the ultra96.conf files supplied with PYNQ.

    image

     

    By running "sensors -u" I figured out that this version of sensors only reports 1 input and 5 outputs for the irps5401 (the version running on Vitis-AI 1.2 reports 5 inputs and 5 outputs).  That's why the labeling on PYNQ ignores the first value (it's only labeling and reporting outputs).

     

    The version that I installed is libsensors 3.4.0.  The version installed on Vitis-AI 1.2 is 3.5.0.  I tried to install that version but the version was not found.  PYNQ is running on Ubuntu 18.04.  I would doubt that this is a version problem, so I'm missing something, but worst case it just means that there will need to be different conf files.

     

    Ralph

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • ralphjy
    ralphjy over 5 years ago in reply to albertabeef

    Hi Mario,

     

    Thanks, what you indicated makes sense when looking at the output with sensors -u.  It's obvious that the PYNQ PMBus library is doing something different to interpret the ultra96.conf file.  Haven't found that code yet.

     

    Since none of these PMICs are specified in the /etc/sensors3.conf, I guess the sensors output must just be default behavior.

     

    I'll need to verify that the PYNQ output is correct.  The sensors command does not run from the command line in PYNQ.  I'll try installing the sensors package and see if that correlates.

     

    Ralph

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • albertabeef
    albertabeef over 5 years ago in reply to ralphjy

    Ralph,


    Regarding the labels specified for the irps5401 device, pin1-pin5 and pout1-pout5 are associated with power1-power10, and iin1-iin4 and iout1-iout5 are associated with curr1-curr9, as follows:

      pin1 == power1

      pin2 == power2

      ...

      pin5 == power5

      pout1 == power6

      pout2 == power7

      ...

      pout5 == power10

    A little different for the currents:
       iin1 == curr1 

       iin2 == curr2

      ...

      iin4 == curr4

      iout1 == curr5

      iout2 == curr6

      ...

      iout5 == curr9

     

    To discover what this fixed mapping is for a device, call the "sensors" command with the "-u" option to display raw data.  It will generate this type of output:

    pin1:

      power1_input: 0.156

      power1_alarm: 0.000

    ...

    pin5:

      power5_input: 0.062

      power5_alarm: 0.000

    pout1:

      power6_input: 0.188

    ...

    pout5:

      power10_input: 0.047

     

    iin1:

      curr1_input: 0.007

      curr1_alarm: 0.000

    ...

    iin4:

      curr4_input: 0.093

      curr4_alarm: 0.000

    iout1:

      curr5_input: 0.109

      curr5_max: 2.000

      curr5_crit: 2.500

      curr5_max_alarm: 0.000

      curr5_crit_alarm: 0.000

    ...

    iout5:

      curr9_input: 0.039

      curr9_max: 0.652

      curr9_crit: 0.718

      curr9_max_alarm: 0.000

      curr9_crit_alarm: 0.000

     

    To verify if the ultra96.conf file is correct (which I think it is not), you can run the "sensors" command with the "-c" option, and specify the .conf file.

    Hope this helps, and please let me know what you think of the above explanation,
    Mario.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • ralphjy
    ralphjy over 5 years ago in reply to ctammann

    Hi Chris,

     

    I did verify that last night on the Ultra96v2.  I have the old 3A and 3.5A limits.  Have other limits changed? - I noticed comparing to your readback that other current limits are also different. (sorry - I've got this captured in a text file vs a screenshot).  Also noted that your readout doesn't have as many input readings - is there a flag or config that I should set?

     

    irps5401-i2c-6-43

    Adapter: i2c-0-mux (chan_id 4)

    vin1:          5.09 V  (min =  +4.12 V, crit max =  +5.50 V)

    vin2:          5.06 V  (min =  +4.12 V, crit max =  +5.50 V)

    vin3:          5.06 V  (min =  +4.12 V, crit max =  +5.50 V)

    vin4:          5.12 V  (min =  +4.12 V, crit max =  +5.50 V)

    vin5:          4.98 V  (min =  +0.00 V, crit max =  +6.00 V)

    vout1:         1.80 V  (crit min =  +1.65 V, min =  +1.70 V)

                           (max =  +1.90 V, crit max =  +1.95 V)

    vout2:         1.20 V  (crit min =  +1.10 V, min =  +1.15 V)

                           (max =  +1.25 V, crit max =  +1.30 V)

    vout3:         1.10 V  (crit min =  +1.00 V, min =  +1.05 V)

                           (max =  +1.15 V, crit max =  +1.20 V)

    vout4:       851.00 mV (crit min =  +0.75 V, min =  +0.80 V)

                           (max =  +0.90 V, crit max =  +0.95 V)

    vout5:         3.31 V  (crit min =  +2.48 V, min =  +2.90 V)

                           (max =  +3.73 V, crit max =  +4.14 V)

    temp1:        +53.0 C  (high = +120.0 C, crit = +128.0 C)

    temp2:        +53.0 C  (high = +120.0 C, crit = +128.0 C)

    temp3:        +53.0 C  (high = +120.0 C, crit = +128.0 C)

    temp4:        +53.0 C  (high = +120.0 C, crit = +128.0 C)

    temp5:        +53.0 C  (high = +120.0 C, crit = +128.0 C)

    pin1:        156.25 mW

    pin2:          0.00 W

    pin3:         93.75 mW

    pin4:          1.16 W

    pin5:        812.50 mW

    pout1:       156.25 mW

    pout2:         0.00 W

    pout3:        93.75 mW

    pout4:         1.06 W

    pout5:       546.88 mW

    iin1:         31.00 mA

    iin2:          0.00 A

    iin3:         23.00 mA

    iin4:        226.00 mA

    iout1:        93.00 mA (max =  +0.50 A, crit max =  +0.75 A)

    iout2:         0.00 A  (max =  +2.00 A, crit max =  +2.50 A)

    iout3:       109.00 mA (max =  +1.00 A, crit max =  +1.50 A)

    iout4:         1.26 A  (max =  +3.00 A, crit max =  +3.50 A)

    iout5:       165.00 mA (max =  +0.72 A, crit max =  +0.72 A)

     

    I also looked at the VCU voltage on my UltraZed-EV and that looks okay.  If I interpreted it correctly.

     

    irps5401-i2c-3-4a

    Adapter: i2c-0-mux (chan_id 1)

    vin1:         12.16 V  (min = +10.50 V, crit max = +14.00 V)

    vin2:         12.06 V  (min = +10.50 V, crit max = +14.00 V)

    vin3:         12.06 V  (min = +10.50 V, crit max = +14.00 V)

    vin4:         12.06 V  (min =  +9.00 V, crit max = +14.00 V)

    vin5:          3.33 V  (min =  +0.99 V, crit max =  +4.00 V)  ALARM (MIN)

    vout1:       898.00 mV (crit min =  +0.60 V, min =  +0.75 V)

                           (max =  +1.02 V, crit max =  +1.25 V)

    vout2:         1.20 V  (crit min =  +1.00 V, min =  +1.05 V)

                           (max =  +1.32 V, crit max =  +1.35 V)

    vout3:         1.10 V  (crit min =  +0.80 V, min =  +0.90 V)

                           (max =  +1.25 V, crit max =  +1.35 V)

    vout4:       480.00 mV (crit min =  +4.60 V, min =  +4.75 V)

                           (max =  +6.00 V, crit max =  +5.40 V)

    vout5:         1.80 V  (crit min =  +1.36 V, min =  +1.58 V)

                           (max =  +2.04 V, crit max =  +2.27 V)

    temp1:        +40.0 C  (high = +100.0 C, crit = +120.0 C)

    temp2:        +40.0 C  (high = +100.0 C, crit = +120.0 C)

    temp3:        +40.0 C  (high = +100.0 C, crit = +120.0 C)

    temp4:        +40.0 C  (high = +100.0 C, crit = +120.0 C)

    temp5:        +40.0 C  (high = +100.0 C, crit = +120.0 C)

    pin1:          0.00 W

    pin2:          0.00 W

    pin3:          0.00 W

    pin4:          0.00 W

    pin5:          0.00 W

    pout1:         0.00 W

    pout2:         0.00 W

    pout3:         0.00 W

    pout4:        93.75 mW

    pout5:         0.00 W

    iin1:          0.00 A

    iin2:          0.00 A

    iin3:          0.00 A

    iin4:          0.00 A

    iout1:         0.00 A  (max =  +2.50 A, crit max =  +3.00 A)

    iout2:         0.00 A  (max =  +2.81 A, crit max =  +3.75 A)

    iout3:        15.00 mA (max =  +2.50 A, crit max =  +3.75 A)

    iout4:        10.56 A  (max =  +3.50 A, crit max =  +4.00 A)

    iout5:         0.00 A  (max =  +0.65 A, crit max =  +0.72 A)

     

     

    Another question - I was looking at adding labeling in the sensors.conf file and looking at the ultra96.conf example from the PYNQ build it looks like the first set of pins are ignored?  Is there a description of what the sensors program is doing relative to the conf settings?   It appears that for this particular Vitis-AI 1.2 build that there aren't any labels set for these PMICs in either /etc/sensors3.conf or /etc/sensors.d/sensors.conf, but the pins come out 1-5 rather than 2-6.  Seems odd.

     

    From ultra96.conf:

    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"

     

    Thanks,

    Ralph

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube