Jump to content
43oh

Fred

Members
  • Content Count

    885
  • Joined

  • Last visited

  • Days Won

    43

Everything posted by Fred

  1. It could be worse. They could have called it the Internetduino.
  2. I'd say that if the FET / hub side of things is where the problem is, then it makes a good candidate to be programmed using the FET on the other launchpad and left permanently in your project. You could even cut the broken FET part off. (Edited for phone keyboard typos.)
  3. The detachable BSL programmer is a good idea, but why not have it on the other end - still removable but connected by default?
  4. One thing the TRF7970 has taught me is that QFN is a PITA. Well, I'm actually off to meet monsonite on the pub. Let's hope that doesn't adversely affect his ability to get an LED blinking by sunrise!
  5. Send to work now. Thanks. Sent from my Nexus 6 using Tapatalk
  6. I can't seem to post anything or reply from Tapatalk recently. Reading works fine. Just me?
  7. Hi from another UK member.
  8. I know the FET in the G2 LaunchPad was limited to what microcontrollers you could program with it - i.e. the "value line" topping out at the G2955. I don't know if this has changed with the introduction of more powerful LaunchPads. Anyway, I wouldn't assume that a FR2433 would work in the DIP socket of the G2.
  9. When something doesn't work one of the first things I do is swap I/O pins. Even if I'm pretty sure it's right. In fact this exact thing happened last night between a LPCXpresso1769 and an SD card. (Sorry for the MSP430 infidelity - I'm working on some Smoothieboard improvements.)
  10. I've managed a few. Swapping VCC and VSS on my first etched PCB was a good one. I'm glad I'm not the only one who's done that. I also noticed that a TS430RGC64USB target board that I had supported the F5510 that I was coding for. Great! So I stuck it in and wondered why it didn't work. It turns out that a LQFP48 will fit in a QFN64 socket. It might not fit that well or work, but it goes in. Amazingly neither of these (and probably worse that I've forgotten) damaged the MSP430.
  11. True - but they're good value if you know in advance that the electronics are junk. And for most of us on here it's something we'd be comfortable fixing - and probably enjoy it too.
  12. Awesome work as always. What are you using the Smoothieboard for? The mill or the laser? I've recently switched my laser over to one and started contributing to the software. Nothing much so far - just added TTL laser control for now. I'm hoping to add PPI (pulsed cutting) later to help with making mylar solder stencils. Coding for the NXP LPC1769 isn't as nice as any of TI offerings so far. Believe it or not I miss CCS!
  13. My first PCB had vcc and vss switched. Nothing a couple of bodge wires and cut tracks couldn't fix. My tips: Add a few test points. If you have distinct sections like a microcontroller and a peripheral, then add traces between them can be probed or cut. If one bit is wrong you can at least isolate it and make sure the rest it is OK before you make version 2.0.
  14. Have you tried disabling the P1 interrupts with P1IE before clearing P1IFG? Unlikely, but worth trying. Also, don't forget that on releasing the button you will get button presses too, as the contacts don't separate cleanly either.
  15. Fred

    Ultra Low Power

    Earlier versions of CCS could be added to an existing Eclipse installation. Not the case now though. I agree it's not the slickest IDE bit worth it for the debugging and tools like EnergyTrace.
  16. Fred

    Ultra Low Power

    Glad you solved it, Sven. And sorry your thread got turned into a 3-way IDE battle on the way there.
  17. Fred

    Ultra Low Power

    That looks OK to me a first glance. PxREN is ignored for outputs, but you might as well set it to something consistent. I'm not a Linux user, but I know TI does support Linux. You've probably seen this page, but just in case... http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv6 CCS is based on Eclipse so if you have any quirks with your particular distro, maybe check for any tips to get Eclipse installed.
  18. Fred

    Ultra Low Power

    Fair enough. I quickly scanned the article on a small screen and only spotted LPM3. I do find it odd that when someone asks specifically about low power that you're directing them to Energia. Energia makes it a little less obvious what mode you're in - i.e. someone else's abstracted code handles it for you rather than setting it yourself. It doesn't do EnergyTrace - you have to go into CCS for that. If someone was already using Energia or struggling with CCS then fair enough, but why direct them away from a good IDE that they are already using to a less capable one that they're not familia
  19. Fred

    Ultra Low Power

    CCS is pretty good at giving you tips on power consumption. The Low Power Advisor should analyse your code when it compiles. You will get tips like setting unused pins to output and low. EnergyTrace++ on the later LaunchPads and MSP-FET let's you measure actual consumption very accurately. Personally, I wouldn't recommend Energia if you want fine control over power consumption and low power modes. Can you even get LPM4 with Energia? I'm not sure.
  20. Pretty much everything supersedes the Arduino. Why anyone would want to use that abomination of an IDE and miss out on features like proper debugging is beyond me.
  21. I notice there is a switch to use CMSIS for driverlib planned for March. I wonder if that may coincide with any other announcements? (All this wild speculation reminds me of the time just before the MSP432 was announced.)
  22. Thanks for the clarification, Mark. It did seem likely that the MSP432 was the direction that TI was taking, but it's good to know for sure. (I ended up tagging a few more 432s on the back of an order for the CC2650 LaunchPad anyway.) Antarctica? It sounds like you could be testing the limits of that -40C spec!
  23. Mine just arrived. It looks like a nice board, but the software and documentation seems a little lacking and I'm not getting very far with it. Flash Programmer 2 fails to upgrade the firmware that the documentation suggests is needed. The "SimpleLink Starter" app isn't in either the Apple of Android app stores. The SensorTag version can't see the device. I can see it from my phone but it refuses to pair. I'm just going through the guide here on how to set up a development environment for the SensorTag. I hope that will get me going in the right direction.
  24. There are example in MSP430Ware that cover the F149. Taker a look in the folder MSPWare_2_40_00_37\examples\devices\MSP430F1xx\MSP430x13x_MSP430F14x_MSP430F15x_MSP430F16x_Code_Examples\C. For instance there's fet140_uart01_09600.c that does a simple echo.
  25. I've not really used the F149, but MSPWare has good examples for those sort of things - at least it does for other devices.
×
×
  • Create New...