L.R.A

I don't think a schmitt trigger is that much necessary for this case, i usually use that just for buttons.
As for converting 5V to 3.3V, the easiest way is use a voltage divider with 2 resistors. Though the encoder output should be digital, and the TM4C123GH6PM is 5V tolerant in most pins, in that case it's not necessary the conversion

BTW @L.R.A, I will have two new LCD BPs in about a week or two, both 2.4", one with touch.

I've reviewed many affordable screens at http://embeddedcomputing.weebly.com/displays.html. Check T-Haoyu or East Rising.

I have found the Energia pin map pdf's are difficult to match with the (several) pin numbering systems so I created an Excel spreadsheet to combine all of these. It's in a spreadsheet so you can sort on any column. This makes it much easier to find the pins and their functions. The pin functional groups are color coded. 
 
Two sample images of the tables are included, one based on the Boosterpack pins (booster_pack), and the second on the breadboard pins (breadboard). Numbering lists include physical pins X6-X9, boosterpack pins A1- D2, GPIO pins PA-PQ, and digital pin-to-port numbers 1-95
TM4C1294 Board Pinouts_V3.zip

Eheh, i wish it was like that. I have to much to study to not consider Sunday just another week day (dam you MatLab and Fourier)

could you provide the code you are using?
 
Also are you sure that it's transmitting at 33Khz?
I am not experienced with Serial IR but this i what i know of the tiva.
 
If instead of the low power mode you use normal mode, the frequency of the data being transmitted should be the same as a normal UART, you configure it the same, but remember to configure the CLK after calling UARTEnableSIR not never before.
 
in low power mode:
Operating in low-power IrDA mode adjusts the width of the infrared pulse transmitted to three  times the period of the internally generated baud clock.     Taken from the datasheet, page 914   The UARTILPR register stores the 8-bit low-power counter divisor value used to derive the low-power SIR pulse width clock by dividing down the system clock (SysClk). All the bits are cleared when reset.   The internal IrLPBaud16 clock is generated by dividing down SysClk according to the low-power divisor value written to UARTILPR. The duration of SIR pulses generated when low-power mode is enabled is three times the period of the IrLPBaud16 clock. The low-power divisor value is calculated as follows:   ILPDVSR = SysClk / FIrLPBaud16 where FIrLPBaud16 is nominally 1.8432 MHz.     Because the IrLPBaud16 clock is used to sample transmitted data irrespective of mode, the ILPDVSR field must be programmed in both low power and normal mode,such that 1.42 MHz < FIrLPBaud16 < 2.12 MHz, resulting in a low-power pulse duration of 1.41–2.11 μs (three times the period of IrLPBaud16). The minimum frequency of IrLPBaud16 ensures that pulses less than one period of IrLPBaud16 are rejected, but pulses greater than 1.4 μs are accepted as valid pulses.         I hope it helped, i never used any serial IR so i'm probably missing something

Just a bit of explanation on how to use the Prescaler Match:
 
in PWM mode the prescaller holds the most significant bits, working as a timer extension.
 
if you have a wide timer in PWM, it has 32bits and the prescaler has 16bits. If you have the Load value of the timer at 0 and the prescaler value at 1, then it means you have a number of 48bits, witht the 32st bit being 1, number 4294967296, At 80Mhz this would mean that the timer would have a period of
1/80Mhz * 4294967296  53s, less than 0.02Hz.
 
The use of the prescaller for the wide timer in PWM mode will generally not be the most useful since the wide timer is alredy 32bits and can make any PWM low frequency starting at 1Hz, for the normal timers (which are 16bits in pwm mode) it's more useful to do something like control a servo which requires 50Hz PWM, something impossible with a 16bit timer with a source of 80Mhz system clock.
 
If you want to set a match, which in PWM mode is when a signal turns from 1 to 0, setting the duty, you need to not only use TimerMatch, but also do so for the prescaler. This is because TimerMatch only sets the match for the 32bits of the timer, for the prescaler bits you need to change other register (hence the different function).
 
