• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 39 subscribers
  • Views 144 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL1835MOD: WL1835MODGBMOCR

qinghua teng
Prodigy 20 points
Part Number: WL1835MOD

hello

      we use WL1835MODGBMOCR wifi chip, but now there is   a registration requirement which Need to set wifi to work at a given  frequency or channel,. Do you have some corresponding tools that meet the requirements？

       we try to using iwconfig ，but failed? Check the relevant information, it may be the reason of the SDIO bus driver？ do you have any advise?  and then , we use iw  dev wlan0 set freq 2412 HT20 command? it also failed , it report an error that  Device or Resource busy (-16);

above ，We all try on the 3.14 kernel version.

Looking forward to your reply！ thanks

  • 0
    TI__Genius 13052 points

    Hi Qinghua,

    First, I want to make sure you followed the WiLink 8 Hardware Integration Guide. This will ensure you have your hardware setup correct. The WiLink 8 Getting Started Guide may also be of use to you to double check your settings. 

    Can you try taking logs using: dmesg | grep wl?

    Thanks,

    Jacob

  • 0
    Prodigy 20 points

    Hi Jacob:

    it work well in our machine.

    dmesg | grep wl logs:

    wlan-en-regulator: 1800 mV
    wl18xx_driver wl18xx.0.auto: Direct firmware load failed with error -2
    wl18xx_driver wl18xx.0.auto: Falling back to user helper
    wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
    wlcore: loaded
    wlcore: driver version:
    wlcore: compilation time: Thu Sep 16 18:02:46 2021
    wlcore: PHY firmware version: Rev 8.2.0.0.212
    wlcore: firmware booted (Rev 8.9.0.0.17)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlcore: down
    wlcore: PHY firmware version: Rev 8.2.0.0.212
    wlcore: firmware booted (Rev 8.9.0.0.17)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

  • 0 in reply to qinghua teng
    TI__Genius 13052 points

    Hi Qinghua,

    Are you in AP mode? Does the build work without setting the frequency? Kernel 3.14 is very old, I would recommend upgrading to our latest version.

    If you are in AP mode, can you try setting the frequency via the channel selection in 5.2.1 in the WiLink8 R8.8 Linux Wi-Fi Driver Release Build User's Guide?

    Thanks,
    Jacob

  • 0 in reply to Jacob B.
    Prodigy 20 points

    Hi Jacob,

    Due to the   product development had been completed, it it is unlikely to upgrade the kernel version.

    We don't use AP mode，but when I try , it failed .there is logs of run " hostapd -B -d -i wlan0 -P /var/run/hostapd-wlan0.pid ./hostapd.conf "

    random: Trying to read entropy from /dev/random
Configuration file: ./hostapd.conf
ctrl_interface_group=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-14-72:1
nl80211: Supports Probe Response offload in AP mode
nl80211: Using driver-based off-channel TX
nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 00 00 00 00 00 00 00 40
nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 00 00 00 00 00 00 00 40
nl80211: Supported vendor command: vendor_id=0x80028 subcmd=0
nl80211: Supported vendor command: vendor_id=0x80028 subcmd=1
nl80211: Supported vendor command: vendor_id=0x80028 subcmd=2
nl80211: Supported vendor event: vendor_id=0x80028 subcmd=0
nl80211: Supported vendor event: vendor_id=0x80028 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x16fff70
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x16fff70 match=
nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ) nl_handle=0x16fff70 match=
nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ) nl_handle=0x16fff70 match=
nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC) nl_handle=0x16fff70 match=
nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH) nl_handle=0x16fff70 match=
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x16fff70 match=
    nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=06
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=0a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fff70 match=7f
nl80211: Could not configure driver mode
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=4)
netlink: Operstate: ifindex=4 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=0 use_monitor=0
nl80211 driver initialization failed.
hostapd_interface_deinit_free(0x16fd318)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x16fd318)
wlan0: interface state UNINITIALIZED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: AP-DISABLED 
hostapd_cleanup(hapd=0x16ff390 (wlan0))
wlan0: CTRL-EVENT-TERMINATING 
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=(nil) drv_priv=(nil) -> hapd_deinit
hostapd_interface_free(0x16fd318)
hostapd_interface_free: free hapd 0x16ff390
hostapd_cleanup_iface(0x16fd318)
hostapd_cleanup_iface_partial(0x16fd318)
hostapd_cleanup_iface: free iface=0x16fd318

    Do you have any other suggestions？ 

    Thinks!

  • 0 in reply to qinghua teng
    TI__Genius 13052 points

    Hi Qinghua,

    Are you able to bring the wlan0 device up with a command like: sudo ip link set wlan0 up or sudo ifconfig wlan0 up? 

    What is the output after running those commands?

    Thanks,

    Jacob