UART2 not working in http_application_update example

RE: UART2 not working in http_application_update example

khodidas — Thu, 01 Aug 2019 04:12:52 GMT

Hi,

Making "CONFIG_LTE_AUTO_INIT_AND_CONNECT=n" solved the issue.

Now printk and UART2 both are working

Regards,

Smitesh Mali

RE: UART2 not working in http_application_update example

Didrik Rokhaug — Wed, 31 Jul 2019 12:50:29 GMT

I get output from printk, and I am able to transmit data and register an IRQ on UART2.

The application tries to establish an LTE connection before it outputs anything.

Can you try to disable the automatic connection, just to see if getting the connection takes longer time than you have been waiting for output (it might take several minutes).

In your prj.conf file, one of the lines should say

CONFIG_LTE_AUTO_INIT_AND_CONNECT=y

Please try to change the "y" to "n," and see if you get a line saying "Press Button 1 to start the FOTA download" in your terminal.

P.S.

Remember to turn the config on again afterwards, so that you are able to get an internet connection

RE: UART2 not working in http_application_update example

khodidas — Wed, 31 Jul 2019 11:02:56 GMT

Hi,

do you get "printk" data on pc in 1.0.0 sdk and UART2 is working or not ?

Regards,

Smitesh Mali

RE: UART2 not working in http_application_update example

khodidas — Tue, 30 Jul 2019 11:55:05 GMT

Hi,

I downloaded "1.0.0" sdk and added "UART_2" related code to "http_application_update" project.

In this firmware i am not getting any hard fault error but also not getting "printk" print on the pc.

So not being able to know whether application is running or not and UART 2 is working or not.

Following are the print on the pc

