WhyCan Forum(哇酷开发者社区)

刚开始勾的bluez 3.x编译，后来改成bluez 5.x,任然没有bluetoothctl，找了好久没找到原因，干脆make clean之后重新make，终于有bluetoothctl了

绑定之后能连上发数据吗？

折腾了还是没出来，Realtek Three-wire UART (H5) protocol support，先不管了，勾上这个Three-wire UART (H5) protocol support后试试先

果然没有报H5 协议的错误
Realtek Bluetooth :Received reliable seqno 7 from card
Realtek Bluetooth :rtk_hw_cfg.rx_index 100

Realtek Bluetooth :Init Process finished
Realtek Bluetooth post process
Device setup complete

linux5.2配置选项并没有
[ ※]   Realtek Three-wire UART (H5) protocol support

# ./opt/btstack/sbin/rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h4
Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H4
Realtek Bluetooth :Realtek hciattach version 2.5

Realtek Bluetooth :config offset(f4),length(8)
Realtek Bluetooth :config baud rate to :4928002, hwflowcontrol:5f, 1
Realtek Bluetooth :config offset(27),length(1)
Realtek Bluetooth :config offset(fe),length(1)
Realtek Bluetooth :config offset(15b),length(4)
Realtek Bluetooth :config offset(1e3),length(1)
Realtek Bluetooth :Get config baud rate from config file:4928002
Realtek Bluetooth :Load FW OK
Realtek Bluetooth ERROR: Check signature error!
Realtek Bluetooth :baudrate in change speed command: 0x2 0x80 0x92 0x4

Realtek Bluetooth :H4 Change uart Baudrate after write
Initialization timed out.

压缩成zip，拷贝到板子上unzip
执行：
sudo ./rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5

./rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5有反应
Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 2.5

Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8

Realtek Bluetooth :Get SYNC Resp Pkt

Realtek Bluetooth :Get SYNC pkt-active mode

Realtek Bluetooth :3-wire config pattern resend : 1 , len: 10
Realtek Bluetooth :Get CONFG pkt-active mode

Realtek Bluetooth :Get CONFG resp pkt-active mode

Realtek Bluetooth :H5 init finished

Realtek Bluetooth ERROR: can't access bt config file:/lib/firmware/rtl_bt/rtlbt_config, errno:2

Realtek Bluetooth ERROR: Get Config file error, just use efuse settings
Realtek Bluetooth ERROR: Can't access firmware, errno:2
Realtek Bluetooth ERROR: Get BT firmware error
Can't initialize device: No such file or directory

根据自己选择的串口，设备树添加相关的定义

发现代码仓库中代码已失效，找到本站的下载文件rtl8723bs_bt

TF卡走线受到感染或者太长了

@晕哥

试了V3S插着TF卡短接MISO进不了fel模式

网络不一定能用，应该要用USB比较合适

不修改内核的情况下，怎么设置watchdog 的时间呢？

搞定了，引脚定义没放在pinctrl下面

@晕哥

我用的是V3S linux5.2
代码复制过去的，event出不来，原有的matrix key是evet0，lradc是event1，触摸屏是event2，串口2也注释掉了，开机没有打印PB2中断对应的inputx

@Quotation

请问怎么读LRADC寄存器电压值？

没有这个文件，也没有/sys/class/gpio/gpio64这个目录

估计是读写权限的问题，没有root权限

一开始用PE22作为中断脚申请不到，后面改成PB3就可以了

input: generic ft5x06 (82) as /devices/platform/soc/1c2ac00.i2c/i2c-0/0-0038/input/input1

怎么设置分辨率的？lv_conf.h没看到有
#define LV_HOR_RES_MAX          (480)  //屏幕水平宽度 根据实际使用修改
#define LV_VER_RES_MAX          (320)  //屏幕垂直高度 根据实际使用修改

检查TF卡槽触点及焊接有没有问题

