H3863 测试 SLE 延时异常

Viewed 154

一、描述你遇到的问题

测试 H3863 开发板,数据传输时延问题。
A H3863 作为 server 板子, 数据接收函数内,拉高 GPIO3 引脚;
B H3863 作为 client 板子,client 发送函数内,拉高 GPIO3 引脚;
当 B -> A 发送数据时,正常应该 B 先拉高引脚,然后 A 接收到数据拉高引脚,但是实际情况为 A 作为接收端,居然比 B 发送端引脚拉高时间早。

目前基本可以定位为封装的库内数据处理存在较大时延差异。

二、你具体做的所有步骤结果截图

client 代码修改

这个函数随后被注册到被封装的库


server 代码修改

这个函数同样被注册到封装库内

三、当前开发板状态全景照片

client

四、开发板串口所有日志

server:
boot.
Flash Init Fail! ret = 0x80001341
verify_public_rootkey secure verify disable!
verify_params_key_area secure verify disable!
verify_params_area_info secure verify disable!
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
SSB Uart Init Succ!
SSB Flash Init Succ!
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
Flashboot Uart Init Succ!
Flashboot Malloc Init Succ!
Flash Init Succ!
No need to fix SR!
flashboot version : 1.10.101
[UPG] upgrade init OK!
No need to upgrade...
flash_encrypt disable.
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
APP|Debug uart init succ.
[UPG] upgrade init OK!
APP|init_dev_addr, mac_addr:0xb1,0x 0,0x73,0x2d,0x**,0x**,
xo_trim_temp_comp val:0 0
APP|AT uart init succ.
los_at_plt_cmd_register EXCUTE
APP|WARNING: main_initialise::thread[11] func is null
cpu 0 entering scheduler
APP|btc open
[RADAR_LOG] alg ctrl read from nv [1][2][0][0][1][1][20]
device_main_init: 0!
===hal_initialize_phy===225===
device_module_init:: succ!
cali_set_cali_mask:old[0x0] -> new[0x1fa2]

fe_rf_initialize
cali_offline_cali_entry enter
cali_set_cali_done_flag:old[0x0] -> new[0x1]

rf cali OK. time cost:22, ret:0
[ACore] sle enable cbk in, result:0
sle enable
[sle uart server] sle uart add service in
[sle uart server] sle uart add service, server_id:1, service_handle:1, property_handle:2
[sle uart server] start service cbk callback server_id:1, handle:1, status:0
[sle uart server] sle uart add service out
[sle uart server] sle_uart_local addr: 0x01 0x02 0x03 0x04 0x05 0x06
[ACore] sle set announce param, handle:1, mode:3, min_interval:c8, max_interval:c8, tx_power: 18
[ACore] sle set announce param, own addr:0x01::::05:06
[ACore] sle set announce param, peer addr:0x00:
:::00:00
[sle uart server] data.announce_data_len = 6
[sle uart server] data.announce_data: 0x01 0x02 0x01 0x02 0x02 0x00
[sle uart server] local_name_len = 15
[sle uart server] local_name: 0x73 0x6c 0x65 0x5f 0x75 0x61 0x72 0x74 0x5f 0x73 0x65 0x72 0x76 0x65 0x72
[sle uart server] data.seek_rsp_data_len = 20
[sle uart server] data.seek_rsp_data: 0x0c 0x02 0x0a 0x10 0x0b 0x73 0x6c 0x65 0x5f 0x75 0x61 0x72 0x74 0x5f 0x73 0x65 0x72 0x76 0x65 0x72
[sle uart server] set announce data success.
[ACore] sle start announce in, adv_id:1
[ACore] sle adv cbk in, event:0 status:0
[ACore] sle adv cbk in, event:1 status:0
[ACore] sle adv cbk in, event:2 status:0
[ACore] sle adv cbk in, event:3 status:0
[sle uart server] sle announce enable callback id:01, state:0
[sle uart server] init ok
xo update temp:3,diff:0,xo:0x3083c
[Connected]
addr:ee::::8d:5c, handle:00
[ACore] sle adv cbk in, event:7 status:0
[sle uart server] connect state changed callback conn_id:0x00, conn_state:0x1, pair_state:0x1, disc_reason:0x0
[sle uart server] connect state changed callback addr:ee:
:::8d:a13edc
[sle uart server] sle announce terminal callback id:01
[sle uart server] pair complete conn_id:00, status:0
[sle uart server] pair complete addr:ee:::**:8d:a13edc
[sle uart server] ssaps ssaps_mtu_changed_cbk callback server_id:0, conn_id:0, mtu_size:208, status:0

client:
boot.
Flash Init Fail! ret = 0x80001341
verify_public_rootkey secure verify disable!
verify_params_key_area secure verify disable!
verify_params_area_info secure verify disable!
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
SSB Uart Init Succ!
SSB Flash Init Succ!
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
Flashboot Uart Init Succ!
Flashboot Malloc Init Succ!
Flash Init Succ!
No need to fix SR!
flashboot version : 1.10.101
[UPG] upgrade init OK!
No need to upgrade...
flash_encrypt disable.
verify_image_key_area secure verify disable!
verify_image_code_info secure verify disable!
APP|Debug uart init succ.
[UPG] upgrade init OK!
APP|init_dev_addr, mac_addr:0x35,0x 0,0x73,0xba,0x**,0x**,
xo_trim_temp_comp val:0 0
APP|AT uart init succ.
los_at_plt_cmd_register EXCUTE
APP|WARNING: main_initialise::thread[11] func is null
cpu 0 entering scheduler
APP|btc open
[RADAR_LOG] alg ctrl read from nv [1][2][0][0][1][1][20]
device_main_init: 0!
===hal_initialize_phy===225===
device_module_init:: succ!
cali_set_cali_mask:old[0x0] -> new[0x1fa2]

fe_rf_initialize
cali_offline_cali_entry enter
cali_set_cali_done_flag:old[0x0] -> new[0x1]

rf cali OK. time cost:22, ret:0
xo update temp:3,diff:0,xo:0x3083c
[SLE Client] try enable.
[ACore] sle enable cbk in, result:0
sle enable: 0.
sle enable
[SLE Client] try enable.
[SLE Client] sle enbale fail !
[adv_report] event_type: 0x03, addr_type: 0x0000, addr: 01::::05:06
[adv_report] data length: 6, data: 0x01 0x02 0x01 0x02 0x02 0x00
[adv_report] event_type: 0x0b, addr_type: 0x0000, addr: 01:
:::05:06
[adv_report] data length: 20, data: 0x0c 0x02 0x0a 0x10 0x0b 0x73
[sle uart client] sle uart scan data :
[sle uart client] sle uart scan data : 

sle_uart_server
[Connected]
addr:01:::**:05:06, handle:00
[sle uart client] conn state changed disc_reason:0x0
[sle uart client] SLE_ACB_STATE_CONNECTED
[sle uart client] sle_low

2 Answers

当前开发板照片无法上传,可能太大了,可以给其他方式上传,这个论坛,已上传手机拍摄的照片,就无法连接。

如果确定是封装库内的问题,就不用纠结了,等待海思更新吧,我们也没有源码

那 H3863 的空口时延可以达到多少?这个有参数吗?我们使用工程测试,一直测试都非常不对劲。

errcode_t ssaps_register_callbacks(ssaps_callbacks_t *func);这个函数可以麻烦帮忙确定下,是海思封装库内的函数吗?

空口硬件是12M,实际使用只能使用到4M。
是,所有SLE底层都被海思封装了