Simple Question About Memory Map and Region

[MANGO]

Hi, this is kind of a basic question.

So please forgive me if this is too easy...

This picture is from nRF51822_PS_3.1.pdf.

Also these pictures is from the nRF51_Series_Reference_manual v3.0.pdf

==1. The SRAM has the data.

Then what's inside the RAM where the address at 0x6000 0000 to 0xA000 0000 ?

If its has different things case by case, then what usually this RAM holds?

==2. The RAM where the address at 0x6000 0000 to 0xA000 0000, is a DRAM?

Or this RAM dropped a "S'?

==3. At the nRF51822_PS_3.1.pdf page 64, it says that

"The flash memory is organized in 256 byte rows starting at CODE and UICR start address.".

I use pstorage functions provided from the SDK 7.2 with SoftDevice S110.

When I save data using pstorage_store or pstorage_update function,

(skipping the cmd_queue stuffs)

the data are saved at "reserved" places in memory map in between

Code, FICR, and UICR?

Edited : Added Memory Screen when debugging

-Regards, Mango922

[RK]

1. Nothing. That picture is the generic Cortex-M0 diagram which shows the possible blocks on a Cortex-M0 system. The nrf51 manual shows what blocks are actually implemented. So there's nothing up at 0x60000000-0xA0000000.

2. The data is stored in the topmost flash pages of the CODE region, ie on 256k flash chips from 0x3fc00 or 0x3f800 or lower if you want more than a couple of kb of storages. Or if there's a bootloader installed at the top, just below that. pstorage comes out of your flash memory allocation.

[MANGO]

Oh, thanks! At no. 1, I was quite confused that one picture was written "reserved"

but the other was written as "RAM". No wonder why the picture gave me confusion.

I have checked the sd_flash_write function at pstorage.c.

It calculates the page number, so you're right about writing directly at flash memory.

/********************/

Actually, my problem is that without using pstorage_load, I want to check the flash memory

directly when I'm debugging. I use IAR 7.1 and J-Link Edu.

I had a problem that when I call pstorage_load, it sometimes read other blocks instead.

So, in short, I can't check the flash memory

when I'm looking at the memory screen right?

(I'll add a picture about the "memory screen" at the question.)

Then is there a way to check the flash memory while debugging with IAR, J-Link Commander, or etc?