Problem Description:
Simple Peripheral application crash and stopped advertising after an unsuccessful connection

Steps to reproduce:
1.Flash the Simple_Peripheral hex and open TeraTerm terminal for it
2.Flash the hci_test hex to the Master device
3.Open the HCI Tester and run the enclosed script that will perform connection with invalid parameters (need change the peer address in the script. Use the address from the terminal RP Addr. Also check the peer address type is set to random in the create connection command). The HCI Tester script (LL_Connection_Master.txt) will stop after the master initialization. Now manually run the connection command (line #62) - mouse right button click when the cursor on this line and choose "Run Selected".

Test variables:
scanInt = TIME_2_5MS_IN_625US
scanWindow = TIME_2_5MS_IN_625US
connInt range: 0x0006 to 0x0C80 Time = x 1.25ms
connectInt = TIME_625MS_IN_1_25MS
Slave latency range: 0x0000 to 0x01F3
connectLatency = 0
Supervision timeout Range: 0x000A to 0x0C80 Time = N * 10 ms
connectTimeout = TIME_10S_IN_10MS

Problem: the Simple Peripheral stopped advertising and the terminal shows *ERROR* >>DEFAULT SPINLOCK! . Also the counter Num Conns: 1 (invalid connection counted as established)

Note:
Issue also reproduced with public address.
For public address we noticed the device gets the SPINLOCK only on the second connection attempt (and not on the first like in RPA). In the first attempt the "Num Conns" is wrongly increased by 1.