TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

RonanB96 — Mon, 08 Jul 2019 08:27:37 GMT

Updating to the latest SEGGER embedded studio seemed to fix it, was using v416 now on v418

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

RonanB96 — Fri, 05 Jul 2019 16:21:50 GMT

Same here, using your hex also gave the exact same ISR spinning error

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Thu, 04 Jul 2019 14:34:40 GMT

Thanks, I will do 🙂

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

slomusti — Thu, 04 Jul 2019 14:31:29 GMT

Thank you, HW has been already reviewed by your colleagues via email and passed without comments. We have multiple boards running well with with old modem firmware and a few with an unknown problem of not being able to connect, but at client is running well on all.

The new modem FW is running well on the DK as well as the at client example. Thus the above error is somewhat HW related, not sure how.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

slomusti — Thu, 04 Jul 2019 14:20:10 GMT

Thank you. Unfortunately this does not resolve the issue, I get the error below:

Note that this is being tested on our custom board, however should be no different to DK. I have the latest NRF connect 3.0.0, manually updated nrfjprog to the latest version and installed the latest modem FW 1.0.0.

Håkon Alseth any thoughts what else to try?

bsdlib irrecoverable error: 3
ASSERTION FAIL [0] @ ../src/main.c:23
***** Kernel Panic! *****
Current thread ID = 0x20021a80
Faulting instruction address = 0x217c8
***** Booting Zephyr OS v1.14.99-ncs2 *****
Flash region		Domain		Permissions
00 0x00000 0x08000 	Secure		rwxl
01 0x08000 0x10000 	Non-Secure	rwxl
02 0x10000 0x18000 	Non-Secure	rwxl
03 0x18000 0x20000 	Non-Secure	rwxl
04 0x20000 0x28000 	Non-Secure	rwxl
05 0x28000 0x30000 	Non-Secure	rwxl
06 0x30000 0x38000 	Non-Secure	rwxl
07 0x38000 0x40000 	Non-Secure	rwxl
08 0x40000 0x48000 	Non-Secure	rwxl
09 0x48000 0x50000 	Non-Secure	rwxl
10 0x50000 0x58000 	Non-Secure	rwxl
11 0x58000 0x60000 	Non-Secure	rwxl
12 0x60000 0x68000 	Non-Secure	rwxl
13 0x68000 0x70000 	Non-Secure	rwxl
14 0x70000 0x78000 	Non-Secure	rwxl
15 0x78000 0x80000 	Non-Secure	rwxl
16 0x80000 0x88000 	Non-Secure	rwxl
17 0x88000 0x90000 	Non-Secure	rwxl
18 0x90000 0x98000 	Non-Secure	rwxl
19 0x98000 0xa0000 	Non-Secure	rwxl
20 0xa0000 0xa8000 	Non-Secure	rwxl
21 0xa8000 0xb0000 	Non-Secure	rwxl
22 0xb0000 0xb8000 	Non-Secure	rwxl
23 0xb8000 0xc0000 	Non-Secure	rwxl
24 0xc0000 0xc8000 	Non-Secure	rwxl
25 0xc8000 0xd0000 	Non-Secure	rwxl
26 0xd0000 0xd8000 	Non-Secure	rwxl
27 0xd8000 0xe0000 	Non-Secure	rwxl
28 0xe0000 0xe8000 	Non-Secure	rwxl
29 0xe8000 0xf0000 	Non-Secure	rwxl
30 0xf0000 0xf8000 	Non-Secure	rwxl
31 0xf8000 0x100000 	Non-Secure	rwxl
Non-secure callable region 0 placed in flash region 0 with size 32.


