This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP-EXP430FR5969: Problem running both LCD and JSON code together

Part Number: MSP-EXP430FR5969
Other Parts Discussed in Thread: BOOSTXL-SHARP128, MSP430FR5969,

Hello Team,

I'm posting on behalf of my customer:

I am running on the MSP-EXP430FR5969 Launchpad with a BOOSTXL-SHARP128 LCD attached.  I am trying to display on the LCD while using simple JSON communications via eUSCI A in UART mode.  I am essentially combining the example BOOSTXL-SHARP128_GrlibEample_FR5969 with the example msp430fr5969.  I am using the initialization code from each of those examples verbatim. I'm using functions  GrPixelDraw() or GrLineDrawV() to display data on the LCD.  If I run both initialization functions ( HAL_LCD_initDisplay() for the LCD & GUI_Init() for the UART), it seems that the code that writes to the LCD runs but nothing actually displays up on the LCD.  If I comment out the GUI_Init() function, then the data written to the LCD now displays.  (Interestingly, the function GrImageDraw() appears to work just fine.  Hmmm)

I know the LCD display routines use eUSCI B in SPI mode to send data to the display.  I should be able to run both eUSCI A in UART mode and eUSCI B in SPI mode at the same time.  But something in the UART mode setup seems to conflict the the SPI communication.  

Any help would be greatly appreciated!

Regards,

Renan

  • Hello Renan,

    What their code setup is telling you, is that the initialization functions of either example they are copying from, is overwriting some settings from the other. thus only the last init function executed is getting them results. They will have to setup/initialize their device in same or similar matter that the examples they are pulling form, but will need to adjust for any conflicts. 

    Also keep in mind that the UART example with JSON was probably only built for that one example, and does not account for other processes in the system. That means, it could be blocking of other functionality of the device as UART can be slow and JSON takes a lot of data transfers to do. That's why GUI Composer now supports MessagePack for MSP430.

**Attention** This is a public forum