(盈鹏飞嵌入式T113-S4主板)-BT蓝牙播放(RTL8723DU)音乐功能测试

全志T113核心板一张表介绍其参数|性能|功耗|-盈鹏飞嵌入式 如果您的应用场景是工业级,或者有严苛的温控要求,那么T113-i会是比较好的选择,因为它的工作温度范围更广,能更好地满足这些需求。随着市场应用的逐渐细化,细分市场的处理器逐渐浮出水面,盈鹏飞嵌入式顺应市场大势,推出了以全志主控T113-i/S3/S4和A40I(T3)的相关核心模块产品和主板,那么这些处理器到底有什么优势?特别要说明的是,T113-S3/S4的内存容量是固定的(不支持扩展),这可能会限制其在某些应用中的使用。全志T113系列中的T113-i和T113-S3两款芯片,在知名度上不相上下。 阅读详情

SBC-T113S产品特性:

  • 采用Allwinner公司Cortex-A7双核T113-S3/S4处理器,运行最高速度为1.2GHZ;
  • 内置64-bit XuanTie C906 RISC-V协处理器(仅T113-S4支持);
  • 支持JPEG/MJPEG视频编码,最大分辨率1080p@60fps;支持多格式1080P@60fps视频解码 (H.265,H.264, MPEG-1/2/4);
  • 支持RGB666/LVDS/MIPI-DSI,分辨率最高1920x1080;
  • 支持128-256M Bytes DDR3 SDRAM,其中T113-S3内置128MB;T113-S4内置256MB;
  • 支持SPI NAND存储和启动(默认:256MB)或者EMMC启动(默认:4GB,最大32GB);
  • 支持一路USB2.0 OTG(设计为TYPE-A接口);支持二路USB2.0 HOST;
  • 支持七路RS232通信或者6路RS232和1路RS485(非隔离);
  • 支持一路CAN BUS通信(非隔离);
  • 支持一路10/100M以太网;
  • 稳定的操作系统的支持,可预装LINUX 5.4(Preempt)或者OpenWRT;
  • 经典尺寸主板,尺寸为120*100MM;

SBC-T113S产品功能评估图:

使用主板蓝牙播放音乐 

对蓝牙设备进行配对连接后,还要判断是否正常连接。通常使用l2ping指令来判断,指令执行如下:

root@T113-Embfly:~# l2ping -f -s 512 -c 10 -t 1 F4:4E:FD:3B:95:A6

Ping: F4:4E:FD:3B:95:A6 from 40:80:E1:F1:BE:0C (data size 512) ...

[ 3279.159111] rtk_btcoex: update_hid_active_state: handle 0x0003, interval 0

[ 3279.166985] rtk_btcoex: HID not connected, nothing to be down

512 bytes from F4:4E:FD:3B:95:A6[ 3279.173466] rtk_btcoex: update_hid_active_state: handle 0x0003, interval 0

 id 0 time 528.15ms

[ 3279.184013] rtk_btcoex: HID not connected, nothing to be down

512 bytes from F4:4E:FD:3B:95:A6 id 1 time 49.30ms

512 bytes from F4:4E:FD:3B:95:A6 id 2 time 32.41ms

512 bytes from F4:4E:FD:3B:95:A6 id 3 time 32.44ms

512 bytes from F4:4E:FD:3B:95:A6 id 4 time 32.44ms

512 bytes from F4:4E:FD:3B:95:A6 id 5 time 32.45ms

512 bytes from F4:4E:FD:3B:95:A6 id 6 time 32.46ms

512 bytes from F4:4E:FD:3B:95:A6 id 7 time 32.45ms

512 bytes from F4:4E:FD:3B:95:A6 id 8 time 32.46ms

512 bytes from F4:4E:FD:3B:95:A6 id 9 time 32.46ms

10 sent, 10 received, 0% loss

root@T113-Embfly:~#

l2ping的指令这里不做详细介绍,需要了解的可以baidu.com。

为了方便演示音乐的播放,在/embfly_test目录下提供了一个播放音乐脚本bt_play_source.sh,脚本内容如下:

#!/bin/sh

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

# file bt_play_source.sh

# version 0.0.1

# date 2018-05-06

#

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

#insmod /lib/modules/4.9.170/xradio_btlpm.ko

bt_clear()

{

    killall -9 hciattach

    killall -9 bluetoothd

    killall -9 bluetoothctl

    hciconfig hci0 down

#   echo 0 > /sys/class/rfkill/rfkill0/state

}

echo $#

