Wireless MCUのトピックRe: NVM broken with BLE

NVM broken with BLE

mateuszwielgos — Thu, 25 Jan 2018 14:55:09 GMT

I just updated my project to the newest maintenance release of KW41Z SDK (framework v. 5.3.3 -> 5.3.4, bluetooth v. 1.2.3 -> 1.2.4).

Whenever App_NvmWrite is called in order to save bond data to NVM, NvMoveToRam fails with gNVM_PointerOutOfRange_c. It appears that NVM pData RAM pointers are no longer valid, instead they are uninitialized (0xffffffff).

If I revert BLE middleware to 1.2.3 while keeping framework at 5.3.4, things do work okay, so I believe the issue is somewhere within BLE libs.

Can anyone replicate?

Re: NVM broken with BLE

stephanie_m — Wed, 07 Feb 2018 00:01:51 GMT

Hello,

I'm not quite sure the SDK version you are using, there was a new one on January 31st could you please help me download the new SDK and try to use it again?

If the issue persists let me know so I can investigate.

Regards,

Estephania

Re: NVM broken with BLE

mateuszwielgos — Wed, 07 Feb 2018 14:21:49 GMT

Hi Estephania,

I logged into the MCUXpresso SDK builder and according to it the newest release is "KSDK 2.2.0 (released 2018-01-19)". This is the one that I am trying to upgrade to.

Re: NVM broken with BLE

stephanie_m — Wed, 07 Feb 2018 21:25:22 GMT

Does this happen with any example you use? are you using developing your own application?

Regards,

Estephania

Re: NVM broken with BLE

mateuszwielgos — Tue, 13 Feb 2018 19:42:41 GMT

I examined my linker memory configuration and it contains errors, however, it somehow worked in the previous release.

user.ldt:

NV_STORAGE_SECTOR_SIZE = ( 2 * 1024 );
NV_STORAGE_MAX_SECTORS = (4);
NV_STORAGE_START_ADDRESS = ((0x0007FFFF) - ( 2 * 1024 ) + 1) - 1;
NV_STORAGE_END_ADDRESS = NV_STORAGE_START_ADDRESS - (NV_STORAGE_MAX_SECTORS * NV_STORAGE_SECTOR_SIZE) + 1;

.cproject:

Memory locations in user.ldt refer to space reserved for PROGRAM_FLASH, which is not right. I resized NVM_TABLE_FLASH and now all is good.