This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Disconnect on S130 v2, HCI Error 0x2A

Hello,

I've an issue with several smart-phone models when I use the softdevice S130 v2

I did tests with PCA10028 and the example "ble_app_bps".

I used softdevice S110, S130 V1, S130 V2.0.0, S130 V2.0.1

This work well with S110 and S130 V1, but this fails with S120 V2.x

When I connect with the smartphone inmediately the PCA10028 report a disconnect reason = 0x2A. This happens with some smarthphone, for example, Samsung Galaxy J1 ACE.

I need use the version S130 because our device has to connect to a smartphone and other peripherals simultaneously.

Could you help me? Do you have any idea about this issue?

Thanks & regards

S130 Trace (FAIL): s130_v2_fail.pcapng

S110 Trace (OK): s110_ok.pcapng

Full trace: trace_1.pcapng

Full Trace s110: trace_s110.pcapng

Parents
  • Hi Gabi,

    Thanks for the trace.

    I can clearly see why this happens. At packet #103 and #104 the phone sent LL_VERSION_IND and we haven't answered yet. The phone should wait but it didn't and send LL_FEATURE_REQ. This is not allowed. There should be only one LL command packets at a time. When we have 2 request at the same time we will disconnect and throw out 0x2A because link layer protocol is violated

    You can see that we advertise after that. There are 2 -3 connection request attempt failed after that, but it's not related to the software, simply the connect request was not received by the chip. This could be due to interference or bad RF circuit on the board.

    Which board are you testing with ?

Reply
  • Hi Gabi,

    Thanks for the trace.

    I can clearly see why this happens. At packet #103 and #104 the phone sent LL_VERSION_IND and we haven't answered yet. The phone should wait but it didn't and send LL_FEATURE_REQ. This is not allowed. There should be only one LL command packets at a time. When we have 2 request at the same time we will disconnect and throw out 0x2A because link layer protocol is violated

    You can see that we advertise after that. There are 2 -3 connection request attempt failed after that, but it's not related to the software, simply the connect request was not received by the chip. This could be due to interference or bad RF circuit on the board.

    Which board are you testing with ?

Children
No Data
Related