同一张就卡插到zero开发板，播放音乐正常，而做的板子只有滋滋的声音

v3s做板遇到同样问题，用zero开发板可正常开机，是不是TF卡里V3S太远了，文件系统挂载不了？

10.1寸   RGB  50pin屏幕很常见，不过要对照数据手册，不同厂家  VGH VGL VCOM 背光等电源都会有些不同，一不小心就会把屏幕烧了

我调的是
YT101ISM-45B
HZ-TFT101BT001

dev看下是不是有两个fb，会不会是还有一个RGB接口的屏幕没删掉

LCD_CLK用示波器测得25MHz，明明设置的是51.2MHz,uboot打印也是

Setting up a 1024x600 lcd console (overscan 0x0)
dotclock: 51200kHz = 51000kHz: (1 * 3MHz * 102) / 6
In:    serial@01c28000
Out:   serial@01c28000
Err:   serial@01c28000

simple-framebuffer 43da8000.framebuffer: framebuffer at 0x43da8000, 0x258000 bytes, mapped to 0x(ptrval)
[    1.113758] simple-framebuffer 43da8000.framebuffer: format=x8r8g8b8, mode=1024x600x32, linelength=4096
[    1.133780] Console: switching to colour frame buffer device 128x37
[    1.149740] simple-framebuffer 43da8000.framebuffer: fb0: simplefb registered!

UBOOT 修改分辨率为1024x600
需要修改 u-boot/include/configs/sunxi-common.h 文件

296 #define CONFIG_SUNXI_MAX_FB_SIZE (2 << 20)

改为

296 #define CONFIG_SUNXI_MAX_FB_SIZE (3 << 20)

CONFIG_VIDEO_LCD_MODE="x:1024,y:600,depth:24,pclk_khz:51200,le:198,ri:120,up:21,lo:821,hs:2,vs:2,sync:3,vmode:0"

接上屏幕依然没有显示，换回5寸 800*480还是能显示
执行fb-test

# ./usr/bin/fb-test
fb-test 1.1.0 (rosetta)
fb res 1024x600 virtual 1024x600, line_len 4096, bpp 32

是的，在找背光驱动方案

目前状态是背光微弱，屏幕没有显示内容

40PIN转50PIN只是硬件转换吗？

dev目录有没有fb，可以用工具fb-test测试

用V3S自带的display engine

V3S的板子还有吗？

开机log有没有输出注册fb信息？dev目录下看看有没有fb设备

linux5.2 文件树&de打开了，录制视频屏幕还是没反应

我想要的效果是拍照时候先用屏幕对好位置，然后再点击按下快门，拍照成图片，把摄像头图像通过v4l采集显示到fb上

能否指点一下，谢谢

解决 https://blog.csdn.net/qulang000/article/details/114686525

@shuiyihang
是怎么解决的？我也遇到初始化后雪花屏，执行cat之后是白屏

USB口供电问题，使用直流电源可以了，就是拍照一团黑，只看到大概轮廓

# ls /dev
bus                 ptyva               ttydc
console             ptyvb               ttydd
cpu_dma_latency     ptyvc               ttyde
fb0                 ptyvd               ttydf
full                ptyve               ttye0
gpiochip0           ptyvf               ttye1
i2c-0               ptyw0               ttye2
i2c-1

设备树配的是i2c-1，dev下面有i2c-1

没，我再试试，谢谢

已经添加了C++ support，但是还是没有

https://www.cnblogs.com/listenscience/p/13619930.html

这个试过OK

ESP_12F的INT中断脚是IO5吗？

@542396750@qq.com

@@ -9,7 +9,8 @@ KVERS_ARCH ?= $(shell arch)
# KBUILD is the path to the Linux kernel build tree.  It is usually the
# same as the kernel source tree, except when the kernel was compiled in
# a separate directory.
-KBUILD ?= $(shell readlink -f /lib/modules/$(KVERS_UNAME)/build)
+# KBUILD ?= /work/f1c100s/f1c100s-linux #$(shell readlink -f /lib/modules/$(KVERS_UNAME)/build)
+KBUILD ?= /work/f1c100s/f1c100s-linux

