reaper7

nice headers with spring pins from mill-max for tests on board

Got some parts from mouser today and just wanted to show the really beautiful 128x128 1.28" Sharp LCD (LS013B7DH03) ... I really like this one because it is so much better to read compared to the version on the BoosterPack.
The LPs are running with @@chicken 's Energia Library for the Sharp LCDs.

IIRC you can "fork" the SPI lib and put it in your local libraries dir, then rename it a bit (and the utility/ dir functions since they're C) and just use that instead of SPI. I also have a 9 and 16-bit adapted version of SPI, perhaps I should extend it into a super deluxe SPI alternative for Energia...
 
Sent from my Galaxy Note II with Tapatalk 4

SPI on USCI_A0 working!!!
@@spirilis - thanks for tips where to look

SPI on USCI_A0 working!!!
@@spirilis - thanks for tips where to look

Energia's SPI was never really designed to use USCI_A at all, since the "boosterpack designated" location is on the USCI_B pins only for the various MSP430 LaunchPads.
 
That said, you would need to modify those for sure, but then also rewrite the SPI library's utility/usci_spi.cpp (found in hardware/msp430/libraries/SPI)

bump...
New 0.9a version

Programming a microcontroller for the first time can be a daunting task. What if you can remotely control your microcontroller by simply clicking few buttons on a PC GUI? 
 

 
With Energia support, I was able to port existing Firmata code used for Arduino onto LaunchPads. Firmata is a serial communication protocol that allows a host (PC) sending commands to the microcontrollers (MSP430). You can use it to toggle pins and LEDs, or read digital and analog inputs without writing any C code. This makes it super easy to test out your new sensor or debug your circuit. Bluetooth simply creates a virtual serial port that emulates a physical serial port wire, so you can control and monitor your board remotely.
 
Here is a demo video: 


 
The application GUI is written in NodeJS. The browser is connected to the Node server using web socket. Whenever the user clicks a button, a message is sent to the server and the server will send Firmata commands to the LaunchPad.
 
You can easily expand on top of the demo GUI I created by writing some javascript. Let's say you want to turn on an LED when the temperature is too high. You can let your Node server constantly check the temperature reading. Once it reaches the threshold, then set the LED pin to HIGH. 
 
You can find out the source code of my project at my GitHub page: https://github.com/shengzhao91/FirmataGUI

nice headers with spring pins from mill-max for tests on board

Oshpark sent some new PCBs...
This time some revisions of the board designs I did/do together with @@reaper7
 

 
Left: MSP430G2553 QFN
Middle: MSP430G2955 TSSOP38
Right: MSP430G2955 QFN
 
Thanks to the help of @@spirilis I got the 2955s working in Energia (see HERE).
 
As you might noticed, the solder pads of the QFN footprints are longer than normal ... I did this hoping that it would ease hand soldering these ICs. I soldered the 2955QFN and 2553QFN with a normal hand soldering iron + a lot of flux + solder wick. Worked pretty well ... will do some hot air soldering later to have a comparison.
 
Unfortunately this boards have a minor design flaw ... R3 and R4 were planned as pullups for the I2C EEPROM, but I messed up the routing for these - now they act just as solder bridges. But the next revisions are already in the pipeline This time: G2955 + MTK3339 (PA6C and PA6H) on the bottom + fixed EEPROM/I2C-pullups.
 
 

@@spirilis Works great, now Serial works without any problems. Also my I2C OLED works - very nice !!!
 
For reference, here is the link to spirilis' post / files: http://forum.43oh.com/topic/3594-msp430g2955-launchpad-development/#entry47184

Got my G2955 boards yesterday and soldered the TSSOP-Version today.
First test with Energia showed, that simple sketches (like blinking or software serial) run without problems.
But at the moment I have a lot of difficulties to get the peripherals like HardwareSerial or I2C running.
 
I took the files of L.R.A. (as posted earlier) and modified them according to the data sheet (as far as I could). memory.x and periph.x should (hopefully) be correct, I took the values from the docs.
Had to correct some "pins" in pins_energia.h ... but I couldn't get HardwareSerial running on Pins 25/26 (SoftwareSerial on these pins works) ...
 
So now some questions for those who are more familiar with Energia development:
 
Is it possible to use "msp430" as build.core or do I have to create a new one? (like "lpmsp430g2955.build.core=msp430" in boards.txt)
 
Or the other way around: To which extend do I have to change hardware-related files (like in hardware/msp430/cores/msp430)?
 
So to sum up here is a short list according to @@Rei Vilo 's post:

add board definition for the MSP430G2955 in hardware/msp430/boards.txt -> ok ... question: build.core=msp430 ??? add pins definition for the MSP430G2955 in hardware/msp430/variants/launchpad/pins_energia.h -> adapted Pins 25+26 for TX/RX, but no success create a new file msp430g2955.h out of hardware/tools/msp430/msp430/include/msp430g2553.h -> do I have to modify this file or just copy? create a new file msp430g2955/memory.x out of hardware/tools/msp430/msp430/lib/ldscripts/msp430g2553/memory.x -> should be ok now create a new file msp430g2955/periph.x out of hardware/tools/msp430/msp430/lib/ldscripts/msp430g2553/periph.x -> should be ok now

I should have an Energia beta release for this LaunchPad in about 2 weeks or so. Will update this thread once it is.

Looks like Microsoft is getting started on IoT - so for the .NET programmers - this might be an interesting thing.  I signed up - apparently they're sending out free dev boards - https://www.windowsondevices.com/
Could be a cool sensor hub for instance.

maybe little OT
 
I've used ccs several times,
I've never used import...
and
I'm not going to stop using Energia
Energia is simple and suitable for my applications!
 
ccs is a triumph of form over content and it is hard to move between LP's (for me of course )

So it occurred to me that I might have made a small change or 2 in the last ~1 year since I posted a release zipfile of this code, and since energia.nu now has a link to this thread I'm going to post the latest code up here & change the first post to point here.
Enrf24_v1_8.zip

This library will make it easier to set up calendar mode in the hibernation module of a Tm4C1294 launchpad.
 
This mode automaticaly stores seconds, minutes, hours, days, months, years and day of the week.
It also lets you set up an interrupt with any time interval between 1 seconds and 23:59:59,
 
Currently it seems to be a bug in TivaWare so years and weekdays don't seem to work.
 
 
RTChardware.zip

Yup... and that one looks a lot better too.
 
Regarding DVCC, AVCC, do you know why there are so many capacitors between them? (Schematic from the page)
 

bump...
New 0.9 version

Here you go @@Hassanul, I added a simple method to my Energia library that allows to display images like the TI logo.
 
https://github.com/astuder/MSP430-sharp-LS013B4DN02-memory-display/tree/master/energia
// display TI logo for 2 seconds display.bitmap(pixel_ti_logo, 96, 96, 0); delay(2000);
and yes, my SHARP display is literally catching dust []

from now UIPEthernet library (v02) are available for MSP430F5529LP too
please check on stellarisiti energia forum:
http://forum.43oh.com/topic/7489-energia-library-stellarpad-uipethernet-enc28j60-library/

from now UIPEthernet library (v02) are available for MSP430F5529LP too
please check on stellarisiti energia forum:
http://forum.43oh.com/topic/7489-energia-library-stellarpad-uipethernet-enc28j60-library/

Cross-posting from Stellarisiti...
 
Hi folks-
I sat down and played around with this today for kicks.  Here's a CMSIS_DSP library (includes the .c files from ARM's CMSIS-DSP distribution, header files, and a single CMSIS_DSP.h that includes arm_math.h to make it simpler) for Energia.
 