SRAM region		Domain		Permissions
00 0x00000 0x02000	Secure		rwxl
01 0x02000 0x04000	Secure		rwxl
02 0x04000 0x06000	Secure		rwxl
03 0x06000 0x08000	Secure		rwxl
04 0x08000 0x0a000	Secure		rwxl
05 0x0a000 0x0c000	Secure		rwxl
06 0x0c000 0x0e000	Secure		rwxl
07 0x0e000 0x10000	Secure		rwxl
08 0x10000 0x12000	Non-Secure	rwxl
09 0x12000 0x14000	Non-Secure	rwxl
10 0x14000 0x16000	Non-Secure	rwxl
11 0x16000 0x18000	Non-Secure	rwxl
12 0x18000 0x1a000	Non-Secure	rwxl
13 0x1a000 0x1c000	Non-Secure	rwxl
14 0x1c000 0x1e000	Non-Secure	rwxl
15 0x1e000 0x20000	Non-Secure	rwxl
16 0x20000 0x22000	Non-Secure	rwxl
17 0x22000 0x24000	Non-Secure	rwxl
18 0x24000 0x26000	Non-Secure	rwxl
19 0x26000 0x28000	Non-Secure	rwxl
20 0x28000 0x2a000	Non-Secure	rwxl
21 0x2a000 0x2c000	Non-Secure	rwxl
22 0x2c000 0x2e000	Non-Secure	rwxl
23 0x2e000 0x30000	Non-Secure	rwxl
24 0x30000 0x32000	Non-Secure	rwxl
25 0x32000 0x34000	Non-Secure	rwxl
26 0x34000 0x36000	Non-Secure	rwxl
27 0x36000 0x38000	Non-Secure	rwxl
28 0x38000 0x3a000	Non-Secure	rwxl
29 0x3a000 0x3c000	Non-Secure	rwxl
30 0x3c000 0x3e000	Non-Secure	rwxl
31 0x3e000 0x40000	Non-Secure	rwxl

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_TWIM2		Non-Secure	OK
07 NRF_SPIM3		Non-Secure	OK
08 NRF_TIMER0		Non-Secure	OK
09 NRF_TIMER1		Non-Secure	OK
10 NRF_TIMER2		Non-Secure	OK
11 NRF_SAADC		Non-Secure	OK
12 NRF_PWM0		Non-Secure	OK
13 NRF_PWM1		Non-Secure	OK
14 NRF_PWM2		Non-Secure	OK
15 NRF_PWM3		Non-Secure	OK
16 NRF_IPC		Non-Secure	OK
17 NRF_VMC		Non-Secure	OK
18 NRF_FPU		Non-Secure	OK
19 NRF_EGU1		Non-Secure	OK
20 NRF_EGU2		Non-Secure	OK
21 NRF_GPIOTE1		Non-Secure	OK

SPM: NS image at 0xc000
SPM: NS MSP at 0x20023b68
SPM: NS reset vector at 0xe325
SPM: prepare to jump to Non-Secure image.
bsdlib irrecoverable error: 3
ASSERTION FAIL [0] @ ../src/main.c:23
***** Kernel Panic! *****
Current thread ID = 0x20021a80
Faulting instruction address = 0x217c8
AT+CFUN?
***** Booting Zephyr OS v1.14.99-ncs2 *****
Flash region		Domain		Permissions
00 0x00000 0x08000 	Secure		rwxl
01 0x08000 0x10000 	Non-Secure	rwxl
02 0x10000 0x18000 	Non-Secure	rwxl
03 0x18000 0x20000 	Non-Secure	rwxl
04 0x20000 0x28000 	Non-Secure	rwxl
05 0x28000 0x30000 	Non-Secure	rwxl
06 0x30000 0x38000 	Non-Secure	rwxl
07 0x38000 0x40000 	Non-Secure	rwxl
08 0x40000 0x48000 	Non-Secure	rwxl
09 0x48000 0x50000 	Non-Secure	rwxl
10 0x50000 0x58000 	Non-Secure	rwxl
11 0x58000 0x60000 	Non-Secure	rwxl
12 0x60000 0x68000 	Non-Secure	rwxl
13 0x68000 0x70000 	Non-Secure	rwxl
14 0x70000 0x78000 	Non-Secure	rwxl
15 0x78000 0x80000 	Non-Secure	rwxl
16 0x80000 0x88000 	Non-Secure	rwxl
17 0x88000 0x90000 	Non-Secure	rwxl
18 0x90000 0x98000 	Non-Secure	rwxl
19 0x98000 0xa0000 	Non-Secure	rwxl
20 0xa0000 0xa8000 	Non-Secure	rwxl
21 0xa8000 0xb0000 	Non-Secure	rwxl
22 0xb0000 0xb8000 	Non-Secure	rwxl
23 0xb8000 0xc0000 	Non-Secure	rwxl
24 0xc0000 0xc8000 	Non-Secure	rwxl
25 0xc8000 0xd0000 	Non-Secure	rwxl
26 0xd0000 0xd8000 	Non-Secure	rwxl
27 0xd8000 0xe0000 	Non-Secure	rwxl
28 0xe0000 0xe8000 	Non-Secure	rwxl
29 0xe8000 0xf0000 	Non-Secure	rwxl
30 0xf0000 0xf8000 	Non-Secure	rwxl
31 0xf8000 0x100000 	Non-Secure	rwxl
Non-secure callable region 0 placed in flash region 0 with size 32.


