SDK14.2 Secure DFU Timers

RE: SDK14.2 Secure DFU Timers

Hung Bui — Thu, 08 Feb 2018 10:15:03 GMT

We found it could be due to something wrong when "-flto" optimization is used in the compiler setting. Removing that gcc q4 2017 worked again.

gotthcha — Wed, 07 Feb 2018 16:24:13 GMT

With version 7 2017-q2-major it works fine too

gotthcha — Wed, 07 Feb 2018 15:53:17 GMT

Same issue for me. Used 7 2017-q4-major will downgrade now

schef — Mon, 15 Jan 2018 14:05:24 GMT

I have gcc version 7.2.1 and have the same issue. If i comment out app_timer_start it works.

Yanc — Thu, 11 Jan 2018 15:17:50 GMT

I faced another issue with armgcc 5.4. So I downgrade armgcc to 4.9.3 and all are fine.

Yanc — Thu, 11 Jan 2018 14:24:10 GMT

Hi Vincent,

Thank you for your information. It saves me much time.

I downloaded gcc-arm-none-eabi-5_4-2016q3 and it works now.

Vincent — Thu, 11 Jan 2018 14:04:31 GMT

Hi Yanc,

I just edited my post: I tried the same setup but with armgcc 5.4.1 & it seems to work fine !

Hopes it helps you

Yanc — Thu, 11 Jan 2018 13:51:26 GMT

My laptop is macOS 10.13.2
the compiler version is gcc-arm-none-eabi-7-2017-q4-major-mac
git clone latest micro-ecc from GitHub
nrfjprog version: 9.7.1, JLinkARM.dll version: 6.22c
flash softdevice s132_nrf52_5.0.0_softdevice.hex
The bootloader is blocked at app_timer_start -> timer_start_op_schedule -> timer_list_handler_sched -> NVIC_SetPendingIRQ

I also tested the bootloader_secure_ble example from nRF5-SDk-13.x and it works out of the box. I will download 14.1 and test it again

Hung Bui — Thu, 11 Jan 2018 13:37:55 GMT

The bootloare worked out of the box for me.

Could you let me know what exactly wrong with the app_timer_start() ? What was the return value ret_val when you call that function ?

Also please update the Soft device you use and the compiler you used.

Yanc — Thu, 11 Jan 2018 03:38:30 GMT

I faced same problem. My board is PCA10040. Does anyone have a workground?

Thanks