Bluetooth issue with 1DX Murata module

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:

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

Bryan

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.patch

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

Could you please help me to understand the issue?

Thanks

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

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!

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

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

Thank you bhfletcher for your precious help!

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

Hey Lotfi, did you need to do anything special or different from the instructions on the guide you linked to get wifi working? I've gone through it with the 2020.2 petalinux tools and when the OS attempts to load the driver, I get:

Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2

The top of the guide has some remark about update for petalinux 2017.4, but it doesn't actually say anything about what if anything different we're supposed to do.

Hello,

Nothing different has been done for Wi-Fi.

Be careful with the firmware filenames and paths when you copy them into the rootfs:

Wi-Fi --> /lib/firmware/brcm/

                                             --> brcmfmac43430-sdio.bin

                                             --> brcmfmac43430-sdio.txt

                                             --> brcmfmac43430-sdio.xlnx,zynq-zed.txt (this one is the filename for the zedboard, try to copy the above .txt file and change the name)

boot with the ZedBoard, and try to raise the wlan0 interface with "ifup wlan0"

If it works , you should be able to see your interface with "ifconfig"

So, followup question. How did you get ahold of the firmware images in the first place?

You will find the latest 1DX Murata firmware here: https://github.com/murata-wireless