Memory Map for Msp430fr57xx Family

The device-specific datasheet is the best place to find the memory map, not the user's guide, because the different devices within a family have different memory sizes and so will have different maps. The 5xx user's guide table that you mentioned is a map for the F5438 device specifically (it is mentioned in the note above the table) - "This memory map represents the MSP430F5438 device. Though the address ranges differs from device to device, overall behavior remains the same." To really get the correct address ranges, you need to look at the datasheet.

What information is the FR57xx datasheet table missing that you were looking for? It seems to have the same information just formatted a little differently than the 5xx user's guide table.

Regards,

Katie

See attachment.  Page 1 is the f5529.  Page 2 is the fr5720 which is missing some info.

The FR57xx and F5529 are two vastly different parts with different features and very different memory sizes. Because the FR57xx has a smaller area of memory, it has more gaps in the address space (which is I think what you are pointing out). There is also no USB RAM because the part has no USB module, and the code memory isn't split into blanks because it is smaller (and it doesn't go past 0xFFFF into extended addressing space). There are differences in the two, but I don't think the FR57xx is really providing less information - the memory is just different than the F5529 and has different characteristics.

460822 said:

In addition, CCSv5 creates a .cmd file that contains:

    FRAM : origin = 0xF000, length = 0x0F80

The data sheet lists FRAM Main code memory ranging from 0xC200 -> 0xFF7F.  Any reason .cmd does not specify 0xC2000 -> 0xEFFF?

I'm assuming that is the linker cmd file for the FR5720? Please note that the datasheet lists the memory ranges for all device variants. 0xC200-0xFF7F is for the FR5739 and other devices in the family that have a larger memory. The FR5720 you can see in the same table, is listed to only have memory for 0xF000-0xFF7F - the linker file is device specific because of these memory differences (not same file for entire family). If you open the FR5739 linker cmd file, you'll see that it has 0xC200-0xFF7F defined because this part has larger memory.

Regards,

Katie

I'm surprised you posted a message I deleted after I discovered the error.

I started with an fr5739 kit ... a week later created a new project for the fr5720.

460822 said:

I'm surprised you posted a message I deleted after I discovered the error.

Sorry about that - I responded straight from the email I got when you posted that reply, and didn't see that you had taken the post back down. Hopefully at least my post can help if someone else runs into a similar confusion later and finds this thread.

-Katie