How to get the MQTT publisher example working on the nrf7002DK? I also want to test the TLS after that.

[Arjun Kariat]

Hi,

I am trying to get the MQTT publisher example working on my nrf7002DK board. For this, i have done the following things

- SDK version: 2.6.1

- Board selected: nrf7002dk_nrf5340_cpuapp

- Include the prj.conf, overlay-nrf700x.conf and overlay-sample.conf(not sure if this is required)

- Updated the KConfig entries CONFIG_WIFI_CREDENTIALS_STATIC_SSID and CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD, with my SSID and password

- Build and run the code

This is my terminal output

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
[00:00:00.465,911] <inf> net_config: Initializing network
[00:00:00.465,911] <inf> net_config: Waiting interface 1 (0x20000888) to be up...
uart:~$
[00:00:30.466,583] <inf> net_config: Running dhcpv4 client...
[00:00:30.466,827] <err> net_config: Timeout while waiting network interface
[00:00:30.466,827] <err> net_config: Network initialization failed (-115)
[00:00:30.466,888] <inf> net_mqtt_publisher_sample: attempting to connect:
[00:00:30.467,285] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:33.468,048] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:33.968,536] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:36.969,299] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:37.469,757] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:40.470,489] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:40.970,977] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:43.971,740] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:44.472,198] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:47.472,961] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:47.973,419] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:50.974,182] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:51.474,670] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:54.475,433] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:54.975,891] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:00:57.976,654] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:00:58.477,111] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:01.477,874] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:01.978,363] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:04.979,125] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:05.479,248] <inf> net_mqtt_publisher_sample: try_to_connect: -22 <ERROR>
[00:01:05.479,248] <inf> net_mqtt_publisher_sample: attempting to connect:
[00:01:05.479,644] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:08.480,407] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:08.980,865] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:11.981,628] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:12.482,116] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:15.482,879] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:15.983,337] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9
[00:01:18.984,100] <inf> net_mqtt_publisher_sample: mqtt_connect: -116 <ERROR>
[00:01:19.484,588] <dbg> net_mqtt_sock_tcp: mqtt_client_tcp_connect: (main): Created socket 9

my prj.conf

CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_TCP=y
CONFIG_NET_LOG=y
CONFIG_MQTT_LOG_LEVEL_DBG=y

CONFIG_NET_IPV6_RA_RDNSS=y
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=3
CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=2

CONFIG_PRINTK=y
CONFIG_STDOUT_CONSOLE=y

# Enable IPv6 support
CONFIG_NET_IPV6=n
# Enable IPv4 support
CONFIG_NET_IPV4=y

# Enable the MQTT Lib
CONFIG_MQTT_LIB=y

CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_MY_IPV6_ADDR="2001:db8::1"
CONFIG_NET_CONFIG_PEER_IPV6_ADDR="2001:db8::2"

CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1"
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2"

CONFIG_MAIN_STACK_SIZE=2048

# For IPv6
CONFIG_NET_BUF_DATA_SIZE=256

CONFIG_NET_SHELL=y

CONFIG_ENTROPY_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y

my overlay-nrf700x.conf

# Wi-Fi
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WPA_SUPP=y
CONFIG_NET_L2_ETHERNET=y

# DHCPv4
CONFIG_NET_CONFIG_MY_IPV4_ADDR=""
CONFIG_NET_CONFIG_NEED_IPV4=y
CONFIG_NET_DHCPV4=y

# Connection manager
CONFIG_NET_CONNECTION_MANAGER=y

# Credentials
CONFIG_WIFI_CREDENTIALS=y
CONFIG_WIFI_CREDENTIALS_STATIC=y
CONFIG_WIFI_CREDENTIALS_STATIC_SSID="MySSID"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="MyPassword"

[Håkon Alseth]

Hi,

 

The  zephyr/samples/net/mqtt_publisher sample does not incorporate the net_mgmt or wifi-related calls, as seen in the nrf/samples/wifi/sta (and other nRF7002 samples):

https://github.com/nrfconnect/sdk-nrf/blob/v2.6.1/samples/wifi/sta/src/main.c#L290-L306

 

Have you had a look at the ../ncs/nrf/samples/net/mqtt sample? This sample is setup to run with the nRF7002-DK.

 

Kind regards,

Håkon

[Arjun Kariat]

Thanks for the quick reply. I ll try out this example and update 

[Arjun Kariat]

I was able to get the basic mqtt work without TLS

Steps involved

• Build and run the mqtt sample from /ncs/nrf/samples/net/mqtt
• Build config
  • Board selected: nrf7002dk_nrf5340_cpuapp_ns
  • Config files: prj.conf, boards/nrf7002dk_nrf5340_cpuapp_ns.conf
• Open the terminal: Please note that you get prints on both the COM ports in this project. Connect to the COM port that supports shell
• Connect to Wifi: type the following commands in the shell
  • wifi_cred add MY_SSID WPA2-PSK My_Password
  • wifi_cred auto_connect
• Now the device will connect to Wifi and then start publishing and subscribing to topics mentioned in the LOG
• Modify the KConfigs MQTT_SAMPLE_TRANSPORT_PUBLISH_TOPIC and MQTT_SAMPLE_TRANSPORT_SUBSCRIBE_TOPIC provided in the Kconfig.transport file

I will test the TLS and update soon

[Håkon Alseth]

Hi,

 

Glad to hear that you got the sample up and running. Let me know if you run into any issues with enabling the TLS part.

 

Kind regards,

Håkon

[Arjun Kariat]

Hi I was able to get the TLS also working in this example.

But, i dont want to set the SSID and Password via shell. So i took the Wifi station code and tried to port the mqtt APIs to it. I am able to connect to the MQTT but im getting error 128(Socket is not connected.) error when im trying to publish the data

./cfs-file/__key/communityserver-discussions-components-files/4/wifistaMqtt.zip

[Håkon Alseth]

Hi,

 

 

You're connecting to port 1883, is this intentional?

You should also wait for the MQTT_EVT_CONNACK to occur before doing a publish.

 

You seem to be lacking the TLS handling, ie. the mosquitto certificate?

https://test.mosquitto.org/

 

There's not much handling of the socket itself, meaning that your mqtt_evt_handler will never be called.

 

This lesson can help you along the way:

https://academy.nordicsemi.com/courses/wi-fi-fundamentals/lessons/lesson-4-wifi-fundamentals/

 

https://github.com/NordicDeveloperAcademy/wifi-fund/blob/main/lesson4/wififund_less4_exer2_solution/src/main.c

 

Kind regards,

Håkon

[Arjun Kariat]

Hi Håkon Alseth 

I had gone through the links you have provided. thank you for this. i tried it out in my example and im getting an invalid argument error now.

I have created a mosquitto_ca_cert.h file using the python script provided in the git link. This is the .h file created from the crt file of the ca certificate of the test.mosquitto.org.

Here is the updated code

/cfs-file/__key/communityserver-discussions-components-files/4/8156.wifistaMqtt.zip

Please Note: I have only added the subscribe part here right now.

Please let me know if you want to know anything else

[Arjun Kariat]

I got the issue resolved. the invalid argument issue was due to the wrong build configuration 

changing the board to the cpu_app_ns worked.

is it possible to get the TLS working on the cpu_app build?