[jira] [Commented] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet
[ https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433549#comment-15433549 ] Sterling Hughes commented on MYNEWT-286: where are we on this bug? > nRF51 crashes when receiving large(ish) ACL packet > -- > > Key: MYNEWT-286 > URL: https://issues.apache.org/jira/browse/MYNEWT-286 > Project: Mynewt > Issue Type: Bug > Components: Nimble > Environment: nRF51 USB dongle or devkit >Reporter: Johan Hedberg >Assignee: William San Filippo > > The default L2CAP MTUs of ATT and legacy SMP fixed channels is 23. This works > fine. As soon as LE Secure Connections SMP is attempted (MTU of 65) and the > public key sent the controller stops responding (gdb doesn't work. needs a > hard power cycle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet
[ https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271342#comment-15271342 ] Johan Hedberg commented on MYNEWT-286: -- A little update on this: I can't seem to reproduce the issue on the Arduino 101 (which has the 16 kB RAM variant of the nRF51), however on the nRF51 USB dongle (which has the 32 kB variant) this happens every time. I didn't have a chance to double-check the situation with the devkit yet however. > nRF51 crashes when receiving large(ish) ACL packet > -- > > Key: MYNEWT-286 > URL: https://issues.apache.org/jira/browse/MYNEWT-286 > Project: Mynewt > Issue Type: Bug > Components: Nimble > Environment: nRF51 USB dongle or devkit >Reporter: Johan Hedberg >Assignee: William San Filippo > > The default L2CAP MTUs of ATT and legacy SMP fixed channels is 23. This works > fine. As soon as LE Secure Connections SMP is attempted (MTU of 65) and the > public key sent the controller stops responding (gdb doesn't work. needs a > hard power cycle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet
[
https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254676#comment-15254676
]
Christopher Collins commented on MYNEWT-286:
Thanks, Johan. I haven't had any luck in reproducing this crash. Details of
my setup are below. Could you please point me the specific nimble commit which
you were using when you produced this crash?
*Test setup 1*
* Master: bmd300 running blehci app, controlled by bluetoothctl
* Slave: nrf52pdk preview running blehci app, controlled by btmgmt
* Both boards running code built from commit
4d0a38707bdeeb2061b3089d627fc2cee13f1f6c
*Test setup 2*
* Master: nrf52pdk running blehci app, controlled by bluetoothctl
* Slave: nrf51dk preview running blehci app, controlled by btmgmt
* Both boards running code built from commit
4d0a38707bdeeb2061b3089d627fc2cee13f1f6c
*btmon log from Test setup 1 (hci1=master; hci0=slave)*
{noformat}
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7
[hci1] 1771.171413
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
> HCI Event: Command Complete (0x0e) plen 4
> [hci1] 1771.174704
LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2
[hci1] 1771.174736
Scanning: Enabled (0x01)
Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4
> [hci1] 1771.178689
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 18
> [hci1] 1771.480724
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: 0A:0B:0C:0D:0E:0F (OUI 0A-0B-0C)
Data length: 6
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
TX power: 0 dBm
RSSI: -52 dBm (0xcc)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2
[hci1] 1771.480907
Scanning: Disabled (0x00)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4
> [hci1] 1771.484717
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
< HCI Command: LE Create Connection (0x08|0x000d) plen 25
[hci1] 1771.484746
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Filter policy: White list is not used (0x00)
Peer address type: Public (0x00)
Peer address: 0A:0B:0C:0D:0E:0F (OUI 0A-0B-0C)
Own address type: Public (0x00)
Min connection interval: 50.00 msec (0x0028)
Max connection interval: 70.00 msec (0x0038)
Connection latency: 0x
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x)
Max connection length: 0.000 msec (0x)
> HCI Event: Command Status (0x0f) plen 4
> [hci1] 1771.490698
LE Create Connection (0x08|0x000d) ncmd 1
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 19
> [hci1] 1772.765700
LE Connection Complete (0x01)
Status: Success (0x00)
Handle: 1
Role: Master (0x00)
Peer address type: Public (0x00)
Peer address: 0A:0B:0C:0D:0E:0F (OUI 0A-0B-0C)
Connection interval: 70.00 msec (0x0038)
Connection latency: 0.00 msec (0x)
Supervision timeout: 420 msec (0x002a)
Master clock accuracy: 0x04
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2
[hci1] 1772.765816
Handle: 1
@ Device Connected: 0A:0B:0C:0D:0E:0F (1) flags 0x
02 01 06 02 0a 00..
> HCI Event: LE Meta Event (0x3e) plen 19
>
[jira] [Commented] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet
[ https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251286#comment-15251286 ] William San Filippo commented on MYNEWT-286: Johan: Yes, the value of 260 is "correct" for the nrf51. The ACL packet length should not be related to the 27 byte limit to which you are referring (in theory). Currently, the controller requires maximum length PDU's to be allocated for reception so the mbufs created are quite large. This will probably change in the future, but should not be an issue here. BTW, we have a setup and while we dont see exactly what you are seeing we do see some issues which we are investigating. Should have an answer soon. > nRF51 crashes when receiving large(ish) ACL packet > -- > > Key: MYNEWT-286 > URL: https://issues.apache.org/jira/browse/MYNEWT-286 > Project: Mynewt > Issue Type: Bug > Components: Nimble > Environment: nRF51 USB dongle or devkit >Reporter: Johan Hedberg >Assignee: William San Filippo > > The default L2CAP MTUs of ATT and legacy SMP fixed channels is 23. This works > fine. As soon as LE Secure Connections SMP is attempted (MTU of 65) and the > public key sent the controller stops responding (gdb doesn't work. needs a > hard power cycle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet
[ https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249972#comment-15249972 ] Johan Hedberg commented on MYNEWT-286: -- I wonder if this is related to the fact that nimble currently returns 260 as the max ACL packet length in the response to the "LE Read Buffer Size" HCI command? Is that the correct value for the nRF51? Should it perhaps instead be 27? > nRF51 crashes when receiving large(ish) ACL packet > -- > > Key: MYNEWT-286 > URL: https://issues.apache.org/jira/browse/MYNEWT-286 > Project: Mynewt > Issue Type: Bug > Components: Nimble > Environment: nRF51 USB dongle or devkit >Reporter: Johan Hedberg > > The default L2CAP MTUs of ATT and legacy SMP fixed channels is 23. This works > fine. As soon as LE Secure Connections SMP is attempted (MTU of 65) and the > public key sent the controller stops responding (gdb doesn't work. needs a > hard power cycle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
