Bad value in Number Of Completed Packets over HCI

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
星期一,2017-04-17 00:07
#1
donpedro
Offline
Last seen:3 years 7 months ago
加入:2017-04-10 22:28
Bad value in Number Of Completed Packets over HCI

Hello Dialog,

While investigating the bug in:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl...

I found another bug.

If i ignore the incorrect buffer size returned (from hci_le_read_buffer_size), and just assume 251, it actually works (for TX, not RX). The RX is still fragmented in sizes of 27.

However, the number of completed packets are not reported correctly.

I have attached a trace that shows the problem.

Notice that for every ACL packet sent the chipset reports 2 completed packets, which of course is incorrect as it should be 1.

This makes the upper layer stack think more packets are sent than there is causing a critical failure.

Thanks,

/pedro

Device:
DA1468x
Mon, 2017-04-17 00:08
donpedro
Offline
Last seen:3 years 7 months ago
加入:2017-04-10 22:28
Here is the trace.

Here is the trace.

Attachment:
Package icondialog_14581_bad_completed_packets.zip
Mon, 2017-04-17 11:43
TN_Dialog
Offline
Last seen:5天5小时前
Staff
加入:2013-12-05 15:49
Hi Donpedro,

Hi Donpedro,

Thank you for posting this question and providing detailed description.

I will look into this and I will get back to you as sson as I have an update for you.

Regards

TN_Dialog