BLE设备监控软件清单

BLE_DevMon

需积分: 1 93 浏览量更新于2024-07-23 收藏 152KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

April 11, 2014

Rev 1.0 Software Manifest Page 3 of 15

LGPL v2.1 License

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts

as the successor of the GNU Library Public License, version 2, hence

the version number 2.1.]

Preamble

The licenses for most software are designed to take away your

freedom to share and change it. By contrast, the GNU General Public

Licenses are intended to guarantee your freedom to share and change

free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some

specially designated software packages--typically libraries--of the

Free Software Foundation and other authors who decide to use it. You

can use it too, but we suggest you first think carefully about whether

this license or the ordinary General Public License is the better

strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use,

not price. Our General Public Licenses are designed to make sure that

you have the freedom to distribute copies of free software (and charge

for this service if you wish); that you receive source code or can get

it if you want it; that you can change the software and use pieces of

it in new free programs; and that you are informed that you can do

these things.

To protect your rights, we need to make restrictions that forbid

distributors to deny you these rights or to ask you to surrender these

rights. These restrictions translate to certain responsibilities for

you if you distribute copies of the library or if you modify it.

剩余14页未读，继续阅读

TI_BLE_Software_Developer's_Guide

TI_BLE_Software_Developer's_Guide 是TI发行的蓝牙4.0协议栈开发指南，据有较强的指导意义，可以避免开发人员少走弯路，提高效率。

ble_app_hids_keyboard.rar_BLE HID_NRF52832_ble keyboard_hid app_

