element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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 Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • 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
RIoTboard
  • Products
  • Dev Tools
  • Single-Board Computers
  • RIoTboard
  • More
  • Cancel
RIoTboard
Forum Trouble with ttl to usb interface
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join RIoTboard to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 27 subscribers
  • Views 1816 views
  • Users 0 members are here
  • interrupt
  • ttl
  • usb
  • riotboard
  • display
  • interface
  • usbttl
  • prompt
  • keypress
  • booting
Related

Trouble with ttl to usb interface

Former Member
Former Member over 10 years ago

Hey guys, riotboard noob here!  A local computer store had a USB to TTL serial cable based on the PL2303 chip and I can see the boot information through screen and minicom as my riotboard is booting up so that's working just fine.  However, when it comes to the prompt where I can press any key to interrupt the boot sequence, nothing works.  Neither keypresses on the host computer (Ubuntu Linux) or an attached usb keyboard will interrupt the 3 second timer.  What am I doing wrong?  I apologize in advance if this is a painfully obvious problem.  I'm really stumped, though!

 

Background: I purchased the 7" LCD display and connector board for my riotboard.  I'm following the documentation where it instructs me to interrupt the boot sequence so I can enter the appropriate parameters to enable the screen.

  • Sign in to reply
  • Cancel

Top Replies

  • johnbeetem
    johnbeetem over 10 years ago +1
    I'm not a RIoTboard user but I've done a lot of UART. Here are a few things I'd try. First, make sure the USB UART dongle is working by itself. Unplug it from the RIoTboard and connect the RX and TX bits…
Parents
  • johnbeetem
    0 johnbeetem over 10 years ago

    I'm not a RIoTboard user but I've done a lot of UART.

     

    Here are a few things I'd try.  First, make sure the USB UART dongle is working by itself.  Unplug it from the RIoTboard and connect the RX and TX bits to each other.  Then start up your terminal emulator and see if it echoes the characters you type to the screen.

     

    If this doesn't work, you either have a bad USB UART dongle or you don't have the serial configuration right.  Specifically, be sure that flow control is OFF or NONE since you only have RX and TX.

     

    Once the USB UART echo works, make sure you have the correct serial config for RIoTboard.  You obviously have the Baud rate correct or you wouldn't be seeing the boot trace.  I think the correct setting is 115200N8 so make sure you have parity turned OFF, 8 bits per byte, and flow control OFF.

     

    Otherwise, as Gary says you probably need a 'scope to see the signal from USB UART TX to RIoTboard RX.

     

    Hope this helps!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • johnbeetem
    0 johnbeetem over 10 years ago

    I'm not a RIoTboard user but I've done a lot of UART.

     

    Here are a few things I'd try.  First, make sure the USB UART dongle is working by itself.  Unplug it from the RIoTboard and connect the RX and TX bits to each other.  Then start up your terminal emulator and see if it echoes the characters you type to the screen.

     

    If this doesn't work, you either have a bad USB UART dongle or you don't have the serial configuration right.  Specifically, be sure that flow control is OFF or NONE since you only have RX and TX.

     

    Once the USB UART echo works, make sure you have the correct serial config for RIoTboard.  You obviously have the Baud rate correct or you wouldn't be seeing the boot trace.  I think the correct setting is 115200N8 so make sure you have parity turned OFF, 8 bits per byte, and flow control OFF.

     

    Otherwise, as Gary says you probably need a 'scope to see the signal from USB UART TX to RIoTboard RX.

     

    Hope this helps!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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