energia

Not yet but will be soon.

The MSP430 Wire buffer length is set to 16. If you need a larger buffer, you can edit the file: Linux: <Energia directory>hardware/energia/msp430/libraries/Wire/Wire.h Windows: <Energia directory>hardware\energia\msp430\libraries\Wire\Wire.h macOS: <Energia.app directory>/Contents/Java/hardware/energia/msp430/libraries/Wire/Wire.h and in: Linux: <Energia directory>hardware/energia/msp430/libraries/Wire/utility/twi.h Windows: <Energia directory>hardware\energia\msp430\libraries\Wire\utility\twi.h macOS: <Energia.app directory>/Contents/Java/hardware/energia/msp430/libraries/Wire/utility/twi.h And set BUFFER_LENGTH / TWI_BUFFER_LENGTH to a larger number.

You are right, there is indeed something wrong with SPI. The pins and registers are setup wrong in the SPI library due to incorrect pins in the MSP430FR2355 pins_energia.h header file. Please copy the attached pins_energia.h to the MSP-EXP430FR2355LP variants directory. Windows: <Energia dir>\hardware\energia\msp430\variants\MSP-EXP430FR2355LP Linux: <Energia dir>/hardware/energia/msp430/variants/MSP-EXP430FR2355LP macOS: Energia.app/Contents/Java/hardware/energia/msp430/variants/MSP-EXP430FR2355LP Please let us know if this solved your issue. Robert pins_energia.h

I just now gave this a try with a DS18B20 and it works as expected (see output below). If you applied 5v then pin 10 might now be damaged. I did try with 5v supply knowing I could damage the MSP430 but that worked as well. Try connecting it to pin 6 (P1.4). Also make sure that you change that in your Sketch. It is also unclear to me from the pictures if you have a 4.7k pullup resistor on the data line (middle pin). If you do not, then that's a requirement for it to operate correctly. Also, the LaunchPad should have 2 Serial ports exposed. Make sure you select the right one. ROM = 28 FF 6C 5C 72 15 3 E3 Chip = DS18B20 Data = 1 7C 1 4B 46 7F FF C 10 7F CRC=7F Temperature = 23.75 Celsius, 74.75 Fahrenheit No more addresses. Robert

"No more addresses." means it can't find the sensor. Also, it seems that you wired the sensor to 5v. Note that the MSP430 I/O's are _not_ 5v tolerant. The sensor might have put 5 volt on the line damaging the I/O. Also, if the sensor module you are using is a 5v one, it might not detect the 3.3v signal levers the MSP430 put's out. Do you have a link to the DS18X20 module you are using?

P2.1 and P2.2 are S/W I2C slave (module -1) and does not support I2C Slave. In your Sketch you call Wire.setModule(0) to select hardware I2C. However, looking at the picture you wired the 2 LaunchPad's together on P2.1/P2.2. This is not correct, the hardware I2C module is on P1.7(SDA) and P1.6(SCL). Rewire it to use those pins and that should solve the issue.

p.s. you should use the first Sketch you posted. Also make sure that the master is setup to talk to the right address you specify in the Wire.begin(addr) call.

There is a bug for slave mode which has already been fixed in the git repo. You can work-around it with the following. If you have the latest Energia release installed (1.8.7E21), then edit the file: Linux: <Energia directory>hardware/energia/msp430/libraries/Wire/utility/twi.c Windows: <Energia directory>hardware\energia\msp430\libraries\Wire\utility\twi.c macOS: <Energia.app directory>/Contents/Java/hardware/energia/msp430/libraries/Wire/utility/twi.c Got to line 1183 and replace: 1183 } else if (twi_state == TWI_MRX) { // Master receive mode 1184 // copy data to output register 1185 UCBzTXBUF = twi_txBuffer[twi_txBufferIndex++]; by this: 1183 } else if (twi_state == TWI_STX) { // Slave transmit mode 1184 // copy data to output register 1185 UCBzTXBUF = twi_txBuffer[twi_txBufferIndex++];

Which ISP programmer do you have? If it's compatible with CC1310 then we should be able to figure something out.

Interesting. I did not know about these modules. Thank you for bringing this to my attention. Which module do you have (frequency)? These module are intended to be used as a network processor connected to an MCU. Looking at the user manual there is no serial loader implemented nor a way to update the firmware over the air. With that said, it seems that the modules expose the TCKC, TMSC and RESET line. You should be able to hookup these lines from the LaunchPad's XDS110 if you have one to program it with Energia. Please not that there are pin mappings specific for the LaunchPad that you might want to change.

The key here is to as @LiviuM mentioned to assign a unique client ID to each MQTT client. I have just confirmed that with 2 different client ID's all works as expected.

Although the Arduino IDE should be able to consume the Energia packages, there is a difference between the arduino-builder in Arduino and Energia which makes the msp432 package incompatible with the Arduino IDE. See the pull request here: https://github.com/arduino/arduino-builder/pull/119. I have it on my list to find a different solution and be able to use the stock arduino-builder at which point the Arduino IDE should be able to consume the Energia package. For TivaC and MSP430, it is possible to use it in the Arduino IDE. Just put this in the preferences: http://energia.nu/packages/package_energia_index.json. Then pull up the board manager and install TivaC support.

Can you please open a terminal and type the following command? kextstat -b com.FTDI.driver.FTDIUSBSerialDriver If it does not show something like the below then the driver was not loaded: Index Refs Address Size Wired Name (Version) UUID <Linked Against> 533 0 0xffffff7f831ad000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.3) ECC3AF36-431D-370D-86F2-5237785E9CF8 <110 52 5 4 3 1> In that case try: find /Library/Extensions/ -name *FTDI* This should show something like the below if the driver was installed. If not then reinstall the driver. If it does show something like the below then read on. /Library/Extensions//FTDIUSBSerialDriver.kext /Library/Extensions//FTDIUSBSerialDriver.kext/Contents/MacOS/FTDIUSBSerialDriver If the driver is indeed installed and exists in /Library/Extensions then try to force load it with the following command and check id the Serial port shows up in Energia. sudo kextload -b com.FTDI.driver.FTDIUSBSerialDriver After this you can check if the driver is loaded with the command I listed above.

Can you please provide details on what you see? What does ls /dev/tty.* show?

Which version of the msp430 package are you running? I don't have access to a MSP430FR2433 LaunchPad right now so ma not able to reproduce. Could you try replacing the setup loop with jus a pinMode(LED, OUPUT) to test if it you do see a 2 second blink?