error 34 (0x22) GATT CONN LMP TIMEOUT in nrf connect app

Hello,

I'm using a custom board and i actually have a problem that I never saw before :error 34 (0x22) GATT CONN LMP TIMEOUT.

I have send frames : I did my own custom board with an nrf52805

I'm trying to put a module with different frames, and when I do that my app is disconnecting 5seconds after. I

didn't have a problem for now with a com with a driver 485 but now that I'm putting it, I can't receive any info because I'm getting the error: error 34 (0x22) GATT CONN LMP TIMEOUT. For info, I used the BLE_ app_uart example and changed so info to have the functionality to my custom board.

<info> app_timer: RTC: initialized.
<info> app: Debug logging for UART over RTT started.
<info> app: Connected
<info> app: Data len is set to 0xF4(244)
<info> app: Disconnected

As you can see there is a disconnected device

I'm going to show you what I have on the app NRF connect:

Thank you

Parents

0 user111471 over 4 years ago

Hello , I did what you told me but actually I don't have the hardware interface even if I have installed everything correctly. Could you tell me why? Thank you
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user2111 over 4 years ago in reply to user111471

Check out:
https://infocenter.nordicsemi.com/topic/ug_sniffer_ble/UG/sniffer_ble/troubleshooting.html

Also make sure you have installed the latest nRF Command line tools.

Best regards,
Kenneth
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user2111

Yes I have the latest version of nrf command line tools and made the tuto correctly. Wihtout the sniffer log you can't work with me?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user111471

Now, icant connect my eval board to the computer!! i trued to inject an hex file and now I ca't see the device with USB how can I do??
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user111471

Hello, i arrange the problem with my card no i can develop by using the dev kit, the sniffer log is not working and I can't make it function I don't know why.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 user111471 over 4 years ago in reply to user111471

Hello, i arrange the problem with my card no i can develop by using the dev kit, the sniffer log is not working and I can't make it function I don't know why.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 user2111 over 4 years ago in reply to user111471

Do you have a picture of your hardware setup and a description on how you programmed the board?

Kenneth
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user2111

yes
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user111471
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user111471

I used at first the ble app uart example that I just modified to adapt to the custom board, everything was working fine since this error...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user111471 over 4 years ago in reply to user111471

I tested with another custom board. i don't have the error ... I'm going to give you the errors that I have now.

chen im putting the device for the frames I have this : c

<info> app_timer: RTC: initialized.
<error> app: ERROR 4 [NRF_ERROR_NO_MEM] at D:\nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_uart\main.c:606
PC at: 0x0001A63F
<error> app: End of error report
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel