cancel
Showing results for 
Search instead for 
Did you mean: 

Studio Bluetooth

BoCo_1857246
New Contributor II

I'm following the instructions in the CyBluetool User guide for activating the transmit tests. Even though the device under test (DUT) returns "success" to the commands, there is no corresponding spike on the spectrum analyzer when following the instructions in the user guide. Can you please explain how to get this command to work?

The user guide walks through using Set_Tx_CarrierFrequency_ARM at 2402 MHz. In the following trace you can see that this is successful

10/28/19 08:42:27.502 com35 c> Set_Tx_Carrier_Frequency_ARM

HCI Command

com35@115200

[14 FC 07 ]: 00 02 01 00 00 00 00

opcode = 0xFC14 (64532, "Set_Tx_Carrier_Frequency_ARM")

Carrier_Enable = 0x0 (0, "Carrier on")

Carrier_Frequency_Encoded = 0x2 (2)

Carrier_Frequency = 0x962 (2402, MHz)

Mode = 0x1 (1, "PRBS9")

Modulation Type = 0x0 (0, "GFSK")

Transmit_Power = 0x0 (0, "0 dBm")

Transmit_Power_dBm = 0x0 (0, dBm)

Transmit_Power_Table_Index = 0x0 (0)

10/28/19 08:42:27.508 com35 <c Set_Tx_Carrier_Frequency_ARM

HCI Command Complete Event

com35@115200

[0E 04 ]: 01 14 FC 00

event = 0x0E (14,"Command Complete")

Num_HCI_Command_Packets = 0x1 (1)

Command_Opcode = 0xFC14 (64532, "Set_Tx_Carrier_Frequency_ARM")

Status = 0x0 (0, "Success", "Success")

​But the spectrum analyzer shows no spike at 2402MHz

Capture2.PNG

When I send a LE_Transmitter_Test_[v2] at 2402MHz, I do get the expected result

10/28/19 08:40:20.205  com35 <c LE_Transmitter_Test_[v2]

  HCI Command Complete Event

com35@115200

[0E 04 ]: 01 34 20 00

event = 0x0E (14,"Command Complete")

Num_HCI_Command_Packets = 0x1 (1)

Command_Opcode = 0x2034 (8244, "LE_Transmitter_Test_[v2]")

Status = 0x0 (0, "Success", "Success")

10/28/19 08:42:01.804  com35 c> Set_Tx_Carrier_Frequency_ARM

  HCI Command

com35@115200

[14 FC 07 ]: 00 02 01 00 00 00 00

opcode = 0xFC14 (64532, "Set_Tx_Carrier_Frequency_ARM")

Carrier_Enable = 0x0 (0, "Carrier on")

Carrier_Frequency_Encoded = 0x2 (2)

Carrier_Frequency = 0x962 (2402, MHz)

Mode = 0x1 (1, "PRBS9")

Modulation Type = 0x0 (0, "GFSK")

Transmit_Power = 0x0 (0, "0 dBm")

Transmit_Power_dBm = 0x0 (0, dBm)

Transmit_Power_Table_Index = 0x0 (0)

capture1.PNG

You'll see that with the LE_Transmitter_Test_[v2] command we do see a spike at 2402MHz as expected.

Can you please explain how to get the Set_Tx_CarrierFrequency_ARM to work as shown in the user guide?

0 Likes
1 Solution
BoCo_1857246
New Contributor II

I was unable to reproduce the problem today, everything worked well. I think, perhaps, yesterday I had forgotten to load a non-bluetooth project into the module before starting CyBlueTool. Today I built and downloaded the snip.hal.gpio project first, perhaps I didn't yesterday. Sorry to have bothered you.

View solution in original post

0 Likes
3 Replies
Owen_Zhang123
Moderator
Moderator

We didn't see this problem on CYW20719 before. Could you expend the frequency range of the spectrum analyzer to see if the spike is in other place. Then we can tell if it is caused by the frequency offset.

0 Likes
BoCo_1857246
New Contributor II

I was unable to reproduce the problem today, everything worked well. I think, perhaps, yesterday I had forgotten to load a non-bluetooth project into the module before starting CyBlueTool. Today I built and downloaded the snip.hal.gpio project first, perhaps I didn't yesterday. Sorry to have bothered you.

View solution in original post

0 Likes
BoonT_56
Employee

I loaded a CYW920719Q40EVB-01 board with the Hello sensor app with a change of the default HCI UART baud to 115200 in the wiced platform header file of this EVK platform. After reset, I can use MBT and the board has no issue accepting these HCI test commands.