See energia/msp432-core#44

OS: Windows 10 64bit
IDE Version: Energia 1.8.7E21
Board: MSP_EXP432E401Y
Core: MSP432 EMT Red v5.25.0

Currently I'm having an issue when using both analogWrite and the Servo library. It appears that the Servo library isn't aware of what timers analogWrite is using. Therefore, the two can conflict which causes weird behavior on both the pwm and servo pins.

Pins I'm using for PWM
P2.7, P2.6, P2.4 and P5.7

Pins I'm using for Servo
P3.7 and P3.6

Base example I used for testing is below

// Sweep
// by BARRAGAN <http://barraganstudio.com> 
// Modified for Energia/Stellaris Launchpad by Kevin Balke <[email protected]>
// This example code is in the public domain.

#include <Servo.h> 

#define P2_4  38
#define P2_6  39
#define P2_7  40
#define P5_7  17

#define P3_6  11
#define P3_7  31

Servo myservo1;  // create servo object to control a servo 
Servo myservo2;             // a maximum of eight servo objects can be created 
 
int pos = 0;    // variable to store the servo position 
 
void setup() 
{ 

  myservo1.attach(P3_6);  // attaches the servo on Port F, pin 1 (Red LED pin) to the servo object
  myservo2.attach(P3_7);  // attaches the servo on Port F, pin 1 (Red LED pin) to the servo object

  analogWrite(P2_4,50);
  analogWrite(P2_6,100);
  analogWrite(P2_7,150);
  analogWrite(P5_7,200);      
} 
 
 
void loop() 
{ 
  for(pos = 0; pos < 180; pos += 1)  // goes from 0 degrees to 180 degrees 
  {                                  // in steps of 1 degree 
    myservo1.write(pos);              // tell servo to go to position in variable 'pos' 
    myservo2.write(pos);   
    delay(15);                       // waits 15ms for the servo to reach the position 
  } 
  for(pos = 180; pos>=1; pos-=1)     // goes from 180 degrees to 0 degrees 
  {                                
    myservo1.write(pos);   
    myservo2.write(pos);       // tell servo to go to position in variable 'pos' 
    delay(15);                       // waits 15ms for the servo to reach the position 
  } 
} 

Based on the above example

Based on the above example but I made P5_7 a servo pin and P3_7 a pwm pin.

Based on the above example but I made P5_7 a servo pin and P3_6 a pwm pin.

As you can see at times depending on the order that pwm and servo pins are first used the output can vary. All six pins should have some kind of output but that isn't the case with the above.

MSP432 LaunchPad red and MSP432 LaunchPad pre-series share the same board tag MSP-EXP432P401R, even after just released 4.9.1 of MSP432 LaunchPad red board package.

MSP-EXP432P401R.name=LaunchPad w/ msp432 EMT (48MHz)
MSP-EXP432P401R.name=RED LaunchPad w/ msp432 EMT (48MHz)

The board tag is unique to each board. In the case of the MSP432 LaunchPad red, it should be MSP-EXP432P401RED.

MSP-EXP432P401R.name=LaunchPad w/ msp432 EMT (48MHz)
MSP-EXP432P401RED.name=RED LaunchPad w/ msp432 EMT (48MHz)

Release 5.25.0 uses -O0 instead of -Os as optimisation level.

Is there a reason for that change?

• macOS 10.15.3
• Energia 1.8.11E23

I²C is configured in fast mode 400 kHz by default.

Provide standard mode 100 kHz for compatibility and fast mode plus 1 MHz as well.

Despite #34, it looks like release 5.25.1 kept the wrong definitions.

The Energia Boards Manager lists release 5.23.1 for the MSP432 red.

However, this repository only mentions releases up to 5.6.3.

LCD examples for EDU BoosterPack don't compile on MSP432. (Examples> 09.EducationalBP_MKII>LCD_*)

Error reports multiple definitions of several functions in the display library.

There are quite a few compilation errors and warnings for:

1. The builtin example Sketches.
2. Examples for the builtin libraries.
3. Examples for the libraries included in the MSP432 core packages.

When running on macOS 10.15 Catalina, building against the MSP432P401R raises an error.

/Applications/IDE/Energia.app/Contents/Java/tools-builder/ctags/5.8-arduino11/ctags -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives /var/folders/wn/n7qqb8ss0k3bvpqwfcdwp_7r0000gn/T/arduino_build_325956/preproc/ctags_target_for_gcc_minus_e.cpp
fork/exec /Applications/IDE/Energia.app/Contents/Java/tools-builder/ctags/5.8-arduino11/ctags: bad CPU type in executable
Error compiling for board LaunchPad w/ msp432 EMT (48MHz).

