Wireless Connectivity Forum Discussions

Hi,

I have a CYBT-333047-EVAL board and I am trying to communicate in RAW mode over the HCI UART. I am starting with the TX first.

I see debug traces over HCI if I route the debug through HCI (I tested it using `wiced_set_debug_uart`)

But when I try to get the HCI transport to work with UART_RAW_MODE, I get nothing. Below is the `wiced_transport_cfg_t` structure

const wiced_transport_cfg_t transport_cfg =
{
    .type = WICED_TRANSPORT_UART,
    .cfg =
    {
        .uart_cfg =
        {
            .mode = WICED_TRANSPORT_UART_RAW_MODE,
            .baud_rate =  HCI_UART_DEFAULT_BAUD // 115200
        },
    },
    .rx_buff_pool_cfg =
    {
        .buffer_size  = 0,
        .buffer_count = 0
    },

    .p_status_handler    = NULL,
    .p_data_handler      = NULL,
    .p_tx_complete_cback = NULL
};

Here is what I did :

1. Created a new project using the SPP example
2. Modified the transport_cfg structure to the one above
3. In APPLICATION_START, I call `wiced_transport_init`
4. From the BTM_ENABLED_EVT case, I call `wiced_transport_send_data`

I saw this post which seems pretty straightforward, but I still get nothing:

https://community.infineon.com/t5/Studio-Bluetooth/This-is-a-question-about-raw-mode-sample-code/td-p/225118

What am I missing?

Regards,

M

IEEE 802.11 standard documents are often thousands of pages, do you want to read them word for word? How can I read and master effectively?

Question link: https://www.zhihu.com/question/603817982

Can you talk about learning methods and recommend Infineon products

hello,
i want use Ble and BD/EDR together to advertisement and pairing so is there any example for reference I already take reference from this but it has some hidd functions that don't support in cyw20706.

your help will be appreciated.

Hi IFX team

we are using jetson nano and CYW54591 Wi-Fi BT chipset with module name LBEE5XV1XA-540 we need to do regulatory certification test commands for Bluetooth
Our requirements
1 .  is there any specific tool like WL  to do RF for Bluetooth in jetson platform?
2. if yes please share the procedure and required tools/binaries to do validation
Please comment on the above queries as this critical for us

@Vivek_gunapati @Ramya_R 

hi sir: I've always installed modustoolbox3.1 before, and when I'm on the D drive, I can successfully compile bulid normally. After uninstalling and installing according to the default path, I am now able to create a new project normally, but the following error was reported during the build

C: /users/dsq/modustoolbox/tools_3.1/make/core_version3/startex-v3.mk:159: *** Libraries: recipe-make " "Not found Run " make getlibs " to ensure all required build and code dependencies are present.. STOP.
"C: /users/dsq/modustoolbox/tools_3.1/modus-shell/bin/make cy_make_ide=eclipse CY_IDE_TOOLS_DIR=C: /users/dsq/modustoolbox/tools_3.1 CY_IDE_BT_TOOLS_DIR= --output-sync -j16 all terminated with exit code 2 " . Build might be strange.

Looks like the mtb_shared path hasn't been found, please help take a look

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/AIROC-Wi-Fi%E4%B8%8EWi-Fi-%E8%93%9D%E7%89%99%E7%BB%84%E5%90%88/ModusToolbox3-1%E6%96%B0%E5%BB%BAapplication%E5%90%8E%E6%97%A0%E6%B3%95bulid-%E6%88%90%E5%8A%9F/td-p/650160

Hi,

I'm currently using the Murata LBEE5KL1YN-814 EVK which consists of CYW43439 module.

I've managed to load the driver package v5.15.58-2023_0901 backported for kernel v5.15.0-051500-generic on my Ubuntu 22 Virtual Machine.

However, when i connect the module to my PC, I received these READ errors:-

"[ 260.392927] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd

[ 260.420255] usb 2-1: New USB device found, idVendor=2537, idProduct=1081, bcdDevice= 1.00

