Enabling UARTs on PO Lines to Connect Peripheral

RE: Enabling UARTs on PO Lines to Connect Peripheral

Håkon Alseth — Mon, 19 Aug 2019 06:56:14 GMT

Hi,

You can update to the latest tag by running the lines in the top of this blog post:

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-production-version-v1-0-0-to-nrf9160

Once that is done, you should be on v1.0.0 and the other repo's should also be checked out accordingly.

Kind regards,

Håkon

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Thu, 15 Aug 2019 19:46:34 GMT

Einar,

I have not made changes elsewhere. The source for my project has been submitted under a private ticket.

I loaded the SDK about 3 weeks ago - would that be 1.0.0? How do I tell? Here is the tag list from my nrf directory:

RE: Enabling UARTs on PO Lines to Connect Peripheral

Einar Thorsrud — Thu, 15 Aug 2019 06:45:03 GMT

Hi Gary,

Sounds good.

[quote user="gmdewitt"]I assume I just need to zip the http sample directory that I am using - correct?[/quote]

Yes. But if you have made any other changes elsewhere, then please include those as well. Also please specify which version of nRF Connect SDK you are using (I am assuming the v1.0.0 tag?).

Einar

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Wed, 14 Aug 2019 18:14:51 GMT

Hi Einar,

Instead of "softdevice firmware" above, I meant to say RTOS or modem firmware.

It appears to me that this is probably related to a Zephyr RTOS issue in that it cannot handle multiple user thread ISRs properly.

I will open up a private thread and provide you with the code using my servers - please change servers if you need to pass this to someone else or need to to extensive testing.

I assume I just need to zip the http sample directory that I am using - correct?

What I need to work in the project I send you is to have the HTTP operations, SPI loopback, and a second UART operation all working within the http sample code project. The code I will send you will not have the correct overlays for the UART to be moved to different pins. I do not care where the UART pins are - the debug UART, a second UART, and SPI have to work concurrently with ISRs along with HTTP (modem) operations.

Thanks a lot for your support.

Gary

RE: Enabling UARTs on PO Lines to Connect Peripheral

Einar Thorsrud — Mon, 12 Aug 2019 12:35:31 GMT

Hi Gary,

[quote user="gmdewitt"][/quote]

I removed the following line that was duplicated in the SPI sample - is that OK?

CONFIG_MAIN_STACK_SIZE=4096

Yes, that there is no point in duplicating it.

[quote user="gmdewitt"]I reading older DevZone issues relating to similar spinning ISR issues, there had been some overlaying into the softdevice firmware through errant flash pointers. Could that be a similar issue? If so, how would that be fixed?[/quote]

I am not sure which posts you refer to, but if it mentioned the SoftDevice it is probably not relevant. (The SoftDevice is the proprietary BLE stack we provide for the nRF51 and nRF52 devices.)

[quote user="gmdewitt"]I can upload the project to you but do not want that project public since it points to my servers and do not want to have a bunch of hits from users trying my solution for their needs. Is that possible?[/quote]

Absolutely. You can make a private support case and upload your code there along with a description of how to test it. Please refer to this thread.

Einar

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Mon, 12 Aug 2019 11:29:37 GMT

Thank you for the reply Einar,

That is the SPI example I used. It works well standalone. I was even able to set the clock to 1 MHz since my peripheral cannot use the 4 MHz clock.

I used the http sample from the same GitHub link to be able to use a GET statement to fetch some strings from my test server. That http sample also worked well standalone and I was able to download strings from my server that need to be passed to two peripherals (a screen and a text to speech peripheral).

I tried using a UART to talk to the screen and came up with the ISR spinning issue with that one and submitted a request for help with that issue. While waiting for a reply, I decided to fire up the SPI sample to see if that would work and encountered the same issue when I integrated it with the http sample. I copied the appropriate c-code from the SPI mqin.c into the http main.c files. I updated the prj.conf from the spi sample into the http sample and copied the .overlay files into the main directory.

Here is the main.c content with the merged firmware. I changed the server name so it does not become public. You may also comment out the http calls in the main loop and you get the same failure without trying to go to the server.

