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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
ZedBoard Hardware Design Bluetooth issue with 1DX Murata module
  • 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 Verified Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 325 subscribers
  • Views 2866 views
  • Users 0 members are here
  • bluetooth
  • zedboard
  • wi-fi
  • lbee5kl1dx
  • 1dx pmod
  • 1dx
  • murata
Related

Bluetooth issue with 1DX Murata module

3d_srv
3d_srv over 4 years ago

Hello everybody,

 

I'm trying to enable Wi-Fi & Bluetooth connectivity to the ZedBoard, using the 1DX Wi-Fi/BT module (LBEE5KL1DX-883)

A complete tutorial has already been done here: Adding Wi-Fi and Bluetooth Connectivity to the ZedBoard using the Murata 1DX Pmod

 

I succeeded in enabling Wi-Fi, but I'm facing a persistent issue when I try to enable Bluetooth.

I'm using the Harware design provided here (Reference designs section): https://www.avnet.com/wps/portal/us/products/avnet-boards/avnet-board-families/zedboard/

 

image

 

Here is the script I run to enable Bluetooth:

image

 

And here is the issue (bluetooth LED is turned ON when the script is launched):

image

 

Is somebody able to know where I should go to fix this issue concerning hciattach?

 

Regards

  • Sign in to reply
  • Cancel

Top Replies

  • bhfletcher
    bhfletcher over 4 years ago +2
    Looking at your block diagram, you are using a PL-based, AXI-uart16550 for your Bluetooth UART interface. However, assuming these old comments are accurate, you are pointing things to the PS-based UART0…
  • bhfletcher
    bhfletcher over 4 years ago in reply to 3d_srv +1
    Hopefully some of the other software experts can chime in. From what I can tell from your hardware block diagram, you are using a PL-based UART to connect to the Bluetooth. If the PL-based TTYS* device…
  • 3d_srv
    3d_srv over 4 years ago in reply to bhfletcher +1 verified
    Update: It's working, and it was exactly what I thought : if you want ttyS0 to appear you have to make sure the UART IP block is recognized. The problem is that it's not documented at all: UART 16550 IP…
Parents
  • bhfletcher
    0 bhfletcher over 4 years ago

    Looking at your block diagram, you are using a PL-based, AXI-uart16550 for your Bluetooth UART interface. However, assuming these old comments are accurate, you are pointing things to the PS-based UART0:

    image

     

    I suggest you look at /dev/tty* and see what you actually have there.

     

    Bryan

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • 3d_srv
    0 3d_srv over 4 years ago in reply to bhfletcher

    image

     

    here is the list for /dev/tty. I guess it is initialising PS uart.


    Here is the patch for hciattach command. It is placed in /project-spec/recipe-connectivity/bluez5/bluez5/hciattach-reset-delay-bluez-5.41.patchimage

    Is this patch in the right folder in order to be taken into account?

     

    Could you please help me to understand the issue?

     

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bhfletcher
    0 bhfletcher over 4 years ago in reply to 3d_srv

    Hopefully some of the other software experts can chime in. From what I can tell from your hardware block diagram, you are using a PL-based UART to connect to the Bluetooth. If the PL-based TTYS* device is not showing up in your /dev folder, then I'm guessing that is a devicetree issue, but again, that's not my area of expertise. If you are trying to use the PS-based UART to connect to the Bluetooth, then you need to change your block design.

     

    Bryan

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • bhfletcher
    0 bhfletcher over 4 years ago in reply to 3d_srv

    Hopefully some of the other software experts can chime in. From what I can tell from your hardware block diagram, you are using a PL-based UART to connect to the Bluetooth. If the PL-based TTYS* device is not showing up in your /dev folder, then I'm guessing that is a devicetree issue, but again, that's not my area of expertise. If you are trying to use the PS-based UART to connect to the Bluetooth, then you need to change your block design.

     

    Bryan

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • 3d_srv
    0 3d_srv over 4 years ago in reply to bhfletcher

    So my problem is coming from the UART 16550 block which is not recognized and should be as /dev/ttyS0, isn't it?

     

    It seems that this block raised recent problems:

    https://forums.xilinx.com/t5/Embedded-Linux/Uart-16550-IP-not-showing-up-in-Petalinux/td-p/1187552

     

    I will check if "device tree based probing for 8250 ports" is enabled on the kernel config and I will give an update.

     

    Thanks for your help!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • 3d_srv
    0 3d_srv over 4 years ago in reply to bhfletcher

    Update:

     

    It's working, and it was exactly what I thought : if you want ttyS0 to appear you have to make sure the UART IP block is recognized. The problem is that it's not documented at all:

     

    UART 16550 IP block needs some options available with petalinux-config -c kernel:

     

    - 8250/16550 and compatible serial support

         - Support 8250_core.* kernel options

         - DMA support for 16550 compatible UART controllers

     

    - Devicetree base probing for 8250 ports

     

    - Cadence (Xilinx Zynq) UART support

    - Cadence UART console support

      image

    And then the hciattach function does not return any time out, and Bluetooth pairing works fine.

    Thank you bhfletcher for your precious help!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • bhfletcher
    0 bhfletcher over 4 years ago in reply to 3d_srv

    That is great news! Thank you 3d_srv for sharing these valuable findings with the community!

     

    For anyone else that is interested in experimenting with the Murata 1DX Wi-Fi, this is the same radio that is native on the AES-MINIZED-7Z007-G MiniZed. Or you have the option of adding the AES-PMOD-MUR-1DX-G Pmod to any Pmod-capable board.

     

    Bryan

     

    Murata 1DX PmodMurata 1DX Pmod

    MiniZed with Murata 1DX RadioMiniZed with Murata 1DX Radio

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