flash memory write/read

Evgeny Lunev

Other Parts Discussed in Thread: CC2540, CC2541

I use CC2540 KeyFob Demo Kit (CC2504 - 1.1.a).Development Environment - IAR 8.10.1 for 8051.

In my application I need to write and read substantial amount of information from /to flash memory (up to 100 kb).

I'm trying to use osal_snv_read() and osal_snv_write() functions.

While doing "write" in a cycle by call : osal_snv_write(id + i, len, pBuffer); "id" is incremented by one, "pBuffer" - pointer to array of 250 bytes,

only 3 calls return successfully (in overall 750 bytes written), subsequent calls retrun NV_OPER_FAILED and no data written to flash.

What I'm doing wrong (probably) and what is a best way to write data to non-volatile memory (flash).

over 14 years ago

0 kazola over 14 years ago

Guru 18625 points

Hi Evgeny,

have you take a look to:

http://e2e.ti.com/support/low_power_rf/f/538/t/142042.aspx

Please let me know.

0 Evgeny Lunev over 14 years ago in reply to kazola

Intellectual 475 points

Yes, I saw the post above, but it seemed to me a bit different - where "read" function was called and just once - I'm trying to "write" and it run smoothly 3 times.. if the two cases correlate it looks weird...

0 Evgeny Lunev over 14 years ago in reply to Evgeny Lunev

Intellectual 475 points

Anyway, changing in "hal_flash.c"

halDMADesc_t *ch = HAL_NV_DMA_GET_DESC();

to:

halDMADesc_t *ch = 0;

doesn't make any difference.

0 Javier Longares over 14 years ago in reply to Evgeny Lunev

Intellectual 300 points

Dear Evgeny Lunev,

May be you're not initialiting the token with the osal_nv_init function...

Best regards

---

www.javierlongares.com

www.javierlongares.com/arte-en-8-bits

0 Dirty Harry over 14 years ago in reply to Javier Longares

TI__Mastermind 19350 points

The osal_snv system available with the BLE stack gives less than 2KB of storage, and the BLE stack will be using some of that. So for 100 KB of storage, you will need to devise your own system of writing/reading the pages set aside for this, as well as erasing pages when the page is full.

FYI - the post mentioned above that is also asking about flash read/write is with respect to a proprietary system (not the BLE stack) that does not even have the osal_svn module.

0 Evgeny Lunev over 14 years ago in reply to Javier Longares

Intellectual 475 points

Dear Javier,

Here I would like to reiterate the question from about flash read/write

So the problem is: I call 3 times osal_snv_write() and

it completes with SUCCESS status, but 4 time it returns NV_OPER_FAILED.
I called that function explicitly osal_snv_init() before osal_snv_write func. (and anyway osal_snv_init() called during our app. initializing initiated)

Here exact peace of code:

static void flashMemoryWriteLong(uint8 page, uint8 length, void* pBuffer){
osal_snv_init();

osalSnvId_t id = page;
osalSnvLen_t len =length;
static uint8 resultWr = -1;

for(uint8 i = 0; i < 3; i++){
resultWr = osal_snv_write(id + i, len - i, pBuffer);
}

resultWr = osal_snv_write(3, len, pBuffer);

}

0 Evgeny Lunev over 14 years ago in reply to Dirty Harry

Intellectual 475 points

And along what lines would be the best way to implement such a system?

0 kazola over 14 years ago in reply to Evgeny Lunev

Guru 18625 points

Why don't you debug this code fragment and see what and where you are trying to write.

0 Evgeny Lunev over 13 years ago in reply to kazola

Intellectual 475 points

Hi,

I've tried the above read/write actions on the new CC2541 chip with BLE-254x-1.1b stack and problem still persists.

So, new release it seems doesn't change osal snv functions.

BR,

Evgeny.

Bluetooth®︎

Bluetooth forum

flash memory write/read