Sending MQTT messages using the data_publish function from the mqtt_simple sample

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Mon, 15 Jul 2019 13:55:14 GMT

That seems to be the problem. data_publish() works outside of uart_cb().

Thank you for the help,

hfj

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Hakon — Mon, 15 Jul 2019 12:53:24 GMT

Have you tried calling data_publish() outside of uart_cb()? Calling it inside should not work because uart_cb() is an ISR, and data_publish() uses mutex. More information can be found here.

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Fri, 12 Jul 2019 09:06:32 GMT

I have done some quick testing, putting additional calls to the data_publish function inside the mqtt_evt_handler works now (that also did not work before). Both published messages get picked up by the MQTT broker. It is a step in the right direction! 🙂

/* Echo back received data */
			data_publish(&client, MQTT_QOS_1_AT_LEAST_ONCE,
				"test_message", 12);
            data_publish(&client, MQTT_QOS_1_AT_LEAST_ONCE,
				payload_buf, p->message.payload.len);

Putting calls to this function elsewhere does not seem to work. Since I want to send the data I receive over UART over MQTT I have tried using code from the UART example found here. I've modified the code so that everything sent into COM4 (UART_1 I believe) gets echoed in COM5 (UART_0 I believe). This works. However, if I put a call to data_publish inside the uart_cb function as show below the nRF9160 stops responding and I have to do a reset.

void uart_cb(struct device *x)
{
	uart_irq_update(x);
	int data_length = 0;

	if (uart_irq_rx_ready(x)) {
		data_length = uart_fifo_read(x, uart_buf, sizeof(uart_buf));
		uart_buf[data_length] = 0;
	}

        data_publish(&client, MQTT_QOS_1_AT_LEAST_ONCE, "test", 4);// &test, 1);

        printk("%s", uart_buf);

}

Edit:

Since there are no errors I find it hard to trace what goes wrong. What I did when working with NCS v0.4.0 was following the function calls and just litter the code with calls to printk(), which is also what I tried to do now. The execution seems to stop in the send function inside socket_offload.h at the third printk(): printk("Debug: send 3\n").

static inline ssize_t send(int sock, const void *buf, size_t len,
			   int flags)
{

printk("Debug: send 1\n");
	__ASSERT_NO_MSG(socket_ops);
printk("Debug: send 2\n");
	__ASSERT_NO_MSG(socket_ops->send);
printk("Debug: send 3\n");

        ssize_t stest = socket_ops->send(sock, buf, len, flags);

printk("Debug: send 4\n");

	return stest; // socket_ops->send(sock, buf, len, flags);
}

Thank you for all the help so far,

hfj

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Øyvind — Fri, 12 Jul 2019 08:07:48 GMT

[quote user="hfj"]Sorry, I was editing my post from earlier today. It seems to be working now. [/quote]

Glad to hear! :)

[quote user="hfj"]Does this confirm that I have correctly installed FW v1.0.0?[/quote]

Yes, this confirms that you have the latest modem FW v1.0.0.

[quote user=""]when attempting to call the data_publish function outside the mqtt_evt_handler function it either does not send any data or the nRF9160 stops execution without any error messages[/quote]

Does this work now?

Kind regards,
Øyvind

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Fri, 12 Jul 2019 07:27:32 GMT

[quote userid="81273" url="~/f/nordic-q-a/49639/sending-mqtt-messages-using-the-data_publish-function-from-the-mqtt_simple-sample/197981"]I upgraded to SEGGER v4.18[/quote]

Sorry, I was editing my post from earlier today. It seems to be working now.

[quote userid="81273" url="~/f/nordic-q-a/49639/sending-mqtt-messages-using-the-data_publish-function-from-the-mqtt_simple-sample/197981"]When inputting the command 'AT+CGMR' it returns mfw_nrf9160_1.0.0.[/quote]

Does this confirm that I have correctly installed FW v1.0.0?

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Øyvind — Fri, 12 Jul 2019 07:16:13 GMT

Was this using SES v4.16 or v4.18?

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Fri, 12 Jul 2019 06:00:29 GMT

I tried setting 'zephyr/merged.hex' as the active project by right clicking it in the prject explorer. When rebuilding I get this error, which is the same error as I have been getting previously:

C:\gnuarmemb\bin\arm-none-eabi-objcopy.exe: 'zephyr.elf': No such file
Build failed

The build succeeded after I tried to right click 'zephyr/merged.hex' and select "Build" before building the project again. Having to do these additional steps is what makes me think I have something set up wrong when using v1.0.0 of NCS. None of these problems were present when working with v0.4.0 and v0.4.0-rc3. Additionally, the structure of my project in the project explorer window looks different to yours.

Edit:

I upgraded to SEGGER v4.18 and found the correct way to set the merged hex as he active project:

I deleted the build directory, rebuilt the project and encountered no errors this time. Downloaded the merged.hex through SEGGER and connected to the LTE Link Monitor. Everything seems to be working. When inputting the command 'AT+CGMR' it returns mfw_nrf9160_1.0.0.

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Øyvind — Thu, 11 Jul 2019 14:45:28 GMT

[quote user="hfj"] I am assuming that I am doing something slightly wrong here or that I have some wrong settings.[/quote]

Yes, I think the issue lies in what project was built in the solution of SES. In SES you have Project 'zephyr/zephyr.elf' as Active when it should be Project 'zephyr/merged.hex'. Can you please Right-click on that project, and click "Set as Active project". This should be handled automatically.

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Thu, 11 Jul 2019 14:32:34 GMT