[ 260.420259] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 260.420260] usb 2-1: Product: NS1081

[ 260.420261] usb 2-1: Manufacturer: Norelsys

[ 260.420262] usb 2-1: SerialNumber: 0123456789ABCDE

[ 260.525663] usb-storage 2-1:1.0: USB Mass Storage device detected

[ 260.526797] scsi host3: usb-storage 2-1:1.0

[ 260.529196] usbcore: registered new interface driver usb-storage

[ 260.533836] usbcore: registered new interface driver uas

[ 261.553299] scsi 3:0:0:0: Direct-Access NORELSYS 1081CS0 PQ: 0 ANSI: 6

[ 262.214995] scsi 3:0:0:1: Direct-Access NORELSYS 1081CS1 PQ: 0 ANSI: 6

[ 262.216271] scsi 3:0:0:0: Attached scsi generic sg2 type 0

[ 262.216390] scsi 3:0:0:1: Attached scsi generic sg3 type 0

[ 262.224998] sd 3:0:0:0: [sdb] Media removed, stopped polling

[ 262.230592] sd 3:0:0:1: [sdc] Very big device. Trying to use READ CAPACITY(16).

[ 262.234706] sd 3:0:0:1: [sdc] Using 0xffffffff as device size

[ 262.234710] sd 3:0:0:1: [sdc] 4294967296 512-byte logical blocks: (2.20 TB/2.00 TiB)

[ 262.239138] sd 3:0:0:1: [sdc] Write Protect is off

[ 262.239140] sd 3:0:0:1: [sdc] Mode Sense: 23 00 00 00

[ 262.241159] sd 3:0:0:1: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

[ 262.269359] sd 3:0:0:0: [sdb] Attached SCSI removable disk

[ 262.283411] sd 3:0:0:1: [sdc] Very big device. Trying to use READ CAPACITY(16).

[ 262.288336] sd 3:0:0:1: [sdc] Using 0xffffffff as device size

[ 269.279218] usb 2-1: USB disconnect, device number 2

[ 269.303388] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=7s

[ 269.303392] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303393] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303399] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303424] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303425] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303425] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303427] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303432] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303433] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303433] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303434] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303436] ldm_validate_partition_table(): Disk read failed.

[ 269.303440] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303441] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303441] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303442] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303447] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303448] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303448] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303449] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303453] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303454] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303454] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303456] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303459] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303460] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303461] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303462] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303463] Dev sdc: unable to read RDB block 0

[ 269.303467] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303467] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303468] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303469] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303473] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303474] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00

[ 269.303474] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303475] Buffer I/O error on dev sdc, logical block 0, async page read

[ 269.303485] sd 3:0:0:1: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s

[ 269.303486] sd 3:0:0:1: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 18 00 00 00 08 00 00

[ 269.303486] blk_update_request: I/O error, dev sdc, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

[ 269.303487] Buffer I/O error on dev sdc, logical block 3, async page read

[ 269.303495] sdc: unable to read partition table

[ 269.318871] sdc: detected capacity change from 4294967296 to 0

[ 269.318877] sd 3:0:0:1: [sdc] Attached SCSI removable disk"

Please help to assist.

Thank you.

I'm preparing to have FCC qualification performed on a BLE 4.2 device I created based on A PSoC4. The company that is performing the testing has given me the following requirements (among others). I have no clue how to implement any of these test modes. As far as I can tell, the PSoC4 API doesn't give me the controls I would need to do this (or maybe I just don't know where to look). Can anyone point me in the right direction?

 For BLE Test Mode  

1. Ability to select the operating frequency channels at least the low / mid /high
2. Ability to set all these radios to be ON and continuously transmitting
3. Ability to control the highest duty cycle greater than 100% or at least greater than 98% for FCC/ISED
4. Ability to control ALL supported modes, Modulation, Data Rate, Bandwidth
5. Ability to control the output power maximum power will be implemented in final product.
6. Please check the transmitting signal using a spectrum analyzer to ensure all the above requirements are met.