SRAM region		Domain		Permissions
00 0x00000 0x02000	Secure		rwxl
01 0x02000 0x04000	Secure		rwxl
02 0x04000 0x06000	Secure		rwxl
03 0x06000 0x08000	Secure		rwxl
04 0x08000 0x0a000	Secure		rwxl
05 0x0a000 0x0c000	Secure		rwxl
06 0x0c000 0x0e000	Secure		rwxl
07 0x0e000 0x10000	Secure		rwxl
08 0x10000 0x12000	Non-Secure	rwxl
09 0x12000 0x14000	Non-Secure	rwxl
10 0x14000 0x16000	Non-Secure	rwxl
11 0x16000 0x18000	Non-Secure	rwxl
12 0x18000 0x1a000	Non-Secure	rwxl
13 0x1a000 0x1c000	Non-Secure	rwxl
14 0x1c000 0x1e000	Non-Secure	rwxl
15 0x1e000 0x20000	Non-Secure	rwxl
16 0x20000 0x22000	Non-Secure	rwxl
17 0x22000 0x24000	Non-Secure	rwxl
18 0x24000 0x26000	Non-Secure	rwxl
19 0x26000 0x28000	Non-Secure	rwxl
20 0x28000 0x2a000	Non-Secure	rwxl
21 0x2a000 0x2c000	Non-Secure	rwxl
22 0x2c000 0x2e000	Non-Secure	rwxl
23 0x2e000 0x30000	Non-Secure	rwxl
24 0x30000 0x32000	Non-Secure	rwxl
25 0x32000 0x34000	Non-Secure	rwxl
26 0x34000 0x36000	Non-Secure	rwxl
27 0x36000 0x38000	Non-Secure	rwxl
28 0x38000 0x3a000	Non-Secure	rwxl
29 0x3a000 0x3c000	Non-Secure	rwxl
30 0x3c000 0x3e000	Non-Secure	rwxl
31 0x3e000 0x40000	Non-Secure	rwxl

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_TWIM2		Non-Secure	OK
07 NRF_SPIM3		Non-Secure	OK
08 NRF_TIMER0		Non-Secure	OK
09 NRF_TIMER1		Non-Secure	OK
10 NRF_TIMER2		Non-Secure	OK
11 NRF_SAADC		Non-Secure	OK
12 NRF_PWM0		Non-Secure	OK
13 NRF_PWM1		Non-Secure	OK
14 NRF_PWM2		Non-Secure	OK
15 NRF_PWM3		Non-Secure	OK
16 NRF_IPC		Non-Secure	OK
17 NRF_VMC		Non-Secure	OK
18 NRF_FPU		Non-Secure	OK
19 NRF_EGU1		Non-Secure	OK
20 NRF_EGU2		Non-Secure	OK
21 NRF_GPIOTE1		Non-Secure	OK

SPM: NS image at 0xc000
SPM: NS MSP at 0x20023b68
SPM: NS reset vector at 0xe325
SPM: prepare to jump to Non-Secure image.
bsdlib irrecoverable error: 3
ASSERTION FAIL [0] @ ../src/main.c:23
***** Kernel Panic! *****
Current thread ID = 0x20021a80
Faulting instruction address = 0x217c8

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Håkon Alseth — Thu, 04 Jul 2019 14:16:38 GMT

I think we'll need to check your design/schematic. Could you create a new private case? (I guess you do not want to share your design with the rest of the world)

Link to this case, so that the history is kept 🙂

It might be handled by one of my colleagues, as hardware isn't my strongest feature.

Kind regards,

Håkon

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Thu, 04 Jul 2019 14:09:45 GMT

Yes, my colleague has removed the reset button (in case it was a faulty button or there was an layout errors with the button SMT pads) and multi-metered around the nRESET line and there doesn't seem to be any shorts to GND on that line. No short to ground and no short to any pins around the nRESET pin.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Håkon Alseth — Thu, 04 Jul 2019 14:03:08 GMT