I followed Martins instructions as he wrote them in the link from my original post, using the Programmer v1.2.0 application and the firmware 'mfw_nrf9160_1.0.0.zip'. I went through the same steps again now. In the Programmer app i clicked "Update modem" after clearing the memory with "Erase all". After selecting the firmware and clicking "Write":

The PROG/DEBUG switch is set to nRF91, I don't think I've ever touched it.

Before programming the device I made sure all build folders were deleted, the at-client sample folder looked like in the following picture:

When building the project in SEGGER I go to "File" and chose "Open nRF Connect SDK Project..." and enter the following:

After loading the project:

When first building the project it quite often fails, providing an output (this is just the end of the build log):

Building ‘spm/zephyr/linker_pass_final.cmd’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘spm/zephyr/linker_pass_final.cmd’
Building ‘spm/zephyr/CMakeFiles/spm_linker_pass_final_script_target’ from solution ‘build’ in configuration ‘Common’
Building ‘spm/zephyr/spm_linker_pass_final_script_target’ from solution ‘build’ in configuration ‘Common’
Building ‘spm/zephyr/isr_tables.c’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘spm/zephyr/isr_tables.c’
Building ‘cmake_object_order_depends_target_spm_zephyr_final’ from solution ‘build’ in configuration ‘Common’
Building ‘libspmsecureentries.a’ from solution ‘build’ in configuration ‘Common’
1> Compiling ‘empty_file.c’
2> Compiling ‘isr_tables.c’
Building ‘spm/zephyr/zephyr.elf’ from solution ‘build’ in configuration ‘Common’
1> Linking ‘libspmsecureentries.a’
1> Post-link command 
1> C:\gnuarmemb\bin\arm-none-eabi-objcopy.exe: 'zephyr.elf': No such file
Build failed

The build succeeded after I tried to "Build zephyr/zephyr.elf" before "Build Solution" again. I am assuming that I am doing something slightly wrong here or that I have some wrong settings. Nonetheless, I now have a merged.hex file. Normally I download this to the nRF9160 by connecting to it with J-link in SEGGER and chose the following before navigating to the corresponding build folder and selecting the merged.hex file:

This time, however, I tried doing it like you suggested with the command line. I downloaded the latest nRF Command Line Tool here and followed your instructions.

PS C:\ncs\nrf\samples\nrf9160\at_client\build_nrf9160_pca10090ns\zephyr> nrfjprog -e
Erasing user available code and UICR flash areas.
Applying system reset.
PS C:\ncs\nrf\samples\nrf9160\at_client\build_nrf9160_pca10090ns\zephyr> nrfjprog --program merged.hex -f nrf91 --sectorerase -r --verify
Parsing hex file.
Erasing page at address 0x0.
Erasing page at address 0x1000.
Erasing page at address 0x2000.
Erasing page at address 0x3000.
Erasing page at address 0x4000.
Erasing page at address 0x5000.
Erasing page at address 0x6000.
Erasing page at address 0x7000.
Erasing page at address 0xC000.
Erasing page at address 0xD000.
Erasing page at address 0xE000.
Erasing page at address 0xF000.
Erasing page at address 0x10000.
Erasing page at address 0x11000.
Erasing page at address 0x12000.
Erasing page at address 0x13000.
Erasing page at address 0x14000.
Erasing page at address 0x15000.
Erasing page at address 0x16000.
Erasing page at address 0x17000.
Erasing page at address 0x18000.
Erasing page at address 0x19000.
Erasing page at address 0x1A000.
Erasing page at address 0x1B000.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Erasing page at address 0x1E000.
Erasing page at address 0x1F000.
Erasing page at address 0x20000.
Erasing page at address 0x21000.
Erasing page at address 0x22000.
Erasing page at address 0x23000.
Erasing page at address 0x24000.
Erasing page at address 0x25000.
Erasing page at address 0x26000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.
Applying system reset.
Run.
PS C:\ncs\nrf\samples\nrf9160\at_client\build_nrf9160_pca10090ns\zephyr>

After power cycling and connecting to the LTE Link Monitor and pressing reset again:

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Øyvind — Thu, 11 Jul 2019 13:19:21 GMT

Should not give that output unless you have not updated the modem FW. Did you follow all the steps in Martins instructions? Have you ensured that SW5 is set to nRF91?

Please try to delete all build folders in the at_client folder. When programming the device, can you please describe the steps you have used?

Using a command line, can you please first issue:

nrfjprog -e

Then, still in the command line, find the folder where you have v1.0.0 of at_client e.g. nrf\samples\nrf9160\at_client\build\zephyr

Standing in that folder, run the following (given that you have merged.hex file):

nrfjprog --program merged.hex -f nrf91 --sectorerase -r --verify

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

hfj — Thu, 11 Jul 2019 11:59:05 GMT

I updated NCS to v1.0.0 following Martin Lesund's instructions here. After building the mqtt_simple sample and downloading the merged.hex file I launched nRF Connect v3.0.0 and the LTE Link Monitor v1.0.0. When connecting the device and pressing the reset button on the devboard it gives this output.

I've tried rebuilding and downloading again, both with using the Programmer app v1.2.0 to clear the memory and without it. I have also tried doing this with the at_client sample.

I have tried using the v1.0.0 tag previously, but it has given me some problems when building the solutions in SEGGER.

RE: Sending MQTT messages using the data_publish function from the mqtt_simple sample

Øyvind — Thu, 11 Jul 2019 10:59:58 GMT

Hello,

First, please update to the latest version of NCS v1.0.0. This should work better with modem FW v1.0.0.

What kind of output do you get via LTE Link Monitor in nRF Connect for Desktop?

Kind regards,
Øyvind