Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by cubeberg

  1. Sorry - busy weekend/work week


    On 8/25/2018 at 11:58 AM, NurseBob said:

    Generally, you do not want to leave unconnected pins floating; your device can experience problems when pins float

    Enabling pull up/down resistors should be sufficient for that problem - it's recommended for low-power optimization anyway.  


    Looks like @NurseBob has done an excellent job answering everything else :)  

    FWIW - I like Elecrow over Seeed, etc.  I've always had good luck with them - and they have good customer service for the few times I've had any issues.

  2. 10 hours ago, ak96 said:

    Also, I thought the MSP430 only works with 3.3V. Will 3V be enough?  

    The MSP430G family will run down to 1.8v actually - but the CPU speed you can run at is reduced.  Here's a good discussion from E2E - https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/599159?MSP430G2553-MSP430G2553-Clock-Speed

    10 hours ago, ak96 said:

    I left the pins I'm not using unconnected

    Assuming you've got the space on your board - I'd at least break unused pins out to SMD test points - you never know when you're going to need an extra pin or two.  

    10 hours ago, ak96 said:

    Should I use another header to connect GND/TST/RST or should I add TST and RST to the power header.

    If there's any chance you may want to debug while connected to an external battery - I'd probably suggest at least adding an extra GND pin so you have VCC/GND for battery and TST/RST/GND for the LP debugger. Otherwise - break it out into a different header.  Again, unless you're low on board space.

  3. I'd suggest taking a look at the launchpad schematic - there are probably a couple different places you can find it - but here's one - http://www.ti.com/lit/ug/slau318g/slau318g.pdf (Page 15)

    Pay attention to filter caps on the power lines (10uf and 100nf), as well as the reset pin (I usually just add the the 47k pull-up - although I think the cap is recommended as it prevents problems with power supplies that are slow to start up).  

    For programming - you just need GND, TST and RST - I usually break out a 4 pin header - VCC/TST/RST/GND - for programming/debugging.  Pull all of the jumpers from the Launchpad, pull out the chip, and connect GND/TST/RST from the emulator side of the LP and you can program/debug the board.  I've connected jumpers from the boosterpack headers - but the 47k pull-up on the launchpad can cause problems (I've had a few aggravated troubleshooting sessions caused by that).  Connecting from the emulator side should avoid that.

    FWIW - unless you need 9v for a peripheral - you're going to put off a lot of heat dropping 9v -> 3v, and 9v batteries drain fairly quickly.  You could, however, run straight off of 2xAA or 2xAAA batteries for quite some time with an MSP430, depending on what else is in your circuit. I've even run an MSP430 with an LED and wireless transmitter for months off of a CR2032 by staying in sleep mode as much as possible and using the transmitter infrequently.

  4. @hmjswt - you could easily say that about a lot of things (C vs Assembly, roll your own database, etc.)  :) 

    I'm a web developer - but trying to figure out everything from hardware to reporting can kill a project pretty quickly.  Like @zeke - I've got a lot of unfinished projects - usually because I get bored trying to get over obstacles in the project.  Since DeviceHive supports MQTT - it should be pretty easy to port a project over to something else at a later point in a project.

    I was able to get a simple POC working with a Raspberry Pi on DeviceHive.  Not too bad - it'll be a good place to start working on MQTT for some of the hardware I've got sitting around.  I'm not so sure about deploying DeviceHive though - there are a lot of components to install - although they do have docker instructions.

  5. So I've been horribly quiet in the forums lately - mostly because of a lack of free time.  Since I don't have a dedicated work space - having to break down and set up tools, projects, etc. severely limits how much time I have on projects.  Thankfully - I'm getting a new house with my own room for projects as well as a garage!  I'm hoping this will mean more time to complete projects.

    Most of my components are in cardboard boxes and plastic tubs - well organized but not exactly what I'd like for a nicely organized full workspace.  I know we've had threads for showing off your workspace - but I'd love to hear about what you like best about your workspaces or anything you think might be helpful since I haven't had a dedicated space before.

    So - any suggestions on the following?  I'm definitely not afraid of making my own furniture as well.

    • Organization (small components to WIP projects)
    • Types of work spaces (large open table, bench with shelves, etc.)
    • Sites/videos with information that might be helpful (I'm thinking Adam Savage or Ben Heck videos for instance) 
    • Tools (not soldering iron or oscilloscope, more like magnifying glass, monitor holders, etc.)
    • That one thing that you find invaluable for your workspace.
    • Where to buy affordable stuff (I'm in the US, but non-US places might be good for other forum members)

    I've heard Harbor Freight is bad for tools - but they seem to have pretty cheap component organization options, and I've got one near by.

    And I'm trying to talk the wife into a hidden bookcase as the entrance.  Fingers crossed!  If I pull that one off - I'll have to post a video tour!


  6. @@RobG - I'd have to agree on the piezo - this type of clock is probably too bright for an area where you'd want an alarm.  I have a spot for one on my VFD clock but only populated it for my first test device.  I have three on my desk at work, one with a buzzer that beeps on startup - I should honestly pull the thing off of the board.

  7. I'd suggest downloading the code examples from the product page - http://www.ti.com/product/MSP430G2553/toolssoftware (download link - http://www.ti.com/lit/zip/slac485)

    There are a lot of examples depending on what particular aspect you're looking for.  Here are a couple of examples that might be helpful:

    • msp430g2xx3_P1_04.c - toggle LED when button pushed - using LPM4
    • msp430g2xx3_lpm3_vlo.c - LPM3 - LED toggled every 6 seconds
  8. I believe so - assuming your connections are close enough.  You do need to consider corrosion/oxidation as a potential issue.  One alternative would be to use capacitance as well instead of a straight on/off - assuming you don't wake up too frequently - you should get good battery life out of that as well.

  9. My question is, if I can flashed firmware to MCU, was my MCU have ability to be dead?

    I personally wouldn't rule it out.  Best advice I can give - rule out potential problems, one by one and don't make any assumptions that parts are viable (could be a bad LDO, especially if you're not 100% sure it's genuine)

  • Create New...