If the enable pin is getting 3.3V, that is good. nRESET being at 0V is not so good. Have you checked if it is shorted to GND? Disconnect the battery, and check with a multimeter.

nRESET should go up towards VDD_IO a few ms after the chip is enabled.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Thu, 04 Jul 2019 13:52:24 GMT

Sure thing slomusti

devzone.nordicsemi.com/.../7888.merged.hex

EDIT: not sure why the uploaded file is getting a pre-fixed number, be sure to remove the "7888." from the filename. Apart from that, I downloaded it and flashed it from this post and it works on my DK. Hope it helps :)

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

slomusti — Thu, 04 Jul 2019 13:39:12 GMT

[quote userid="2115" url="~/f/nordic-q-a/49326/tz_nonsecure_func_ptr_create-spm-error-with-v1-0-0-for-nrf9160/196458"]Could you see if these two items resolve the issues seen in this thread?[/quote]

May I ask you to post at client compiled binary please as well for a test. I am trying to determine if compilation is an error on my end or something else.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Thu, 04 Jul 2019 13:36:10 GMT

Thanks for that information, so there isn't anything weird going on with NRESET, it must be something else on the board.

We are supplying VDD with a regulated 3V3 battery supply that is within the tolerances of the VDD line. ( we would like to keep 3V3 if possible as this would allow any device to remain active for longer before the battery supply voltage dips below 3.3V)

Our prototype PCB draws a small current i.e. a few milliamps (10mA), and both the NRESET and ENABLE lines were my first thought as possible areas of concern. From our examination, the LDO is outputting 3.31V (so pretty good LDO) which the ENABLE Pin is receiving. The NRESET was 0V so I thought something was wrong there but if the internal logic isn't getting initialised this would be 0V.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Håkon Alseth — Thu, 04 Jul 2019 13:16:57 GMT

Hi,

Sorry to hear that your prototype is refusing to communicate!

The nRESET signal will be kept low until the Power-on-reset (POR) logic internally releases it. This is normally some milliseconds after it has reached a valid voltage threshold, depending on the rise-time of your supply.

Does the PCB draw any current from the battery?

Have you checked the voltage level on the ENABLE pin?

Kind regards,

Håkon

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Thu, 04 Jul 2019 12:15:05 GMT

Hi again Håkon,

Thanks for the information.

1. This seems to have solved the issue. Funnily enough, I actually had that version of the GCC compiler on my mac in case it was ever needed for this occurance.

2. I was running the 10.2.1 version of nrfjprog as I updated everything yesterday to get the modem firmware onto the DK.

I can now report that the FW build and flashes onto the device correctly for me now with the GCC compiler change.

***** Booting Zephyr OS v1.14.99-ncs2 *****
Flash region		Domain		Permissions
00 0x00000 0x08000 	Secure		rwxl
01 0x08000 0x10000 	Non-Secure	rwxl
02 0x10000 0x18000 	Non-Secure	rwxl
03 0x18000 0x20000 	Non-Secure	rwxl
04 0x20000 0x28000 	Non-Secure	rwxl
05 0x28000 0x30000 	Non-Secure	rwxl
06 0x30000 0x38000 	Non-Secure	rwxl
07 0x38000 0x40000 	Non-Secure	rwxl
08 0x40000 0x48000 	Non-Secure	rwxl
09 0x48000 0x50000 	Non-Secure	rwxl
10 0x50000 0x58000 	Non-Secure	rwxl
11 0x58000 0x60000 	Non-Secure	rwxl
12 0x60000 0x68000 	Non-Secure	rwxl
13 0x68000 0x70000 	Non-Secure	rwxl
14 0x70000 0x78000 	Non-Secure	rwxl
15 0x78000 0x80000 	Non-Secure	rwxl
16 0x80000 0x88000 	Non-Secure	rwxl
17 0x88000 0x90000 	Non-Secure	rwxl
18 0x90000 0x98000 	Non-Secure	rwxl
19 0x98000 0xa0000 	Non-Secure	rwxl
20 0xa0000 0xa8000 	Non-Secure	rwxl
21 0xa8000 0xb0000 	Non-Secure	rwxl
22 0xb0000 0xb8000 	Non-Secure	rwxl
23 0xb8000 0xc0000 	Non-Secure	rwxl
24 0xc0000 0xc8000 	Non-Secure	rwxl
25 0xc8000 0xd0000 	Non-Secure	rwxl
26 0xd0000 0xd8000 	Non-Secure	rwxl
27 0xd8000 0xe0000 	Non-Secure	rwxl
28 0xe0000 0xe8000 	Non-Secure	rwxl
29 0xe8000 0xf0000 	Non-Secure	rwxl
30 0xf0000 0xf8000 	Non-Secure	rwxl
31 0xf8000 0x100000 	Non-Secure	rwxl
Non-secure callable region 0 placed in flash region 0 with size 32.


