MPC5748G Flash Memory Remap

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MPC5748G Flash Memory Remap

Jump to solution
3,324 Views
aleksandar_zece
Contributor I

Hello.

I am working on a bootloader for DEVKIT-MPC5748G,

and have successfully implemented flash memory erase and program operations,

as well as starting the application firmware.

Now I would like to utilize flash memory remap options

in order to be able to have two memory "slots" for application firmware.
That way I can swap between them when I need to update and run new firmware.


I couldn't find any code examples for this, so I wrote it on my own

by looking at the Flash Memory Controller (PFLASH) section in the MCU's reference manual.

However, I can't seem to get the memory remap to work.

I tried to remap 2MB of memory at logical address 0x01000000 to physical address 0x01200000.

I also tried it with 256KB with the same addresses, which didn't work either.

Here's my source code:

// Initializes the flash remap.
static void bootFlashRemapInit()
{
    // Setup the remap logic and physical addresses,
    // per-master enable, and region size.
    PFLASH.PFCRD[0].Word0.R = 0x01200000;
    PFLASH.PFCRD[0].Word1.R = 0x01000000;
    PFLASH.PFCRD[0].Word2.R = 0xffff0015;

    // Enable remap descriptor 0.
    PFLASH.PFCRDE.R = 0xffff0000;

    // Enable instruction remap.
    PFLASH.PFCRCR.B.IRMEN = 1;
}

// Enables the flash remap.
static void bootFlashRemapEnable()
{
    PFLASH.PFCRCR.B.GRMEN = 1;
}

// Disables the flash remap.
static void bootFlashRemapDisable()
{
    PFLASH.PFCRCR.B.GRMEN = 0;
}

Obviously, I call bootFlashRemapInit to initialize the remap, and bootFlashRemapEnable to enable it.