freeTDS也可以正确访问数据源，证明 freetds和unixodbc都是通的，现在只是qt调用不对，重新按新的路径拷贝plugins/sqlservers中的库文件进入试试

# ./isql -v QTDSN sa 123456
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select * from goods
+-----------------+---------------------+----------------------+------+---------------------------------------------------+---------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+-----------------+------------+-----------+----------------------+----------------------+
| GID             | GName               | GPrice               | GUnit| GProvider1                                        | GProvider2                                        | GDescribe                                                                                                                                                                                                                                                                                                   | STKQuantity             | lotno           | productDate| expireDate| outprice             | outprice2            |
+-----------------+---------------------+----------------------+------+---------------------------------------------------+---------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+-----------------+------------+-----------+----------------------+----------------------+
| 123444          | 我得我              | 3.00                 | t    | 收到

按照http://blog.sina.com.cn/s/blog_8d004f070102vgcr.html
重新折腾了好几天，测试freedtds中tsql可以连接到MS数据库，但交叉编译unixodbc后，在移植freetds时，.configure加上--with-unixodbc=/usr/local/unixodbc

报错
./configure: line 16574: /usr/local/arm/unixODBC/bin/odbc_config: cannot execute binary file: Exec format error
./configure: line 16575: /usr/local/arm/unixODBC/bin/odbc_config: cannot execute binary file: Exec format error
configure: error: /sql.h not found

意思是unixODBC中的bin文件是32位的，在Ubuntu下执行不了，不知其他人是怎么通过的，是不是Ubuntu安装支持32位的库就可以解决？

是这个吗？

是没有装odbc插件，感谢

目前可以显示画面，就是色彩不对，STM32单片机显示又是正常的

注释tcon0，fb0就没了

按照 https://www.cnblogs.com/listenscience/p/13619930.html 方法，出现了两个fb，分别是fb0和fb1，fb1才是st7789，文件树注释掉了panel那一段，重新烧录还是有fb0，不知道怎么删掉fb0，只留一个ST7789

数据位8位 波特率115200，无校验，停止位一位

SigmaStar SSD212

wifi模块是ESP8266吗？

修改lv_font目录下lv_font。mk，后面加+=myFont.c编译通过

应该不是改Makefile，
不好意思，我没问对问题。应该是lv_conf.h应该怎么修改才能使用自定义的字库？

只把myFont.c加入lv_font目录和声明LV_FONT_DECLARE(myFont);不够吧？

Makefile是这样的：

#
# Makefile
#
#CC ?= gcc
CC = /home/obm/123/buildroot-2017.08/output/host/bin/arm-linux-gcc

LVGL_DIR_NAME ?= lvgl
LVGL_DIR ?= ${shell pwd}
CFLAGS ?= -O3 -g0 -I$(LVGL_DIR)/ -Wall -Wshadow -Wundef -Wmaybe-uninitialized -Wmissing-prototypes -Wno-discarded-qualifiers -Wall -Wextra -Wno-unused-function -Wundef -Wno-error=strict-prototypes -Wpointer-arith -fno-strict-aliasing -Wno-error=cpp -Wuninitialized -Wmaybe-uninitialized -Wno-unused-parameter -Wno-missing-field-initializers -Wtype-limits -Wsizeof-pointer-memaccess -Wno-format-nonliteral -Wno-cast-qual -Wunreachable-code -Wno-switch-default -Wno-switch-enum -Wreturn-type -Wmultichar -Wformat-security -Wno-ignored-qualifiers -Wno-error=pedantic -Wno-sign-compare -Wno-error=missing-prototypes -Wdouble-promotion -Wclobbered -Wdeprecated -Wempty-body -Wtype-limits  -Wstack-usage=1024 -Wno-unused-value -Wno-unused-parameter -Wno-missing-field-initializers -Wuninitialized -Wmaybe-uninitialized -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wtype-limits -Wsizeof-pointer-memaccess -Wno-format-nonliteral -Wpointer-arith -Wno-cast-qual -Wmissing-prototypes -Wunreachable-code -Wno-switch-default -Wswitch-enum -Wreturn-type -Wmultichar -Wno-discarded-qualifiers -Wformat-security -Wno-ignored-qualifiers -Wno-sign-compare
LDFLAGS ?= -lm
LDFLAGS +=-lts
BIN = demo