CMSIS_DSP_Energia.zip
 
CMSIS-DSP is ARM's standard library for utilizing DSP algorithms on the ARM Cortex-M series chips; in particular it contains optimizations suitable for the Cortex-M4, along with primitives for using the extended instructions.
 
API documentation is located here: http://www.keil.com/pack/doc/CMSIS/DSP/html/index.html
 
The FIR32_TEST example came from something I saw (possibly a CMSIS-DSP stock example) back when I was compiling CMSIS-DSP under Linux for straight C TivaWare use.
 
The library provides 4 datatypes; F32 (float), Q31 (int32), Q15 (int16), Q7 (int8); the latter 3 datatypes can only store fractional (1.0 >= n >= -1.0) numbers, but if your datasets can use that I believe the library makes use of the Cortex-M4's SIMD instructions for parallelism.
 
I couldn't get Energia to include an .a file for the binaries, so I had to copy all the .c files and Energia has to build each one when you use the library; this extends the compile time a bit.
 
Enjoy!

Hi folks-
I sat down and played around with this today for kicks.  Here's a CMSIS_DSP library (includes the .c files from ARM's CMSIS-DSP distribution, header files, and a single CMSIS_DSP.h that includes arm_math.h to make it simpler) for Energia.
 
CMSIS_DSP_Energia.zip
 
CMSIS-DSP is ARM's standard library for utilizing DSP algorithms on the ARM Cortex-M series chips; in particular it contains optimizations suitable for the Cortex-M4, along with primitives for using the extended instructions.
 
API documentation is located here: http://www.keil.com/pack/doc/CMSIS/DSP/html/index.html
 
The FIR32_TEST example came from something I saw (possibly a CMSIS-DSP stock example) back when I was compiling CMSIS-DSP under Linux for straight C TivaWare use.
 
The library provides 4 datatypes; F32 (float), Q31 (int32), Q15 (int16), Q7 (int8); the latter 3 datatypes can only store fractional (1.0 >= n >= -1.0) numbers, but if your datasets can use that I believe the library makes use of the Cortex-M4's SIMD instructions for parallelism.
 
I couldn't get Energia to include an .a file for the binaries, so I had to copy all the .c files and Energia has to build each one when you use the library; this extends the compile time a bit.
 
Enjoy!