7/30/2019 17:16:33.467 [RX] - ***** Booting Zephyr OS v1.14.99-ncs2 *****<CR><LF>
[00:00:00.004,455] <ESC>[0m<inf> mcuboot: Starting bootloader<ESC>[0m<CR><LF>
[00:00:00.012,908] <ESC>[0m<inf> mcuboot: Primary image: magic=unset, copy_done=0x3, image_ok=0x1<ESC>[0m<CR><LF>
[00:00:00.024,169] <ESC>[0m<inf> mcuboot: Scratch: magic=unset, copy_done=0x50, image_ok=0x3<ESC>[0m<CR><LF>
[00:00:00.034,851] <ESC>[0m<inf> mcuboot: Boot source: primary slot<ESC>[0m<CR><LF>
[00:00:00.045,959] <ESC>[0m<inf> mcuboot: Swap type: none<ESC>[0m<CR><LF>
[00:00:00.385,467] <ESC>[0m<inf> mcuboot: Bootloader chainload address offset: 0xc000<ESC>[0m<CR><LF>
[00:00:00.395,355] <ESC>[0m<inf> mcuboot: Jumping to the first image slot<ESC>[0m<CR><LF>
***** Booting Zephyr OS v1.14.99-ncs2 *****<CR><LF>
Flash region<HT> <HT> Domain<HT> <HT> Permissions<CR><LF>
00 0x00000 0x08000 <HT> Secure<HT> <HT> rwxl<CR><LF>
01 0x08000 0x10000 <HT> Secure<HT> <HT> rwxl<CR><LF>
02 0x10000 0x18000 <HT> Secure<HT> <HT> rwxl<CR><LF>
03 0x18000 0x20000 <HT> Non-Secure<HT> rwxl<CR><LF>
04 0x20000 0x28000 <HT> Non-Secure<HT> rwxl<CR><LF>
05 0x28000 0x30000 <HT> Non-Secure<HT> rwxl<CR><LF>
06 0x30000 0x38000 <HT> Non-Secure<HT> rwxl<CR><LF>
07 0x38000 0x40000 <HT> Non-Secure<HT> rwxl<CR><LF>
08 0x40000 0x48000 <HT> Non-Secure<HT> rwxl<CR><LF>
09 0x48000 0x50000 <HT> Non-Secure<HT> rwxl<CR><LF>
10 0x50000 0x58000 <HT> Non-Secure<HT> rwxl<CR><LF>
11 0x58000 0x60000 <HT> Non-Secure<HT> rwxl<CR><LF>
12 0x60000 0x68000 <HT> Non-Secure<HT> rwxl<CR><LF>
13 0x68000 0x70000 <HT> Non-Secure<HT> rwxl<CR><LF>
14 0x70000 0x78000 <HT> Non-Secure<HT> rwxl<CR><LF>
15 0x78000 0x80000 <HT> Non-Secure<HT> rwxl<CR><LF>
16 0x80000 0x88000 <HT> Non-Secure<HT> rwxl<CR><LF>
17 0x88000 0x90000 <HT> Non-Secure<HT> rwxl<CR><LF>
18 0x90000 0x98000 <HT> Non-Secure<HT> rwxl<CR><LF>
19 0x98000 0xa0000 <HT> Non-Secure<HT> rwxl<CR><LF>
20 0xa0000 0xa8000 <HT> Non-Secure<HT> rwxl<CR><LF>
21 0xa8000 0xb0000 <HT> Non-Secure<HT> rwxl<CR><LF>
22 0xb0000 0xb8000 <HT> Non-Secure<HT> rwxl<CR><LF>
23 0xb8000 0xc0000 <HT> Non-Secure<HT> rwxl<CR><LF>
24 0xc0000 0xc8000 <HT> Non-Secure<HT> rwxl<CR><LF>
25 0xc8000 0xd0000 <HT> Non-Secure<HT> rwxl<CR><LF>
26 0xd0000 0xd8000 <HT> Non-Secure<HT> rwxl<CR><LF>
27 0xd8000 0xe0000 <HT> Non-Secure<HT> rwxl<CR><LF>
28 0xe0000 0xe8000 <HT> Non-Secure<HT> rwxl<CR><LF>
29 0xe8000 0xf0000 <HT> Non-Secure<HT> rwxl<CR><LF>
30 0xf0000 0xf8000 <HT> Non-Secure<HT> rwxl<CR><LF>
31 0xf8000 0x100000 <HT> Non-Secure<HT> rwxl<CR><LF>
Non-secure callable region 0 placed in flash region 2 with size 32.<CR><LF>
<CR><LF>
<CR><LF>
SRAM region<HT> <HT> Domain<HT> <HT> Permissions<CR><LF>
00 0x00000 0x02000<HT> Secure<HT> <HT> rwxl<CR><LF>
01 0x02000 0x04000<HT> Secure<HT> <HT> rwxl<CR><LF>
02 0x04000 0x06000<HT> Secure<HT> <HT> rwxl<CR><LF>
03 0x06000 0x08000<HT> Secure<HT> <HT> rwxl<CR><LF>
04 0x08000 0x0a000<HT> Secure<HT> <HT> rwxl<CR><LF>
05 0x0a000 0x0c000<HT> Secure<HT> <HT> rwxl<CR><LF>
06 0x0c000 0x0e000<HT> Secure<HT> <HT> rwxl<CR><LF>
07 0x0e000 0x10000<HT> Secure<HT> <HT> rwxl<CR><LF>
08 0x10000 0x12000<HT> Non-Secure<HT> rwxl<CR><LF>
09 0x12000 0x14000<HT> Non-Secure<HT> rwxl<CR><LF>
10 0x14000 0x16000<HT> Non-Secure<HT> rwxl<CR><LF>
11 0x16000 0x18000<HT> Non-Secure<HT> rwxl<CR><LF>
12 0x18000 0x1a000<HT> Non-Secure<HT> rwxl<CR><LF>
13 0x1a000 0x1c000<HT> Non-Secure<HT> rwxl<CR><LF>
14 0x1c000 0x1e000<HT> Non-Secure<HT> rwxl<CR><LF>
15 0x1e000 0x20000<HT> Non-Secure<HT> rwxl<CR><LF>
16 0x20000 0x22000<HT> Non-Secure<HT> rwxl<CR><LF>
17 0x22000 0x24000<HT> Non-Secure<HT> rwxl<CR><LF>
18 0x24000 0x26000<HT> Non-Secure<HT> rwxl<CR><LF>
19 0x26000 0x28000<HT> Non-Secure<HT> rwxl<CR><LF>
20 0x28000 0x2a000<HT> Non-Secure<HT> rwxl<CR><LF>
21 0x2a000 0x2c000<HT> Non-Secure<HT> rwxl<CR><LF>
22 0x2c000 0x2e000<HT> Non-Secure<HT> rwxl<CR><LF>
23 0x2e000 0x30000<HT> Non-Secure<HT> rwxl<CR><LF>
24 0x30000 0x32000<HT> Non-Secure<HT> rwxl<CR><LF>
25 0x32000 0x34000<HT> Non-Secure<HT> rwxl<CR><LF>
26 0x34000 0x36000<HT> Non-Secure<HT> rwxl<CR><LF>
27 0x36000 0x38000<HT> Non-Secure<HT> rwxl<CR><LF>
28 0x38000 0x3a000<HT> Non-Secure<HT> rwxl<CR><LF>
29 0x3a000 0x3c000<HT> Non-Secure<HT> rwxl<CR><LF>
30 0x3c000 0x3e000<HT> Non-Secure<HT> rwxl<CR><LF>
31 0x3e000 0x40000<HT> Non-Secure<HT> rwxl<CR><LF>
<CR><LF>
Peripheral<HT> <HT> Domain<HT> <HT> Status<CR><LF>
00 NRF_P0<HT> <HT> Non-Secure<HT> OK<CR><LF>
01 NRF_CLOCK<HT> <HT> Non-Secure<HT> OK<CR><LF>
02 NRF_RTC1<HT> <HT> Non-Secure<HT> OK<CR><LF>
03 NRF_NVMC<HT> <HT> Non-Secure<HT> OK<CR><LF>
04 NRF_UARTE1<HT> <HT> Non-Secure<HT> OK<CR><LF>
05 NRF_UARTE2<HT> <HT> Secure<HT> <HT> SKIP<CR><LF>
06 NRF_TWIM2<HT> <HT> Non-Secure<HT> OK<CR><LF>
07 NRF_SPIM3<HT> <HT> Non-Secure<HT> OK<CR><LF>
08 NRF_TIMER0<HT> <HT> Non-Secure<HT> OK<CR><LF>
09 NRF_TIMER1<HT> <HT> Non-Secure<HT> OK<CR><LF>
10 NRF_TIMER2<HT> <HT> Non-Secure<HT> OK<CR><LF>
11 NRF_SAADC<HT> <HT> Non-Secure<HT> OK<CR><LF>
12 NRF_PWM0<HT> <HT> Non-Secure<HT> OK<CR><LF>
13 NRF_PWM1<HT> <HT> Non-Secure<HT> OK<CR><LF>
14 NRF_PWM2<HT> <HT> Non-Secure<HT> OK<CR><LF>
15 NRF_PWM3<HT> <HT> Non-Secure<HT> OK<CR><LF>
16 NRF_IPC<HT> <HT> Non-Secure<HT> OK<CR><LF>
17 NRF_VMC<HT> <HT> Non-Secure<HT> OK<CR><LF>
18 NRF_FPU<HT> <HT> Non-Secure<HT> OK<CR><LF>
19 NRF_EGU1<HT> <HT> Non-Secure<HT> OK<CR><LF>
20 NRF_EGU2<HT> <HT> Non-Secure<HT> OK<CR><LF>
21 NRF_GPIOTE1<HT> <HT> Non-Secure<HT> OK<CR><LF>
<CR><LF>
SPM: NS image at 0x18200<CR><LF>
SPM: NS MSP at 0x20026ce0<CR><LF>
SPM: NS reset vector at 0x1b205<CR><LF>
SPM: prepare to jump to Non-Secure image.<CR><LF>
***** Booting Zephyr OS v1.14.99-ncs2 *****<CR><LF>

Regards,

Smitesh Mali

RE: UART2 not working in http_application_update example

Didrik Rokhaug — Tue, 30 Jul 2019 11:14:13 GMT

Hi.

I was unable to reproduce your error on my end with version 1.0.0.

Can you try to update your ncs version following this guide, and let me know if the problem persists?

Best regards,

Didrik

RE: UART2 not working in http_application_update example

khodidas — Tue, 30 Jul 2019 07:01:32 GMT

Yes , I did.

But it is not working

You can see it non-secure in below print

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

Regards,

Smitesh Mali

RE: UART2 not working in http_application_update example

shibshab — Tue, 30 Jul 2019 06:57:32 GMT

Have you set the UARTE2 peripheral as non-secure in SPM?

The application executes in the non secure context, and can only access peripherals and memory regions explicitly set as non-secure accessible by the SPM (Secure Partition manager).

The SPM is a separate image which is automatically built and merged in when working with the pca10090ns board.
To configure SPM to allow non-secure access to a given peripheral, one must edit the SPM image, not the regular app.

This can be done through menuconfig (not persistent) or in the SPMs prj.conf file (persistent):

Menuconfig:
1.Run ninja spm_menuconfig in the project build folder
2. Navigate to Modules > Nordic nRF Connect > SPM > Current app is SPM
3. Set UARTE2 is Non - Secure

prj.conf:
echo "CONFIG_SPM_NRF_UARTE2_NS=y" >> $ZEPHYR_BASE/../nrf/samples/nrf9160/spm/prj.conf