Jump to content

Search the Community

Showing results for tags 'booster pack'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 6 results

  1. After joining this forum over 3 years ago I thought it overdue that I say hello and contribute something that I hope you will find useful. Attached is a picture of simple booster packs that I make. But are they really a "booster pack"? Hmmm. Debatable! They are cheap and easy to make and I have made 5 of them. I use them all the time because the whole of each project, including the MSP430, is attached to the booster pack. This means I can switch between projects without re-wiring, I can change the model of MSP430 in seconds and I only need one Launchpad. You can see from the picture that I provide two sets of header pins to attach "stuff" to, but provide four header pins for the 3.3V and GND. I also use long-leaded header plugs, partly because I have to solder the strip boards "upside down" (notice the small gap between the strip board and the header sockets) and also because the excess leads are easily accessible test points for things like logic analysers, etc. I keep the strip board to the smallest possible size so that all the Launchpad jumpers remain accessible. I've tried different designs, some with LEDs, switches, small breadboards and more besides, but this is the one I use all the time. I call it a "pop top" because you pop the top off a launchpad and swap it for another, then another. That's all for now. Hopefully it'll not be another 3 years before my next posting!
  2. Hi, I am currently working on a code in Energia that will allow me to upload and send a binary file wirelessly from a client site to the CC3200. So far, the code has successfully accomplished the following: -the board establishes a Wi-Fi network -commands from a laptop can interact with the board (the Energia Simple Wi-Fi Server example (LED ON/OFF) code was tested to ensure this was working) -a 9 byte binary file is sent through Wi-Fi to the board's volatile memory, saved from volatile memory into an on-baord flash memory file, and confirmed by sending it back to the laptop through a serial connection The code is eventually supposed to receive a larger binary file (we hope around 500 KB) that will represent points on a sinusoidal curve. This file will then be sent to the Audio Booster Pack board to play the audio file. I created a flash file which was opened, and written to through a buffer array containing the binary file contents. This method was successful for a 9 byte file, but I learned that a larger 500 KB file cannot be stored in a buffer array so easily. I think this is because of a lack of RAM space on the board. How can I implement a code in Energia in order save this larger binary file to the flash memory? Is the buffer array approach a good method? Latency isn't really an issue, as long as we can fit the whole file on the board, and then play it after. Thanks, any support is greatly appreciated!
  3. I have been using a simulink model and CCSv5 to try and create the .out file for the launchpad however the file is not stored after being disconnected (ie reverts back to the out of box temperature check program) I am trying to control the h-bridges on the booster pack of the drv8711 and have attempted to follow a number of examples such as: http://uk.mathworks.com/matlabcentral/fileexchange/49109-dual-motor-control-with-ti-f28069-launchpad Having difficulty connecting and controlling the board if you could offer any suggestions or advice on simulink control methods I would be most appreciative
  4. As discussed in this thread, I took a first stab at a Booster Pack for the 1.35" SHARP Memory Display. As suggested by @@greeeg, I added two footprints: FPC connector (on the back) zebra strip connector (on the front) While the outline is for the 1.35" variants (LS013B4DN01, LS013B4DN02, LS013B4DN04). The 1.28" (LS013B7DH03) and 1.26" (LS013B7DH01) displays should work too as the FPC cables are of similar length and zebra footprints are identical. The smaller, circular displays might work, but the length of the FPC cable might be too short. The larger displays have the same FPC cable, but will overlap with the LaunchPad connectors. I could fit the next size up (2.7", LS027B7DH01) when rotating the screen 90 degrees. I only supply 3.3V. The current small-sized displays are all 3.3V. The older 1.35" versions specify 5V supply voltage, but in my experience work fine with 3.3V. I don't know about the larger displays. Connections are as follows: SCLK -> P1.5 (SPI CLK) SI -> P1.7 (MOSI) SCS -> P2.5 (SPI CS) DISP -> P2.0 (display on/off) I did go with the BoosterPack recommendations for SCS and DISP, but I'm considering to put them somewhere on the upper 14 pins to maintain compatibility with my original code which was for the MSP430G2231. Not yet connected are EXTMODE and EXTCOMIN. These are to control how the LCD polarity-toggling is driven. If EXTMODE is high, toggling is done through EXTCOMIN, otherwise it's done through SPI. I might pull EXTMODE low with a resistor and expose jumper pads to change the configuration. I filled the front plane with 3.3V and the back plane with GND. The horizontal shape at right below the zebra strip pads is the cutout for the flex cable. Any input is greatly appreciated.
  5. Hi, I am a newbie. I'm currently doing my final project for college. I use MSP430G2553 and 8x8 LED BoosterPack by Olimex. I have been learning the example code in Energia (the one that produces sine wave and scrolling text) but I haven't figure out how to send data to the booster pack. I only succeed to control the buzzer via push button. I have read the manual & schematic for the booster pack. I figured that I need to use three ports to control the LED; CLOCK, LATCH, and DATA ports. However, I couldn't understand the code part that sends data to the LED. I have been trying to light up a single LED in that 8x8 matrix but haven't succeeded, yet. Could anyone give me advice or step-by-step tutorial on how to do it? I really am new to this world--it's been less than a month when I started to 'make friends' with micro controller. I have read the MSP430 manual and am able to control the LED & push button in the LaunchPad, but not the booster pack. I am looking forward to hearing from any of you. This will be a great help. Thanks Regards, Nisrina Rahmah
  6. Hi all, I think I always had the (wrong) impression that the pins on the booster pack are, at least attempted, to be standardized. Obviously this is not true. What I meant by standardized is that for example, the lower left pin is P2_2 on G2553 LP, but it is P4_1 on the new F5529 LP. Looking at the design guide for booster pack at http://processors.wiki.ti.com/index.php/BYOB the "BoosterPack Pinout Standard" chart does not mention exact pin number. I always thought it is "standardized" by pin number but it looks like it is standardized by something else. So, does that mean if one is using CCS or Energia, the program or library may need updating the pin number according to the target LP, unless strict coding practice are in place like using of abstracted variables like RED_LED are followed? How about common SPI / I2C library? By the way, always wondered why the 40-pin layout is done the way it is now. Wouldn't it be more convenient if the extra 20 pins are laid "outside" rather than "inside" to the basic 20-pin settings? That way, we could have easier access to the extra pins when a 20-pin booster pack is in situ..
  • Create New...