Making MQTT Publisher example work on Raspberry Pi 4

RE: Making MQTT Publisher example work on Raspberry Pi 4

Jørgen Holmefjord — Tue, 20 Jul 2021 13:13:36 GMT

Hi, sorry for not getting back to you on this one. Are you still needing help with resolving this issue?

I see that your application log shows "Fatal Error". Can you try building the application in debug configuration (with DEBUG and DEBUG_NRF preprocessor symbols set)? That should reveal at which file/line and error code the application crashes.

RE: Making MQTT Publisher example work on Raspberry Pi 4

AguirreGENROD — Thu, 06 May 2021 14:52:04 GMT

Hi! I wanted to give you an update.

Apparently there was an error during BLE connections that closes connections after 40s, I found a solution in this post. This could explain the behaviour found in past attached logs that showed a timeout disconnection.

I now created a few more captures with that problem solved. The device still can´t connect to MQTT, broker logs are still the same:

2021-05-06T15:30:12: New connection from 2001:db8::70:dfff:fe39:d5e8:49153 on port 1883.
2021-05-06T15:30:12: New client connected from 2001:db8::70:dfff:fe39:d5e8:49153 as nrfPublisher (p1, c1, k60).
2021-05-06T15:30:12: No will message specified.
2021-05-06T15:30:12: Sending CONNACK to nrfPublisher (0, 0)
2021-05-06T15:31:44: Client nrfPublisher has exceeded timeout, disconnecting.

But the device doesn´t disconnect after pressing Button 1 one time, it waits for the CONNACK packet that the RPi never sends. When pressing the button a second time, it crashes.

From the RPi side I am now also capturing from btmon, because it gives a few more low-level details. I noticed tshark captures are the only ones showing the CONNACK packet, with a few retransmission attempts.

I'll attach a few new captures so you can take a look and tell me if you think about anything with this new information.

Thanks in advance, will be waiting for your response.

devzone.nordicsemi.com/.../RPi4B_5F00_Buster_5F00_Publisher_5F00_BMDLog.log

devzone.nordicsemi.com/.../RPi4B_5F00_Buster_5F00_Publisher_5F00_Btmon.pcap

devzone.nordicsemi.com/.../RPi4B_5F00_Buster_5F00_Publisher_5F00_Sniffer.pcapng

devzone.nordicsemi.com/.../RPi4B_5F00_Buster_5F00_Publisher_5F00_Tshark.pcap

RE: Making MQTT Publisher example work on Raspberry Pi 4

AguirreGENROD — Mon, 26 Apr 2021 19:00:45 GMT

Hi,

when logging I got the following disconnect reason:

00> <debug> nrf_sdh_ble: BLE event: 0x11.
00> 
00> <debug> nrf_sdh_ble: BLE GAP DISCONNECTED event reason: 0x8.

For what I read, this is a timeout corresponding to BLE_HCI_CONNECTION_TIMEOUT

RE: Making MQTT Publisher example work on Raspberry Pi 4

Jørgen Holmefjord — Fri, 23 Apr 2021 16:13:01 GMT

It looks like the softdevice reports a BLE_GAP_EVT_DISCONNECTED event (0x11) at the end of the log:

<debug> nrf_sdh_ble: BLE event: 0x11.

Can you log and post the corresponding disconnect reason from ble_gap_evt_disconnected_t?

RE: Making MQTT Publisher example work on Raspberry Pi 4

AguirreGENROD — Thu, 15 Apr 2021 13:01:01 GMT

Hi,

I tried the log configuration, I'll attach the full log I got, but the last lines are the following:

00> <debug> 6lowpan: [CID 0x0040]: >> BLE_IPSP_EVT_CHANNEL_DATA_TX_COMPLETE
00> 
00> <debug> 6lowpan: [CID 0x0040]: Transmission complete.
00> 
00> <debug> 6lowpan: << ipsp_evt_handler
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x76.
00> 
00> <debug> 6lowpan: >> ipsp_evt_handler
00> 
00> <debug> 6lowpan: [CID 0x0040]: >> BLE_IPSP_EVT_CHANNEL_DATA_RX
00> 
00> <debug> 6lowpan:  7B 00 3A 20 01 0D B8 00|{.: ....
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 00|........
00> 
00> <debug> 6lowpan:  00 00 01 FE 80 00 00 00|........
00> 
00> <debug> 6lowpan:  00 00 00 00 70 DF FF FE|....p...
00> 
00> <debug> 6lowpan:  39 D5 E8 88 00 A9 24 C0|9.....$.
00> 
00> <debug> 6lowpan:  00 00 00 20 01 0D B8 00|... ....
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 00|........
00> 
00> <debug> 6lowpan:  00 00 01               |...     
00> 
00> <debug> 6lowpan: Processing received data.
00> 
00> <debug> 6lowpan: Decompressed packet:
00> 
00> <debug> 6lowpan:  60 00 00 00 00 18 3A FF|`.....:.
00> 
00> <debug> 6lowpan:  20 01 0D B8 00 00 00 00| .......
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 01|........
00> 
00> <debug> 6lowpan:  FE 80 00 00 00 00 00 00|........
00> 
00> <debug> 6lowpan:  00 70 DF FF FE 39 D5 E8|.p...9..
00> 
00> <debug> 6lowpan:  88 00 A9 24 C0 00 00 00|...$....
00> 
00> <debug> 6lowpan:  20 01 0D B8 00 00 00 00| .......
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 01|........
00> 
00> <debug> 6lowpan: << ipsp_evt_handler
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x75.
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x74.
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x74.
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x74.
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x74.
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x73.
00> 
00> <debug> 6lowpan: >> ipsp_evt_handler
00> 
00> <debug> 6lowpan: [CID 0x0040]: >> BLE_IPSP_EVT_CHANNEL_DISCONNECTED
00> 
00> <debug> 6lowpan: Channel disconnection.
00> 
00> <debug> 6lowpan: Removed IPSP interface.
00> 
00> <debug> 6lowpan: >> ble_6lowpan_interface_send
00> 
00> <debug> 6lowpan: Uncompressed packet:
00> 
00> <debug> 6lowpan:  60 00 00 00 00 14 06 FF|`.......
00> 
00> <debug> 6lowpan:  20 01 0D B8 00 00 00 00| .......
00> 
00> <debug> 6lowpan:  00 70 DF FF FE 39 D5 E8|.p...9..
00> 
00> <debug> 6lowpan:  20 01 0D B8 00 00 00 00| .......
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 01|........
00> 
00> <debug> 6lowpan:  C0 01 07 5B 00 00 19 8A|...[....
00> 
00> <debug> 6lowpan:  29 4D E4 D9 50 14 0E 00|)M..P...
00> 
00> <debug> 6lowpan:  A2 BD 00 00            |....    
00> 
00> <debug> 6lowpan: Successfully compressed packet.
00> 
00> <debug> 6lowpan: Compressed packet:
00> 
00> <debug> 6lowpan:  7B 00 06 20 01 0D B8 00|{.. ....
00> 
00> <debug> 6lowpan:  00 00 00 00 70 DF FF FE|....p...
00> 
00> <debug> 6lowpan:  39 D5 E8 20 01 0D B8 00|9.. ....
00> 
00> <debug> 6lowpan:  00 00 00 00 00 00 00 00|........
00> 
00> <debug> 6lowpan:  00 00 01 C0 01 07 5B 00|......[.
00> 
00> <debug> 6lowpan:  00 19 8A 29 4D E4 D9 50|...)M..P
00> 
00> <debug> 6lowpan:  14 0E 00 A2 BD 00 00   |....... 
00> 
00> <debug> 6lowpan: Cannot send the packet, error = 0x00008405
00> 
00> <debug> 6lowpan: [CID 0x0040]: Transmission complete.
00> 
00> <debug> 6lowpan: << ble_6lowpan_interface_send
00> 
00> <info> app: >> MQTT_EVT_CONNACK, result 0000C943
00> 
00> <info> app: IPv6 Interface Down.
00> 
00> <debug> 6lowpan: << ipsp_evt_handler
00> 
00> <debug> nrf_sdh_ble: BLE event: 0x11.
00> 
00> <info> app: Physical layer: disconnected.
00> 
00> <info> app: Physical layer in connectable mode.

It identifies an error that I don´t see defined in the code: 0x00008405 (defined BLE_IPSP errors in sdk_errors.h go from 0x8400 to 0x8403) but it does so after a few messages telling the channel is disconnecting, so it may be because of that. I don´t understand much about what could've happened before, but here goes the full log.

Will be waiting for your response, thanks.

devzone.nordicsemi.com/.../BMDLog.log

RE: Making MQTT Publisher example work on Raspberry Pi 4

Jørgen Holmefjord — Wed, 14 Apr 2021 15:04:18 GMT

Try with the following:

#ifndef NRF_LOG_DEFAULT_LEVEL
#define NRF_LOG_DEFAULT_LEVEL 4
#endif

// <e> IOT_BLE_6LOWPAN_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef IOT_BLE_6LOWPAN_CONFIG_LOG_ENABLED
#define IOT_BLE_6LOWPAN_CONFIG_LOG_ENABLED 1
#endif
// <o> IOT_BLE_6LOWPAN_CONFIG_LOG_LEVEL - Default Severity level

// <0=> Off
// <1=> Error
// <2=> Warning
// <3=> Info
// <4=> Debug

#ifndef IOT_BLE_6LOWPAN_CONFIG_LOG_LEVEL
#define IOT_BLE_6LOWPAN_CONFIG_LOG_LEVEL 4
#endif

// <e> MQTT_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef MQTT_CONFIG_LOG_ENABLED
#define MQTT_CONFIG_LOG_ENABLED 1
#endif
// <o> MQTT_CONFIG_LOG_LEVEL - Default Severity level

// <0=> Off
// <1=> Error
// <2=> Warning
// <3=> Info
// <4=> Debug

#ifndef MQTT_CONFIG_LOG_LEVEL
#define MQTT_CONFIG_LOG_LEVEL 4
#endif

RE: Making MQTT Publisher example work on Raspberry Pi 4

AguirreGENROD — Tue, 13 Apr 2021 18:18:50 GMT

Hi,

Which log level would you change?

Looking into sdk_config.h I tried to enable more logs like with IOT_BLE_6LOWPAN_CONFIG_LOG_ENABLED in 1, but when compiling I don´t see any change on the logs viewed.

Respecting BLE Link, the raspberry loses interface bt0, I understand that means the link went down. Also the respective LED in the board starts blinking again

RE: Making MQTT Publisher example work on Raspberry Pi 4

Jørgen Holmefjord — Mon, 12 Apr 2021 15:59:22 GMT

Hi,

Have you tried increasing the log level for the example to DEBUG, to see if you can get more information about why the IPv6 interface goes down?

It does not look like the BLE link is disconnected on the sniffer trace.

Best regards,
Jørgen