Skip to content

GitLab

RELEASENOTE_TAMUL · Changes

Page history
Update RELEASENOTE_TAMUL authored by delly chen's avatar delly chen
Hide whitespace changes
Inline Side-by-side
Showing with 14 additions and 59 deletions
RELEASENOTE_TAMUL.md
View page @ 3655549e
......@@ -6,9 +6,9 @@ AnW Bluetooth Service API, offered two sorts of releases
2. [SDK Release (anwbtsrv_sdk)](#SDKRelease): open source with **AnWBTServiceDemo.cpp**, imported essentials libraries (**.so**), header (**anwbtservice.h**), and App configures (**.xml**)
# RELEASE NOTE
20220121 [TAG:TAMUL_BT_V3](http://192.168.1.51:8088/delly.chen/anw_bt_srv/-/tags/TAMUL_BT_V3)
20220121 [TAG:0.0.03](http://192.168.1.51:8088/delly.chen/anw_bt_srv/-/tags/0.0.0.3)
1. \[FUNC\]supports android auto connect & write data to android
2. \[FUNC\]Add some functions,For details, refer to anwbtservice.h
2. \[FUNC\]Add some functions, For details, refer to anwbtservice.h
20220118 [TAG:TAMUL_BT_V2](http://192.168.1.51:8088/delly.chen/anw_bt_srv/-/tags/TAMUL_BT_V2)
......@@ -19,14 +19,11 @@ AnW Bluetooth Service API, offered two sorts of releases
1. \[FUNC\] supports basic BT pair & connect
# USAGE
1. Support HFP, A2DP, AVRCP, PBAP, .. AnW BT stack
2. Support Device Serarch & Pair, Call, Phonebook, Music, ...
## Pre-Requirement
Modify combo module init script **/etc/init.d/ubloxinit.sh**
```plaintext
echo "[DDMISO] UBLOX Driver"
modprobe jody-w2-sdiouart
......@@ -43,19 +40,16 @@ udhcpc -i mlan0
```
## Run App on targets (tamul_btsrv-.zip)
1. unzip
2. Copy results folder /build/btsrv to target /home/btsrv
3. go to target, in terminal entering /btsrv folder
4. run btsrv_client.sh to launch BTDemo demo app and following the menu commands or
```
> export LD_LIBRARY_PATH="/home/btsrv"
>./BTDemo
```
### set device name
```
================bluetooth menu=================
1.EXIT
......@@ -72,7 +66,6 @@ udhcpc -i mlan0
```
### power on init
```
================bluetooth menu=================
1.EXIT
......@@ -84,11 +77,9 @@ udhcpc -i mlan0
BTPowerOn
...
```
Note: Looking for device name (e.g. TAMUL_MARVELL) from mobile, then pair the device with mobile When mobile shows connected succeed, turn off the BT button from mobile, then turn on the BT button from mobile again. At this time, mobile has paired storage with the device.
### For Iphone carplay spp connect
### spp connect
```
================ BT Test Menu =================
1. Exit
......@@ -103,17 +94,14 @@ Note: Looking for device name (e.g. TAMUL_MARVELL) from mobile, then pair the de
> input connect addr(xx:xx:xx:xx:xx:xx): 11:e8:14:da:61:d4 (for example)
...
```
Note: You can find mobile BT mac from **"Setting->General->About-> Bluetooth"**
Note: You can find mobile BT mac from **"Setting->General->About-> Bluetooth"** (iphone)
```
> input profile_mask: 0x00000040
```
Note: Then, connected.
### For Iphone carplay spp write
### spp write
```
================ BT Test Menu =================
1. Exit
......@@ -126,62 +114,31 @@ Note: Then, connected.
> input num: 10
> input connect addr(xx:xx:xx:xx:xx:xx): 11:e8:14:da:61:d4 (for example)
```
Note: You can find mobile BT mac from **"Setting->General->About-> Bluetooth"** (iphone)
Note: You can find mobile BT mac from **"Setting->General->About-> Bluetooth"**
```
#### CarPlay spp settings
```
>input SPP_data:ff,55,2,0,ee,10 (for example)
```
Note: Then, you can receive data back from **IPHONE**, check log printed:
```plaintext
Note: **ff,55,2,0,ee,10** is specified for **CarPlay**, to check log printed to get successfully responded from iPhone
Note: Then, check log printed to get successfully responded
```
AnWBTService_SPP_DATA_IND_S sppData:
[ff] [55] [2] [0] [ee] [10]
```
### For Android Auto Connect
After BTPowerOn successfully, you can inquiry device from Android phone;
then android phone pair with device, if android phone support AndroidAuto, the mobile phone will actively initiate an android auto connection to the car;
During this process, you can see the data interaction between the mobile phone and the car from the terminal log.
### For Android Auto spp write
```
================ BT Test Menu =================
1. Exit
2. StartInquiry
...
8. ConnectDevice
9. DisconnectDevice
10.SPP_Write
===============================================
> input num: 10
> input connect addr(xx:xx:xx:xx:xx:xx): 11:e8:14:da:61:d4 (for example)
```
#### Android Auto spp settings
```
>input SPP_data:00, 15, 00, 04, 08, 01, 10, 00, 18, 00,20, 95, 01, 20, 99, 01, 20, 9D,01, 20, A1, 01, 20, A5, 01 (for example)
```
Note: Then, you can receive data back from **Android**, check log printed:
Note: **00, 15, 00, 04, 08, 01, 10, 00 ...** is specified for **Android Auto** or inquiry device from Android phone, upon paired, if phone is "Android Auto" supported, the connect request will automatically send to host HU.
Note: Then, check log printed to get successfully responded
```
AnWBTService_SPP_DATA_IND_S sppData:
[0][64][0][5][8][1][10][5][1a][e][39][41][32][37][31][46][46][41][5a][30][30][41][4b][34][20][0][32][4c][a][24][66][32][61][63][66][36][61][33][2d][35][64][64][64][2d][34][31][66][64][2d][62][33][62][63][2d][64][38][39][37][38][30][36][36][33][63][30][63][12][24][30][65][33][34][39][62][63][61][2d][62][30][32][61][2d][34][38][39][31][2d][39][38][38][34][2d][64][65][35][63][65][38][35][33][34][66][30][63](26213|0xB4DFF450)[BTAPI] btsdk_exec_apicb end
```
## Customize on SDK (tamul_release-.zip)
1. unzip
2. in terminal entering ./anwbtsrv_sdk/Demo folder
3. setup tool-chain by command line (source ...) or edit in ./anwbtsrv_sdk/Demo/build_demo.sh
......@@ -192,11 +149,9 @@ AnWBTService_SPP_DATA_IND_S sppData:
> source /opt/poky-tamul/2.5.1/environment-setup-cortexa9hf-neon-poky-linux-gnueabi
> make or ./build_demo.sh
```
then, result is collected in **./Demo/btsrv**
# STRUCTURE (tamul_release-.zip)
<pre>
.
└── Demo
......