olivluca

@@StefanWxx, I see that you had to reduce the mark/space timing by 10-15% wrt the timings in the arduino posts. This is consistent to what I had to do to get the NEC protocol working. I also have a (probably not 100% correct) solution for the led remaining on.
See http://forum.43oh.com/topic/5396-irremote-library-sometimes-leaves-led-on/ for details.
 
Edit: BTW, from the look of it, I'd say that samsung too is using the NEC protocol, so probably there is no need to add a separate sendSamsung function.

I modified the library with the attached patch, now the led doesn't stay on anymore but I cannot control my TV set (lirc, which probably is more tolerant with the timing, recognizes the codes).
 
Edit: I'm not permitted to attach this kind of file, inlined here
--- IRremoteInt.h.orig 2014-04-21 10:29:43.489878975 +0200 +++ IRremoteInt.h 2014-04-21 11:33:19.417113888 +0200 @@ -142,15 +142,16 @@ // P2SEL |= BIT3; // P2.3 option select #define TIMER_PIN_SELECT() ({ \ P2DIR |= BIT3; \ - P2SEL |= BIT3; \ + P2SEL &= ~BIT3; \ + P2OUT &= ~BIT3; \ }) // defines for Timer_A (16 bits) // NOTE: Using A1 instead of A0 because A0 is used by Serial #if defined(IR_USE_TIMERA) #define TIMER_RESET -#define TIMER_ENABLE_PWM (TA1CTL = TASSEL_2 + MC_1) // SMCLK, Up mode -#define TIMER_DISABLE_PWM (TA1CTL = TASSEL_2 + MC_0) // SMCLK, Stop mode +#define TIMER_ENABLE_PWM ({TA1CTL = TASSEL_2 + MC_1; P2SEL |= BIT3;}) // SMCLK, Up mode +#define TIMER_DISABLE_PWM ({TA1CTL = TASSEL_2 + MC_0; P2SEL &= ~BIT3; P2OUT &= ~BIT3;}) // SMCLK, Stop mode #define TIMER_ENABLE_INTR ({ /*TA1CTL |= TAIE;*/ TA1CCTL0 |= CCIE;}) // SH 071112 #define TIMER_DISABLE_INTR ({TA1CTL &= ~TAIE; TA1CCTL0 &= ~CCIE;}) #define TIMER_INTR_NAME TIMER1_A0_VECTOR --- IRremote.cpp.orig 2014-04-21 11:36:07.333117889 +0200 +++ IRremote.cpp 2014-04-21 11:29:03.862107798 +0200 @@ -215,8 +215,8 @@ TIMER_PIN_SELECT(); // P2.3 output and P2.3 option select (when TIMER_PWM_PIN is P2_3) - pinMode(TIMER_PWM_PIN, OUTPUT); - digitalWrite(TIMER_PWM_PIN, LOW); // When not sending PWM, we want it low + //pinMode(TIMER_PWM_PIN, OUTPUT); + //digitalWrite(TIMER_PWM_PIN, LOW); // When not sending PWM, we want it low // TODO: update the comments below

Hi,
 
I created a cheat-sheet for Launchpad, based on  http://www.cheat-sheets.org/#Arduino'>

It is a very reasonable design. Be aware the that voltage being switched must be about one volt higher than the microcontrollers's supply voltage. So if you are running a MSP430 at 3.3V, you could switch a 5V or higher rail, but not the 3.3V. Also be aware that if the higher voltage supply is absent then the microcontoller's output may be overloaded.
 
R1 can be calculated with this formula:  R1 = (Vcc - 0.7) * 10 /  I
 
So for a microcontroller running at 3.6V and a 100 mA load...
R1 = (3.6V - 0.7) * 10 /  0.1 = 290 ohms (use 270 or 330)
 
There will be some small leakage current thru Q2 when it is off. This can be reduced will a resistor between the base and emitter. Using the same value as R1 is fine.
 
 
The circuit as show with D1 is potentially unstable. There is a high gain uncompensated feedback loop that could become unstable with a reactive (capacitive and/or inductive) load.

cd /home/ad/Desktop/energia-0101E0009/lib/
mv librxtxSerial.so librxtxSerial.so.orig
mv librxtxSerial64.so librxtxSerial.so

cd /home/ad/Desktop/energia-0101E0009/lib/
mv librxtxSerial.so librxtxSerial.so.orig
mv librxtxSerial64.so librxtxSerial.so

Hi all, this is true on LP 1.5, maybe someone can confirm on older versions.
I did a quick search about this on the forums and it doesn't seem to have been mentioned already.
 
TP3 and TP1 near the USB connector allow you to get access to ground and the USB 5V
TP3 is ground, TP1 is USB +5V.

 
I soldered pins there on one of my LP for easy cable connection

OTOH, since I won't be cascading the next monitor from this one, it won't probably do me too much good even if it could work, after all impedance matching is to avoid reflections in the cable, it's not only about giving the correct voltage levels.

Download the zip file from the page linked by Rickta59
 
Unzip it somewhere
 
cd where_you_unzipped_it
 
cd linux-3.0/cdcacm-0.1/
 
make clean
 
make
 
This should produce a cdcacm.ko file
 
sudo modprobe -r cdc_acm (just in case it's been already loaded)
 
sudo insmod ./cdcacm.ko

Download the zip file from the page linked by Rickta59
 
Unzip it somewhere
 
cd where_you_unzipped_it
 
cd linux-3.0/cdcacm-0.1/
 
make clean
 
make
 
This should produce a cdcacm.ko file
 
sudo modprobe -r cdc_acm (just in case it's been already loaded)
 
sudo insmod ./cdcacm.ko

After 4 months (to the day) of hard work by the Energia team, Energia release 0101E0009 - 12/06/2012 it is ready to go! A full list of new features and bug fixes will be posted on the github wiki page later this week.
 
Highlights for this release are:
 
- StellarPad aka EK-LM4F120XL support (http://www.ti.com/tool/EK-LM4F120XL).
- FraunchPad aka MSP-EXP430FR5739 FRAM support (http://www.ti.com/tool/MSP-EXP430FR5739).
- Lots of bug fixes.
 
The release is available for download @ http://energia.nu/download/
Pin mapping for the new boards is posted here: https://github.com/energia/Energia/wiki/Hardware courtesy of @rei-vilo.
 
Thanks to all Energia users for your continued support and providing us with invaluable feedback!
 
Thanks to Energia team members @StefanS, @ReaganR, @rei-vilo, @Rickta59, @pbrier, @clyvb for making this release possible.
 
Special thanks to @bluehash for his continued support with 43oh.com.
 
Enjoy the new release!
 
Robert

https://github.com/energia/Energia/downloads ... it is up there .. energia.nu just hasn't been updated.

It's not the serial that's broken but the String class that has some problems with reallocating memory:
viewtopic.php?f=38&t=3296

viewtopic.php?t=2474

Maybe you need this patched version of cdc-acm (I do)
https://github.com/energia/Energia/wiki ... munication

Since I'm running an old distribution and the bundled binaries require a newer glibc, I used that script and (after installing all required dependencies) it worked. I had to use the mspdebug in the binary distribution (the script didn't build it).

Since I'm running an old distribution and the bundled binaries require a newer glibc, I used that script and (after installing all required dependencies) it worked. I had to use the mspdebug in the binary distribution (the script didn't build it).