Fstorage read and write at SDK11

RE: Fstorage read and write at SDK11

Waqar Ahmed — Wed, 19 Apr 2017 11:37:58 GMT

i have compile your code but it only show at segger rtt only the start and erasing a flash page at adresss0x7900 .neither writing nor reading the data

RE: Fstorage read and write at SDK11

Stefan Birnir Sverrisson — Fri, 28 Oct 2016 08:41:01 GMT

If you call flash storage function from an interrupt handler you can not wait for the callback in the interrupt handler, because then you will block the callback which has the same priority. You need instead to call the flash storage function from main context. There are primarily two ways to do that. One way is to use the scheduler. Another way is to call the flash storage function conditionally in the main loop, where you only call it when a specific flag is true. Then you set that flag true in the interrupt handler (ancs interrupt handler)

RE: Fstorage read and write at SDK11

Ted — Fri, 28 Oct 2016 03:38:09 GMT

System seems halt when I call the function of fds_record_write from BLE ancs profile. Can I not access fstorage from BLE ancs profile? Is it correct? Do you know how to do it?

RE: Fstorage read and write at SDK11

emdi — Wed, 26 Oct 2016 10:55:46 GMT

I think the problem might be with your conversion from byte to words. The string "data: abcdef" is 12 characters long, plus the implicit string terminator character '\0', that's a total of 13 bytes. When you set length_words field of the chunk like this:

record_chunk.length_words = (sizeof(device_data)+1)/4;

My guess is that sizeof(device_data) will be 13 + 1 (which you add manually) / 4 equals to 3.5, which gets rounded down to 3, which is wrong since the string is 12 characters long but you need the 13th character (string terminator) to print correctly.

It works with "data abcdef" because that's one character shorter, thus 12 + 1 / 4 = 3,25 which gets rounded down to 3, which is right in this case because that's exactly the length of the string including the terminator character (implicit).

If you want approximate you should add 3. I would try like this: length_words = (sizeof(data) + 3) / 4

RE: Fstorage read and write at SDK11

Ted — Wed, 26 Oct 2016 10:50:46 GMT

Write hexadecimal code semms successfully. But write ASCII string include specail characters will cause fail. Can you test it with special characters like "~!@#$%^&*()_+-="?

RE: Fstorage read and write at SDK11

Ted — Wed, 26 Oct 2016 09:13:07 GMT

I print it by hexadecimal code, because it cannot print non-ASCII data. If I set the second data to 0x2222="data: abcdef". I got the message as follows. Writing Record ID = 1 set write_flag Writing Record ID = 2 set write_flag Writing Record ID = 3 set write_flag Start searching... Found Record ID = 1 Tablet1 Found Record ID = 2 Data = ?? Found Record ID = 3 Data = 0x0000001a

If I set the second data to 0x2222="data abcdef". I got the message as follows. Writing Record ID = 1 set write_flag Writing Record ID = 2 set write_flag Writing Record ID = 3 set write_flag Start searching... Found Record ID = 1 Tablet1 Found Record ID = 2 Data = data abcdef Found Record ID = 3 Data = 0x0000001a

The two strings are only different at a character of ':' .ble_pstorge_1.c

RE: Fstorage read and write at SDK11

Stefan Birnir Sverrisson — Wed, 26 Oct 2016 08:39:18 GMT

There is fstorage example code available here for SDK 10. There is also available simple fds code here for SDK 11. Discussion on the difference between pstorage, fstorage and fds is briefly discussed here

Update 26.10.2016 Below is fstorage example for SDK 11.0.0. The example writes two words to flash and then reads the flash contents. Result is printed on UART (UART settings: 115200 BAUD, 8N1, hardware flow control disabled)

ble_app_template_with_fstorage_operations.zip

Update 2 26.10.2016 I attach another SDK 11.0.0 example with the following UART output

ble_app_template_with_fstorage_operations_ascii.zip

RE: Fstorage read and write at SDK11

emdi — Wed, 26 Oct 2016 07:20:00 GMT

You are printing it as a hex number instead of a string. If your string is null terminated, simply use %s in NRF_LOG_PRINT(). Something like this: char * p_data; p_data = flash_record.p_data; NRF_LOG_PRINTF("Data: %s\r\n", (uint32_t)p_data);

RE: Fstorage read and write at SDK11

Ted — Wed, 26 Oct 2016 03:28:06 GMT

It seems some wrong at the function of fds_record_write(). It cannot write special character like ASCII 0x21 to 0x2f etc. How to fix it if I say correctly?

RE: Fstorage read and write at SDK11

Ted — Wed, 26 Oct 2016 02:51:10 GMT

My source code at attach file.

print messages as follows: Writing Record ID = 1 set write_flag Writing Record ID = 2 set write_flag Writing Record ID = 3 set write_flag Start searching... Found Record ID = 1 Data = 0x6c626154 0x 317465 Found Record ID = 2 Data = 0x 8fb5 0x20002bf0 0xfffffff9 Found Record ID = 3 Data = 0x 1a

Second data (0x2222="data: abcdef") is always error. Can you guide me what it is?ble_pstorge.c

RE: Fstorage read and write at SDK11

emdi — Tue, 25 Oct 2016 12:50:13 GMT

I think you might want to use the 'fds' library for that. Have a look here: infocenter.nordicsemi.com/index.jsp

RE: Fstorage read and write at SDK11

Ted — Tue, 25 Oct 2016 09:48:25 GMT

Can the third parameter change to 26 (uint8_t)?