Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Nguyen Hoan Hoang — Mon, 18 Feb 2019 23:40:33 GMT

Is it connectable ? When you scan it with nRFConnect, does it shows as connectable ? May be something you missed in the config.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Lorenzo — Thu, 14 Feb 2019 17:01:49 GMT

Hi Nguyen,

thanks for your help! Do you mean APP_ADV_DURATION? Cause I already had it in 10 ms. However, apart from strange behaviour, the main problem is that I cannot connect, while I always see correct advertising packets. I will continue debug asap.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

awneil — Thu, 14 Feb 2019 15:43:45 GMT

[quote userid="2121" url="~/f/nordic-q-a/43660/strange-behaviour-migrating-from-sdk-15-0-0-to-sdk-15-2-0/170865"]I had a look at SDK v15.0 and SDK v15.2 and saw no difference regarding the advertising module.[/quote][quote userid="3482" url="~/f/nordic-q-a/43660/strange-behaviour-migrating-from-sdk-15-0-0-to-sdk-15-2-0/171190"]in 15.2, ADV timeout value was changed to 10ms instead of sec[/quote]

That seems a pretty significant difference to me!

😮

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Nguyen Hoan Hoang — Thu, 14 Feb 2019 15:07:10 GMT

Is there a advertisement timeout value in your code ? in 15.2, ADV timeout value was changed to 10ms instead of sec.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Hung Bui — Thu, 14 Feb 2019 14:21:19 GMT

Yes, but you need to explore the "info" memory and then find the file name and line number of the code that asserted.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Lorenzo — Thu, 14 Feb 2019 11:19:10 GMT

Hi Hung,

have you seen my reply above with the attached screenshot of error codes?

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Hung Bui — Thu, 14 Feb 2019 09:40:03 GMT

I don't think it's the issue with Flash and RAM configuration (since you are not updating with major softdevice change). Please try to debug. You can follow this guide. We need to know what exactly which line of code at which file threw the assertion.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Lorenzo — Wed, 13 Feb 2019 15:09:05 GMT

Checked the headers location and they're fine.

Now I've only advertising and LED blinking to show that the board is alive.

I've tried to connect and the first attempt have been positive (but just for a couple of seconds).

Second attempt suddenly gave this error:

What could it be?

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Hung Bui — Wed, 13 Feb 2019 13:54:44 GMT

Correct, you just need to match that the header files you included in your project is from \components\softdevice\s132\headers of the SDK V15.2 and the softdevice you flash is v6.1

Please check why it's disconnected and which assert you have from the softdevice. Reducing your application functionality to the point that it only advertise and wait for a connection can help pinpoint the issue.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Lorenzo — Wed, 13 Feb 2019 13:48:11 GMT

Could it be that I've simply copy-pasted the RAM start address and size from previous project which used S132 v6.0?

Or is it that if those values were wrong nothing could work?

I had these values:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x26000

FLASH_SIZE=0x5a000

RAM_START=0x20004368

RAM_SIZE=0xbc98

But if I had to change them, I'd not know which values to put.

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Lorenzo — Wed, 13 Feb 2019 12:39:19 GMT

Hi Hung,

thanks for you answer. However, advertising_start() is not called before advertising_init(). I've tried to trick the issue by starting the timer before the call to advertising_init() (with advertising_start() being called after advertising_init() since the timer takes a while to expire) and it worked fine, but then the other connection problem remains, so there must be something more.

Your suggestion could be the solution, but I don't understand how should I "match the api header files", could you give just one example please? I thought developing with SDK 15.2 and flashing the S132 v6.1 to the board before flashing the firmware was sufficient, isn't it?

RE: Strange behaviour migrating from SDK 15.0.0 to SDK 15.2.0

Hung Bui — Wed, 13 Feb 2019 12:31:31 GMT

Hi Gino,

I had a look at SDK v15.0 and SDK v15.2 and saw no difference regarding the advertising module. It must be something else inside your application.

Maybe you would need to look for the use of m_adv_start_timer_id() in your code if it's started before the advertising module initialized or not.

Please note that SDK v15 use softdevice version 6.0 when the SDK v15.2 uses softdevice v6.1. You need to match the api header files to the softdevice you actually use on the board.