#Collect the files to compile
MAINSRC = ./main.c

include $(LVGL_DIR)/lvgl/lvgl.mk
include $(LVGL_DIR)/lv_drivers/lv_drivers.mk
include $(LVGL_DIR)/lv_examples/lv_examples.mk
#include $(LVGL_DIR)/lv_examples/lv_tests/lv_test_theme/lv_test_theme.mk

OBJEXT ?= .o

AOBJS = $(ASRCS:.S=$(OBJEXT))
COBJS = $(CSRCS:.c=$(OBJEXT))

MAINOBJ = $(MAINSRC:.c=$(OBJEXT))

SRCS = $(ASRCS) $(CSRCS) $(MAINSRC)
OBJS = $(AOBJS) $(COBJS)

## MAINOBJ -> OBJFILES

all: default

%.o: %.c
    @$(CC)  $(CFLAGS) -c $< -o $@
    @echo "$(CC) $<"
   
default: $(AOBJS) $(COBJS) $(MAINOBJ)
    $(CC) -o $(BIN) $(MAINOBJ) $(AOBJS) $(COBJS) $(LDFLAGS)

clean:
    rm -f $(BIN) $(AOBJS) $(COBJS) $(MAINOBJ)

typedef struct _lv_indev_drv_t {

    /**< Input device type*/
    lv_indev_type_t type;

    /**< Function pointer to read input device data.
     * Return 'true' if there is more data to be read (buffered).
     * Most drivers can safely return 'false' */
    bool (*read_cb)(struct _lv_indev_drv_t * indev_drv, lv_indev_data_t * data);

    /** Called when an action happened on the input device.
     * The second parameter is the event from `lv_event_t`*/
    void (*feedback_cb)(struct _lv_indev_drv_t *, uint8_t);

#if LV_USE_USER_DATA
    lv_indev_drv_user_data_t user_data;
#endif

    /**< Pointer to the assigned display*/
    struct _disp_t * disp;

    /**< Task to read the periodically read the input device*/
    lv_task_t * read_task;

    /**< Number of pixels to slide before actually drag the object*/
    uint8_t drag_limit;

    /**< Drag throw slow-down in [%]. Greater value means faster slow-down */
    uint8_t drag_throw;

    /**< At least this difference should between two points to evaluate as gesture */
    uint8_t gesture_min_velocity;

    /**< At least this difference should be to send a gesture */
    uint8_t gesture_limit;

    /**< Long press time in milliseconds*/
    uint16_t long_press_time;

    /**< Repeated trigger period in long press [ms] */
    uint16_t long_press_rep_time;
} lv_indev_drv_t;

MD，可以了，由于版本差异，evdev_read的形参没对应上
bool evdev_read(lv_indev_data_t * data);改为
bool evdev_read(lv_indev_drv_t * indev_drv,lv_indev_data_t * data);

您好，有注册的。

触摸屏幕有打印出坐标

tsc2007@48 {
        compatible = "ti,tsc2007";
        reg = <0x48>;
        interrupt-parent = <&gpio1>;
        interrupts = <0x2 0x8>; 0x2 为什么要这样填？
        gpios = <&gpio1 2 0>;
        ti,x-plate-ohms = <660>;
    };

