BOOSTXL-K350QVG-S1: MSP430F5529LP or MSP-EXP432E401Y

I just got it working on the MSPM0G3507, but here is GRLIB for the MSP430:

https://www.ti.com/tool/MSP-GRLIB

Thanks for your rapid response Keith

I did use the example in the MSP-GRLIB for the MSP430F5529LP. The touch seems to work fine as it interrupts at the correct place, but nothing displays on the LCD. I wasn't sure if there was a trick to getting it working, but seems like others have got the code working on the launchpad, so there must be a hardware issue. I will have to try debug it.

Sorry, I don't have a 5529LP here to try, just a 2311 which does not have a grlib example. I can say that it works fine on my late, great MSP432P401R and, as I said, I ported it to the MSPM0G3507.

I guess I should point out that porting the *display* was the easy part. It was the touch that involved the most fiddling.

Thanks Keith. I've been meaning to try out the MSP-M0 - maybe this is a kick in the pants to get a board!

Sadly, mine was the other way round. The touch worked first time on the MSP430F5529

was the porting easy enough for the MSP-M0? Did you port from the MSP432P401R example code?

Not *that* difficult, yes, based on the MSP432P401R, but have no fear, I have you covered:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1399285/mspm0g3507-port-of-grlib-for-boostxl-k350qvg-s1/5355649?tisearch=e2e-sitesearch&keymatch=%20user%3A301692#5355649

Note, that I think you will be the first person to use this besides me, so YMMV!

Very probable - especially since I am still not sure if the display from RS Components is working or not???

Hi Keith

Me AGAIN - apologies the MSPM0 is new for me!

Received my LP-MSPM0G3507, so all good on that front. I took your code and tried to compile in CCS. There were obviously a few includes that it couldn't find but after sorting through all of these, I finally got to the below error messages. Seems to automatically choose the g3505 in the late stages of the build (see Sysconfig warnings which pops up at 64% of the build) and then has conflict issues. I have tried to edit the Sysconfig, but it warns that the files are autogenerated and it reverts back to the auto selection of the G3505 when I try build again. Do you have any advice to sort this out?

You're getting two copies of the linker .cmd file. One is in "Generated Source"; since you're using Sysconfig, you probably want that one.

Right-click on the one in your Project folder, then "Exclude from build".

I don't know about the G3505 thing (I don't know much about Sysconfig).Can you change it in "Build Settings->General->Variant and core"?

As you can tell, I had not tried compiling with the just-released SDK. I will upgrade my project and try a build.

I upgraded and had no issues with .cmd files, I did have an issue with a missing #define in dl_sysctl_mspm0g1x0x_g3x0x.h

#define SYSCTL_MCLKCFG_UDIV_DIVIDE3              ((uint32_t)0x00000020U)         /* !< ULPCLK is MCLK/3 (divided-by-3) */

Then I found out that I had an old version of the code there, so the LCD works, but not the touch screen. I will re-work it and post it next week. ARRRGGGG!

Thanks for the response Bruce. Tried your suggestion, but I could not get it to work. I have done a complete new project and copied relevant files from Keith's project. Finally managed to get it to build! 

Thanks for all the assistance Keith. Still couldn't get your project to build - must be an issue on my side. Started with fresh empty project and copied your files(thank you). managed to get it to build now, but sadly the display still does not work. Therefore, it must be the display. RS Components are going to swap it out for me. Here is my project that now builds - GRLib_mspm0g3507_wdm.zip

BTW, seems like the touch is a calibration issue. The touch does work, as I added toggling of the LED in the touch_calibrate() function, and the touch does function, but the xMin and yMin don't fall into the required constraints below.

static bool validateCalibration(void){
uint16_t i = 0;

if((touch_calibrationData.xMin < 620) &&
(touch_calibrationData.xMin > 520) &&
(touch_calibrationData.yMin < 1000) &&
(touch_calibrationData.yMin > 900))
{
return(true);
}

Those only apply to the MSP432P401R, when you change MCU's you must change the constants.

Also, with zoey's help, I have updated the example to work with the latest SDK:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1424079/mspm0g3507-link-errors-transitioning-to-latest-sdk