topic AX210 Bluetooth Advertisement in Wireless

AX210 Bluetooth Advertisement

rlorenzoleal — Wed, 13 Mar 2024 13:32:41 GMT

To whom it may concern.

We're in the Bluetooth qualification process for a product using a AX210 as controller with BlueZ as host in an embedded Linux system.

To do so, we need to run certain tests and configure the device in specific modes.

Right now we're trying to configure specific advertisement modes by using hcitool and providing hci command directly to the AX210.

When we try to configure a advertising mode, we get an error with the response "Command Disallowed" (0x0c)

The specific command is

hcitool -i hci0 cmd 0x08 0x0006 00 A0 00 F0 01 00 00 C0 07 E8 D6 97 17 07 00

Here is the response from btmon

@ RAW Open: hcitool (privileged) version 2.22 {0x0003} [hci0] 12820.341956 < HCI Command: LE Set Advertising Parameters (0x08|0x0006) plen 15 #3078 [hci0] 12820.342151 Min advertising interval: 25600.000 msec (0xa000) Max advertising interval: 38400.000 msec (0xf000) Type: Connectable directed - ADV_DIRECT_IND (high duty cycle) (0x01) Own address type: Public (0x00) Direct address type: Public (0x00) Direct address: 17:97:D6:E8:07:C0 (OUI 17-97-D6) Channel map: 37, 38, 39 (0x07) Filter policy: Allow Scan Request from Any, Allow Connect Request from Any (0x00) > HCI Event: Command Complete (0x0e) plen 4 #3079 [hci0] 12820.344053 LE Set Advertising Parameters (0x08|0x0006) ncmd 1 Status: Command Disallowed (0x0c) @ RAW Close: hcitool {0x0003} [hci0] 12820.344177

As you can see, my parameters are OK and conform to the command specification, however it gets rejected.

How can I configure this properly?

Thanks in advance

Re:AX210 Bluetooth Advertisement

RamyerM_Intel — Fri, 15 Mar 2024 09:01:32 GMT

Hello rlorenzoleal,

Thank you for posting in the communities. May I please now what product are you referring to? Would you also prefer if we continue our conversation by private messages as I noticed you did not specify it in your initial post.

Ramyer M.

Intel Customer Support Technician

Re:AX210 Bluetooth Advertisement

RamyerM_Intel — Mon, 25 Mar 2024 06:50:42 GMT

Hello rlorenzoleal,

I am just looking for an update regarding the information we requested. Kindly please let me know about this information so we can identify the next steps that needs to be taken to solve this issue.

Ramyer M.

Intel Customer Support Technician

Re:AX210 Bluetooth Advertisement

RamyerM_Intel — Thu, 28 Mar 2024 03:04:10 GMT

Hello rlorenzoleal,

I hope you are doing well. We will proceed in closing your case for now as we have not heard a response from you in the past few days. If you have further questions, please submit a post as this thread will no longer be monitored.

Ramyer M.

Intel Customer Support Technician

Re: Re:AX210 Bluetooth Advertisement

AlexAlexAlex — Tue, 02 Apr 2024 14:08:23 GMT

Hello,

I am recently working on a bluetooth low energy related project, and have similar issues on both AX201 and AX210, which are built-in adapter for two of our lab workstation. Both workstation use Ubuntu 22.04. We have tested reset adapter, reboot the workstation, but the problem persist.

We have tried few other commands and they works including HCI Command: LE Set Random Address (0x08|0x0005), excepts

LE Set Advertising Data (0x08|0x0008)
LE Set Advertising Parameters (0x08|0x0006)
LE Set Advertise Enable (0x08|0x000a)

You may observe the btmon.log, when I attempted to set BLE Adv. Data, Parameters, and Start Broadcasting, the adapters all replied Command Disallowed. I have a Realtek USB Dongle which can use the same script and accomplish the test on the same systems, as well as a Raspberry Pi 4.

Thanks for the help

----------

After I read the log carefully, I noticed the hciconfig has set the Random Address and Set the Advertising prior my script. I suspect this is caused by the Ubuntu service.

Re: Re:AX210 Bluetooth Advertisement

bm16ton — Thu, 29 Jan 2026 06:53:20 GMT

So the issue is that linux isnt setting the event mask correctly. To get passive scanning working on linux with ax2xx series i do the following.
reset; hci 03 03 0
then set event mask to something like 3dbff807fffbffff (shown here in wrong endian)
hci cmd 03 01 3dbfffffffffffff

This does work on older firmwares that i have tried but its buggy in pretty much every area not just this. My current firmware is Firmware Version: 133-20.25 timestamp 2025.20 tho some of the older firmwares report a higher number? So can get confusing. Ive tried to spread this info, was hopedul arch bluetooth page would pick it up, but alas.