However, using embedXcode succeeds.

Might be related to energia/cc13x2-core#6

Sending float numbers with Blynk fails with the MSP432RED 5.23.1 package, but works with the MSP432 3.8.0 package.

    float p = random(220, 330) / 10.0;
    Blynk.virtualWrite(1, p); // °C

Might be related to #17.

The same code behaves differently when used against the RED LaunchPad w/ msp432 EMT (48MHz) boards package release 5.6.1 and the LaunchPad w/ msp432 EMT (48MHz) boards package release 3.8.0.

The code uses the vsprintf() function to format a number. It seems to be missing when targeting the RED LaunchPad w/ msp432 EMT (48MHz) boards package release 5.6.1.

Results

• With RED LaunchPad w/ msp432 EMT (48MHz) boards package release 5.6.1

oC

• With LaunchPad w/ msp432 EMT (48MHz) boards package release 3.8.0

+23.4 oC

Code

#include "stdarg.h"
#include "stdio.h"

char bufferOut[128];

String formatString(const char * format, ...)
{
  va_list args;
  va_start(args, format);
  vsprintf(bufferOut, format, args);

  va_end(args);
  return String(bufferOut);
}

float temperature = 23.4;

void setup() {
  Serial.begin(9600);
  delay(500);

  Serial.println();
  Serial.println((formatString("%+6.1f oC", temperature)));
}

void loop() {

}

Boards Packages Releases

OS: Windows 10 64bit
IDE Version: Energia 1.8.7E21
Board: MSP_EXP432E401Y
Core: MSP432 EMT Red v5.25.0

Building any program or example that uses the Tone library results in this error.

makefile:153: recipe for target 'toneMelody.out' failed C:/Users/a0273011/workspace_v9-rslk-test11111/msp432r_MSP-EXP432P401R_core/Debug\libmsp432r_MSP-EXP432P401R_core.a(Tone.o): In function tone(unsigned char, unsigned int, unsigned long)':
C:/ti/energia_msp432r_5.25.0/cores/msp432r/ti/runtime/wiring/Tone.cpp:107: undefined reference to toneTimerId' collect2.exe: error: ld returned 1 exit status gmake[1]: *** [toneMelody.out] Error 1 gmake[1]: Target 'secondary-outputs' not remade because of errors. gmake: *** [all] Error 2 makefile:146: recipe for target 'all' failed

This problem doesn't exist on the previous release 5.23.1

Has been verified on Energia IDE, CCS Cloud and CCS IDE using v5.25.0.

It looks like the definitions for SPI_MODE0 and 1 (and the definitions for SPI_MODE2 and 3) have been swapped when going from 5.23.1 to 5.25.0. My perusal of the TI documentation seems to indicate that the 5.23.1 versions were correct.

5.23.1\cores\msp432r\ti\runtime\wiring\SPI.h

#define SPI_MODE0 SPI_POL0_PHA0
#define SPI_MODE1 SPI_POL0_PHA1
#define SPI_MODE2 SPI_POL1_PHA0
#define SPI_MODE3 SPI_POL1_PHA1

5.25.0\cores\msp432r\ti\runtime\wiring\SPI.h

#define SPI_MODE0 SPI_POL0_PHA1
#define SPI_MODE1 SPI_POL0_PHA0
#define SPI_MODE2 SPI_POL1_PHA1
#define SPI_MODE3 SPI_POL1_PHA0

The same code using PWM for the RGB LED works on the black but not on the red MSP432P401R LaunchPad.

• Black MSP432P401R LaunchPad with board package 3.8.0

The RGB LEDs display yellow, orange and red colours.

• Red MSP432P401R LaunchPad with board package 5.6.2

The RGB LEDs display none of the colours.

• Minimal sketch

void setup() {
  // put your setup code here, to run once:
  pinMode(RED_LED, OUTPUT);
  pinMode(GREEN_LED, OUTPUT);
  pinMode(BLUE_LED, OUTPUT);
}

void setRGB(uint8_t red, uint8_t green, uint8_t blue)
{
  analogWrite(RED_LED, red);
  analogWrite(GREEN_LED, green);
  analogWrite(BLUE_LED, blue);  
}

void loop() {
  // put your main code here, to run repeatedly: 
  setRGB(127, 127, 0); // yellow
  delay(1000);
  setRGB(127, 63, 0); // orange
  delay(1000);
  setRGB(127, 0, 0); // red
  delay(1000);  
}

