Jump to content


  • Content Count

  • Joined

  • Last visited

About Techgique

  • Rank
    Noob Class

Profile Information

  • Gender
  • Location
    San Diego
  • Interests
    Music, Electronics, Golf, Automation
  1. Well I am hoping to access a few sound snippets of human voice that shout out phrases. Nothing too long, but better quality would be ideal. I was hoping to have the msp handle the triggering functions (motion detector causes the triggering) and the peripherals handle the audio. So the msp is simply too slow four something like this? I noticed a few chips that were mp3 decoders and had built in converters, so maybe that is the route I should be wandering down. Price is a concern along with legality which is why I am shying away from the sd hassle, though it seems as long as I don't claim to
  2. Uhg, Just got a look at the SD legal language and it appears that even in the "free" SPI mode, you would still have to join their little club and pay the HALA in order to implement SD in any designs. Back to the drawing board.
  3. Hi everyone, thank you for the info and lively discussion :thumbup: So I will migrating over to MicroSD for this project because my eeprom simply isn't holding enough data and even the larger ones 2Mb will start to suffer when accessing quality audio. Additionally, the MicroSD card will enable quick sound loading and testing with the female mount that I will be able to use in the design. From what I read in John Davies' MSP430 Microcontroller Basics, it seems that the hook up would be MOSI of MSP430 to MOSI of the SD card (or whatever the naming convention of the SD card is), then MISO of
  4. I'm using the launchpad for dev (2452) but ultimately would like to lower real estate with an AFE251. I'll be pushing audio onto the dac, I just came up on an eeprom programmer to more easily burn the audio in, but it will definitely need a constant sample rate. Thanks guys, time to hit the includes and books!
  5. Techgique

    I2C vs. SPI

    So now that I have a little clearer view of the declarations on the pins, I can start diving into communication between peripherals. Prior to getting code going and digging through user guides, I was hoping to get an experienced perspective from anyone that had dealt with both forms of communication. My goal is to pull pcm audio in hex off of an eeprom and send it through a dac. From what i've read it seems that spi would be better to begin with since I have a dedicated in and out rather than a combo port. The Queston is am I correct in thinking that I would be able to talk to the eepr
  6. Not being too obvious at all, because remember this may help many lurkers that are afraid to ask their questions. This is all much appreciated and that final note on the pins makes sense and I can see how that could throw a monkey wrench into the whole program by clearing everything. Like I noted before too, those shortcuts are wonderfully helpful and assist in more efficient coding, so I will definitely update that little ditty. With the button discussion, it would totally work different from an electrical perspective, so I tried to get all remants of buttoness out of the program in o
  7. @roadrunner84 I hope that anyone that needs clarification gets a chance to read this. This was immensely helpful and I feel that I have a much better understanding of the specific areas I was struggling with. Admittedly, the interpretation of code I put together from reading sections of code and their accompanying definitions got a little sloppy, so I appreciate your combing through any vague references. The way you put it into perspective helped me to visualize the 8 bits sitting there with ones or zeros, depending upon what we are doing with the port. @yyrkoon You were both essen
  8. Hi Guys, I'm hoping that this is a basic question, as I'm trying to learn in steps rather than bombarding myself with the volumes of guides and sheets. Right now, I'm trying to get a better understanding of the pin declarations. It seems that there are a few ways to set pins, direct pins, etc. In this code I am simply trying to sense a voltage from my motion sensor (which works, I tested that), then, if a HIGH read, place a HIGH on a different pin (1.6, the launchpad LED). I would greatly appreciate a few words regarding the PIN vs POUT vs PDIR rather than the pieces of use
  9. Though Ironically it actually rained yesterday. Hello everyone, I am roughly halfway through my BS in EE and love the things I have heard regarding the MSP430. Starting with the Arduino and making fun little home projects was cool, but I really wanted to start ramping up my tinkering experience and move into making more sophisticated, professional products. My programming knowledge is decent (C, C++, ASM), and fear not, I will not be asking for help with my homework, as the MSP430 is not used in my curriculum lol! I have a BA in Communications currently, but it really wasn't for me an
  • Create New...