Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by gordon

  1. Tripped over this by accident while watching one of Travis Goodspeed's talks: Efficient Micro Mathematics
  2. [tipdf]SLAU320[/tipdf] comes closest. SBW is serialized JTAG, SBW RST is JTAG SRST#.
  3. Nice, but you have spent about $165140 more than would have been necessary for a quick start . The AFE253 can conveniently be programmed with the $4.30 LaunchPad, AFE253 is ~$6-ish in one-off. Not saying the UIF will not do you good, it just wasn't strictly necessary. The difference would have better been spent on The Book. Anyway, your best friends will be [tipdf]SLAU144[/tipdf] and the device-specific datasheets. Most of the stuff you find regarding the LaunchPad and the G2452/G2553 will basically apply as they are part of the same family. This should get you going.
  4. ... unless it was delivered as a custom (or even "custom") part to one of IRF's customers in which case they very well may just politely shake you off.
  5. Tap into the existing one (assuming the freezer has one)?
  6. Re-cap it. Just unconditionally re-cap it. Chip Quik worked for me on several similar occasions. You can also relatively easily (but be careful) cut at the feet with a Dremel or something and off the heatsink goes.
  7. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25672 Good luck.
  8. You mean it's building msp430-libc that errors out? Try something to the effect of Index: build-mspgcc =================================================================== --- build-mspgcc (revision 84) +++ build-mspgcc (working copy) @@ -388,6 +388,8 @@ ${MAKE} install cd ../../ +unset CFLAGS LDFLAGS + cd "msp430-libc-${libc_ver}/src" [ -d Build ] && rm -rf Build echo '!!! libc make' (exact context may differ)
  9. Should work (does on everything else, and since the procedure is part of the GCC build procedure, it really shouldn't depend on where you are building the beast). http://gcc.gnu.org/install/prerequisites.html Careful studying of the various config*.logs and the like would probably be more helpful than guesswork .
  10. There's a blog entry over at Todd Harrison's place of Todd repairing a car stereo VFD. There are other stuff in there too, but there's also a bit about VFDs as such; some might find it useful.
  11. The DS18B20 is a whole different animal. oPossum, Zeke and maybe RobG have posted Maxim 1-Wire code a good while back, search the forums, here's a link for starters: viewtopic.php?f=10&t=456
  12. No debugging, though (last I checked).
  13. He said precision, not resolution.
  14. GCC + MSPDebug + the LP drivers should suffice. You can rip them out of Energia, I suppose (or you can just install Energia and not use the Energia bit).
  15. You could have a simple firmware that just blinks a LED and hide it behind an "Identify device" button. If you can read the USB descriptors off the device, the serial number is a unambiguous and unique identification of a LaunchPad (mspdebug -s).
  16. Completely unscientific hunch (not even a Windows user myself): install Energia into a directory that has no space in its path (assuming your name has a space in it).
  17. ... but it still might be better safe than sorry (again, depending on what your compiler does).
  18. And a LOT of current... He is going to heat freaking gallons of water, doubtful that a couple of tens (or even hundreds) of mAs is of concern in this case...
  19. I do everything with a 3.2mm (.126") Hakko T18-D32 chisel tip, from DIP down to 0805 (routinely)/0603 (rarely, pretty much the limit of my sight/handshaking) and TSSOP/QFP. Tried the tiny tips, turned out to be mostly worthless (they do save the day every now and then, but for routine work, meh). ... uhm, is this a firestarter? I would be cautious with that. The product catalog lies that it's 900*F (and not temperature controlled), if you exchange the tip for a smaller one it'll probably shoot to seventh heaven... Better invest in a temperature controlled iron (or a hot air station, o
  20. I am pretty sure you can just #define PROGMEM to oblivion, should bringing unchanged code over tickle your fancy. (It has to do with the AVR being Harvard and this IIRC is their way of tricking data to be "code" (so as to make it reside in flash or something), whereas even the concept doesn't exist on a von Neumann '430.) Ed. well, yeah, then you still have to constify, so unchanged won't fly too far anyway... .
  21. Binary constants are not standard C but a GCC extension -- not sure if IAR has them. Just use decimal or hex instead.
  22. BH, For some reason the forum now doesn't recognize forum links written as viewtopic.php?f=35&t=1684&p=22458#2258 It used to turn them into proper URLs referencing to itself. Very convenient. Can you check what's up? Not sure, but could it have anything to do with the new "quick reply" thing? (It doesn't work in the full editor either, but maybe when you installed that it had some unexpected consequences too.) Thanks,
  23. Because the booster pack layout doesn't originate at (0,0). Also because it is not exactly 50mm x 50mm, see http://43oh.com/forum/viewtopic.php?f=9 ... =40#p11420
  • Create New...