wilywyrm

I assume you mean the 2452 and the 2553? Basically what you said was right, except the 2553 has a USCI (Universal Serial Communication Interface) so you can talk to a computer through the hardware UART or to other chips via SPI or I2C. For chips without a hardware UART, you have to implement it in software, and instead of a USCI, you would have a USI (Universal Serial Interface) for just SPI and I2C communication. EDIT: At 600+ pages, I personally wouldn't print it because eventually you will miss the Ctrl-F ability of a pdf.

Thanks! Fixed it, and since it looked like there was too much free board space, I added current limiting resistors on the low side.

Hi everyone! Haven't posted here in a long time, so I thought I'd share something I'm working on. Picture this: you and your friends have gotten together for some sweet pen-and-paper roleplaying action. It's the first round of combat, and everyone's getting ready to roll initiative. But then disaster strikes! The family dog has eaten the d20, and you were all sharing the same set of dice because YOUR FRIENDS ARE ALL TOO CHEAP TO BUY THEIR OWN! The obvious solution is to buy sets for them and give it to them for Christmas or something, but there's no fun in that. Cue MSPDice, a f

Hi again guys, I got the UART to work thanks to Rickta and pabigot but now am having trouble generating a PWM signal to control my servos. What I'm trying to do is use TA1CCR0 and the timer overflow interrupt to generate a square wave. Instead of CCR0 determining the period length like usual, I'm trying to use a clock of 3MHz (DCO 12MHz / 4) to get a overflow every 65536/3000000 = ~21.8ms for period length and use CCR0 to take care of pulse width. CCR0 should be serviced twice every period, once to start the pulse and another to end the pulse. Every time the CCR0 interrupt is service

They got discontinued after March last year. I guess not enough big manufacturers wanted them anymore. NXP still makes them, though, and I think nobody's link shows what I'm talking about.

To be honest, that makes it sound like TI knew all this and still singled him out...

Today was... a learning experience. I had wanted to use an external crystal to provide a 16MHz MCLK and spent all day trying to figure how, but it looks like the G2553 doesn't even have the capability to use an oscillator above 50kHz! I hope they provide that in a later G-series generation, but in the meantime, I'll have to use the DCO like in Rick's code. Plan is now a 1MHz MCLK, 500kHz SMCLK for the controller's SPI bus, and 32.768kHz for the UART. All the advice and links you gave will definitely help with fully understanding UART functionality, but for now I'll leave good enough alo

pabigot, thanks for the suggestion. I need to try that tomorrow. Rick, thank you SO much for the code. I'm actually getting output now! I did have to modify your code a little and take out some C++ stuff since mspgcc doesn't want to compile the cpp file. I'll post it tomorrow for reference, but it does work and I understand it for the most part. The (comparatively small) trouble now is that I don't get this modulation business. Could you explain the UCA0BR1 register? The datasheet goes a little over my head on the first read, and mainly I want to know how to adjust the registers for dif

Thanks for the help, guys! Still don't have it fixed or really know why, though. Does the code without the change output a single 'a'? I'm using a Rev 1.4 launchpad right now, but I do have a 1.5 also. I don't think the problem is with the jumpers because it works with TI's unmodified code example perfectly. Sorry for not being clear, and "interrupt-based" meant hardware USCI (USCIAB0RX_VECTOR, USCIAB0TX_VECTOR, all that good stuff). If hitting the port with a unsolicited continuous stream of 'a's will kill the port, how do I not kill it without sending something first? The goal

I'm doing a robot arm project for a competition at my school, and I'm having real trouble with getting the g2553 hardware UART to work. For the life of me, I can't figure out why it's not printing anything at all. I compiled the TI code example that I'm modifying and it works just fine on my Linux box with Cutecom, but when I make transmission not interrupt-based, I get nothing! :x The functions I have in there were what I planned to use with a timer to send strings after a TimerA interrupt, but eventually I stripped it down to just writing to the TX buffer. Still nothing. Shouldn't it give

It shouldn't. I imagine they reserved the Launchpad chips from some batch earlier in the year. For what it's worth, I ordered mine on the 22nd and got it today. It's a 1.5!

I have to say, I don't think typing all that out will save anyone any time.

Well, that's the thing. I think it cost them so much to ship those boxes that they changed all their deals to "free shipping on orders over $50". I may have single-handedly killed that for you guys. :cry:

All this is hilarious and so true. I once ordered from Arrow. They packed the whopping 2 ATMegas I ordered in a full tray designed for 64 chips and wrapped it all in an outrageously cushioned box about 3 feet wide. And don't get me started on Element14. Last year they had a free shipping promotion and I took advantage of it to put in a full E12 set of through-hole and SMD resistors from 10 Ohms to 1M Ohms in one of mine. Individually. Big mistake. They packed each value of resistor in its own padded paper envelope. All 120 of them. That took up so much space they had to send two 6 feet

Oops, never mind.