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.

BOOSTXL-SHARP128: LCD Scrambled output? Defective?

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

I am using modified code from the MSP430EXP5969 example library to run the BOOSTXL-SHARP128 on the MSP430EXP5994. During LCD initialization when the LCD_DISP pin is turned on the Sharp LCD screen scrambles all its pixels. LCD initialization continues and once complete, the screen remains in a scrambled pixel state and GRLIB draw/flush commands fail to alter the output of the LCD. I suspect the LCD has failed and I need to RMA it, but I cannot be certain.

The code I am running can be found here. github.com/.../MSP430EXPFR5994-SHARP128LCD

  • Hi Jason,

    There are two things I'd like for you to try out:

    1)  Could you please use the MSP-EXP430FR5969 TI provided example code for the Sharp128 Booster-pack to see if you still see the same scrambled output?

    2) If you have another Launchpad then I'd like to see if the same pixel scrambling follows the booster-pack to another board

    If the TI provided example code fixes the scrambling then I would look at the source code to see if something is being initialized incorrectly.

    Best regards,

    Matt

  • in main.c I see:

    > * Disable the GPIO power-on default high-impedance mode to activate

    > * previously configured port settings

    I expected this to be followed by something like

    > PM5CTL0 &= ~LOCKLPM5;   // aka PMM_unlockLPM5()

    but I don't see it. Is this being done somewhere else?

  • i rolled it into the definition of the board_init() function so it would trigger before pins were set to high by the HAL_LCD_init_Display().  That way I could see which pin was causing the LCD to scramble.

  • Jason,

    Have you gotten a chance to run the 2 tests I mentioned in the previous comment?

    -Matt

  • The only other launch pad I have is the MSP430EXPFR2355. I've been trying to get code working on that for the LCD but haven't yet got something that compiles.

    As for the 5969 code, that's essentially what I am using except I've remapped the pins on the header-file and renamed a few things. Not sure what exactly you are asking me to do here.

  • Jason,

    Allow me to clarify. I am trying to figure out if the cause of the issue is HW or SW based. Thus, I'd like for you to use the following link (http://dev.ti.com/tirex/explore/node?devices=MSP430FR5969&node=AA1MkappYPoegdZS15VIxg__IOGqZri__LATEST) which takes you to the Sharp128 Graphocs Library example project for the MSP430FR5969 ( MSP-EXP430FR5969_Grlib_Example_Sharp128 ). Import this example project into CCS and run it on your Launchpad + BoosterPack stackup to see if the output is still scrambled.

    Best regards,


    Matt

  • In my case there was a define to switch between the 96x96 and the 128x128. Once set correctly, everything was fine.

    My define was called BOARD_DISPLAY_SHARP_SIZE

  • I tried to run the code given at the link, however it failed to run on the EXPFR5994 board.

  • Jason,

    I saw the reference to MSP-EXP430FR5969 in the initial post and mistakenly thought that was the platform you were working with.

    Unfortunately there is no out-of-box example in the TI Resource Explorer for the MSP-EXP430FR5994 yet but there is an E2E post where Luis RC explains in detail how to modify the drivers in GRLib to support the platform you are on. In fact, he provides a zipped project which you could download and run on your board (MSP-EXP430FR5994) just to see if the LCD populates correctly. It will not show the proper FFT signals without the audio boosterpack attached but it should print the title screen correctly.

    Best regards,

    Matt 

  • OK, I've got the code working now. The header file needed further modification. The screen still scrambles after the LCD Display pin is set to high, but the scrambling is cleared now upon reaching the grClearDisplay command and the code draws the example objects appropriately.

**Attention** This is a public forum