Problem with Hello Sensor in BCM92073X_LE_KIT

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hello,

has someone any problem with the hello_sensor apps?

Sometime i've a problem with this apps. Sometime works this apps pretty well.

The Trace list:

12:15:57 - Broadcom Debug Port: BLEAPP CFA dhello_sensor_create()1.0001 18 02 16 00 00 2a 48 65 6c 6c 6f 00 00 00 00 00 00 00 00 00 00 00 02 18 00 01 2a 23 20 56 7c 05 cf 6e b4 c3 41 77 28 51 82 7e 1b 32 2a 00 26 f6 69 91 68 ee c2 be 44 4d b9 5c 3f

12:15:57 - 2d c3 8a 48 65 6c 6c 6f 20 30 0a 2d 00 1a 89 07 4a 2f 3b 7e a6 81 44 3f f9 a8

12:15:57 - f2 9b 5e 0a 18 02 4f 00 29 2a 42 72 6f 61 64 63 6f 6d 02 51 00 24 2a 31 32 34 34 00 00 00 00 02 53 00 23 2a 93 b8 63 80 5f 9f 91 71 0f 18 02 63 00 19 2a 64 02 01 06 03 19 00 02 06 09 48 65 6c 6c 6f 02 0a 04

12:15:57 -  permission check retCode = 00 0 00 00 23 20 56 7c 05 cf 6e b4 c3 41 77 28 51 82 7e 1b 02 01 05 11 07 23 20 56 7c 05 cf 6e b4 c3 41 77

12:15:57 - 28 51 82 7e 1b 06 09 48 65 6c 6c 6f

12:15:57 - blecm evt handler:

12:15:57 - 0e 04 01 08 20 00

12:15:57 - blecm evt handler: 0e 04 01 09 20 00

12:15:57 - blecm evt handler:

12:15:57 - 0e 04 01 08 20 00

12:15:57 - blecm evt handler:

12:15:57 - 0e 04 01 0a 20 0c

12:15:57 - blecm evt handler

12:15:57 - 0e 04 01 06 20 00

12:15:57 - blecm evt handler:

12:15:57 - 0e 04 01 0a 20 00

12:15:57   Trace Decoding Error - Could not find line number 314

12:15:57   UUID  : 2800

12:15:57   Attribute bytes

12:15:57   Handle: 0062

12:15:57   Perm  : 0002

12:15:57   Len, Max Len : 0005, 0005

12:15:57   UUID  : 2803

12:15:57   Attribute bytes

12:15:57   Handle: 0063

12:15:57   Perm  : 0002

12:15:57   Len, Max Len : 0001, 0001

12:15:57   UUID  : 2A19

12:15:57   Attribute bytes

12:15:57   Gatt DB Dump complete

12:15:57   bd_addr[5:2] = 20 73 7A 14

12:15:57   bd_addr[1:0] = 9B92 00

12:15:57   GPIO 0001 (11)

12:15:57   GPIO 0000 (104)

12:15:57   GPIO 0014 (1003)

12:15:57   GPIO 0015 (20)

12:15:57   GPIO 0028 (2001)

12:15:57   Interrupt mask[0,1]:0001 0000

12:15:57   Interrupt mask[2]:0000

12:15:57   GPIO_WP:OFF= 00

12:15:57   GPIOBTN1:OFF=1,INT:0

12:15:57   GPIO_LED:OFF=1

12:15:57   GPIOBAT

12:15:57   GPIO_BUZ:OFF=0

12:15:57   Battery level: 0/100

12:15:57   Fine Timer(0 ms, 0/sec)

12:15:59 - *#04FF1EF7009201030000073A2A500000000007522A500001000007021F0100hello_sensor_timeout:0hello_sensor_timeout:1

12:16:01 - hello_sensor_timeout:hello_sensor_timeout:3

12:16:05 - hello_sensor_timeout:hello_sensor_timeouthello_sensor_timeout:6hello_sensor_timeout:7

12:16:06 - hello_sensor_timeout:8

12:16:09 - hello_sensor_timeout:hello_sensor_timeout:10hello_sensor_timeout:11

12:16:11 - hello_sensor_timeout:1hello_sensor_timeout:13

12:16:12 - hello_sensor_timeout:14

12:16:13 - hello_sensor_timeout:15

12:16:15 - hello_sensor_timeout:hello_sensor_timeout:17

12:16:16 - hello_sensor_timeout:18

12:16:17 - hello_sensor_timeout:19

12:16:21 - hello_sensor_timeout:20hello_sensor_timeout:hello_sensor_timeouhello_sensor_timeout:23

12:16:22 - hello_sensor_timeout:24

12:16:25 - hello_sensor_timeout:25hello_sensor_timeout:hello_sensor_timeout:27

12:16:26 - hello_sensor_timeout:28

12:16:27 - hello_sensor_timeout:29

12:16:27 - ecm evt handler:

12:16:27 - 0e 04 01 06 20 00

after it shows "ecm evt handler: ", then the BCM92073X_LE_KIT is not working well ("read" and "write" function are not working anymore).


0 Likes
1 Solution
VictorZ_46
Employee
Employee
5 comments on blog 25 sign-ins 250 likes received

The trace shows startup and does not show any connection events.  For the first 30 seconds after startup application performs high duty advertisements sending advertisements every 32 slots (20 msec).  After 30 seconds (I believe this is where you see the trace) advertisements are changed to low duty cycle (interval 1024 slots = 640 msec).  Client still can connect, but to reliably see the advertisements it needs to listen (scan) much more.

The advertisement parameters are configured in hello_sensor_cfg.  Please note that decreasing advertisement interval or increasing duration that device performs high duty advertisements directly affects the battery life of your device.

View solution in original post

3 Replies
VictorZ_46
Employee
Employee
5 comments on blog 25 sign-ins 250 likes received

The trace shows startup and does not show any connection events.  For the first 30 seconds after startup application performs high duty advertisements sending advertisements every 32 slots (20 msec).  After 30 seconds (I believe this is where you see the trace) advertisements are changed to low duty cycle (interval 1024 slots = 640 msec).  Client still can connect, but to reliably see the advertisements it needs to listen (scan) much more.

The advertisement parameters are configured in hello_sensor_cfg.  Please note that decreasing advertisement interval or increasing duration that device performs high duty advertisements directly affects the battery life of your device.

Anonymous
Not applicable

Ok, maybe that's the problem, why i sometimes can't connect to the BCM92073X_LE_KIT.

Is that right, that my client is the BCM_92073X_LE_KIT? or maybe the Handphone?

How is it actually, sometimes i can't send any data to the client?

I press the "Write" button on the LE Hello Client, but the data doesn't come to the Client (BCM92073X_LE_KIT just ignore it).   

0 Likes

I am sorry, I do not understand the question.  How we test this application is we load hello_sensor on one 20737 board and hello_client on another 20737 board.  Connect from iOS LightBlue to the board with hello_client.app.  Push the and hold for 6 seconds application button on the hello_client.  That should establish connection to hello_sensor.  Now if you momentarily push button on hello_client or hello_sensor the message will go to iOS.

0 Likes