/*
 * Copyright (c) 2018 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
 */

#include <zephyr.h>
#include <net/socket.h>
#include <stdio.h>
#include <uart.h>
#include <string.h>
#include <spi.h>

//=========START SPI TEST SECTION============
static const struct spi_config spi_cfg = {
	.operation = SPI_WORD_SET(8) | SPI_TRANSFER_MSB |
		     SPI_MODE_CPOL | SPI_MODE_CPHA,
	.frequency = 1000000,
	.slave = 0,
};

struct device * spi_dev;

static void spi_init(void)
{
	const char* const spiName = "SPI_3";
	spi_dev = device_get_binding(spiName);

	if (spi_dev == NULL) {
		printk("Could not get %s device\n", spiName);
		return;
	}
}

void spi_test_send(void)
{
	int err;
	static u8_t tx_buffer[1];
	static u8_t rx_buffer[1];

	const struct spi_buf tx_buf = {
		.buf = tx_buffer,
		.len = sizeof(tx_buffer)
	};
	const struct spi_buf_set tx = {
		.buffers = &tx_buf,
		.count = 1
	};

	struct spi_buf rx_buf = {
		.buf = rx_buffer,
		.len = sizeof(rx_buffer),
	};
	const struct spi_buf_set rx = {
		.buffers = &rx_buf,
		.count = 1
	};

	err = spi_transceive(spi_dev, &spi_cfg, &tx, &rx);
	if (err) {
		printk("SPI error: %d\n", err);
	} else {
		/* Connect MISO to MOSI for loopback */
		printk("TX sent: %x\n", tx_buffer[0]);
		printk("RX recv: %x\n", rx_buffer[0]);
		tx_buffer[0]++;
	}	
}

//=========END SPI TEST SECTION=============


//======START UART Test Section============
/********************
static u8_t uart_buf[1024];

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;
	}
	printk("%s", uart_buf);
}
******************/
static u8_t uart_buf0[1024];
static u8_t uart_buf1[1024];
static char *command0 = "This Is A Test of UART0\r\n";
static char *command1 = "This Is A Test of UART1\r\n";
u8_t i = 0;

void uart_cb0(struct device *x)
{
	uart_irq_update(x); //start processing interrupts in the ISR
	int data_length = 0;
        printk("Callback!\r\n");
	if (uart_irq_rx_ready(x)) { //check if UART RX buffer has a received char
		data_length = uart_fifo_read(x, uart_buf0, sizeof(uart_buf0)); //read ata from FIFO
		uart_buf0[data_length] = 0;
	}
	printk("cb0 - %s", uart_buf0);
}

void uart_cb1(struct device *x)
{
	uart_irq_update(x);
	int data_length = 0;
        printk("Callback!\r\n");
	if (uart_irq_rx_ready(x)) {
		data_length = uart_fifo_read(x, uart_buf1, sizeof(uart_buf1));
		uart_buf1[data_length] = 0;
	}
	printk("cb1 - %s", uart_buf1);
}


void uart_send_str(struct device *uart, char *str){
    printk("Transmit! %s\r\n",str);
    u32_t len = strlen(str);
    while (len--) {
        uart_poll_out(uart, *str++);
    }
}
//======END UART TEST Section ==================

//=====START HTTP Section===================
//#define HTTP_HOST "google.com"
//#define HTTP_PORT 80
//#define RECV_BUF_SIZE 8192


#define HTTP_HOST "my.server"
#define HTTP_PORT 80
#define RECV_BUF_SIZE 8192
char recv_buf[RECV_BUF_SIZE + 1];
char header_store[RECV_BUF_SIZE + 1];

int blocking_recv(int fd, u8_t *buf, u32_t size, u32_t flags)
{
	int err;

	do {
		err = recv(fd, buf, size, flags);
	} while (err < 0 && errno == EAGAIN);

	return err;
}

int blocking_send(int fd, u8_t *buf, u32_t size, u32_t flags)
{
	int err;

	do {
		err = send(fd, buf, size, flags);
	} while (err < 0 && errno == EAGAIN);

	return err;
}

