Rei Vilo

Check 
Add a New Board to Energia

Check the menu Files > Examples > LCD_LaunchPad.

Check the menu Files > Examples > LCD_LaunchPad.

The SD_TM4C library worked out of the box.
Configuration:
LaunchPad: MSP432P401R red Energia: 1.8.7E21 Boards package: Energia MSP432 EMT 5.23.1 SD card: Kingston 8 GB formatted in MS-DOS (FAT32).  

 

Have you tried the SD_TM4C library?

You need to read the data-sheets of the MCU and the sensor and check the mA provided and used.

The Sensor Controller isn't supported by Energia. 
Actually, it requires a specific IDE, called Sensor Controller Studio (link).
I tried and played with the examples, but they are rather sophisticated.
I'm looking for a very basic application for my Low Power Home Network Weather Monitoring with a clock (every 10 mn) and a push-button (manual) to raise an event and wake up the main core.

There is code available to implement I2C communication between the MSP430 and the HDC2010 temperature-humidity sensor, but it's a bit like an onion -- you have to peel away layer after layer in various libraries to drill down into what is happening at the register level.  I decided to write some transparent demo code for this sensor that is self-contained: everything related to the I2C interface is in a single C program.  It has been successfully tested with the F5529 Launchpad.  This is a simple MCU polling operation that periodically makes a T-H measurement using the on-demand mode of the sensor. The data is sent to the serial port for display on a terminal program.  The on-board heater is activated for a few seconds upon reset. I have not implemented the temperature-humidity high/low interrupts. One could also configure the sensor to output data periodically and toggle its DRDY pin to wake-up the MCU from LPM4.  Polling code is here:
https://github.com/microphonon/HDC2010
The HDC2010 is a tiny sensor with a 6-bump BGA footprint.  TI makes an evaluation module that uses an MSP430F5528 to interface the sensor with a configuration/graphing GUI program.  Their program only runs on 64-bit Windows.  The portion of the PCB hardware containing the sensor can be broken off (permanently) to reduce thermal mass and allow placement in a project.  I decided to make my own breakout boards (see photo), but just learned that MikroElektronika started selling essentially the same thing for $13 (MIKROE-2937).
 

You can combine the LaunchPad with LCD with a second LCD. 
The MSP-EXP430FR4133 with LCD goes for USD14 while the MSP-EXP430FR2433 is USD10.
The larger MSP-EXP430FR6989 with LCD is USD18 vs. USD16 for the MSP-EXP430FR5969.
If power consumption is critical, why not consider an e-ink screen? Pervasive Displays have a wide range of displays, B&W and also tri-colours with red. All are supported with an Energia library.

At this state, we need to know more about your project.
And no need to double post your question at Which MSP430 to pick? Advice please. This is against netiquette: see Netiquette for Newbies.
 

Read the FAQ.
 

@poulichp I confirm:
Optional step - Format the image to 32-bit PNG with https://www.imagemagick.org/script/index.php  Step 1 - Use the utility https://github.com/vaskevich/png2c to convert the PNG file into a C-array. Step 2 - Use the example LCD_screen_Logos from the EduBPMKII_Screen and adapt it to match the size of the image and the Kentec 3.5" SPI display. Image

Screen

Sounds like time to read the manual.  Look at the memory map of the device and I think you'll have some insights into why you're running into problems. This is not an area where I have any other useful experience.  Of course, there's also e2e as a resource.
 

When you post a question asking for help, please provide minimal information about your configuration, both hardware and software, including:  
model of LaunchPad used and revision number model of the MCU used model of BoosterPack used or model of the sensor or actuator or screen optionally, links to the sensor or actuator or screen data sheet name and version of the IDE used  OS the IDE is running on whenever possible, minimal code to replicate the issue optionally, all kinds of measures that may be useful, like logic analyser trace, oscilloscope screen-shots, ...  
Example:  
LaunchPad MSP430G2 revision 1.5  

It looks like the I²C implementation requires a specific period between write and read. 

It looks like the I²C implementation requires a specific period between write and read. 

Thanks.
The above content is listed at the top of all Energia forums.

Have you checked the usual suspects at I²C Check-List
https://forum.43oh.com/topic/13067-suggestion-add-a-faq

See 
 
 

Some topics come aver and over again. Here are the most frequent questions.
Wouldn't be nice to have all of them in one single place?
Listed questions:
Netiquette for Newbies What Information to Provide When Asking for Help I²C Check-List  Porting an Arduino library to Energia Use Pins Number instead of Pins Names with Energia Add a New Board to Energia LaunchPad and BoosterPack Pins Maps Boards Supporting the Galaxia Library  
 
Netiquette for Newbies  What Information to Provide When Asking for Help  I²C Check-List  Porting an Arduino library to Energia  

The MSP430G2553 has two I²C ports available. See I²C Check-List at
 

The I²C implementation on pins 9 and 10 is software-based (or bit-banging). Some functions may work differently from the hardware ones. 
Let me try with a very standard I²C device. 

Have a tried running Node-RED on a dedicated Raspberry Pi Wireless? At USD10, it is worth experimenting to get a precise idea of the lag.
Does your application need to display all the thermometers, or only those with an issue?
You may rename the thread on the first post

You can easily interface Node-RED with a SQL database to store and retrieve all the data. Among many other options, mySQL, SQLlite...
How often each sensor is reporting temperature? How critical is temperature?

You're welcome, and congratulations for the test! I'm impressed by how many things you've achieved in just one hour

@cubeberg I haven't tried DeviceHive because the dashboard (provided by Grafana) is external.
I'm surprised how well Node-RED works on a very basic and cost-effective Raspberry Pi Zero Wireless.
As an additional benefit, the Raspberry Pi Zero Wireless features Bluetooth, so I can connect my SensorTag as per this project or this one.
I'm using a USD25 Chinese tablet running on Android as a screen with Chrome running in kiosk mode.

Just like many other hobbyists, I can't afford the not-invented-here syndrome due to lack of time and resources, as you rightly point out. 
Good luck with your project!