Now the 2s blink.
If you want the LED to change state every 2 second you can set the PWM to a period of 4s, and a duty of 50%, this will make it change from 1-0 and back to 1, every 2s.
At 40MHz, you do 4s * 1/40Mhz = 160000000, which needs 40bits, so the prescaler is needed. This number needs in the prescaler the value 0x9 and in the timert the value, 0x896800 - 1 (-1 because, remember tha the 0 counts). These are the load values.
Now to set the duty to 50%, you have the (160000000-1) /2 = 79999999,5, lets say just 79999999. It's 0x4C4B3FF, which has values in the prescaler. So we do prescaler match with 0x4 TimerMatch with 0xC4B3FF.
With this you have a LED that changes state every 2s by using a 4s period PWM.
 
If you actually need the led to every 2s to do a short blink, i think you now see how the prescaller works to do that.

The code vault is to post working codes, not to ask questions, please refer to the general forum for that.
 
if you check the datasheet you can see all the reset sources, i image you are using the tm4c123 launchpad:
5.2.2.1 Reset Sources The TM4C123GH6PM microcontroller has six sources of reset: 1. Power-on reset (POR) (see page 214). 2. External reset input pin (RST) assertion (see page 215). 3. A brown-out detection that can be caused by any of the following events: (see page 216). ■ V DD under BOR0. The trigger value is the highest VDD voltage level for BOR0. ■ VDD under BOR1. The trigger value is the highest VDD voltage level for BOR1. 4. Software-initiated reset (with the software reset registers) (see page 217). 5. A watchdog timer reset condition violation (see page 217). 6. MOSC failure (see page 218).  
If you use TivaWare you can do SysCtlReset(void);, For a reset with only using registers please check page 217 of the datasheet

Hi guys!
 
So i made a blog. Since i am the only in the robotics club that uses TI devices i was asked to teach about the Tiva. Well, what i can at least. And I'll post in the blog all the codes and tutorials.
 
It's still very early under-construction and will be something i will be doing along the school year. I am teaching it to some colleagues and will before the sessions, post the tutorials and some codes, but also post more codes after as examples. I will post basic info about the peripherals.
 
I hope it helps anyone that needs it. Also any feedback is appreciated, teaching someone live is different and i can forget some details while writing. Also i never done something like this, i usually do give lots of explanations but always live and more exercise driven.
 
Blog:
https://sites.google.com/site/luiselectronicprojects/tutorials

It's in the UARTLCRH register in the bit1, named PEN.
 
I haven't tried direct register access in a while in Energia but try using
 
UARTLCRH  |= 0b10;
 
 
With Tiva you need to add the MCU header file but i can't find any CC3200 header file in the Energia files :/

Servo library has been added. You can take the files from here: https://github.com/energia/Energia/tree/master/hardware/cc3200/libraries/Servo and put the Servo folder into your Energia folder under hardware/cc3200/libraries/

In the TivaWare folder there should be a folder called "exampes"->"boards"->"ek-tm4c123gxl".
Also for PWM with the timers i have here some examples. ADC and PWM with the PWM module i still don't have them there
https://sites.google.com/site/luiselectronicprojects/tutorials/tiva-general-purpose-timers

My mailman brought me 2 new Tiva launchpads + some l293d (not in picture)