int blocking_connect(int fd, struct sockaddr *local_addr, socklen_t len)
{
	int err;

	do {
		err = connect(fd, local_addr, len);
	} while (err < 0 && errno == EAGAIN);

	return err;
}

void app_http_get_header(void)
{
	struct sockaddr_in local_addr;
	struct addrinfo *res;

	local_addr.sin_family = AF_INET;
	local_addr.sin_port = htons(0);
	local_addr.sin_addr.s_addr = 0;

	printk("HTTP example\n\r");

	int err = getaddrinfo(HTTP_HOST, NULL, NULL, &res);

	printk("getaddrinfo err: %d\n\r", err);
	((struct sockaddr_in *)res->ai_addr)->sin_port = htons(HTTP_PORT);

        //http://my.server/rt/dev_test_falcon_20190722/sample_body?k=falcon_key&format=text  
	char send_buf[] =
                "GET /rt/dev_test_falcon_20190722/sample_header?k=falcon_key&format=text HTTP/1.1\r\nHost:my.server:80\r\nConnection: close\r\n\r\n";
        //char send_buf[] =
        //        "GET /rt/dev_test_falcon_20190722/sample_body?k=falcon_key&format=text HTTP/1.1\r\nHost:my.server:80\r\nConnection: close\r\n\r\n";
	//char send_buf[] =
	//	"GET / HTTP/1.1\r\nHost: www.google.com:80\r\nConnection: close\r\n\r\n";
	int send_data_len = strlen(send_buf);

	int client_fd = socket(AF_INET, SOCK_STREAM, 0);

	printk("client_fd: %d\n\r", client_fd);
	err = bind(client_fd, (struct sockaddr *)&local_addr,
		   sizeof(local_addr));
	printk("bind err: %d\n\r", err);
	err = blocking_connect(client_fd, (struct sockaddr *)res->ai_addr,
			       sizeof(struct sockaddr_in));
	printk("connect err: %d\n\r", err);
        printk("COMMAND USED: %s\r\n",send_buf); 

	int num_bytes = send(client_fd, send_buf, send_data_len, 0);

	printk("send err: %d\n\r", num_bytes);

	//int tot_num_bytes = 0;
        //bool buf_rcvd = false;

	//do {
		/* TODO: make a proper timeout *
		 * Current solution will just hang 
		 * until remote side closes connection */
		num_bytes =
			blocking_recv(client_fd, recv_buf, RECV_BUF_SIZE, 0);
		//tot_num_bytes += num_bytes;
                printk("\r\nnum_bytes = %i\r\n",num_bytes);
		//if (num_bytes <= 0) {
		//	break;
		//}
		printk("%s\r\n", recv_buf);
                //header_store = recv_buf;
                printk("Got Here!\r\n");
                printk("Finished. Closing socket\r\n");
                freeaddrinfo(res);
                err = close(client_fd);
}

