Wi-Fi Bluetooth for Linux Forum Discussions

Hello,

Firstly, this is my setup

#############                                                                     ############

#                     #                    RF cables                                   #                    #

#      DUT1      #===================================#       DUT2    #

#                     #                            ||                                          #                    #

#############                           ||                                         ############

                                                     ||

                                                     ||

                                                     ||

                                     ###################

                                     #                                  #

                                     # Spectrum analyser   #

                                     #                                  #

                                     ###################

I putted  DUT1 in tx mode in channel 7 and txchain 3 ( tx in 2 antennas), and i putted DUT2 in rx mode in channel 7.

when i put the DUT2 in rxchain 1 ( Antenna 1) and check the value of wl pkteng_stats to get the rssi : i get the value of -14 dbm

and when  put the DUT2 in rxchain 2 (Antenna 2), i have a fixed value of rssi : -128dbm

when i put the DUT2 in rxchain 3 (Antenna 1 and 2) i have -14 in rssi value.

I want to know why the antenna 2 is blocked at -128dbm ?

is there any other commands to get the rssi value by antenna ?

i already tested the command : wl phy_rssi_ant and the retuen was :

rssi[0] 0  rssi[1] 0  rssi[2] 0  rssi[3] 0

the command : wl rssi return 0 also.

Best regards.

Hello,

We are trying to integrate a 1DX Murata module (based on BCM43430  chip) on a productbased on an Atmel (now Microchip) ATSAMA5D31 MPU running a 3.10 Linux Kernel.  Is there any drivers revision compliant with such setup ?

Regarding Wifi

When compiling the out of tree backport provided on the following cypress webpage (https://community.cypress.com/servlet/JiveServlet/download/15932-1-39799/cypress-fmac-v4.14.52-2018_0928.zip) , we ended up with four kernel modules, including the low level cfg80211 layer.

Is there any (potentially old) version where cfg80211 did not need to be backported ?

Indeed our goal is to have a single kernel on several different products with different WIFI/BT modules,  we would appreciate to keep the standard cfg80211 driver and just to add a few more kernel modules to support a BCM43430  based radio module.

Regarding Bluetooth

Bluez5 seems to be manadatory to support bcm43xx device when using hciattach. Could you confirm?

Is there any documentation regarding kernel configuration to support the bluetooth feature of BCM43430 chip? We did not find any related information on cypress website

Regards

bmoraine

I have seen numerous posts on this "community" forum that are locked by moderators saying, for example, "The CYW89359 is a device targeted towards the Automotive space, and as such is not supported here on the WICED community, which is designed to support broad market devices only." 

Well, if the moderators lock these discussions, then this is not much of a "community" forum. If threads are locked, then discussion is shut down and other developers are unable to post replies that might actually be helpful and answer the asked questions. Referring technical questions and developers to sales and factory support is rarely all that helpful, let alone immediate, compared to actual "community" support.

Can we at least leave threads unlocked so that replies to these questions are possible? Or should we all just move to stackoverflow to ask our questions?

Thanks in advance,

--Joe

Hi!

The Team here at wolfSSL is excited to see the merger of these two great communities - Cypress and WICED.

We wanted to inform you of a solution for securing your many IoT projects!

wolfSSL uses a dual license model to provide cutting edge security for open source and commercial projects alike. Our embedded SSL/TLS library already supports many chip vendors, because of this it is optimal for securing WICED wireless and Bluetooth devices like the Adafruit WICED WiFi Feather - STM32F205 with Cypress WICED WiFi or Adafruit Feather M0 WiFi - ATSAMD21 + ATWINC150 for example.

For a list of vendors supported by wolfSSL, see: https://wolfssl.com/wolfSSL/Partners.html

For all your security needs, contact: info@wolfssl.com

For help or guidance on a project, contact: support@wolfssl.com

- The wolfSSL Team

Message was edited by: Kaleb Himes

Hi,

We are unable to change the Wi-Fi available channels that appears in the "iw list". We want to be able to connect to channels 12 and 13. Seems that by default, the module uses the USA regulatory channels.

iw list:
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)

We have tried to install crda:

iw reg set JP
iw reg get
global
country JP: DFS-JP
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM
        (4910 - 4990 @ 40), (N/A, 23), (N/A)
        (5030 - 5090 @ 40), (N/A, 23), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
        (5490 - 5710 @ 160), (N/A, 23), (0 ms), DFS
global
country JP: DFS-JP
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM
        (4910 - 4990 @ 40), (N/A, 23), (N/A)
        (5030 - 5090 @ 40), (N/A, 23), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
        (5490 - 5710 @ 160), (N/A, 23), (0 ms), DFS

The CRDA shows that all is configured to accept the channles 12 and 13, but iw list, is showing the same available channels.

We have tried to use wl command:

wl -i wlan0 country JP
wl -i wlan0 channels
1 2 3 4 5 6 7 8 9 10 11 12 13 14

The wl shows that all is configured correctly, but any changes in iw list.

Nothing works.

Our linux only is can see the channels from 1 to 11.

About our linux:

Linux xxxxxx 4.1.15-2.0.1+gb63f3f5 #3 SMP PREEMPT Wed May 31 21:54:57 CEST 2017 armv7l armv7l armv7l GNU/Linux

Can anyone help us? We are really stuck on this. ( 4 days at lest with no result )

Thank you so much in advance to read this post.

Dear Everyone,

I am porting 43438 to samsuang 4412 platform. I have finished the platform driver , and connect the 43438 device to the Host SDIO port.

The driver run as below:

dhd_module_init: Enter

[  717.489594] tomitest. enable
CONFIG_WIFI_CONTROL_FUNC

[  717.495162] ## Calling
platform_driver_register

[  717.511256] ## wifi_probe

[  717.512441] wifi_set_power = 1

[  717.515692] BCM_wifi_power: 1

[  717.518427] [CYW43438] +++
BCM_wifi_power : wlan poweron

[  717.675453] [CYW] ---BCM_wifi_power

[  717.677468] wifi_set_carddetect = 1

[  717.681074] [CYW]
---BCM_wifi_set_carddetect

[  717.685226]
+sdhci_s3c_sdio_card_detect

[  717.689026] -sdhci_s3c_sdio_card_detect

[  717.694531] dhd_bus_register: Enter

[  717.705095]

[  717.705099] Dongle Host Driver,
version 5.90.125.94.1

[  717.705104] Compiled in
drivers/net/wireless/bcmdhd on Dec  5 2017 at 01:55:03

[  717.775049] *******mmc2:
inserted!!!!!******

From the log as above, the host SDIO driver has scaned the device, but it can't find 43438 until timeout.

I catch the SDIO timing sequence  using logic analyzer , it show as below.        

  Time,  

   Value,Description  ,

1. 0.0169056800,      
   0x400000C0039C, CMD0
2. 0.0182246400,      
   0x480000C089FC, CMD8
3. 0.0216734600,      
   0x000000000257, CMD0
4. 0.0261158800,      
   0x20000006AA1F, CMD32
5. 0.0274248400,      
   0x14000000016F, CMD20
6. 0.0276926400,      
   0x14000000016F, CMD20
7. 0.0279604400,      
   0x14000000016F, CMD20
8. 0.0282282200,      
   0x14000000016F, CMD20
9. 0.0296623200,      
   0x70000000065C, CMD48
10. 0.0309737800,      
    0x70000000065C, CMD48
11. 0.0322827200,      
    0x70000000065C, CMD48

...

The host has scaned devices using CMD, but the device(43438) coundn't be founded.

So, who can give me support to fix this issue?