SRAM region		Domain		Permissions
00 0x00000 0x02000	Secure		rwxl
01 0x02000 0x04000	Secure		rwxl
02 0x04000 0x06000	Secure		rwxl
03 0x06000 0x08000	Secure		rwxl
04 0x08000 0x0a000	Secure		rwxl
05 0x0a000 0x0c000	Secure		rwxl
06 0x0c000 0x0e000	Secure		rwxl
07 0x0e000 0x10000	Secure		rwxl
08 0x10000 0x12000	Non-Secure	rwxl
09 0x12000 0x14000	Non-Secure	rwxl
10 0x14000 0x16000	Non-Secure	rwxl
11 0x16000 0x18000	Non-Secure	rwxl
12 0x18000 0x1a000	Non-Secure	rwxl
13 0x1a000 0x1c000	Non-Secure	rwxl
14 0x1c000 0x1e000	Non-Secure	rwxl
15 0x1e000 0x20000	Non-Secure	rwxl
16 0x20000 0x22000	Non-Secure	rwxl
17 0x22000 0x24000	Non-Secure	rwxl
18 0x24000 0x26000	Non-Secure	rwxl
19 0x26000 0x28000	Non-Secure	rwxl
20 0x28000 0x2a000	Non-Secure	rwxl
21 0x2a000 0x2c000	Non-Secure	rwxl
22 0x2c000 0x2e000	Non-Secure	rwxl
23 0x2e000 0x30000	Non-Secure	rwxl
24 0x30000 0x32000	Non-Secure	rwxl
25 0x32000 0x34000	Non-Secure	rwxl
26 0x34000 0x36000	Non-Secure	rwxl
27 0x36000 0x38000	Non-Secure	rwxl
28 0x38000 0x3a000	Non-Secure	rwxl
29 0x3a000 0x3c000	Non-Secure	rwxl
30 0x3c000 0x3e000	Non-Secure	rwxl
31 0x3e000 0x40000	Non-Secure	rwxl

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_TWIM2		Non-Secure	OK
07 NRF_SPIM3		Non-Secure	OK
08 NRF_TIMER0		Non-Secure	OK
09 NRF_TIMER1		Non-Secure	OK
10 NRF_TIMER2		Non-Secure	OK
11 NRF_SAADC		Non-Secure	OK
12 NRF_PWM0		Non-Secure	OK
13 NRF_PWM1		Non-Secure	OK
14 NRF_PWM2		Non-Secure	OK
15 NRF_PWM3		Non-Secure	OK
16 NRF_IPC		Non-Secure	OK
17 NRF_VMC		Non-Secure	OK
18 NRF_FPU		Non-Secure	OK
19 NRF_EGU1		Non-Secure	OK
20 NRF_EGU2		Non-Secure	OK
21 NRF_GPIOTE1		Non-Secure	OK

SPM: NS image at 0xc000
SPM: NS MSP at 0x20023b68
SPM: NS reset vector at 0xe325
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS v1.14.99-ncs2 *****
The AT host sample started
AT
OK
AT+CGMR
mfw_nrf9160_1.0.0
OK

One question I have Håkon that isn't related to this but has us a little stumped.

We have built up our first prototype for the nRF9160 but are not able to communicate to it. Both JLink and the nRF Programmer can't seem to detect the core.

We have run a multi-meter around the board and everything seems to be getting supplied the power it needs as per the OPS guidleines. We have noticed that the NRESET line is 0V. From the OPS we know that there is an internal pull up resistor to VDD on the NRESET pin and from metering the DK we know that there is 2V on the reset button for the pca10090. Is the NRESET pin supplied with voltage from the moment the VDD line is supplied or does the NRESET line only get supplied Voltage after the core have been initialised with FW. Just trying to figure out if we have an issue with VDD being supplied with power as we can't see under the SiP.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Håkon Alseth — Thu, 04 Jul 2019 09:18:57 GMT

