NatureTM

The other day I was driving some transistors, and I forgot to put a resistor between the base of the transistor and the MSP430 pin -- effectively a short. It took awhile, but I ended up frying the port. I could run and upload code and stop at breakpoints, but toggling pins didn't have an effect on the output. When I realized my mistake, I touched the MSP and it was pretty warm. I don't know if this really answers your question, but it seemed worth mentioning.

Looks like DanAndDusty beat me to it, but here's what I had. We pretty much said the same thing. If you only want the LED to be turned on once (so to speak,) you could disable the interrupt or stop the timer when you set the LED. // Timer A0 interrupt service routine #pragma vector=TIMERA0_VECTOR __interrupt void Timer_A (void) { timerCount = (timerCount + 1) % COUNTDOWN; if(timerCount ==0){ P1OUT ^= (LED_0 + LED_1); // **** 1-shot occured, stop interrupt from repeating **** CCTL0 &= ~CCIE; // clears the interrupt enable bit } } Or you could use: // **** 1-shot occured,

I bought a 2.5kV "laser" power supply from a surplus store this afternoon. It runs off of 9V and that's all the specs I have. The power input wires were yanked out of the base, so I got it at half price! A little drilling and soldering and I should be in business. This is the first time I've played with anything HV so I had a couple questions maybe someone can answer. I plan to be cautious when "experimenting," but how dangerous is this thing really? Will it be safer to run off a 9V battery vs 9 volts from a PSU I plug into the wall? I'm guessing it would be but I don't really know.

Student, huh. I'll bet it was an overconfident engineer!

Great timing too! I just had my first day of work at my summer job, and I found out I have tomorrow off in addition to Monday. Ooo-Wee! Stopped at the liquor store on the way home. Let me know if you want me to email you a drink! :arrow:

I like it. I've actually wished there was something like this in the past. When users have asked, "How do I get (some peripheral) working with launchpad," there have been times when I wanted to respond, "I'll do it for you if you buy me one!" I was worried someone would be offended if I said that, so this is perfect. I also really liked that you used me as the example! 8-) Sounds like a great idea!

I really liked the glitchy sound you added Fabrice. Was that in the original? I didn't see it in the video.

If I were to try to see how fast I could get it to run, I'd use one of those DCO-setting functions from the calibration thread. I'd set the DCO, log that setting though serial, then perform some operations and test the result of the operations against an expected value. If they match, increment DCO and repeat. Maybe changing the clocks so often might make sending serial too messy, however. I think you could work around it. For the test operation, I'd think multiplying two doubles would work. That should go through a bunch of different CPU opcodes since it's done in software. I'd also be

I ran my ADC-based random number generator's output through the DIEHARD battery of tests for randomness quality and it failed miserably. I tried different pins for the ADC and a few different things in the code and all the results were terrible. That should probably have been expected, but a little part of me was still hopeful. I guess we shouldn't use it for any kind of cryptography. I also took a closer look at how I was removing the bias. I think I just pulled that code out of my booty, because the fact that it led to low bias output seems to just have been luck. It works when t

Hi! Thanks for choosing 43oh. I look forward to trying EasyMSP.

Someone in IRC had this problem, but I forgot the username. I think he was able to resolve the issue. It could be worthwhile to mention it in there and idle in the room for several hours for a response. There are several people that use the IRC but not the forums. When we were discussing it in there, a couple of us pretty much rubbed our fingers all over the pins of the chip and weren't able to reproduce the issue, so it's something that isn't supposed to happen. I wish I remembered how it was resolved (if it was.)

I checked out your blog post. It looks like a fun way to practice your C++. It's probably beyond the scope of what you're looking to do, but I wonder how well something like this would work on an MSP430 through serial.

- add a section in the family guide for the capsense hardware

My hard drive crashed, and I'm working off a fresh install of Windows and CCS. Now I'm getting the error too! I'll reinstall CCS when I get around to it and let you know how it goes.

I'm glad I know about it now too. No problem.

I was looking for example code for RF2500 last night and came across some TI code for using the ADC as a random number generator. The function was in assembly, so I rewrote it in C: bool getRandomBit(){ ADC10CTL1 |= INCH_5; ADC10CTL0 |= SREF_1 + ADC10SHT_1 + REFON + ADC10ON; ADC10CTL0 |= ENC + ADC10SC; while(ADC10CTL1 & ADC10BUSY); return ADC10MEM & 0x01; } Pin 1.5 is floating unconnected, and is measured by the adc. The LSB is used as the random bit. There's a twist though. Pin 1.4 is also floating unconnected, and is used as Vref+, so the top end of the range is float

It should work the way you say, so I wrote something quick to test it. #include void main(){ DCOCTL = CALDCO_1MHZ; BCSCTL1 = CALBC1_1MHZ; WDTCTL = WDTPW + WDTHOLD; P1DIR &= 0x00; // all pins input P1REN |= 0xFF; // enable all internal resistors while(1){ P1OUT |= 0xFF; // set all internal resistors pull-up if(P1IN != 0xFF) // test if all are actually pulled high while(1); // pin(s) are low, fail, hold here P1OUT &= 0x00; // set all internal resistors pull-down if(P1IN != 0x00) // test if all are actually pulled low while(1); // pin(s) are high, fail,

MIDI is *so* last month

Nice to see your progress with the evalbot. Mine is just sitting on my desk like a paperweight. So you have the captouch booster and the RF2500 connected to the launchpad at the same time, and the RF2500 board retransmits the UART wirelessly? If I understand that correctly, that's so cool!!!

Welcome!

I'm not sure about your question regarding the timer, but I've found the internal resistors to work great for I2C communications, and they allowed me to eliminate an external pullup resistor from my midi input circuit. I'm a little confused about your question regarding the timer in output mode. The internal resistors are generally used on input pins. They need to be weak enough so the pin with the internal pull-up can be set low by an external device. Same with pins pulled-down internally -- an external device should be able to set them high. Is this an answer to your question?

I used to get that problem periodically, but not often. When I upgraded my computer, I had to reinstall everything, including CCS. It stopped after that. OS = Win 7 64 w/UAC enabled before and after upgrade. Are you using an old install of CCS that has been upgraded several times? That was the case for me when I used to see that error. I'm with the others in suggesting uninstall/reinstall.

That is awesome! You lucky dog.

Got my prize in the mail today! I wish I could start using it right away, but I decided to not keep up with my calculus class for the past month. My exam is the day after tomorrow. I did 3 weeks worth of units today, and I get to do another two weeks worth tomorrow. "Dave, my mind is going. I can feel it. I can feel it. My mind is going. There is no question about it."