RWB

Yes, it works!   Thanks to Pabigot
 

Yes, it works!   Thanks to Pabigot
 

I don't own CCS. so I can't give you a definite solution to your problem. However I would advise you follow the reccomendation in the comment block you posted above  
// It is required that the display buffer is a multiple of 512 Bytes Given the size of your array 0x3520 (13600 bytes) I think that should be a starting point, since that is not a multiple of 512.

I have been playing around with these Sharp Memory LCD's also. I like how sharp the 128x128 pixel & 2.7 Inch TFT versions have the black pixel color instead of the mirror silver finish which I don't like.
 
The ultra low power consumption is awesome. 
 
They require lots of SRAM so its taken me as a newbie to all this a long time to find some solutions that have enough memory to actually run the 128x128 pixel 1.28 inch screen and especially the 2.7 Inch 400x240 pixel screen that takes 12,000 bytes of memory. 
 
Looking at the ultra low power consumption of this screen + FRAM + the new MSP430FR5969 + Sharp LCD screen combo for the killer price of $30 ! 
 
I hear that the FRAM can be partitioned so if you need more SRAM you can just adjust your FRAM allocations to meet your needs like increasing the SRAM size. Is this possible? Or is it possible to runs Sharps 2.7 Inch screen with the the new MSP430FR5969?
 
And one last question is about the current best library for the Sharp Memory LCD's & the new MSP430FR5969. Is the library that comes with the new the new MSP430FR5969 + LCD Screen combo being sold by TI considered a full featured library? 
 
 

I'd say that the TI library is fully featured. But it also takes up ~10kb on the new FRAM board. 
 
You don't increase SRAM size per say. As long as your running < 8MHz FRAM Read/Write is just as fast as SRAM. It is very easy to use the FRAM as a frame buffer. I've done this in all my projects. For security you should read up how to enable the memory protection unit, in-case some buggy code wants to rewrite your program :S
The FRAM buffer approach is used in the code I've linked above. I admit it could be prettier. Assuming you don't run out of FRAM you could easily use 12Kb for a screen buffer.
 
I to much prefer the black and grey sharp panels. I wonder if the inclusion of the white/silver is because sharp sold them to TI cheaply?

I have been playing around with these Sharp Memory LCD's also. I like how sharp the 128x128 pixel & 2.7 Inch TFT versions have the black pixel color instead of the mirror silver finish which I don't like.
 
The ultra low power consumption is awesome. 
 
They require lots of SRAM so its taken me as a newbie to all this a long time to find some solutions that have enough memory to actually run the 128x128 pixel 1.28 inch screen and especially the 2.7 Inch 400x240 pixel screen that takes 12,000 bytes of memory. 
 
Looking at the ultra low power consumption of this screen + FRAM + the new MSP430FR5969 + Sharp LCD screen combo for the killer price of $30 ! 
 
I hear that the FRAM can be partitioned so if you need more SRAM you can just adjust your FRAM allocations to meet your needs like increasing the SRAM size. Is this possible? Or is it possible to runs Sharps 2.7 Inch screen with the the new MSP430FR5969?
 
And one last question is about the current best library for the Sharp Memory LCD's & the new MSP430FR5969. Is the library that comes with the new the new MSP430FR5969 + LCD Screen combo being sold by TI considered a full featured library?