如果使用PE0作为中断引脚，中断号应该怎么填？

仿写 panel_simple.c中800*480的代码。好了

参考 https://whycan.com/t_1522.html

光标闪没问题，我想问下有全屏刷成红或者蓝，有测试指令吗？

还是要移植lvgl才能画矩形、圆形那些图案？

貌似是TF卡座太松了接触不良，wifi模块比TF卡薄，我压一下卡座弹片，重新插进去，就没出现了

可以了，按照下面流程：
insmod r8723bs.ko
ifconfig -a
ifconfig wlan0 up
wpa_supplicant -B -d -i wlan0 -c /etc/wpa_supplicant.conf（按照上面步骤走，手机提示有设备连入）
udhcpc -i wlan0（执行这一步才能接人网络）
udhcpc: sending discover
重新添加dhcp，再编译，还是一样
查看网络状态wpa_cli -iwlan0 status
测试网络ping 123.149.232.30
按CTRL+C停止Ping

# insmod r8723bs.ko
[   58.380884] r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
[   58.416880] RTL8723BS: module init start
[   58.420842] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[   58.428059] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[   58.436988] pnetdev = 33023edb
[   58.485664] RTL8723BS: rtw_ndev_init(wlan0)
[   58.492380] RTL8723BS: module init ret =0
# ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb0      Link encap:Ethernet  HWaddr 96:1B:35:97:E5:08
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 84:20:96:AB:35:09
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

# ifconfig wlan0 up
[   78.453132] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
# wpa_supplicant -B -d -i wlan0 -c /etc/wpa_supplicant.conf
wpa_supplicant v2.6
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=1
Priority group 5
   id=0 ssid='cxk'
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-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x196618
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0104
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=040a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=040b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=040c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=040d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=090a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=090b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=090c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=090d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0409506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=7f506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0a1a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0505
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x196618 match=0500
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
Add interface wlan0 to a new radio phy0
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 20 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR)
nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS) (no IR)
nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR)
nl80211: 57240-63720 @ 2160 MHz 0 mBm
nl80211: Added 802.11b mode based on 802.11g information
wlan0: Own MAC address: 84:20:96:ab:35:09
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlan0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan0: Setting scan request: 0.100000 sec
wlan0: WPS: UUID based on MAC address: a422be9d-114f-543e-a249-6422664005d5
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Daemonize..
# [  101.384703] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[  101.558770] RTL8723BS: start auth
[  101.569959] RTL8723BS: auth success, start assoc
[  101.586298] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
[  101.593498] RTL8723BS: assoc success
[  101.748536] RTL8723BS: send eapol packet
[  101.821986] RTL8723BS: send eapol packet
[  101.845836] RTL8723BS: set pairwise key camid:4, addr:b6:64:aa:d9:23:09, kid:0, type:AES
[  101.876654] RTL8723BS: set group key camid:5, addr:b6:64:aa:d9:23:09, kid:1, type:AES
wpa_cli -iwlan0 status
bssid=b6:64:aa:d9:23:09
freq=2447
ssid=cxk
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
address=84:20:96:ab:35:09
uuid=a422be9d-114f-543e-a249-6422664005d5
# ping baidu.com
ping: bad address 'baidu.com'
# ping www.baidu.com
ping: bad address 'www.baidu.com'
# ping 123.149.232.30
PING 123.149.232.30 (123.149.232.30): 56 data bytes
ping: sendto: Network is unreachable
# udhcpc -i wlan0
udhcpc: started, v1.27.1
udhcpc: sending discover
udhcpc: sending select for 192.168.43.35
udhcpc: lease of 192.168.43.35 obtained, lease time 3599
deleting routers
adding dns 192.168.43.1
# ping 123.149.232.30
PING 123.149.232.30 (123.149.232.30): 56 data bytes
64 bytes from 123.149.232.30: seq=0 ttl=112 time=121.242 ms
64 bytes from 123.149.232.30: seq=1 ttl=112 time=77.505 ms
64 bytes from 123.149.232.30: seq=2 ttl=112 time=85.317 ms
64 bytes from 123.149.232.30: seq=3 ttl=112 time=80.254 ms
64 bytes from 123.149.232.30: seq=4 ttl=112 time=103.382 ms