void app_http_get_body(void)
{
	struct sockaddr_in local_addr;
	struct addrinfo *res;

	local_addr.sin_family = AF_INET;
	local_addr.sin_port = htons(0);
	local_addr.sin_addr.s_addr = 0;

	printk("HTTP example\n\r");


	int err = getaddrinfo(HTTP_HOST, NULL, NULL, &res);

	printk("getaddrinfo err: %d\n\r", err);
	((struct sockaddr_in *)res->ai_addr)->sin_port = htons(HTTP_PORT);

        //http://my.server/rt/dev_test_falcon_20190722/sample_body?k=falcon_key&format=text  
	//char send_buf[] =
        //        "GET /rt/dev_test_falcon_20190722/sample_header?k=falcon_key&format=text HTTP/1.1\r\nHost:my.server:80\r\nConnection: close\r\n\r\n";
        char send_buf[] =
                "GET /rt/dev_test_falcon_20190722/sample_body?k=falcon_key&format=text HTTP/1.1\r\nHost:my.server:80\r\nConnection: close\r\n\r\n";
	//char send_buf[] =
	//	"GET / HTTP/1.1\r\nHost: www.google.com:80\r\nConnection: close\r\n\r\n";
	int send_data_len = strlen(send_buf);

	int client_fd = socket(AF_INET, SOCK_STREAM, 0);

	printk("client_fd: %d\n\r", client_fd);
	err = bind(client_fd, (struct sockaddr *)&local_addr,
		   sizeof(local_addr));
	printk("bind err: %d\n\r", err);
	err = blocking_connect(client_fd, (struct sockaddr *)res->ai_addr,
			       sizeof(struct sockaddr_in));
	printk("connect err: %d\n\r", err);
        printk("COMMAND USED: %s\r\n",send_buf); 

	int num_bytes = send(client_fd, send_buf, send_data_len, 0);

	printk("send err: %d\n\r", num_bytes);

	//int tot_num_bytes = 0;
        //bool buf_rcvd = false;

	//do {
		num_bytes =
			blocking_recv(client_fd, recv_buf, RECV_BUF_SIZE, 0);
		//tot_num_bytes += num_bytes;
                printk("\r\nnum_bytes = %i\r\n",num_bytes);
		//if (num_bytes <= 0) {
		//	break;
		//
                printk("RX Buffer size = %i\r\n", sizeof(recv_buf));
		printk("%s\r\n", recv_buf);
                printk("Got Here!\r\n");
                printk("Finished. Closing socket\r\n");
                freeaddrinfo(res);
                err = close(client_fd);
}

int main(void)
{
	app_http_get_header();
	app_http_get_body();

        spi_init();
        int i = 0;
        while (i < 100){
          spi_test_send();
          i++;
        }

        //////////UART setup
	//struct device *uart0 = device_get_binding("UART_0");
	//uart_irq_callback_set(uart0, uart_cb0);
	//uart_irq_rx_enable(uart0);
        //printk("uart0 ready\n");

	//struct device *uart1 = device_get_binding("UART_1");
        //uart_irq_callback_set(uart1, uart_cb1);
	//uart_irq_rx_enable(uart1);
        //printk("uart1 ready\n");

        //struct device *uart = device_get_binding("UART_0");
	//uart_irq_callback_set(uart, uart_cb);
	//uart_irq_rx_enable(uart);
	//printk("UART loopback start!\n");
        ////////////

        //uart_send_str(uart0, command0);
        //uart_send_str(uart1, command1);

	while (1) {
                //uart_send_str(uart1, command1);
               // uart_send_str(uart0, command0);
		k_cpu_idle();
	}
}

Here is the integrated prj.conf

CONFIG_BSD_LIBRARY=y
CONFIG_GPIO=n
CONFIG_SERIAL=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_NETWORKING=y
CONFIG_NET_BUF_USER_DATA_SIZE=1
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_NET_RAW_MODE=y
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
CONFIG_LOG=n
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_HEAP_MEM_POOL_SIZE=1024
# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_MAIN_STACK_SIZE=4096
# SPI
CONFIG_SPI=y
CONFIG_SPI_3=y
CONFIG_SPI_3_NRF_SPIM=y
CONFIG_SPI_3=y 
CONFIG_SPI_NRFX=y

I removed the following line that was duplicated in the SPI sample - is that OK?

CONFIG_MAIN_STACK_SIZE=4096

Today I upgraded the modem firmware to 1.0.0 but still fail with the same issue. I am going to try to move the HTTP working firmware into the now stand alone working firmware to see if that will work. However, I still have to be able to add a UART to the mix as well and expect to see some of the same issues.

I reading older DevZone issues relating to similar spinning ISR issues, there had been some overlaying into the softdevice firmware through errant flash pointers. Could that be a similar issue? If so, how would that be fixed?

I can upload the project to you but do not want that project public since it points to my servers and do not want to have a bunch of hits from users trying my solution for their needs. Is that possible?

Thank you for your support,

Gary

RE: Enabling UARTs on PO Lines to Connect Peripheral

Einar Thorsrud — Mon, 12 Aug 2019 07:28:33 GMT

Hi,

I am sorry for the late reply.