OS: Windows 10 64bit
IDE Version: Energia 1.8.7E21
Board: MSP_EXP432E401Y
Core: MSP432 EMT Red v5.25.0

A student received the below error message when uploading code to their launchpad. I'm waiting for the verbose output but for now here is the error message that I received.

Sketch uses 40536 bytes (15%) of program storage space. Maximum is 262144 bytes.
Global variables use 8032 bytes (12%) of dynamic memory, leaving 57504 bytes for local variables. Maximum is 65536 bytes.
boost::filesystem::create_directories: Access is denied: "C:\Users\1#p\AppData\Local\Texas Instruments"
If this continues, please run fsclean or set TI_APPDATA_DIR to directory you have permissions to access
An error occurred while uploading the sketch

Same as #12 but for release 5.23.1.

LED1 is referred in MSP432R Launchpad pinout. But no LED1 is defined properly in the pins_energia.h file, so I got "LED1 was not declared". The version I used is 5.6.1.

Which issues does version 5.6.2 fix?

Thank you!

During build the system claims that it can not find java with an error that
{runtime.ide.path}/java/bin/java
could not be found

changing this in platfrom.txt fixes the issue (locally)
#build.ino2cpp.cmd.windows={runtime.ide.path}/java/bin/java
build.ino2cpp.cmd.windows=c:/energia-1.6.10E18/java/bin/java

i think it will be a really good idea to enable to read the temperature of the device, for long run it would let us test stability of the device

The examples provided by Energia for the Anaren CC110L fail to compile against the MSP432.

In file included from ~/Library/Energia15/packages/energia/hardware/msp432/3.8.0/libraries/AIR430BoostEuropeETSI/utility/A110x2500Radio.cpp:29:0:
~/Library/Energia15/packages/energia/hardware/msp432/3.8.0/libraries/AIR430BoostEuropeETSI/utility/Platform.h:31:31: fatal error: driverlib/rom_map.h: No such file or directory
 #include <driverlib/rom_map.h>

                               ^
compilation terminated.

when rom_map.h has migrated to driverlib/MSP432P4xx/rom_map.h.

Change lines 31-33 to

#include <driverlib/MSP432P4xx/rom_map.h>
#include <driverlib/MSP432P4xx/gpio.h>
#include <driverlib/MSP432P4xx/spi.h>

SPI doesn't work as expected on MSP432 RED.

SPI modes seem to be mixed on MSP432R in silicon.

• Mode0 and Mode1 are inverted.
• Mode2and Mode3 are inverted.

For more information, please refer to MSP432P401R Device Erratasheet (Rev. O).

Different options:

• Try building against against LaunchPad w/ MSP432 EMT (48 MHz) and not RED LaunchPad w/ MSP432 EMT (48 MHz)

• Edit file ~/Library/Energia15/packages/energia/hardware/msp432/3.8.0/libraries/EduBPMKII_Screen/Screen_HX8353E.cpp and replace line 92

    SPI.setDataMode(SPI_MODE0);

by

#if defined(ENERGIA_ARCH_MSP432R)
#warning Horrible patch for hardware bug
    SPI.setDataMode(SPI_MODE1);
#else
    SPI.setDataMode(SPI_MODE0);
#endif

I am having issues getting basic serial print usage working.

OS: Windows 10 64bit
IDE Version: Energia 1.8.7E21
Board: MSP_EXP432E401Y
Core: MSP432 EMT Red v5.23.1

When uploading the below code serial monitor outputs garbage text. However, doing a soft reset (hitting reset button) fixes this issue.
This code results in garbage text output:

void setup() {
  // put your setup code here, to run once:
  Serial.begin(9600);
}

void loop() {
  // put your main code here, to run repeatedly: 
  Serial.println("hey");
}

Root cause is likely the same but this code doesn't generate any output when you upload it. Doing a soft reset output text but its garbage text.

void setup() {
  // put your setup code here, to run once:
  Serial.begin(9600);
  Serial.print("hey");
}

void loop() {
  // put your main code here, to run repeatedly: 

}

Sometimes a delay fixes some of these issues. But with the below example it outputs text but its still has some garbage included.

void setup() {
  // put your setup code here, to run once:
  Serial.begin(9600);
  delay(10000);
  Serial.print("hey");
}

void loop() {
  // put your main code here, to run repeatedly: 

}

This is a continuation of #10.

The BLE library used to work with release 5.23.1 but no longer with latest release 5.29.0.

Building the example SerialOverBLE against the MSP432P401R fails with the following error:

In file included from /Users/ReiVilo/Documents/Projets/Energia/libraries/BLE/src/BLE.cpp:13:0:
/Users/ReiVilo/Documents/Projets/Energia/libraries/BLE/src/BLEBoard.h:16:44: fatal error: variants/MSP_EXP432P401R/Board.h: No such file or directory
 #include "variants/MSP_EXP432P401R/Board.h"
                                            ^
compilation terminated.

Note: This issue is posted on the MSP432 Red repository because the BLE library repository does not feature the issue section.

See https://github.com/ti-simplelink/ble_energia/issues/2

The Launchpad MSP-EXP432P4111 should be supported in Energia.

Release 5.25.0 includes variants/MSP_EXP432P4111 but without file pin_names_energia.h.

Similarly, boards.txt doesn't list MSP_EXP432P4111.

Is there an ETA for MSP_EXP432P4111 being supported by Energia?

Release 5.6.2 uses MSP-EXP432P401R instead of MSP-EXP432P401RR for the MSP-EXP432P401R red, prompting confusion with the MSP-EXP432P401R black.

Release 5.6.1 was using MSP-EXP432P401RR for the MSP-EXP432P401R red.

Tested using 5.6.1

1. attachInterrupt( ) does not work for RISING setting.
2. attachInterrupt( ) works only one time after initialization.

OS: Ubuntu 16.04
IDE Version: Energia 1.8.7E21
Board: MSP_EXP432P401R
Core: MSP432 EMT Red v5.23.1

When building a program on a laptop running Ubuntu the students kept getting this compile error. Based on google search it seems the compiler requires this package. But we were unable to find a solution. This prevented the student from compiling any program.

According to distributors, the MSP432P401R is end-of-life and not recommended for new designs.

The vsprintf() function used to format a number does not work properly on floats, even with explicit #include "stdarg.h"and #include "stdio.h", with MSP432 red release 5.23.1.

• Results

With RED LaunchPad w/ msp432 EMT (48MHz) boards package release 5.23.1

oC

• Expected result

e.g. with LaunchPad w/ msp432 EMT (48MHz) boards package release 3.8.0

+23.4 oC

• Code

#include "stdarg.h"
#include "stdio.h"

char bufferOut[128];

String formatString(const char * format, ...)
{
  va_list args;
  va_start(args, format);
  vsprintf(bufferOut, format, args);

  va_end(args);
  return String(bufferOut);
}

float temperature = 23.4;

void setup() {
  Serial.begin(9600);
  delay(500);

  Serial.println();
  Serial.println((formatString("%+6.1f oC", temperature)));
}

void loop() {

}

This issue replaces #11 as the black MSP432 LaunchPad is deprecated.

Is I²C slave implemented on the MSP432?

I was unable to run this very basic program on the MSP432. I tried

• MSP432 standard and MSP432 red,
• ports myWire(0) and myWire(1).

However, the very same program runs fine on the old MSP430G2553 on port myWire(0).

The Arduino Uno board is connected to the LaunchPad through a logic level converter with the required pull-up resistors.

• Slave

#include "Energia.h"
#include "Wire.h"
#define myLED RED_LED

// I2C slave 0x22 command[value]
// - Command
// A: on
// C: off


// MSP432
// 0 = pins 14=SCL 15=SDA
// 1 = pins  9=CLK 10=SDA
//TwoWire myWire(0); // fails
TwoWire myWire(1); // fails also

//// MSP430G2553 - works!
//// 0 = legacy   pins 14=SCL 15=SDA, master and slave
//// 1 = software pins  9=CLK 10=SDA, master only
//TwoWire myWire(0);

void ReceiveEventI2C(int howMany)
{
    uint8_t command = myWire.read();

    switch (command) {
        case 'A':
            digitalWrite(myLED, HIGH);
            break;

        default:
            digitalWrite(myLED, LOW);
    }
}

void RequestEventI2C()
{

}

void setup()
{
    pinMode(myLED, OUTPUT);

    myWire.begin(0x22);
    myWire.onReceive(ReceiveEventI2C);
    myWire.onRequest(RequestEventI2C);
}

void loop()
{
}

• Master

#include "Arduino.h"
#include "Wire.h"
#define I2C_SLAVE 0x22

void send(uint8_t command)
{
    Wire.beginTransmission(I2C_SLAVE);
    Wire.write(command);
    Wire.endTransmission();
}

void setup()
{
    Wire.begin();
    Serial.begin(9600);
}

void loop()
{
    Serial.println("A");
    send('A');
    delay(1000);

    Serial.println("C");
    send('C');
    delay(1000);
}