**BLE HID键盘应用详解** 本教程将深入探讨`ble_app_hids_keyboard.rar`中的蓝牙低功耗（BLE）人机接口设备（HID）键盘应用，该应用是基于Nordic Semiconductor的NRF52832微控制器的。这个例程已被验证为功能完备，...

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context) { uint16_t conn_handle = p_ble_evt->evt.gap_evt.conn_handle; uint16_t role = ble_conn_state_role(conn_handle); // Based on the role this device plays in the connection, dispatch to the right handler. if (role == BLE_GAP_ROLE_PERIPH || ble_evt_is_advertising_timeout(p_ble_evt)) { ble_evt_dispatch(p_ble_evt, p_context); } else if ((role == BLE_GAP_ROLE_CENTRAL) || (p_ble_evt->header.evt_id == BLE_GAP_EVT_ADV_REPORT)) { ble_module_central_evt(p_ble_evt, p_context); } }

这是一个 Bluetooth Low Energy (BLE) 事件处理函数，用于处理 BLE 事件。它首先从事件中获取连接句柄和连接角色信息，然后根据角色信息将事件分发给不同的处理函数。如果设备角色是 BLE_GAP_ROLE_PERIPH，或者事件...

if(capture_type == BATTERY_CAPTURE_TYPE_UP) { //初始化呼吸 led_module_show_adapter_operation(); g_battery_module_mgr.b_low_voltage = false; g_battery_module_mgr.capacity.init_time = my_fw_timer_hw_get_cnt(); g_battery_module_mgr.capacity.before_charge_persentage = p_batt->battery_persentage; battery_module_tick_check_process(); if(rower_module_get_ble_app_handle() != BLE_CONN_HANDLE_INVALID) { peer_module_disconnect(rower_module_get_ble_app_handle()); } } else { //去除呼吸\常亮，判断是否是闪烁 led_module_show_adapter_cease(); g_battery_module_mgr.capacity.b_discharge_delay = true; g_battery_module_mgr.capacity.charge_time =0; g_battery_module_mgr.capacity.voltage_init = battery_module_get_software_cal_voltage(); g_battery_module_mgr.capacity.after_charge_persentage = p_batt->battery_persentage; my_fw_tm_start(ROWER_MODULE_EVENT_TIMEOUT,0,NULL,ROWER_TIMEOUT); }

这段代码看起来像是关于电池管理的代码，根据 `capture_type` 的不同取值，执行不同的操作。...同时，如果 rower_module_get_ble_app_handle() 返回的值不是 BLE_CONN_HANDLE_INVALID，还会断开与 BLE 设备的连接。

ble_evt_dispatch(p_ble_evt, p_context)和ble_module_central_evt(p_ble_evt, p_context)的区别

`ble_evt_dispatch(p_ble_evt, p_context)`是一个通用的BLE事件分派函数，它会将收到的BLE事件分派到相应的处理函数中去。而`ble_module_central_evt(p_ble_evt, p_context)`是一个特定模块（central）的BLE事件处理...

#define DEVICE_NAME "BL618_GATT" // 设备名称 #define PROFILE_NUM 1 // 设备支持的服务数量 #define PROFILE_A_APP_ID 0 // 第一个服务的ID static void gap_event_handler(ble_event_t event); static void gatt_event_handler(ble_event_t event); int main(void) { // 初始化蓝牙协议栈 bluetooth_init(gap_event_handler, gatt_event_handler); // 设置设备名称 bluetooth_set_device_name(DEVICE_NAME); // 创建一个服务 bluetooth_gatt_create_service(PROFILE_NUM); // 添加服务的特征值 bluetooth_gatt_add_char(PROFILE_A_APP_ID, "CHAR_A", 0xFF01, 0x20, NULL); // 开始广播 bluetooth_start_advertising(); while (1) { // 等待事件 bluetooth_wait_for_event(); } return 0; } static void gap_event_handler(ble_event_t event) { switch (event->type) { case BLE_GAP_EVENT_ADV_IND: { // 收到广播包，可以连接该设备 ble_gap_connect(&event->gap_event.adv_ind.address); break; } case BLE_GAP_EVENT_CONNECTED: { // 连接成功，可以开始 GATT 操作 break; } case BLE_GAP_EVENT_DISCONNECTED: { // 断开连接，重新开始广播 bluetooth_start_advertising(); break; } default: break; } } static void gatt_event_handler(ble_event_t event) { switch (event->type) { case BLE_GATT_EVENT_READ: { // 处理读操作 break; } case BLE_GATT_EVENT_WRITE: { // 处理写操作 ble_err_t err = ble_gatt_server_send_indication(event->conn_handle, 0x1234, raw_data, sizeof(raw_data)); // 发送通知给主机 if (err != BLE_ERR_NONE) { // 发送失败，需要处理错误 break; } break; } default: break; } }给出无注释代码

ble_err_t err = ble_gatt_server_send_indication(event->conn_handle, 0x1234, raw_data, sizeof(raw_data)); // 发送通知给主机 if (err != BLE_ERR_NONE) { // 发送失败，需要处理错误 break; } ...

void ble_conn_handler(uint8_t conn_id, T_GAP_CONN_STATE new_state, uint16_t disc_cause) { struct ble_gap_event event; memset(&event, 0, sizeof(event)); switch (new_state) { case GAP_CONN_STATE_CONNECTED: { DBG_DIRECT("BLE connected, conn_id:%d\n", conn_id); event.type = BLE_GAP_EVENT_CONNECT; event.connect.conn_handle = conn_id; notify_ble_event_to_listeners(&event); } break; case GAP_CONN_STATE_DISCONNECTED: { DBG_DIRECT("BLE disconnected, conn_id:%d, reason:0x%02x\n", conn_id, (uint8_t)disc_cause); event.type = BLE_GAP_EVENT_DISCONNECT; event.disconnect.reason = (uint8_t)disc_cause; event.disconnect.conn.conn_handle = conn_id; notify_ble_event_to_listeners(&event); } break; default: break; } }

函数中使用了一个结构体ble_gap_event来记录蓝牙连接状态的事件，当连接状态为GAP_CONN_STATE_CONNECTED时，将事件类型设为BLE_GAP_EVENT_CONNECT，并记录连接句柄，然后调用notify_ble_event_to_listeners函数通知...

ti_ble_vendor_specific_hci_guide.pdf

ti_ble_vendor_specific_hci_guide.pdf 是关于 TI 公司蓝牙低功耗（BLE）供应商特定的 HCI（Host Controller Interface）指南。在这个指南中，TI 公司为供应商提供了关于如何在特定设备上实现 BLE 技术的详细指导。 ...

#define DEVICE_NAME "BL618_GATT" // 设备名称 #define PROFILE_NUM 1 // 设备支持的服务数量 #define PROFILE_A_APP_ID 0 // 第一个服务的ID static void gap_event_handler(ble_event_t event) { // 处理 GAP 事件 } static void gatt_event_handler(ble_event_t event) { // 处理 GATT 事件 } int main(void) { // 初始化蓝牙协议栈 bluetooth_init(gap_event_handler, gatt_event_handler); // 设置设备名称 bluetooth_set_device_name(DEVICE_NAME); // 创建一个服务 bluetooth_gatt_create_service(PROFILE_NUM); // 添加服务的特征值 bluetooth_gatt_add_char(PROFILE_A_APP_ID, "CHAR_A", 0xFF01, 0x20, NULL); // 开始广播 bluetooth_start_advertising(); while (1) { // 等待事件 bluetooth_wait_for_event(); } return 0; static void gap_event_handler(ble_event_t event) { switch (event->type) { case BLE_GAP_EVENT_ADV_IND: { // 收到广播包，可以连接该设备 ble_gap_connect(&event->gap_event.adv_ind.address); break; } case BLE_GAP_EVENT_CONNECTED: { // 连接成功，可以开始 GATT 操作 break; } case BLE_GAP_EVENT_DISCONNECTED: { // 断开连接，重新开始广播 bluetooth_start_advertising(); break; } default: break; } } static void gatt_event_handler(ble_event_t event) { switch (event->type) { case BLE_GATT_EVENT_READ: { // 处理读操作 break; } case BLE_GATT_EVENT_WRITE: { // 处理写操作 ble_gatt_server_send_indication(event->conn_handle, 0x1234, raw_data, sizeof(raw_data)); // 发送通知给主机 break; } default: break; } } } }优化

以下代码有什么错误static struct bflb_device_s uart0; extern void shell_init_with_task(struct bflb_device_s shell); static int btblecontroller_em_config(void) { extern uint8_t __LD_CONFIG_EM_SEL; volatile uint32_t em_size; em_size = (uint32_t)&__LD_CONFIG_EM_SEL; if (em_size == 0) { GLB_Set_EM_Sel(GLB_WRAM160KB_EM0KB); } else if (em_size == 321024) { GLB_Set_EM_Sel(GLB_WRAM128KB_EM32KB); } else if (em_size == 641024) { GLB_Set_EM_Sel(GLB_WRAM96KB_EM64KB); } else { GLB_Set_EM_Sel(GLB_WRAM96KB_EM64KB); } return 0; } void bt_enable_cb(int err) { if (!err) { bt_addr_le_t bt_addr; bt_get_local_public_address(&bt_addr); printf("BD_ADDR:(MSB)%02x:%02x:%02x:%02x:%02x:%02x(LSB) \n", bt_addr.a.val[5], bt_addr.a.val[4], bt_addr.a.val[3], bt_addr.a.val[2], bt_addr.a.val[1], bt_addr.a.val[0]); ble_cli_register(); } } int main(void) { board_init(); configASSERT((configMAX_PRIORITIES > 4)); uart0 = bflb_device_get_by_name("uart0"); shell_init_with_task(uart0); /* set ble controller EM Size / btblecontroller_em_config(); / Init rf / if (0 != rfparam_init(0, NULL, 0)) { printf("PHY RF init failed!\r\n"); return 0; } // Initialize BLE controller #if defined(BL702) || defined(BL602) ble_controller_init(configMAX_PRIORITIES - 1); #else btble_controller_init(configMAX_PRIORITIES - 1); #endif // Initialize BLE Host stack hci_driver_init(); bt_enable(bt_enable_cb); vTaskStartScheduler();#define DEVICE_NAME "BL618_GATT" #define PROFILE_NUM 1 #define PROFILE_A_APP_ID 0 static void gap_event_handler(ble_event_t event); static void gatt_event_handler(ble_event_t event); int main(void) { bluetooth_init(gap_event_handler, gatt_event_handler); bluetooth_set_device_name(DEVICE_NAME); bluetooth_gatt_create_service(PROFILE_NUM); bluetooth_gatt_add_char(PROFILE_A_APP_ID, "CHAR_A", 0xFF01, 0x20, NULL); bluetooth_start_advertising(); while (1) { bluetooth_wait_for_event(); } return 0; } static void gap_event_handler(ble_event_t event) { switch (event->type) { case BLE_GAP_EVENT_ADV_IND: { ble_gap_connect(&event->gap_event.adv_ind.address); break; } case BLE_GAP_EVENT_CONNECTED: { // 连接成功，可以开始 GATT 操作 break; } case BLE_GAP_EVENT_DISCONNECTED: { // 断开连接，重新开始广播 bluetooth_start_advertising(); break; } default: break; } } static void gatt_event_handler(ble_event_t *event) { switch (event->type) { case BLE_GATT_EVENT_READ: { // 处理读操作 break; } case BLE_GATT_EVENT_WRITE: { ble_err_t err = ble_gatt_server_send_indication(event->conn_handle, 0x1234, raw_data, sizeof(raw_data)); // 发送通知给主机 if (err != BLE_ERR_NONE) { // 发送失败，需要处理错误 break; } break; } default: break; } }

2. 在函数 `main()` 中，代码缺少头文件引用，需要添加头文件 `bluetooth.h`、`ble_gap.h` 和 `ble_gatt.h`。 3. 在函数 `main()` 中，变量 `raw_data` 未定义，需要先定义并赋值。 4. 在函数 `main()` 中，调用 `...

static void on_disconnect(ble_cd_t * p_cd, ble_evt_t const * p_ble_evt) { UNUSED_PARAMETER(p_ble_evt); p_cd->conn_handle = BLE_CONN_HANDLE_INVALID; }

这是一个在 BLE 库中的回调函数，用于处理设备与中心设备（手机等）连接断开的情况。其中，p_cd 是一个指向连接描述符的指针，p_ble_evt 是一个指向 BLE 事件的指针。在函数体中，首先使用 UNUSED_PARAMETER 宏将 ...

NRF5函数nrf_ble_gatt_init

nrf_ble_gatt_init函数是nRF5软件开发包中用于初始化GATT（通用属性）协议栈的函数。该函数包含以下参数： 1. ble_gatt_t * p_gatt：指向GATT协议栈的结构体指针。 2. ble_gatts_attr_md_t * p_attr_md：指向属性...

对以下代码进行注释并给出可复制代码static void ble_tp_notify_task(void *pvParameters) { int err = -1; char data[244] = {0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09}; while(1) { err = bt_gatt_notify(ble_tp_conn, get_attr(BT_CHAR_BLE_TP_NOT_ATTR_VAL_INDEX), data, (tx_mtu_size - 3)); BT_WARN("ble tp send notify : %d", err); } } static void ble_tp_not_ccc_changed(const struct bt_gatt_attr attr, u16_t value) { int err; BT_WARN("ccc:value=[%d]",value); if(tp_start) { if(value == BT_GATT_CCC_NOTIFY) { if(xTaskCreate(ble_tp_notify_task, (char)"bletp", 256, NULL, TP_PRIO, &ble_tp_task_h) == pdPASS) { created_tp_task = 1; BT_WARN("Create throughput tx task success."); } else { created_tp_task = 0; BT_WARN("Create throughput tx task fail."); } } else { if(created_tp_task) { BT_WARN("Delete throughput tx task."); vTaskDelete(ble_tp_task_h); created_tp_task = 0; } } } else { if(created_tp_task) { BT_WARN("Delete throughput tx task."); vTaskDelete(ble_tp_task_h); created_tp_task = 0; } if(value == BT_GATT_CCC_NOTIFY) { err = bt_gatt_notify(ble_tp_conn, get_attr(BT_CHAR_BLE_TP_NOT_ATTR_VAL_INDEX), "notify", strlen("notify")); BT_WARN("ble tp send indatcate: %d", err); } } } static struct bt_gatt_attr attrs[]= { BT_GATT_PRIMARY_SERVICE(BT_UUID_SVC_BLE_TP), BT_GATT_CHARACTERISTIC(BT_UUID_CHAR_BLE_TP_RD, BT_GATT_CHRC_READ, BT_GATT_PERM_READ, ble_tp_recv_rd, NULL, NULL), BT_GATT_CHARACTERISTIC(BT_UUID_CHAR_BLE_TP_WR, BT_GATT_CHRC_WRITE |BT_GATT_CHRC_WRITE_WITHOUT_RESP, BT_GATT_PERM_WRITE|BT_GATT_PERM_PREPARE_WRITE, NULL, ble_tp_recv_wr, NULL), BT_GATT_CHARACTERISTIC(BT_UUID_CHAR_BLE_TP_IND, BT_GATT_CHRC_INDICATE, 0, NULL, NULL, NULL), BT_GATT_CCC(ble_tp_ind_ccc_changed, BT_GATT_PERM_READ | BT_GATT_PERM_WRITE), BT_GATT_CHARACTERISTIC(BT_UUID_CHAR_BLE_TP_NOT, BT_GATT_CHRC_NOTIFY, 0, NULL, NULL, NULL), BT_GATT_CCC(ble_tp_not_ccc_changed, BT_GATT_PERM_READ | BT_GATT_PERM_WRITE) };

将代码发送的数据改为一串数字1234567890static void gatt_event_handler(ble_event_t *event) { switch (event->type) { case BLE_GATT_EVENT_READ: { // 处理读操作 break; } case BLE_GATT_EVENT_WRITE: { // 处理写操作 ble_err_t err = ble_gatt_server_send_indication(event->conn_handle, 0x1234, raw_data, sizeof(raw_data)); // 发送通知给主机 if (err != BLE_ERR_NONE) { // 发送失败，需要处理错误 break; } break; } default: break; } }

static void gatt_event_handler(ble_event_t *event) { switch (event->type) { case BLE_GATT_EVENT_READ: { // 处理读操作 break; } case BLE_GATT_EVENT_WRITE: { // 处理写操作 uint8_t raw_data[] = {...

sd_ble_gattc_discover_primary_services函数

正确答案是sd_ble_gattc_discover_primary_services()函数。该函数可以发现远程设备的所有主服务，包括私有服务。以下是一个使用sd_ble_gattc_discover_primary_services()函数发现远程设备私有服务列表的示例代码：...

注释以下代码#define TP_PRIO configMAX_PRIORITIES - 5 static void ble_tp_connected(struct bt_conn conn, u8_t err); static void ble_tp_disconnected(struct bt_conn conn, u8_t reason); static int bl_tp_send_indicate(struct bt_conn conn, const struct bt_gatt_attr attr, const void data, u16_t len); struct bt_conn ble_tp_conn; struct bt_gatt_exchange_params exchg_mtu; TaskHandle_t ble_tp_task_h; int tx_mtu_size = 20; u8_t tp_start = 0; static u8_t created_tp_task = 0; static u8_t isRegister = 0; static struct bt_conn_cb ble_tp_conn_callbacks = { .connected = ble_tp_connected, .disconnected = ble_tp_disconnected, }; static void ble_tp_tx_mtu_size(struct bt_conn conn, u8_t err, struct bt_gatt_exchange_params params) { if(!err) { tx_mtu_size = bt_gatt_get_mtu(ble_tp_conn); BT_WARN("ble tp echange mtu size success, mtu size: %d", tx_mtu_size); } else { BT_WARN("ble tp echange mtu size failure, err: %d", err); } } static void ble_tp_connected(struct bt_conn conn, u8_t err) { if(err || conn->type != BT_CONN_TYPE_LE) { return; } int tx_octets = 0x00fb; int tx_time = 0x0848; int ret = -1; BT_INFO("%s",func); ble_tp_conn = conn; . ret = bt_le_set_data_len(ble_tp_conn, tx_octets, tx_time); if(!ret) { BT_WARN("ble tp set data length success."); } else { BT_WARN("ble tp set data length failure, err: %d\n", ret); } exchg_mtu.func = ble_tp_tx_mtu_size; ret = bt_gatt_exchange_mtu(ble_tp_conn, &exchg_mtu); if (!ret) { BT_WARN("ble tp exchange mtu size pending."); } else { BT_WARN("ble tp exchange mtu size failure, err: %d", ret); } } static void ble_tp_disconnected(struct bt_conn conn, u8_t reason) { if(conn->type != BT_CONN_TYPE_LE) { return; } BT_INFO("%s",func); ble_tp_conn = NULL; } static int ble_tp_recv_rd(struct bt_conn conn, const struct bt_gatt_attr attr, void *buf, u16_t len, u16_t offset) { int size = 9; char data[9] = {0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09}; memcpy(buf, data, size); return size; }

这段代码是一个基于Bluetooth Low Energy (BLE)协议的通信协议实现。其中定义了一些函数和变量。具体解释如下： - #define TP_PRIO configMAX_PRIORITIES - 5：定义了一个优先级常量，其值为FreeRTOS系统的最大...

int32_t aciga_connect_adv_start(void) { int err; struct ble_gap_adv_params adv_param = { .conn_mode = (BLE_GAP_CONN_MODE_UND), .disc_mode = (BLE_GAP_DISC_MODE_GEN), }; if (conn_count == CONFIG_BT_MAX_CONN) { return 0; } BT_DBG("bt_mesh_is_provisioned=%d", bt_mesh_is_provisioned()); if (is_aciga_lowpower_enable()) { adv_param.itvl_min = ADV_SCAN_UNIT(lp_interval); adv_param.itvl_max = ADV_SCAN_UNIT(lp_interval); } else { adv_param.itvl_min = ADV_SCAN_UNIT(100); adv_param.itvl_max = ADV_SCAN_UNIT(100); } aciga_adv_data[ACIGA_FLAG_OFFSET] = bt_mesh_is_provisioned() ? 1 : 0; aciga_ble_gap_adv_set_data(aciga_adv_data, ACIGA_ADV_LEN); if (aciga_rsp_data[0] > 0) { aciga_ble_gap_adv_rsp_set_data(aciga_rsp_data, aciga_rsp_data[0] + 1); } err = aciga_ble_gap_adv_start(0, NULL, INT32_MAX, &adv_param); if (err) { BT_ERR("Advertising failed: err %d", err); return 0; } aciga_adv_started = true; return INT32_MAX; }

这段代码是用于启动 BLE 广播的函数。其中，通过 BLE_GAP_ADV_PARAMS 结构体设置了广播参数，包括连接模式、发现模式以及广播间隔。如果已经连接的设备数量等于最大连接数，则直接返回 0。根据当前是否已经完成了...

static void db_disc_handler(ble_db_discovery_evt_t * p_evt) { ble_cds_on_db_disc_evt(&m_cds_c, p_evt); ble_sts_on_db_disc_evt(&m_sts_c, p_evt); ble_ftms_on_db_disc_evt(&m_ftms_c, p_evt); }

这是一段 C 语言代码，其中定义了一个函数 `db_disc_handler`，它的参数是一个指向 `ble_db_discovery_evt_t` 结构体的指针 `p_evt`。在函数体内，分别调用了三个不同的函数 `ble_cds_on_db_disc_evt`、`ble_sts_on_...

我的上一个问题里面 if ((strcmp(p_gap_evt->params.connected.peer_addr.addr, DEVICE_ADDR_1) == 0) || (strcmp(p_gap_evt->params.connected.peer_addr.addr, DEVICE_ADDR_2) == 0) || (p_ble_evt->evt.gap_evt.params.connected.peer_id_addr_info.p_id_addr->addr_type == BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE)这里为什么是判断设备地址而不是设备名称或者UUID呢？

在 BLE（蓝牙低功耗）协议中，每个设备都有一个唯一的 MAC 地址作为其硬件标识符。因此，通过检查连接事件中的设备地址，可以确定正在连接的设备。而设备名称和 UUID（通用唯一标识符）是可配置的，并且可以在不同的...

ESP_BLE_ADV_FLAG_GEN_DISC

根据提供的引用内容，ESP_BLE_ADV_FLAG_GEN_DISC是广播标志之一，用于指示广播数据是通用发现模式。在ESP32中，可以使用以下代码设置广播标志为ESP_BLE_ADV_FLAG_GEN_DISC： ```c esp_ble_adv_data_t adv_data = { ...

liuyi350

粉丝: 1
资源: 5