您好，这个固件已经放在这个目录下了

# cd /
# ls
bin         lib         media       proc        run         tmp
dev         lib32       mnt         r8723bs.ko  sbin        usr
etc         linuxrc     opt         root        sys         var
# cd lib/firmware/rtlwifi/
# ls
rtl8723bs_nic.bin
#

你好，dts是这样的，没看出引脚占用

// SPDX-License-Identifier: (GPL-2.0+ OR X11)
/*
* Copyright 2018 Icenowy Zheng <icenowy@aosc.io>
*/

/dts-v1/;
#include "suniv-f1c100s.dtsi"

#include <dt-bindings/gpio/gpio.h>

/ {
    model = "Lichee Pi Nano";
    compatible = "licheepi,licheepi-nano", "allwinner,suniv-f1c100s",
             "allwinner,suniv";

    aliases {
        serial0 = &uart0;
        spi0 = &spi0;
    };

    chosen {
        stdout-path = "serial0:115200n8";
    };

    panel: panel {
        compatible = "qiaodian,qd43003c0-40", "simple-panel";
        #address-cells = <1>;
        #size-cells = <0>;
        enable-gpios = <&pio 4 6 GPIO_ACTIVE_HIGH>;

        port@0 {
            reg = <0>;
            #address-cells = <1>;
            #size-cells = <0>;

            panel_input: endpoint@0 {
                reg = <0>;
                remote-endpoint = <&tcon0_out_lcd>;
            };
        };
    };

    reg_vcc3v3: vcc3v3 {
        compatible = "regulator-fixed";
        regulator-name = "vcc3v3";
        regulator-min-microvolt = <3300000>;
        regulator-max-microvolt = <3300000>;
    };
};

&de {
    status = "okay";
};

&mmc0 {
    vmmc-supply = <&reg_vcc3v3>;
    bus-width = <4>;
    broken-cd;
    status = "okay";
};

&otg_sram {
    status = "okay";
};

&spi0 {
    partnctrl-names = "default";
    pinctrl-0 = <&spi0_pins_a>;
    status = "okay";
    spi-max-frequency = <50000000>;
    flash: w25q128@0 {
        #address-cells = <1>;
        #size-cells = <1>;
        compatible = "winbond,w25q128", "jedec,spi-nor";
        reg = <0>;   
        spi-max-frequency = <50000000>;
        partitions {
            compatible = "fixed-partitions";
            #address-cells = <1>;
            #size-cells = <1>;

            partition@0 {
                label = "u-boot";
                reg = <0x000000 0x100000>;
                read-only;
            };

            partition@100000 {
                label = "dtb";
                reg = <0x100000 0x10000>;
                read-only;
            };

            partition@110000 {
                label = "kernel";
                reg = <0x110000 0x400000>;
                read-only;
            };

            partition@510000 {
                label = "rootfs";
                reg = <0x510000 0xAF0000>;
            };
        };
    };
};

&tcon0 {
    pinctrl-names = "default";
    pinctrl-0 = <&lcd_rgb666_pins>;
    status = "okay";
};

&tcon0_out {
    tcon0_out_lcd: endpoint@0 {
        reg = <0>;
        remote-endpoint = <&panel_input>;
    };
};

&uart0 {
    pinctrl-names = "default";
    pinctrl-0 = <&uart0_pins_a>;
    status = "okay";
};

&usb_otg {
    dr_mode = "otg";
    status = "okay";
};

&usbphy {
    usb0_id_det-gpio = <&pio 4 2 GPIO_ACTIVE_HIGH>; /* PE2 */
    status = "okay";
};