if [ $# -lt 1 ]; then

    echo "less arams"

    echo "example: bt_init.sh Mi10S"

    exit

fi

BT_NAME=$1

# reset bt

#echo "reset bt"

#echo 0 > /sys/class/rfkill/rfkill0/state

#sleep 1

#echo 1 > /sys/class/rfkill/rfkill0/state

#sleep 1

# bt bind uart

#echo "bt bind uart"

#hciattach -n ttyS1 xradio > /dev/null 2>&1 &

#sleep 8

# bt power on

echo "bt power on"

hciconfig hci0 up   

hciconfig hci0 piscan

# bt scan

echo "bt scan"

i=0

while [ $i -le 5 ]

do

    echo "scan $i times"

    str=`hcitool scan | grep $BT_NAME`

    echo $str

    if [ "x$str" != "x" ]; then

       echo "find $BT_NAME"

       break;

    fi

    let i++

done  

if [ $i -ge 5 ]; then

    echo "no find $BT_NAME"

    bt_clear

    exit

fi

array=(${str// / })

i=0

BT_MAC=""

for var in ${array[@]}

do

    echo $i $var

    if [ $i -eq 0 ]; then

           BT_MAC=$var

    fi

    let i++

done

echo "BT_MAC: $BT_MAC"

# bluetoothd service

bluetoothd -n &

bluealsa -p a2dp-source &

#str=`bluetoothctl scan on | grep Mi10S`

echo "scan on"

bluetoothctl scan on &

sleep 8

bluetoothctl scan off

killall -9 bluetoothctl

if [ ! -e /tmp/.bt ]; then

    bluetoothctl trust $BT_MAC

    bluetoothctl pair $BT_MAC

    touch /tmp/.bt

fi

bluetoothctl connect $BT_MAC

sleep 5

aplay -D bluealsa:DEV=$BT_MAC /embfly_test/wfxy.wav

#aplay -D bluealsa:HCI=hci0,DEV=$BT_MAC,PROFILE=A2DP /embfly_test/wfxy.wav

测试BT音频的音箱是EDIFIER M350,它支持BT4.2,而SBC-T113S主板配置的WIFI模块(RTL8723DU)也是支持BT4.2,两者可以正常通信,播放音乐的指令如下:

root@T113-Embfly:/embfly_test# ./bt_play_source.sh EDIFIER M350

2

bt power on

[12258.705313] rtk_btusb: btusb_open start

[12258.709667] rtk_btusb: btusb_open hdev->promisc ==0

[12258.715185] rtk_btusb: download_patch start

[12258.719956] rtk_btusb: chip type value: 0x71

[12258.725961] rtk_btusb: chip_type->status = 0x0, chip_type->chip = 0xbeef

[12258.733620] rtk_btusb: HCI reset.

[12258.747951] rtk_btusb: read_ver_rsp->lmp_subver = 0x6f71

[12258.754011] rtk_btusb: read_ver_rsp->hci_rev = 0x92b7

[12258.759741] rtk_btusb: patch_entry->lmp_sub = 0x8723

[12258.765333] rtk_btusb: Firmware already exists

[12258.770355] rtk_btusb: Rtk patch end 1

[12258.774559] rtk_btusb: chip type value: 0x71

[12258.779381] rtk_btusb: btusb_open set HCI UP RUNNING

[12258.785081] rtk_btcoex: Open BTCOEX

[12258.789042] rtk_btusb: btusb_open end

[12258.803978] rtk_btcoex: BTCOEX hci_rev 0x92b7

[12258.808971] rtk_btcoex: BTCOEX lmp_subver 0x6f71

[12258.814251] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc1b

[12258.870038] debugfs: File 'le_min_key_size' in directory 'hci0' already present!

[12258.878383] debugfs: File 'le_max_key_size' in directory 'hci0' already present!

[12258.886735] debugfs: File 'force_bredr_smp' in directory 'hci0' already present!

bt scan

scan 0 times

[12258.922073] rtk_btcoex: hci (periodic)inq start

[12275.580027] rtk_btcoex: inquiry complete

F4:4E:FD:3B:95:A6 EDIFIER M350

find EDIFIER

0 F4:4E:FD:3B:95:A6

1 EDIFIER

2 M350

BT_MAC: F4:4E:FD:3B:95:A6

scan on

bluetoothd[1817]: Bluetooth daemon 5.50

bluetoothd[1817]: Starting SDP server

bluetoothd[1817]: kernel lacks bnep-protocol support

bluetoothd[1817]: System does not support network plugin

bluetoothd[1817]: Bluetooth management interface 1.14 initialized

bluetoothd[1817]: Sap driver initialization failed.

bluetoothd[1817]: sap-server: Operation not permitted (1)

bluetoothd[1817]: Failed to set privacy: Rejected (0x0b)

[CHG] Controller 40:80:E1:F1:BE:0C Discoverable: no

bluetoothd[1817]: Endpoint registered: sender=:1.15 path=/A2DP/MPEG24/Source/1

[CHG] Controller 40:80:E1:F1:BE:0C Class: 0x00080000

bluetoothd[1817]: Endpoint registered: sender=:1.15 path=/A2DP/SBC/Source/1

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 0000110a-0000-1000-8000-00805f9b34fb

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 00001801-0000-1000-8000-00805f9b34fb

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 00001200-0000-1000-8000-00805f9b34fb

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb

[CHG] Controller 40:80:E1:F1:BE:0C UUIDs: 00001800-0000-1000-8000-00805f9b34fb

[12277.080992] rtk_btcoex: hci (periodic)inq start

Discovery started

[CHG] Controller 40:80:E1:F1:BE:0C Discovering: yes

[NEW] Device 34:29:EF:2C:E3:55 34-29-EF-2C-E3-55

[NEW] Device 34:29:EF:38:D9:1B 34-29-EF-38-D9-1B

[CHG] Device F4:4E:FD:3B:95:A6 RSSI: -36

[NEW] Device 4E:3C:D4:78:B4:2D K3_2db478

[NEW] Device 7D:3A:EA:81:4E:FC lck1_7D3AEA814EFC

[NEW] Device 20:23:06:4C:2B:9D UAF028

[NEW] Device 20:23:06:3C:9D:68 UAF028

[NEW] Device 2C:58:B9:7A:9A:41 2C-58-B9-7A-9A-41

[NEW] Device 02:68:EB:0E:98:4F 02-68-EB-0E-98-4F

[NEW] Device 86:2A:FD:9A:9C:9B 86-2A-FD-9A-9C-9B

[CHG] Device 20:23:06:4C:2B:9D UUIDs: 0000ffb0-0000-1000-8000-00805f9b34fb

[CHG] Device 20:23:06:4C:2B:9D ManufacturerData Key: 0x0aa5

[CHG] Device 20:23:06:4C:2B:9D ManufacturerData Value:

  c7 a5 d4 fa 20 23 06 4c 2b 9d 02 00              .... #.L+...

[NEW] Device B4:A8:28:37:51:6A B4-A8-28-37-51-6A

[NEW] Device 4A:9E:BD:60:98:E7 4A-9E-BD-60-98-E7

[NEW] Device 78:2B:46:43:EE:31 LAPTOP-A8M5JMVI

[NEW] Device 5E:FE:AA:31:7B:D2 5E-FE-AA-31-7B-D2

[CHG] Device 2C:58:B9:7A:9A:41 UUIDs: 0000fe78-0000-1000-8000-00805f9b34fb

[CHG] Device 2C:58:B9:7A:9A:41 ManufacturerData Key: 0x0065

[CHG] Device 2C:58:B9:7A:9A:41 ManufacturerData Value:

  01 c9 05                                         ...

[NEW] Device 75:A1:79:AF:E3:A2 75-A1-79-AF-E3-A2

[CHG] Device 20:23:06:3C:9D:68 RSSI: -66

Failed to stop discovery: org.bluez.Error.Failed

./bt_play_source.sh: line 99:  1819 Killed                  blue[12284.659328] rtk_btcoex: hci (periodic)inq cancel/exit

toothctl scan on

Changing F4:4E:FD:3B:95:A6 trust succeeded

Attempting to pair with F4:4E:FD:3B:95:A6

Failed to pair: org.bluez.Error.AlreadyExists

Attempting to connect to F4:4E:F[12288.864074] rtk_btusb: btusb_notify: hci0 evt 1

D:3B:95:A6

[12288.873009] rtk_btcoex: hci create connection, start paging

[12289.149014] rtk_btcoex: connected, handle 0003, status 0x00

[12289.155495] rtk_btcoex: Page success

[CHG] Device F4:4E:FD:3B:95:A6 Connected: yes

[12289.429127] rtk_btcoex: l2cap op 2, len 16, out 1

[12289.434453] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x0019, scid 0x0040

[12289.442703] rtk_btcoex: list_allocate_add: Add a2dp signal channel

[12289.481698] rtk_btcoex: l2cap op 3, len 20, out 0

[12289.487238] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0043, scid 0x0040, result 0x0000

[12289.497064] rtk_btcoex: l2cap connection success, update connection

[12289.504106] rtk_btcoex: update_profile_connection: is_add 1, profile_index 2

[12289.512069] rtk_btcoex: update_profile_connection: phci_conn->profile_bitmap 0x04

[12289.520588] rtk_btcoex: rtk_notify_profileinfo_to_fw: BufferSize 5

[12289.527688] rtk_btcoex: rtk_notify_profileinfo_to_fw: NumberOfHandles 1

[12289.535192] rtk_btcoex: rtk_notify_profileinfo_to_fw: handle 0x0003

[12289.542269] rtk_btcoex: rtk_notify_profileinfo_to_fw: profile_bitmap 0x0004

[12289.550158] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc19

bluetoothd[1817]: Endpoint registered: sender=:1.15 path=/A2DP/SBC/Source/2

[12289.736933] rtk_btcoex: l2cap op 2, len 16, out 1

[12289.742278] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x0019, scid 0x0041

[12289.750539] rtk_btcoex: list_allocate_add: Add a2dp media channel

[12289.789200] rtk_btcoex: l2cap op 3, len 20, out 0

[12289.794732] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0044, scid 0x0041, result 0x0000

[12289.804548] rtk_btcoex: l2cap connection success, update connection

[12289.811622] rtk_btcoex: update_profile_connection: is_add 1, profile_index 2

[12289.819566] rtk_btcoex: update_profile_connection: phci_conn->profile_bitmap 0x04

[12289.848242] rtk_btcoex: l2cap op 2, len 16, out 1

[12289.853576] rtk_btcoex: l2cap op 2, len 16, out 1

[12289.859020] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x0001, scid 0x0042

[12289.867302] rtk_btcoex: PSM(0x0001) do not need parse

Connection successful

[12289.873025] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x0017, scid 0x0043

[12289.883375] rtk_btcoex: l2cap op 2, len 16, out 0

[12289.889163] rtk_btcoex: l2cap op 3, len 20, out 1

bluetoothd[1817]: Control: Refus[12289.895167] rtk_btcoex: l2cap op 3, len 20, out 1

ing unexpected connect

[12289.903610] rtk_btcoex: PSM(0x0017) do not need parse

[12289.910998] rtk_btcoex: l2cap op 3, len 20, out 0

[12289.916390] rtk_btcoex: l2cap op 3, len 20, out 0

[12289.921835] rtk_btcoex: RX l2cap conn req, hndl 0x0003, PSM 0x0017, scid 0x0045

[12289.930131] rtk_btcoex: PSM(0x0017) do not need parse

[12289.935809] rtk_btcoex: TX l2cap conn rsp, hndl 0x0003, dcid 0x0044, scid 0x0045, result 0x0001

[12289.945697] rtk_btcoex: TX l2cap conn rsp, hndl 0x0003, dcid 0x0044, scid 0x0045, result 0x0003

[12289.955522] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0046, scid 0x0042, result 0x0000

[12289.965325] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0047, scid 0x0043, result 0x0004

[12291.078635] rtk_btcoex: l2cap op 2, len 16, out 1

[12291.083994] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x0017, scid 0x0043

[12291.092250] rtk_btcoex: PSM(0x0017) do not need parse

[12291.130453] rtk_btcoex: l2cap op 3, len 20, out 0

[12291.136012] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0048, scid 0x0043, result 0x0000

bluetoothd[1817]: Can't open inp[12291.185041] rtk_btcoex: l2cap op 2, len 16, out 1

ut device: No such file or direc[12291.192907] rtk_btcoex: TX l2cap conn req, hndl 0x0003, PSM 0x001b, scid 0x0044

tory (2)

bluetoothd[1817]: AVRCP: failed to init uinput for F4:4E:FD:3B:95:A6

[12291.212948] rtk_btcoex: l2cap op 3, len 20, out 0

[12291.218445] rtk_btcoex: RX l2cap conn rsp, hndl 0x0003, dcid 0x0049, scid 0x0044, result 0x0000

[12291.228350] rtk_btcoex: l2cap connection success, update connection

[12291.235495] rtk_btcoex: update_profile_connection: is_add 1, profile_index 3

[12291.243542] rtk_btcoex: update_profile_connection: phci_conn->profile_bitmap 0x0c

[12291.252051] rtk_btcoex: rtk_notify_profileinfo_to_fw: BufferSize 5

[12291.259119] rtk_btcoex: rtk_notify_profileinfo_to_fw: NumberOfHandles 1

[12291.266665] rtk_btcoex: rtk_notify_profileinfo_to_fw: handle 0x0003

[12291.273713] rtk_btcoex: rtk_notify_profileinfo_to_fw: profile_bitmap 0x000c

[12291.281560] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc19

[12292.078397] rtk_btcoex: l2cap op 6, len 16, out 1

[12292.083736] rtk_btcoex: TX l2cap disconn req, hndl 0x0003, dcid 0x0046, scid 0x0042

[12292.092414] rtk_btcoex: handle_l2cap_discon_req: handle 0x0003, dcid 0x0046, scid 0x0042, dir 1

Playing WAVE '/embfly_test/wfxy.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

bluetoothd[1817]: /org/bluez/hci0/dev_F4_4E_FD_3B_95_A6/fd0: fd(21) ready

[12295.004864] rtk_btcoex: update_profile_state: is_busy 1, profile_index 2

[12295.012583] rtk_btcoex: update_profile_state: phci_conn->profile_status 0x04

[12295.020539] rtk_btcoex: rtk_notify_profileinfo_to_fw: BufferSize 5

[12295.027562] rtk_btcoex: rtk_notify_profileinfo_to_fw: NumberOfHandles 1

[12295.034984] rtk_btcoex: rtk_notify_profileinfo_to_fw: handle 0x0003

[12295.042054] rtk_btcoex: rtk_notify_profileinfo_to_fw: profile_bitmap 0x000c

[12295.049942] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc19

[12295.056210] rtk_btcoex: rtl_process_media_data: Length 637

[12295.062408] rtk_btcoex: rtp: v 2, cc 0, pt 96

[12295.067327] rtk_btcoex: syncword: 9c

[12295.071335] rtk_btcoex: freq 48kHz

[12295.075183] rtk_btcoex: blocks 16

[12295.078928] rtk_btcoex: channel mode JOINT_STEREO

[12295.084206] rtk_btcoex: allocation method LOUDNESS

[12295.089600] rtk_btcoex: subbands 8

[12295.093417] rtk_btcoex: rtl_process_media_data: bitpool 32

[12295.099625] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc51

[12295.746707] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 42

[12296.786712] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

[12297.826743] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 62

[12298.866741] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 61

[12298.986698] rtk_btcoex: l2cap op 2, len 16, out 0

[12298.992133] rtk_btcoex: RX l2cap conn req, hndl 0x0003, PSM 0x0001, scid 0x004a

[12298.992138] rtk_btcoex: l2cap op 3, len 20, out 1

[12299.005810] rtk_btcoex: PSM(0x0001) do not need parse

[12299.011588] rtk_btcoex: TX l2cap conn rsp, hndl 0x0003, dcid 0x0042, scid 0x004a, result 0x0000

[12299.906751] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

[12300.946768] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

[12301.417951] rtk_btcoex: l2cap op 6, len 16, out 0

[12301.423487] rtk_btcoex: RX l2cap disconn req, hndl 0x0003, dcid 0x0042, scid 0x004a

[12301.432256] rtk_btcoex: handle_l2cap_discon_req: handle 0x0003, dcid 0x0042, scid 0x004a, dir 0

[12301.986775] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

[12303.026785] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 62

[12304.066798] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

[12305.106802] rtk_btcoex: count_a2dp_packet_timeout: a2dp_packet_count 60

Aborted by signal Interrupt...

[12305.781101] rtk_btcoex: HCI OP Disconnect, handle 0003, reason 0x15

aplay: pcm_write:2053: write error: Interrupted system call

bluetoothd[1817]: Terminating

root@T113-Embfly:/embfly_test# [12305.871038] rtk_btcoex: disconn cmpl evt: status 00, handle 0003, reason 15

bluetoothd[1817]: No reply to Su[12305.878928] rtk_btcoex: process disconn complete event.

spend request

[12305.887616] rtk_btcoex: hci disconn, hndl 3, psm 19, dcid 43, scid 40, profile 2

[12305.897388] rtk_btcoex: disconn_profile: profile_ref[2] 2

bluetoothd[1817]: Endpoint unreg[12305.903492] rtk_btcoex: Delete profile: hndl 0x0003, psm 0x0019, dcid 0x0043, scid 0x0040

istered: sender=:1.15 path=/A2DP[12305.915503] rtk_btcoex: hci disconn, hndl 3, psm 19, dcid 44, scid 41, profile 2

/MPEG24/Source/1

bluetoothd[181[12305.926571] rtk_btcoex: disconn_profile: profile_ref[2] 1

7]: Endpoint unregistered: sende[12305.935424] rtk_btcoex: rtk_check_del_timer: handle 0x0003

r=:1.15 path=/A2DP/SBC/Source/1[12305.944381] rtk_btcoex: Delete profile: hndl 0x0003, psm 0x0019, dcid 0x0044, scid 0x0041

[12305.956260] rtk_btcoex: hci disconn, hndl 3, psm 1b, dcid 49, scid 44, profile 3

bluetoothd[1817]: Endpoint unreg[12305.964791] rtk_btcoex: disconn_profile: profile_ref[3] 1

istered: sender=:1.15 path=/A2DP[12305.973627] rtk_btcoex: rtk_check_del_timer: handle 0x0003

/SBC/Source/2

[12305.982567] rtk_btcoex: Delete profile: hndl 0x0003, psm 0x001b, dcid 0x0049, scid 0x0044

[12305.993063] rtk_btcoex: rtk_notify_profileinfo_to_fw: BufferSize 2

[12306.000011] rtk_btcoex: rtk_notify_profileinfo_to_fw: NumberOfHandles 0

[12306.007460] rtk_btcoex: rtk_vendor_cmd_to_fw: opcode 0xfc19

[12306.066821] rtk_btusb: btusb_notify: hci0 evt 2

[12306.081254] rtk_btusb: btusb_flush add delay

bluetoothd[1817]: Stopping SDP server

bluetoothd[1817]: Exit

[12306.096182] rtk_btusb: btusb_close

[12306.119973] rtk_btcoex: Close BTCOEX

[12306.123994] rtk_btcoex: -x

音乐响起,恭喜你!感谢您使用评估盈鹏飞嵌入式的SBC-T113S主板!

T113 Longan 系统配置(Linux) 本系列调试说明记录了Linux在全志T113-S3/S4平台上的移植过程,说明过程中可能会技术瑕疵,希望大家提供宝贵意见。本文移植的硬件平台来自于盈鹏飞嵌入式的SBC-T113S(处理器是T113-S3)主板。产品功能评估图:产品尺寸:以下为T113 Longan 系统配置(Linux) 阅读详情

相关推荐

(盈鹏飞嵌入式T113-S4主板)-主板上电、串口、USB调试及LED测试

Linux系统提供了一个独立的子系统以方便从用户空间操作LED设备,该子系统以文件的形式为LED设备提供操作接口,这些接口位于/sys/class/leds目录下。主板的调试方式之一是用串口进行调试,主要是方便查看系统的打印信息,在做系统的底层驱动调试时使用很方便。调试串口是CPU的UART0(Linux软件中配置),通过PH2.0_1X4的接口件引出。接入电源后,主板即启动。主板的调试方式之一是ADB调试,可以通过USB(TYPE-A)线将电脑和主板的CN4相连,在系统起来之后,电脑会识别到USB设备。

szembed的博客 1324

盈鹏飞嵌入式T113-S4主板_Tina5.0通过Luci配置系统

uhttpd是一个功能全面、轻量级的Web服务器,是Web管理界面LuCI的默认服务器,支持SSL、CGI、Lua。uhttpd是单线程,但支持多个实例。

szembed的博客 1611

(盈鹏飞嵌入式T113-S4主板)-RGB666液晶屏显示

该接口设计时,默认连接的是我司的EAC-LCD70L这个模组,该屏幕可以支持800X480的7寸液晶屏和1024X600的7寸液晶屏。备注:如果EAC-LCD70L配电容式触摸屏,那么SBC-T113S通过CN25与EAC-LCD70L的CN4相连;如果EAC-LCD70L配电阻式触摸屏,那么SBC-T113通过CN24与EAC-LCD70L的CN4相连;EAC-LCD70L的CN1的一脚务必于SBC-T113S主板的CN23的一脚对应。1*6Pin 0.5mm上接。1*6Pin 1.0mm上接。

szembed的博客 1301

(盈鹏飞嵌入式T113-S4主板)-Tina5.0系统蓝牙测试

如果通过lsmod指令未发现可用的bt驱动(rtk_btusb),则可以通过insmod指令进行驱动插入,bt的驱动在/lib/modules/5.4.61/目录。另外,bt的驱动还需要两个配置文件,当bt驱动加载时,务必保证rtl8723du_config 和rtl8723du_fw两个文件在/lib/firmware/的目录下,否则bt驱动加载不成功。检查完成后,我们要开始使能hci设备了,并运行bluetoothd服务,如果不提前运行他们,后续的指令不能正常执行,特别是后续的。

szembed的博客 1968

全志Longan和Tina系统T113-S3-(Tina Linux 系统介绍)

Tina Linux是全志科技基于Linux内核开发的针对智能硬件类产品的嵌入式软件系统。Tina Linux基于openwrt-14.07 版本的软件开发包,包含了 Linux 系统开发用到的内核源码、驱动、工具、系统中间件与应用程序包。Tina系统软件架构如图所示。从下至上分别为Kernel && Driver、Libraries、System Services、Applications 四层。

szembed的博客 6330

(盈鹏飞嵌入式T113-S4主板)-Tina5.0系统RS232&RS485测试

本次测试标准串口 COM11已经连接主板的调试串口,待测试串口连接KIT-CP2105的增强型串口(COM12),连接工作准备好后,开始进行测试工作。此时可以在串口调试小助手的发送区输入要发送的的数据,选择自动发送或手动发送,调试终端则会显示接收的数据,同时主板将数据返回给串口调试小助手。测试过程按“Ctrl+c”终止测试指令。由上图可以看到,转接板已经正确连接,并可以识别到两个串口设备,增强型串口(Enanced COM,COM12)和标准串口(Standard COM,COM11)。

szembed的博客 1145

(盈鹏飞嵌入式T113-S4主板)-RTC 时钟测试

特别说明:如果存在/dev/rtc0和rtc1,那么/dev/rtc0是CPU自带硬时钟,/dev/rtc1是HYM8563硬件时钟。查看硬件时钟,检查是否是上面hwclock -w所设置的时钟。使用hwclock写入硬件时钟。图13 电池座BAT1。

szembed的博客 755

(盈鹏飞嵌入式T113-S4主板)-BT蓝牙功能(RTL8723DU)测试

如果通过lsmod指令未发现可用的bt驱动(rtk_btusb),则可以通过insmod指令进行驱动插入,bt的驱动在/lib/modules/5.4.61/目录(如果是Preempt linux,则驱动在/lib/modules/5.4.61-rt37目录)。另外,bt的驱动还需要两个配置文件,当bt驱动加载时,务必保证rtl8723du_config 和rtl8723du_fw两个文件在/lib/firmware/的目录下,否则bt驱动加载不成功。是一个交互式且易于使用的工具,用于控制蓝牙设备。

szembed的博客 1510

T113 Linux 系统-Linux QT

本系列调试说明记录了Linux在全志T113-S3/S4平台上的移植过程,说明过程中可能会技术瑕疵,希望大家提供宝贵意见。本文移植的硬件平台来自于盈鹏飞嵌入式的SBC-T113S(处理器是T113-S3)主板。

szembed的博客 2981

Ubuntu QtCreator配置交叉编译环境(QT)

本系列调试说明记录了在全志T113-S3/S4平台上的移植过程,说明过程中可能会技术瑕疵,希望大家提供宝贵意见。本文移植的硬件平台来自于盈鹏飞嵌入式的SBC-T113S(处理器是T113-S3)主板。

szembed的博客 1857

飞凌OK113i-C全志T113-i开发板 rtl8723du WIFI 功能测试及蓝牙驱动移植

飞凌 OK113i-C 全志T113-i开发板板载一个RTL8723du wifi/蓝牙二合一模块,板子出厂已经移植好了WIFI驱动但是蓝牙驱动没有,所以这篇文章我们主要做蓝牙驱动的移植和功能验证。在下找到选项。默认是开启的。

DOT小文哥的博客 2715

MQ1RDW2-T113-S3[使用日记3] WLAN/BT 切换成 RTL8723DS

对于 MQ1RDW2-T113-S3 SDK 已经移植了 RTL8723DS 的驱动,但是默认使用的是 RTL8189FS,和板卡不一样,需要修改自动加载驱动文件,位于 Tina-Linux/target/allwinner/t113-mq_r/busybox-init-base-files/etc/init.d/rc.modules。

qq_44696031的博客 1097

(盈鹏飞嵌入式T113-S4主板)-触摸屏测试(电阻式触摸屏)

从evtest指令得到的信息是:/dev/input/event1节点来自sunxi-ts设备,这个设备是T113-i的电阻式触摸屏控制器。校验前除了满足电阻式触摸屏和主板的硬件连接外,还要满足的条件是tslib已经被移植到主板上,并进行了环境变量的设置。另外,为了确认是本次的触摸屏校验有效,建议先删除之前的校验文件,该文件是位于/etc目录下的pointercal文件。执行ts_calibrate操作指令后,液晶屏显示设备上会显示校准界面,此时点击校准准星进行校准,依次点击五次后,校准测试完成。

szembed的博客 1211

【全志T113-S3_100ask】12-1 Linux蓝牙通信实战(BLE简介)

BLE(Bluetooh Low Energy)蓝牙BLE技术是一种短距离、低成本、可互操作性的无线技术,它利用许多的智能手段最大限度地降低其功耗。BLE技术的工作模式非常适用于微型无线传感器(每半秒交换一次数据)或使用完全异步通信的遥控器等其它外设传送数据。这些设备发送的数据量非常小(通常也就几个字节),而且发送的次数也很少(例如每秒几次到每分钟一次,甚至更少)。...

第四维度的博客 5015

[全志T113]:RTL8723BS驱动

[全志T113]:RTL8723BS驱动

LINKKEEE的博客 1461

MT6771 Android13 背光曲线调试与光感数据校准实战

本文详细介绍了MT6771平台在Android 13系统上进行背光曲线调试与光感数据校准的实战经验。针对高亮度环境下背光误调节问题,深入分析了光感数据上报机制,并提供了驱动层配置修改、背光曲线优化及常见问题解决方案,帮助开发者快速定位并解决类似问题。

moon9的博客 287

盈鹏飞嵌入式T113-s4主板终端信息_tina5 Linux

【代码】盈鹏飞嵌入式T113-s4主板终端信息_tina5 Linux。

szembed的博客 1017

WebVTT中的文本轨道(Text Tracks,TT)到底是什么鬼?

WebVTT,全称是The Web Video Text Tracks Format,意思是网络视频文本轨道格式。那么到底什么是文本轨道(Text Tracks)呢?这篇文章希望一探究竟。

码农1479的博客 1985

【全志T113-S3_100ask】——什么是BLE?

蓝牙是一种短距离的通讯技术,可以实现固定设备和移动设备之间进行数据交换。传统蓝牙:蓝牙3.0之前;低功耗蓝牙:蓝牙4.0规下。

weixin_53532647的博客 667

DLMS-Blue-Book蓝皮书—曲线类

attribute_index 1 指的是第 1 个属性(即 logical_name),attribute_index 2 指的是第 2 个属性,等等;如果其他“曲线通用类”对象捕获了这个缓冲区,它们的缓冲区也将被清空,以保证它们的缓冲区条目是同质的。如果捕获对象是曲线通用类的缓冲区,则 data_index 标识缓冲区(即列)中的捕获对象(即内部曲线通用类中的列);如果曲线通用类已排序,则调用捕获方法将把新条目存储在缓冲区中的适当位置,移动所有后续条目,并可能丢失最不相关的条目。

一个bug是bug,多个bug能work 1452

Oracle EBS 寄销/VMI(1)-->基础设置

名词解释:     BPA:一揽子采购协议     BPR:一揽子发放     SR:来源补充规则     ASL:合格供应商列表     VMI: 供应商管理库存     寄售(Consignment)是把货物放在客户那里,客户要用的时候才付款的库存,一般是指卖方把

陈显平的专栏-Oracle EBS 1万+

全志T113 芒果派MQ-Dual(T113) QT+电容触摸

注意:ARM编译工具的绝对路径 QMAKE_CC,QMAKE_CXX,QMAKE_LINK,QMAKE_LINK_SHLIB 地址是SDK绝对路径(错误可能会提示maybe you forgot to setup the environment )通过虚拟机共享文件夹将SDK目录下的out/t113-mq-r/tina_t113-mq_r_uart0.img.文件放到Window系统,运行PhoenixCard工具将镜像文件烧写到SD卡中,注意。如果再次进入安装程序, 要在CD/DVD取消系统镜像文件。

noabcd32的专栏 6398

【信号与系统】Multisim 仿真信号合成与分解

软件 Multisim 进行方波信号的产生、分解和合成,观察信号波形的分解与合成,加深对信号频谱的理解。

AXYZdong的博客 2万+
上一篇: (盈鹏飞嵌入式T113-S4主板)-BT蓝牙功能(RTL8723DU)测试
下一篇: OpenWRT系统启动过程
szembed
博客等级 码龄18年 1475粉丝 256原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值