I am not sure what the problem is here. Which SPI example have you used? Can you try using/looking at this SPI example, which we know is functional? If yous till have problems after that, perhaps you can upload a completed project demonstrating the issue that I can test on my side?

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Sun, 11 Aug 2019 23:24:37 GMT

Hello,

I realize you are busy and I know an engineer was assigned several days ago - however, I have not received any assistance yet.

I am short on time so I decided to go ahead and use a SPI connection instead of UART and have encountered the same error break as follows. I simply copied the SPI sample code main.c into the http main.c code, added the SPI3 info into the from the spi sample into the http prj.conf, and copied the .overlay files from the spi sample to the http sample main directory.

If I continue the execution in debug, the COM23 nRFConnect LTE Link Monitor trace indicates the following. There must be another setting somewhere to allow the SPI ISR to operate in the non-secure state. Can someone point me to where this can be resolved. A similar correction may be in order for the UART issue. It is probably something simple.

Could not get SPI_3 device
Exception occurred in Secure State
***** HARD FAULT *****
  Fault escalation (see below)
***** BUS FAULT *****
  Precise data bus error
  BFAR Address: 0x50008120
***** Hardware exception *****
Current thread ID = 0x20020134
Faulting instruction address = 0x9300
Fatal fault in ISR! Spinning...

The LTE Link Monitor Trace shows the SPIM3 to be OK and non-secure as peripheral 12.

Peripheral		Domain		Status
00 NRF_P0		Non-Secure	OK
01 NRF_CLOCK		Non-Secure	OK
02 NRF_RTC1		Non-Secure	OK
03 NRF_NVMC		Non-Secure	OK
04 NRF_UARTE1		Non-Secure	OK
05 NRF_UARTE2		Secure		SKIP
06 NRF_IPC		Non-Secure	OK
07 NRF_VMC		Non-Secure	OK
08 NRF_FPU		Non-Secure	OK
09 NRF_EGU1		Non-Secure	OK
10 NRF_EGU2		Non-Secure	OK
11 NRF_TWIM2		Non-Secure	OK
12 NRF_SPIM3		Non-Secure	OK
13 NRF_TIMER0		Non-Secure	OK
14 NRF_TIMER1		Non-Secure	OK
15 NRF_TIMER2		Non-Secure	OK
16 NRF_SAADC		Non-Secure	OK
17 NRF_GPIOTE1		Non-Secure	OK

If anyone can suggest a solution, please reply.

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Thu, 08 Aug 2019 10:43:43 GMT

Here is the UART1 and UART0 information contained in nrf9160_pca10090ns.dts_compiled file:

			uart0: uart@8000 {
				compatible = "nordic,nrf-uarte";
				reg = < 0x8000 0x1000 >;
				interrupts = < 0x08 0x01 >;
				status = "ok";
				label = "UART_0";
				current-speed = < 0x1c200 >;
				tx-pin = < 0x1d >;
				rx-pin = < 0x1c >;
				rts-pin = < 0x1b >;
				cts-pin = < 0x1a >;
			};

			uart1: uart@9000 {
				compatible = "nordic,nrf-uarte";
				reg = < 0x9000 0x1000 >;
				interrupts = < 0x09 0x01 >;
				status = "ok";
				label = "UART_1";
				current-speed = < 0x1c200 >;
				tx-pin = < 0x01 >;
				rx-pin = < 0x00 >;
				rts-pin = < 0x0e >;
				cts-pin = < 0x0f >;
			};

RE: Enabling UARTs on PO Lines to Connect Peripheral

GaryD — Tue, 06 Aug 2019 15:15:49 GMT

One additional note: If I continue after the fault condition defined in Problem 1, I get the following messages on the connect terminal: I also loaded the .hex file for the nRF52840 provided for UART1 in the Case ID 226331.

Exception occurred in Secure State
***** HARD FAULT *****
  Fault escalation (see below)
***** BUS FAULT *****
  Precise data bus error
  BFAR Address: 0x50008120
***** Hardware exception *****
Current thread ID = 0x20020130
Faulting instruction address = 0x19df8
Fatal fault in ISR! Spinning...