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
  • 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
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • 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
PicoZed Hardware Design Possible Carrier errata? USB device mode.
  • 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 5 replies
  • Subscribers 338 subscribers
  • Views 545 views
  • Users 0 members are here
Related

Possible Carrier errata? USB device mode.

Former Member
Former Member over 10 years ago

I'm trying to get my picozed to operate in USB device mode, and apart from the massive struggle with Petalinux kernel configuration, I'm starting to wonder if the hardware is not part of the problem as well.

According to page 74 of the USB phy datasheet:
(http://ww1.microchip.com/downloads/en/DeviceDoc/3320.pdf)

The Vbus pin of the phy needs to be connected (with appropriate series resistance and bypass capacitance) to the +5V power coming from the host.

The jumpers on the carrier board allow for appropriate configuration in terms of Rvbus and Cvbus mentioned above, but diode D5 on the carrier board is preventing the phy from seeing the +5V from the host. I suspect that this will prevent it from enabling its pull-up speed-identification resistor on D+ which is what tells the host that a device is connected.

Can anybody confirm for me that their PicoZed+Carrier board is capable of operating in device mode? and if so can you share your linux image and/or kernel configuration options?

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    0 Former Member over 10 years ago

    Diode D5 on the PicoZed Carrier Card is connected to UDB_VBUS_UART in the USB UART circuit, which is not the USB interface you are attempting to use. D15, which is connected to the USB_VBUS, is a circuit protection device that should not interfere with normal operation.

     

    Please do not make duplicate posts of the same question. I will delete the duplicate post.]

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 10 years ago

    Diode D5 on the PicoZed Carrier Card is connected to UDB_VBUS_UART in the USB UART circuit, which is not the USB interface you are attempting to use. D15, which is connected to the USB_VBUS, is a circuit protection device that should not interfere with normal operation.

     

    Please do not make duplicate posts of the same question. I will delete the duplicate post.]

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • Former Member
    0 Former Member over 10 years ago in reply to Former Member

    Oops. I meant D15..



    Yes, I know it's a protection device, but I'm not convinced that it isn't interfering. Electrically, the carrier board is capable of meeting the datasheet specified configurations for host and OTG mode, but it is not for device mode.



    Can you point me to any examples of a Picozed + CC setup working in device mode? I'm really really stuck.



    Also sorry about the double post... The captcha images and I were not getting along yesterday.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 10 years ago in reply to Former Member

    Have a look at this evaluation board that microchip makes for the USB3320.


    http://ww1.microchip.com/downloads/en/DeviceDoc/evb3320.pdf

    This board is configured "Out of the box" to operate in device mode, and they have it connected just as the datasheet recommends, with 10k ohms of series resistance and a 2.2uF bypass cap on the usb connector side.


    Furthermore, if you read page 3 of the user manual here:

    http://ww1.microchip.com/downloads/en/DeviceDoc/evb3320user.pdf


    It clearly states that, "The USB controller must detect VBUS when a USB cable is attached in device mode"


    D15 on the Carrier Card will prevent VBUS detection and prevent the phy from operating properly in device mode.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 10 years ago in reply to Former Member

    Hi Troy,

     

    I do not think that D15 should prevent VBUS detection, but you could always short the device to test the theory.

     

    I am still investigating, but I think the more likely source of your issue is that the USB_OTG_CPEN signal on the PZCC FMC Carrier card, driven by the CPEN pin of the 3320 on the PicoZed SOM, is being asserted. This will cause U15 to drive USB_VBUS, as it should in Host or OTG mode which is the default for the PicoZed. I suspect that your PetaLinux driver will need to write to the 3320 to de-assert CPEN for USB device mode to operate correctly.

     

    -Gary

    • 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 © 2025 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