Verdin imx8mp RF Tests

Hello,
I want to perform WIFI/Bluetooth regulatory compliance tests on the Verdin iMX8MP SOM. Therefore, I set up the toradex minimal reference image and included the necessary drivers and the labtool, which is provided by the meta-toradex-wifi layer.
I followed the instructions described in the meta-toradex-wifi layer and built the image. This worked fine.
For testing, I started the labtool utility and performed the WIFI tests, which worked fine as well. However, the only thing that did not worked was the bluetooth tests. Labtool is immediately crashes when bluetooth tests are selected.

As pointed out here Verdin imx8mp wifi / bluetooth RF tests and LabTool - #6 by Amik7, I rebuild the whole image again from scratch (deleted sstate-cache, builds and downloads directory). This didn’t resolved the issue.

I tried cleaning the kernel-modules as described in the same thread:

bitbake -c cleanall kernel-module-btmrvl
bitbake kernel-module-btmrvl

This failed, but I think this is not relevant, because the according class (verdin imx8mp) does not include it anyway.

MACHINEOVERRIDES_prepend_verdin-imx8mp = "interface-diversity-sd-uart:"
MACHINEOVERRIDES_prepend_apalis-imx8 = "interface-diversity-pcie-usb:"

MACHINE_EXTRA_RDEPENDS_append_interface-diversity-sd-uart = " \
    kernel-module-mlan \
    kernel-module-moal \
    kernel-module-wifimrvl \
    toradex-wifi-config \
"

I attached the log files according to this thread: Verdin imx8mp wifi / bluetooth RF tests and LabTool - #5 by rafael.tx

Thanks in advance for your support.

BR
Josef
firmware-content.log (571 Bytes)
toradex-wifi-config.conf (180 Bytes)
moal.conf (108 Bytes)
dmesg-bluetooth.log (1000 Bytes)
log.do_fetch.20993 (46.2 KB)
dmesg_mlan.log (622 Bytes)

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello Josef,

Thank you for reaching out with your issue regarding the Bluetooth tests on the Verdin iMX8MP SOM. It sounds like you’ve done a thorough job setting up your environment and troubleshooting so far. Let’s see if we can pinpoint the issue with a few additional steps:

  1. Examine System Logs: Start by reviewing the dmesg logs and any other relevant logs for error messages related to Bluetooth. These logs can offer insights into what might be causing the labtool to crash.

  2. Driver Verification: Double-check that all necessary Bluetooth drivers are installed and loaded correctly. Since you’re using the meta-toradex-wifi layer, ensure that Bluetooth-related drivers are included and properly configured in your build.

  3. Bluetooth Stack Configuration: Verify that the Bluetooth stack is configured correctly. This includes ensuring that the Bluetooth service is active and the hardware is initialized properly. Commands like hciconfig can help you check the status of Bluetooth interfaces.

  4. Driver Compatibility: Ensure that the drivers are compatible with the kernel version in your build. Incompatibilities can sometimes lead to crashes or unexpected behavior.

  5. Rebuild with Debugging: If possible, try rebuilding the labtool with debugging enabled. This might provide more detailed output when the crash occurs, helping to identify the issue.

  6. Alternative Testing Tools: If the problem persists, consider using alternative tools for Bluetooth testing to determine if the issue lies with the labtool or the system configuration.

I hope these steps help you resolve the issue. If you have any further questions or need additional assistance, feel free to reach out.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Verdin imx8mp wifi / bluetooth RF tests and LabTool.

Hello @joschi2804,
It looks like your Bluetooth interface is not up. Did you try to unblock it from rfkill?

rfkill list
rfkill unblock <bluetooth interface number>

And then manually bring up the hci interface:

hciconfig hci0 up

After these procedures, could you try to use labtool again?

Hello @rafael.tx

thanks for the quick response. I tried this already, but it was not working either.
hciconfig responses following:

root@verdin-imx8mp-07129924:~# hciconfig hci0 up
[  199.486021] Bluetooth: hci0: Wait for CTS failed with -110
[  199.486021]
[  199.493088] Bluetooth: hci0: Failed to set baudrate

Hi @rafael.tx

it seems that the problem is related to the used SOM module. I am using right now the 1.0D variant instead of 1.1A.
If I change the toradex-wifi-config to following, I am able to select the bluetooth tests, but WIFI tests are then not working.

blacklist mlan btbcm btqca
install mlan /bin/false
install btbcm /bin/false
install btqca /bin/false

#blacklist mwifiex mwifiex_sdio btmrvl btmrvl_sdio
#install mwifiex /bin/false
#install btmrvl /bin/false

Is this a valid approach or is it possible that you add some “fix” to the meta-toradex-wifi layer?

BR

Hello @joschi2804,

Can you do another build for the image as follows and give it a try:

Modify the meta-toradex-wifi/classes/toradex-wifi-nxp-proprietary-driver.bbclass file from
MACHINEOVERRIDES_prepend_verdin-imx8mp = "interface-diversity-sd-uart:"
to
MACHINEOVERRIDES_prepend_verdin-imx8mp = "interface-diversity-sd-sd:"

I have not tried it, but looks like this should work.

Hi,

sorry for late response. I tried it out today, but labtool still not working. The new bluetooth interface is up and running.

root@verdin-imx8mp-07129924:~# hciconfig
hci1:   Type: Primary  Bus: SDIO
        BD Address: 48:E7:DA:FE:90:BC  ACL MTU: 1021:7  SCO MTU: 120:6
        UP RUNNING
        RX bytes:740 acl:0 sco:0 events:51 errors:0
        TX bytes:1256 acl:0 sco:0 commands:51 errors:0

hci0:   Type: Primary  Bus: UART
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:4 acl:0 sco:0 commands:1 errors:0

root@verdin-imx8mp-07129924:~#

The labtool response with following:

root@verdin-imx8mp-07129924:~# ./labtool
Name:           Dut labtool
Version:        1.1.0.188
Date:           Apr  5 2011 (23:00:00)

Note:

1. =========WiFi tool=============
2. =========BT   tool=============

Enter CMD 99 to Exit

Enter option: 2
Name:           DutApiClass
Interface:      Version:        1.1.0.188
Date:           Apr  5 2011 (23:00:00)

Note:

Initialize drvwrapper for BT ....
BT interface is not present
 Dut_Bt_OpenDevice: 0xFFFFFFFF
De-Initialize drvwrapper for BT....
root@verdin-imx8mp-07129924:~#

Hi,
i modified now the /etc/modprobe.d/toradex-wifi-config.conf to the following:

# blacklist mlan btxxx
# install mlan /bin/false
# install btxxx /bin/false

blacklist mwifiex mwifiex_sdio btmrvl btmrvl_sdio btbcm btqca
install mwifiex /bin/false
install btmrvl /bin/false
install btqca /bin/false
install btbcm /bin/false

With this setup I am able to test bluetooth and Wifi at the same time.
Is this the correct approach?

BR

Hello @joschi2804,

To the best of my knowledge, if you can start the test for WiFi and Bluetooth with the build that you have, that should suffice for the certification purposes. You will be running your application-specific build on your device in production anyway. Let me pull in @rafael.tx here to confirm.

Hello @rudhi.tx, @joschi2804,
If the labtool commands are working and providing the expected output on the radio side, everything should be good.

From experience supporting customers, I believe the certification tests that need to be executed are relatively simple, with requirements to set the radio to transmit pulses at fixed frequency and power.

Rafael

1 Like