Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by zborgerd

  1. I'm using the same version of Ubuntu with no real problems. Could you post what you see that indicates the port shutting down? Is it dmesg ouput? I've got rules in /etc/udev/rules.d/ to blacklist Modem Manager for TI devices. I had a custom set but I think that the TI/Red Hat GCC or Energia installed something newer. 70-mm-no-ti-emulators.rules ACTION!="add|change", GOTO="mm_usb_device_blacklist_end" SUBSYSTEM!="usb", GOTO="mm_usb_device_blacklist_end" ENV{DEVTYPE}!="usb_device", GOTO="mm_usb_device_blacklist_end" # TI USB Emulators ATTRS{idVendor}=="2047", ATTRS{idProduct
  2. That explains it. My SN falls after the range that Adrian mentions in the post about the update, and was manufactured / shipped right after that. Thanks for the info!
  3. Not sure. Did the original LaunchPad MSP-EXP430G2 ever get support for the newer tilib / MSP Debug Stack V3? I've not updated the emulator on mine, so it's still running the old original ez430-rf2500 firmware. The Spy-bi-wire will work even with the UART pins disconnected, but you cannot use the backchannel for UART communications. Should program just fine though.
  4. I don't think it's firmware unless it's *really* ancient. I've been using a 1.4 LP with the 2553, and my 1.4 LPs are from 4/2011 and have never had a firmware update. It predates the G2553. The only thing that I have to do on mine is swap the UART TX/RX pins if I wish to use the backchannel. What OS are you using? Can you communicate instead with the MSP430 Flasher? http://processors.wiki.ti.com/index.php/MSP430_Flasher_-_Command_Line_Programmer?DCMP=MSP430&HQS=Other+OT+msp430flasher
  5. Just got my half-price MSP-FET in the mail today. MSP-FET Backchannel UART support was added in MSP Debug Stack The firmware version and driver versions match this on my system. I default my terminal (Linux) to 9600 bps and this is normally fine with the FR5969 and F5529 Launchpad built-in EZ-FET. However, when I use the MSP-FET on the 5969 LP, I have to bump the speed of the port up to something higher and back down to 9600 before data begins to pass correctly. Has anyone else observed this? Again, the EZ-FET on the same FR5969 LP is fine. When I switch to the JTAG heade
  6. As I suggested... We've taken a few steps backwards. I'm sure that we can get it all ironed out quickly though. Lot of bright people in these forums.
  7. This is awesome! Sad to see that the HubPages site is down. Any estimated price for the kit?
  8. Anyone else notice that the compiler throws a lot of pointless warnings for mcu headers that aren't included as system includes? For instance: -isystem/opt/ti/gcc/include is fine where -Iopt/ti/gcc/include generates the following: /opt/ti/gcc/include/msp430fr5969.h:1256:1: warning:
  9. Still, that's nice code for people who can use it. Thanks for posting it!
  10. I ordered a FET even though we almost don't need them with Launchpad EZ-FETs. I'm sure it has its advantages with the speed boost and standard connector / cable.
  11. So, I've finally tried this in binary form to get it running quickly. Initial assessment is that the build and packaging is a bit weird. Interesting that libmsp430 is included, and in the /bin directory, but that's probably for the GDB agent with firmware update capability. Overall it's organized better than the beta version. It's a bit less forgiving than MSPGCC was with iinclude files and LD paths, but I guess that's what Makefiles are for. The included slau591.pdf manual makes it all pretty clear, and it's standard for GCC anyway. Seems to compile a few basic examples. Going to ha
  12. I'm still using yours... Cause it works. For what any of that's worth. May try Red Hat / TI's some day. Not yet. Appreciate the efforts though from all parties.
  13. I think that Energia will get an update soon. If you want to compile the library, you may be able to do it with hidapi and libboost. You may be able to loosely follow the Linux instructions here: http://forum.43oh.com/topic/5706-use-mspdebug-to-upgrade-msp430fr5969/ http://www.colotronics.blogspot.com.ar/2014/08/msp430-toolchain-in-ubuntu-1404-with.html Be aware that even if you can flash the board, you may run into problems with corruption and other issues that I've mentioned in other threads,. I guess that using TI's MSP-GCC-ELF compiler might resolve some of this as well as u
  14. I would assume that you need the newest MSP430 debug stack to support the new FR5969 LP with EnergyTrace. Older versions will not work. I compiled my own for Linux. Not sure of the procedure for Mac OS X. Where did you get it previously? Energia? http://processors.wiki.ti.com/index.php/MSP_Debug_Stack
  15. I still think that all of the sites should share a common forum, each with sections relative to the architecture. This would keep everything contained and also expose other users to the other relevant platforms. I hardly even bother checking C2k Central and Stellarisiti anymore, since there is just so little activity.
  16. What are your experiences so far? I've considered compiling it, and I think I even saw a prebuilt version for Linux on TI's site.
  17. So, my MSPGCC is not running any of the patches specified here: http://sourceforge.net/p/mspgcc/mailman/message/29796245/ There is a very good chance that this is the cause of my problems with having to frequently recover with the BSL.
  18. Glad you were able to get it to work. It gave me some grief for a while as well. I've had to recover this board so many times lately between the FET problems and other issues, that I'll probably just go back to one of my other MSP430 devices for a while.
  19. If it is a bug, I seem to be locking it up even when it's a valid target and a very simple UART application seems to be fine. It's odd, because I don't have this problem with other MSP430 devices and msp430-gcc.
  20. I've managed to lock my FR5969LP twice today now. In such a case, it gives no warning that the security fuse is blown, yet no tools recognize the device ("Unknown Device" error) and it will fail to load another program. I seem to be able to recover it with a CP2102 UART and: mspdebug flash-bsl -d /dev/ttyUSB0 With the UART DTR and RTS wired to the RESET and TEST pins per the manual... Even though it appears that the mass erase fails, it does seem to recover the device. What has everyone else used in these situations?
  21. It can timeout and may be related to Modem Manager, but I've not yet determined this. I disabled Modem Manager on these devices with some udev rules and need to confirm if it changes things. The flasher is supposed to come with some binary firmware, but even it seems to flash unreliably on Linux. What I can say is that my tilib library (built from scratch) on Linux believed that my FET was outdated and did demand an update... And failed. But I'm pretty new to the eZ FET lite (been a while since I've worked with an MSP430) so I'm not yet sure about the finer details.
  22. You can also find the DLL included in the Flasher utility ( http://processors.wiki.ti.com/index.php/MSP430_Flasher_-_Command_Line_Programmer ), or build it from the source code, which is what I did on Linux. http://processors.wiki.ti.com/index.php/MSPDS_Open_Source_Package
  23. So I built a new tilib and the board is fine with all of my tools. Unfortunately, I've been running into a lot of problems with FET corruption on this FR5969LP board and also the 5529LP. The flash ultimately fails on Linux but seems to recover on a Windows machine with the flasher utility. But now that I have the FET fiwmare up-to-date, everything seems to work well.
  24. Pretty sure that this new release of tilib is mandatory. I have an older version and this board reports as unrecognized. Going to update it later.
  • Create New...