I GOT ERROR 11 when fds_init();

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Tue, 21 Apr 2020 13:59:31 GMT

I'm not sure which issue you fixed, I tested both ways in the project you uploaded and they both seem to work fine here.

RE: I GOT ERROR 11 when fds_init();

Aku — Tue, 21 Apr 2020 01:19:01 GMT

I just fix the problem in a MYSTERIOS way

just moved the fds initial up

AND IT WORKS

WHY????

i'm so confused, is this a bug?

since another IDE has no problem on the original code , and the original code can work on nrf52dk

by the way i'm using SEGGER Embedded Studio for ARM

and i use internal rtc

RE: I GOT ERROR 11 when fds_init();

Aku — Tue, 21 Apr 2020 00:32:32 GMT

I just try to use my nrf52dk and it worked.......

and if i use my own custom board it failed

but why?

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Mon, 20 Apr 2020 14:49:09 GMT

Hi,

I do not see error 11 in the second project, but I do see error 3 (FDS_ERR_UNALIGNED_ADDR) from call to fds_record_write() in kls_fds_write(). You need to align the data that you pass to this function. Since wait_for_fds_ready() is called regardless of the error returned from fds_record_write(), the application will get stuck here when no write has been scheduled.

You can solve the error by adding align-attribute to the array definitions:

uint8_t __attribute__((aligned(4))) default_pwd[9] = { 0xAA,0xA2,0x05,0x48,0x59,0x50,0x52,0x4f }; //HYPRO
uint8_t __attribute__((aligned(4))) default_record_interval[5] = { 0xBB,0XB1,0x01,0x14,0x00 }; //20
uint8_t __attribute__((aligned(4))) default_device_name[7] = { 0xCC,0xC3,0x04,0x47,0x54,0x30,0x36 };//GT06

Best regards,
Jørgen

RE: I GOT ERROR 11 when fds_init();

Aku — Mon, 20 Apr 2020 09:17:24 GMT

this is the origin code i got

devzone.nordicsemi.com/.../0420.zip

and i put it to a clean ble_app_template in SDK15.3

it may loss someting to include

after i fix it,i got it compile as below

devzone.nordicsemi.com/.../6685.ble_5F00_app_5F00_template.rar

and i'm using nrf52832 on my custom board

Thank you

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Mon, 20 Apr 2020 08:55:11 GMT

Different compilers/linkers may generate different sized hex-files for the same code, it depends on how it translates the high-level code into machine code and how optimized the code is.

If there is a big difference in size, it may be that the softdevice is merged with one file, but not with the other?

Can you upload the full project, for us to reproduce and debug this issue?

RE: I GOT ERROR 11 when fds_init();

Aku — Mon, 20 Apr 2020 04:04:21 GMT

the original code is not compiled by segger and worked fine

it was compile by visual stidio with visualgdb

and i am asked to edit some functions

but i dont have visual stidio and visualgdb

so i try segger and it show me these errors

I can see that my hex is much smaller than the original one

but why?

the code are same

RE: I GOT ERROR 11 when fds_init();

Aku — Fri, 17 Apr 2020 00:56:41 GMT

And here are what i program originally,bootloader(with setting) and hex from my main code

devzone.nordicsemi.com/.../boot_5F00_settingV1.hex

devzone.nordicsemi.com/.../origin.hex

RE: I GOT ERROR 11 when fds_init();

Aku — Fri, 17 Apr 2020 00:52:13 GMT

1. I tried 3,6,20 ,and only found that the address had changed

2. I always run erase all before i write

3. I will upload it below

thanks

devzone.nordicsemi.com/.../nRF_5F00_Connect_5F00_Programmer_5F00_1587084499777.hex

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Thu, 16 Apr 2020 13:29:29 GMT

To me they look similar, just one section is gone. What value did you set FDS_VIRTUAL_PAGES_RESERVED to?

If you do not know what data is stored in flash, I would recommend you to run an erase all operation to clear the flash. Alternatively, if you could use the "Save to file" option in nRF Connect programmer app and upload the file, along with information about the ranges of all regions that show up in the window, that could help us identify what is stored in your flash.

RE: I GOT ERROR 11 when fds_init();

Aku — Thu, 16 Apr 2020 03:22:58 GMT

i change the FDS_VIRTUAL_PAGES_RESERVED and the problem is still there.

but i found that the address of the three 8 byte region changed

so are these three region my FDS_VIRTUAL_PAGES?

why are they only 8 byte?

i think they should be 1024?

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Wed, 15 Apr 2020 09:36:47 GMT

Yes, that is the equivalent function in nRF Connect programmer app.

It looks like you have multiple data blocks located at the top of your flash. FDS will try to initialize itself at the end (top) of the flash, or right below the bootloader if that is present. If you want to store other data, you can add an offset of reserved pages between the end of flash/bootloader and where FDS is initialized by setting FDS_VIRTUAL_PAGES_RESERVED.

RE: I GOT ERROR 11 when fds_init();

Aku — Wed, 15 Apr 2020 02:23:37 GMT

Is 'nrfjprog -e' command same as Erase all in nrfconnect programmer?

and it seems that there is much space remain in flash

by the way i set FDS_VIRTUAL_PAGES 3

FDS_VIRTUAL_PAGE_SIZE 1024

FDS_VIRTUAL_PAGES_RESERVED 0

actually i just want to save device name and some settings that user can set in app

may not exceed 100byte

RE: I GOT ERROR 11 when fds_init();

Jørgen Holmefjord — Tue, 14 Apr 2020 15:50:25 GMT

Hi,

Error 11 corresponds to FDS_ERR_NO_PAGES, which means that fds_init cannot install the FDS file system because there is not enough room in the Flash. Have you tried erasing the entire flash using 'nrfjprog -e' command before running the example? Is your application taking up all the space in the flash?

Best regards,
Jørgen