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 Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultrazed Hardware Design Ultrazed-EV: Unable to locate the Infineon power chips. ( PMBUS )
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 354 subscribers
  • Views 1158 views
  • Users 0 members are here
  • ultrazed-ev
  • i2c
  • infineon;
  • pmbus
Related

Ultrazed-EV: Unable to locate the Infineon power chips. ( PMBUS )

deville
deville over 6 years ago

Hi Avnet,

 

Currrently i'm tying to make a connection with all the I2C devices on the Ultrazed-EV board. I managed to reach the eeproms, the gpio extender and the i2C mux but i'm struggling to make this final I2C connection to the Infineon chips.

 

I see all the chips via the Infineon software and the USB005 dongle which gives me a nice overview of the chips and their correlating  addresses ( image below )

image

 

However I don't seem to manage to connect to them via the Zynqmp Linux root files system. The address 0x6a , which is the PLL chip behind the i2c mux, seems to been found by it's diver.  I think there should be 4 Infineon chips in this i2c region/channel (U18, U19 U21 end U22 )

 

image

 

Can someone point out to me how I can make these infineon chips appear in the root file system?  Any help is very welcome..

 

Thanks Deville

  • Sign in to reply
  • Cancel
  • deville
    0 deville over 6 years ago

    I found this solution rather quickly in the end.

     

    I must have used a device tree snippet from the zcu102 board or just made a plain mistake. Either way I used (the device tree ) compatible string  "nxp,pca9542" instead of the I2C chip used on the Ultrazed board.  "pca9543" 

    Both devices are using the same driver  ( drivers/i2c/muxes/i2c-mux-pca954x.c ) but the pca9542 chip is a mux, while pca9543 is in fact a switch. This mixup caused the driver to treat the device differently, trying to set a mux channel ( value 0x04 )

     

    Now I have my devices:

    image

     

    Thanks Avnet !

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • deville
    0 deville over 6 years ago in reply to deville

    Another Issue popped up after finding the previous solution. On the UltraZed-EV board there are some Infineon chips with PMBUS capabilities present like i mentioned at the start of this thread.

     

    These chips have no drivers present in my kernel ( 4.14 ) so I used the generic PMBUS driver. However there should be some PMBUS Sysfs entries present once booted but this seems not to be working.

     

    All I get is:

    [zynqmp@zynqmp ~ ]$ dmesg | grep pmbus
    [    1.475625] pmbus 1-004b: PMBus status register not found
    [    1.475921] pmbus 1-004c: PMBus status register not found
    [    1.476212] pmbus 1-0049: PMBus status register not found
    [    1.476503] pmbus 1-004a: PMBus status register not found
    [    1.490635] pmbus 2-0046: No attributes found
    [    1.504554] pmbus 2-0047: No attributes found
    [    1.520525] pmbus 2-0048: No attributes found

     

    Can you give me any advice on this issue Avnet?  Should I be doing my own readout from userspace? ( I can do readouts and manipulations via the I2C tools )

     

    Thanks in advance

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • narrucmot
    0 narrucmot over 6 years ago in reply to deville

    Hi deville,

    Can you share your <petalinux project folder>/project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi file with me?  I suspect it is missing the correct descriptions of the I2C mux and Infineon PMICs.

     

    Thanks,

    Tom

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • deville
    0 deville over 6 years ago in reply to narrucmot

    Hi narrucmot

     

    Yes certainly, I must say I don't use Petalinux but it just should be same.

     

    Thanks for your help on this. 

     

     

    &i2c1 {
         status = "okay";
         clock-frequency = <100000>;
         i2c-eeprom1@50 {
              #size-cells = <0>;
              #address-cells = <1>;
              compatible = "at,at24c08";
              reg = <0x50>;
         };
    
         /*later kernels onnn,pca9654 */
         io_expander: gpio@20 {
              compatible = "onsemi,pca9654";         
              reg = <0x20>;
              pinctrl-names = "default";
              pinctrl-0 = <&i2c1_pins>;
              gpio-controller;
              #gpio-cells = <2>;
              /*interrupt-parent = <&gic>;*/
              /*interrupts = <23 IRQ_TYPE_LEVEL_LOW>;*/
         };
    
         i2c-switch@70 { /* U7 on UZ3EG SOM, U8 on UZ7EV SOM */
              compatible = "nxp,pca9543";
              #address-cells = <1>;
              #size-cells = <0>;
              reg = <0x70>;
              i2c@0 {
                   #address-cells = <1>;
                   #size-cells = <0>;
                   reg = <0>;
                   versaclock@6a {
                        compatible = "idt,5p49v5935" ;
                        reg = <0x6a> ;
                   };
                   mac-eeprom2@51 {
                        #size-cells = <0>;
                        #address-cells = <1>;
                        compatible = "at,at24c08";
                        reg = <0x51>;
                   };
                   ir38063_4b: ir38063@4b { /* IR38063 - U18   */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x4b>;
                   };
                   ir38063_4c: ir38063@4c { /* IR38063 - U19   */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x4c>;
                   };
    
                   irps5401_49: irps54012@49 { /* IRPS5401 - U21   */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x49>;
                   };
                   irps5401_4a: irps54012@4a { /* IRPS5401 - U22   */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x4a>;
                   };
              };
              i2c@1 { /* i2c mw 70 0 1 */
                   #address-cells = <1>;
                   #size-cells = <0>;
                   reg = <1>;
                   irps5401_46: irps54012@46 { /* IRPS5401 - U24   */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x46>;
                   };
                   irps5401_47: irps54012@47 { /* IRPS5401 - U25 */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x47>;
                   };
                   irps5401_48: irps54012@48 { /* IRPS5401 - U26 */
                        #clock-cells = <0>;
                        compatible = "generic,pmbus";
                        reg = <0x48>;
                   };
              };
         };
    };

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • 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