I found out in the errata for my chip mask (https://www.nxp.com/docs/en/errata/MPC5748G_0N78S.pdf)

that this chip has a known problem when trying to remap flash memory in address range 0x00F90000-0x00FBFFFF.

This is not the address range I am working with,

but it got me thinking that there might be problems with the flash addresses I am working with as well.

Does anybody have an idea of what the problem might be?

Are there errors in my source code, or could the chip itself have an error?

Thanks in advance!

Labels (1)
0 Kudos
Reply
1 Solution
2,924 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

there's important note in the reference manual:

pastedImage_1.png

That means you should use mirrored address like this:

PFLASH.PFCRD[0].Word0.R = 0x09200000;
PFLASH.PFCRD[0].Word1.R = 0x01000000;

Then you will see content of address 0x01000000 at address 0x09200000 (not at 0x01200000 - this remains unchanged). The rest of your initialization seems to be correct.

Regards,

Lukas

View solution in original post

0 Kudos
Reply
5 Replies
2,925 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

there's important note in the reference manual:

pastedImage_1.png

That means you should use mirrored address like this:

PFLASH.PFCRD[0].Word0.R = 0x09200000;
PFLASH.PFCRD[0].Word1.R = 0x01000000;

Then you will see content of address 0x01000000 at address 0x09200000 (not at 0x01200000 - this remains unchanged). The rest of your initialization seems to be correct.

Regards,

Lukas

0 Kudos
Reply
2,924 Views
aleksandar_zece
Contributor I

Hey Lukas, thank you very much for answering! I definitely overlooked this.

However, this still didn't solve my problem. The remap is still not working, I'm simply always accessing the original location and not the remapped one.

In the meantime, I made a small test program in S32 Design Studio for Power Architecture, for MPC5748G, which has two functions that blink different LEDs, and are placed at two distinct memory locations.

Here's the source code:

#include "derivative.h" /* include peripheral declarations */

#define PA10 10
#define PA7 7

extern void xcptn_xmpl(void);

__attribute__ ((section(".text1"))) void blink1()
{
    uint32_t i;

    // Initialize DS4 LED.
    SIUL2.MSCR[PA10].B.SSS = 0;
    SIUL2.MSCR[PA10].B.OBE = 1;
    SIUL2.MSCR[PA10].B.IBE = 0;
    SIUL2.GPDO[PA10].B.PDO_4n = 1;

    while (1)
    {
        for (i = 0; i < 100000; i++);
        // Blink DS4 LED.
        SIUL2.GPDO[PA10].B.PDO_4n = !SIUL2.GPDO[PA10].B.PDO_4n;
    }
}

__attribute__ ((section(".text2"))) void blink2()
{
    uint32_t i;

    // Initialize DS5 LED.
    SIUL2.MSCR[PA7].B.SSS = 0;
    SIUL2.MSCR[PA7].B.OBE = 1;
    SIUL2.MSCR[PA7].B.IBE = 0;
    SIUL2.GPDO[PA7].B.PDO_4n = 1;

    while (1)
    {
        for (i = 0; i < 100000; i++);
        // Blink DS5 LED.
        SIUL2.GPDO[PA7].B.PDO_4n = !SIUL2.GPDO[PA7].B.PDO_4n;
    }
}

int main(void)
{
    // Configure and enable interrupts.
    xcptn_xmpl();

    // Setup the remap logic and physical addresses,
    // per-master enable, and region size.
    PFLASH.PFCRD[0].Word0.R = 0x09100000; // logical address
    PFLASH.PFCRD[0].Word1.R = 0x01200000; // physical address
    PFLASH.PFCRD[0].Word2.R = 0xffff0012; // 256KB region

    // Enable remap descriptor 0.
    PFLASH.PFCRDE.R = 0xffff0000;

    // Enable instruction remap.
    PFLASH.PFCRCR.B.IRMEN = 1;

    // Enable flash remap.
    PFLASH.PFCRCR.B.GRMEN = 1;

    blink1();
    blink2(); // Won't be called but placed here so it would be included in the output file.

    while (1);
}

I also added the needed program sections to the flash linker file

...

MEMORY
{

    flash_rchw : org = 0x00FA0000, len = 0x4
    cpu0_reset_vec : org = 0x00FA0000+0x10, len = 0x4
    cpu1_reset_vec : org = 0x00FA0000+0x14, len = 0x4
    cpu2_reset_vec : org = 0x00FA0000+0x04, len = 0x4

    m_text : org = 0x01000000, len = 256K
    m_text1 : org = 0x01100000, len = 256K
    m_text2 : org = 0x01200000, len = 256K
    m_data : org = 0x40000000, len = 768K
}

...

.text1 :
{
    *(.text1)
} > m_text1

.text2 :
{
    *(.text2)
} > m_text2

...

I've checked the generated .srec file, and the functions are indeed placed at the desired locations.

If I've understood it correctly, this code should call the blink2 function instead of blink1, since the memory has been remapped so that logical address 0x01100000 will point to the physical address 0x01200000. It still doesn't work, and always calls the blink1 function. I've tried setting the 27th bit (e.g. 0x09100000) in both the logical and physical addresses on or off, but none of the combinations work. And it's not that the execution will jump to an unprogrammed area in the flash memory, it just always accesses the original, unmapped location of 0x01100000.

Can you see any problems in this example? Maybe something else I forgot to initialize?

Thank you very much for your time.

0 Kudos
Reply
2,924 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

as I wrote, the remapping is visible only in mirrored flash address space. Normal address space remains unchanged after remapping. That means your code must be compiled to execute from mirrored flash address space (if it is not position independent code). And that also means you can't execute that code from normal address space.

Because there were more questions about this, I shared simple example here to show effect of the remapping:

https://community.nxp.com/docs/DOC-342943 

Regards,

Lukas

0 Kudos
Reply
2,924 Views
aleksandar_zece
Contributor I

Hey Lukas, thank you very much, again!

Sorry I didn't answer earlier, I couldn't return to working on this problem until recently.

Now I've done exactly as you said, compiling the code to execute from the mirrored flash address space,

and it works like a charm!

Thanks for all your help! You've saved me a lot of time and probably spared me a lot of frustration. :smileyhappy:

0 Kudos
Reply
2,188 Views
FAISAL0323
Contributor II

May I know how to compile the code to execute from the mirrored flash address space? What does it actually mean?

0 Kudos
Reply