Btw after SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOD);
you need about 3 clock cycles before you access the GPIO registers without a a fault ISR happening (sometimes it doesn't happen). SysCtlDelay(3); would be enough for any peripheral

Source: http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/368493.aspx
 
Just wanted to share something that i think it's important to note and some of you might not know, i sure didn't.

by the way there is sometigh you can implement to "simulate having the vbat".
 
If you use a diode with a 3V batery and you power the launchpad with 3.3V you can actualy always power the launchpad even when the main power goes out.
you "waste" a ADC to check the voltage supply, if it's 3V or bellow then you enter sleep mode.
 
The diode is simply to only alow the 3V batery to power the launchpad when the main power supply stops

Well i'll try to explain.
 
Flash is a non-volatile memory, meaning that it retains the memory stored even when you stop powering it. The RAM is volatile so it loses all the data store when you stop powering it. FRAM is a type of RAM but it retains the data even after power off.
 
Flash is the least expensive of the 3 so it's normally bigger and due to being non-volatile you use it to store the code and you can also save there data, like your HDD in your computer. Flash is also the slowest of them all and it has a life time, i think the MSP flash has about 100k erase-write cycles. Note that although flash is access and writing is much slower than a RAM it's faster than a HDD, it's like a SSD.
 
RAM is very fast and can be accessed tons of times without wearing out. It's volatile so you can't use it to save a permanent code, although you can save there code and run from there, if you power down the MCU then you lost all the code. It's more expensive than the flash hence the smaller size compared to Flash. It's the best to store variable since it's the fastest and that i necessary when doing math and other operations. 
 
FRAM is the most expensive of the 3. It can work as a Flash since it's non-volatile and you can use it as a RAM since it's so fast. It's faster, less power consuming and it lasts even longer than a RAM.
FRAM is also a RAM because RAM stands for random access memory. RAM doesn't exactly stand for a volatile memory although that is mostly the case.
I think MSP is the first micro controller with the FRAM 
Note that unlike the Flash the FRAM wears out even with just reading it while the Flash is just with erase and write. Also the FRAM is slower than SRAM is remember right. One big advantage i read up is that since it's so fast compared to Flash, you can execute a code quicker (you read it quicker) so you can then have the MCU in standby by a longer percentage of time, so it's good to save power

Hi guys!
 
So i made a blog. Since i am the only in the robotics club that uses TI devices i was asked to teach about the Tiva. Well, what i can at least. And I'll post in the blog all the codes and tutorials.
 
It's still very early under-construction and will be something i will be doing along the school year. I am teaching it to some colleagues and will before the sessions, post the tutorials and some codes, but also post more codes after as examples. I will post basic info about the peripherals.
 
I hope it helps anyone that needs it. Also any feedback is appreciated, teaching someone live is different and i can forget some details while writing. Also i never done something like this, i usually do give lots of explanations but always live and more exercise driven.
 
Blog:
https://sites.google.com/site/luiselectronicprojects/tutorials

Yes, you can use them simultaneously.  The timers are separate devices.
As Kartman notes you can split either or both timers  - WTIMER0A and WTIMER0B are both 32 bit timers.
TIMER0 is a 32 bit timer, or TIMER0A and TIMER0B are 16 bit timers.

Yay pictures 

If you don't need much drive strength just use 2mA. Normaly it's enough. Only at high switching speeds more is needed

WIZpix is an internet enabled RGB pixel controller with built in PoE. 
 
WIZpix uses W5500 internet appliance to connect to internet and MSP430F5172 MCU to control RGB pixels.
Built-in DC/DC converter allows use of PoE, which eliminates need for directly connected power supply, ability to place controller far away from the outlet, and use of only one inexpensive CAT-5 cable. 
It

CC3200 users: Don't forget to visit http://energia.nu/cc3200guide/ and follow the directions there; this firmware update can only be done on Windows at the moment unfortunately, but it's important for this Energia release to work.
 
Sent from my Galaxy Note II with Tapatalk 4

http://forum.43oh.com/topic/2321-tlc5940-board/#entry20577

I am happy to announce that release 0101E0013 just went up on http://energia.nu. This release adds support for the awesome CC3200 WiFi LaunchPad and CC3100 BoosterPack for MSP430 and TivaC.
 
I want to thank everybody for their support and contributions. Energia would not have been possible without such an awesome community!
 
Details of the release can be found on http://energia.nu