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
      • 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
Avnet Boards General Recycling Com port numbers while testing MicroZed boards
  • 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 1 reply
  • Subscribers 353 subscribers
  • Views 174 views
  • Users 0 members are here
Related

Recycling Com port numbers while testing MicroZed boards

Former Member
Former Member over 11 years ago

Hi,

I have an application using a MicroZed board and a custom carrier board. Now that it is almost ready I would like to test multiple combinations of these two.
Some of the initial testing is done buy means of the USB <=> serial port bridge chip.

That works just fine but every time I connect a different MicroZed board a different driver is installed and an individual com port number is assigned.

How could I arrange things so that it always uses the same com port number when I connect to a MicroZed board.

It would make life a bit easier so any suggestion/idea would be much appreciated.

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

    The CP2104 USB-UART used on the MicroZed has a unique serial number for each device. This is normally a good feature in that you can connect multiple MicroZed SOMs to a host at the same time and each will automatically be assigned an individual driver/com port.

     

    In the case of testing though it can be annoying. We ran into this issue with testing at our CM (Contract Manufacturer) and determined that there were 3 options:

     

    1.       CM has to uninstall the COM after each test

    2.       CM has to specifically assign the COM during each test

    3.       CM lets the PC increment the COM, and likewise has to increment their Terminal connection. After 50+ tests, they’ll have to go in and delete all the unused COM ports.

     

    There might be one other possibility if you have a limited number of unique MicroZeds that you wanted to exchange repeatedly. This app note from SiLabs indicates that you can reprogram the ID in the CP2104:

     http://www.silabs.com/support%20documents/technicaldocs/an144.pdf

     

    You might be able to program all of your MicroZed CP2104s to the same ID number, as long as you never plan to have more than one attached to the host at the same time. I have not tried this.

     

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