Hi,

There seems to be two issues that might be related in this thread:

1. TrustZone defines not working with GCC 6 or GCC 8. We are aware of this, and it is reported internally, but for now; please use GCC 7 (2018-Q2). GCC 8 has had other issues, like linking errors on the windows platform, so it has been ruled out for now.

2. nrfjprog v10.1.1 has an issue where it does not properly do a sectorerase on nRF9160 in certain corners (which ninja/west calls in the background). This should be fixed with the latest version v10.2.1, available for download here: https://www.nordicsemi.com/?sc_itemid=%7B56868165-9553-444D-AA57-15BDE1BF6B49%7D

Could you see if these two items resolve the issues seen in this thread?

Kind regards,

Håkon

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Eirik Aa — Thu, 04 Jul 2019 09:16:16 GMT

When you run west update you need to remove, chackin or reset your changes to the reposetories or the git checkout (during west update) will fail and you will have an inconsistent SDK setup at your machine.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Eirik Aa — Thu, 04 Jul 2019 09:13:27 GMT

I am already using the 'gcc-arm-none-eabi-7-2018-q2-update' and are having the same problem.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

Eirik Aa — Thu, 04 Jul 2019 09:10:00 GMT

***** Booting Zephyr OS v1.14.99-ncs2 *****
Flash region            Domain          Permissions
00 ***** Hardware exception *****
Current thread ID = 0x20001870
Faulting instruction address = 0x30100
Fatal fault in ISR! Spinning...

I have the same error... ISR ( slomusti ) this is with your hex file

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

DevinCallahan — Wed, 03 Jul 2019 20:55:59 GMT

I had to change toolchain versions when I updated to v1.0.0. I was getting the same error when using "gcc-arm-none-eabi-8-2018-q4-major" as the toolchain. The "nRF Connect v3.0.0 -Getting Started Assistant" app was updated at some point, and the toolchain it says to install is now "gcc-arm-none-eabi-7-2018-q2-update". When I switched to that it started working. Though all of this is on Linux, the toolchain world may be different for mac.

I think Arm added handling for a new intrinsic related to the TrustZone stuff.

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

slomusti — Wed, 03 Jul 2019 20:53:23 GMT

No idea about hte error, but that may as well be the error I am getting but not seeing due to some baudrate problem. Give this at client fw a go and please let me knowdevzone.nordicsemi.com/.../at_5F00_client_2D00_build_5F00_nrf9160_5F00_pca10090ns_2D00_V1_5F00_0_5F00_0_2D00_merged.hex if it works for you.

EDIT: The above firmware is known not to work, see below for answers!

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093 — Wed, 03 Jul 2019 16:10:13 GMT

Yes I did this as well, fresh install of the repos, west update, git checkout and pip3 the 3 required python module scripts as in the 'Getting Started Assistant' but it still didn't work :/

Do you happen to have at_client's merged.hex? The asset_tracker won't work on my DK as I have no NB-IoT network in my current location (and the NB-IoT network I do have can't use the Dynamic Amazon IP address the asset_tracker needs for nRF Cloud 😅) but the at_client would allow me to test the modem firmware update in the mean time.

EDIT:

Oh dear, I get an immediate hardware fault with that hex file, and that's during the boot up information, not the main application. :/

***** Booting Zephyr OS v1.14.99-ncs2 *****
Flash region		Domain		Permiss***** Hardware exception *****
Current thread ID = 0x20001870
Faulting instruction address = 0x30100
Fatal fault in ISR! Spinning...

RE: TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

slomusti — Wed, 03 Jul 2019 16:05:18 GMT

I have managed to build 1.0.0 by updating the branch and west and pip3 with latest requirements on Ubuntu. While this is not particularly helpful for your issue, it does mean it is buildable. Attaching a built asset tracker firmware if you wish to test things with it if that helps. I face the following issue with it: https://devzone.nordicsemi.com/f/nordic-q-a/49328/nrf91-sdk-v1-0-0-at-command-baud-problem devzone.nordicsemi.com/.../build_5F00_nrf9160_5F00_pca10090ns_2D00_v1_5F00_0_5F00_0_2D00_merged.hex