sdk-6.1: stackoverflow due to reduced stack size for BLE configuration

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

cross mob
AxLi_1746341
Level 7
Level 7
10 comments on KBA 5 comments on KBA First comment on KBA

I notice on sdk-6.1, a printf("#"); in ble scan result callback can cause hang.

Remove the printf then it works.

It's pretty common to do such printf for debug purpose.

On sdk-6.0.1:

00:00:02.624000 GKI_create_task func=0x80182d5  id=1  name=BTU  stack=0x0  stackSize=6144

00:00:02.632000 GKI_create_task func=0x80197f5  id=0  name=HCISU  stack=0x0  stackSize=4096

On sdk-6.1:

00:00:01.066000 GKI_create_task func=0x8017d1d  id=1  name=BTU  stack=0x0  stackSize=4096

00:00:01.074000 GKI_create_task func=0x801954d  id=0  name=HCISU  stack=0x0  stackSize=3072

I believe other users may find the existing application fails due to this stack size change.

Would you consider change the stack size back?

Or alternatively provide user an argument to override default settings.

0 Likes
1 Solution
Anonymous
Not applicable

Thanks for the feedback. I will forward your suggestions to the design team.

View solution in original post

0 Likes
3 Replies
Anonymous
Not applicable

Which device are you testing this on?

I tested with the hps_client_keypad example, added a printf("scan callback") within the callback and faced no issues with a 43438.

0 Likes

yssu

How do you make sure the reduced stack size in sdk-6.1 has no impact on user's existing application?

I believe you cannot guarantee that, that is why I suggest to allow user to set the stack size.

Especially, sometimes people needs bigger stack size in debug build.

0 Likes
Anonymous
Not applicable

Thanks for the feedback. I will forward your suggestions to the design team.

0 Likes