Jump to content

zborgerd

Members
  • Content Count

    348
  • Joined

  • Last visited

  • Days Won

    2
  1. zborgerd

    Issues with MSP430G2 HW UART on Ubuntu 14.04

    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}=="0010", ENV{ID_MM_DEVICE_IGNORE}="1" ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0013", ENV{ID_MM_DEVICE_IGNORE}="1" ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0014", ENV{ID_MM_DEVICE_IGNORE}="1" ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0203", ENV{ID_MM_DEVICE_IGNORE}="1" ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0204", ENV{ID_MM_DEVICE_IGNORE}="1" LABEL="mm_usb_device_blacklist_end"
  2. zborgerd

    Could not communicate with FET error = 35

    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. zborgerd

    Could not communicate with FET error = 35

    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. zborgerd

    Could not communicate with FET error = 35

    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 3.4.1.0. 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 header with the MSP-FET, the behavior is different. There seem to be some differences in the UART behavior on the EZ-FET vs the MSP-FET.
  6. zborgerd

    Sharp PSP LCD LQ043T1DG01 $10 Shipped.

    Awww. Too slow!
  7. zborgerd

    GCC for MSP430 officially out of beta

    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.
  8. zborgerd

    C-Programmable Logic Controller with MSP430

    This is awesome! Sad to see that the HubPages site is down. Any estimated price for the kit?
  9. zborgerd

    GCC for MSP430 officially out of beta

    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:
  10. zborgerd

    Daylight Saving Time detection and adjustment

    Still, that's nice code for people who can use it. Thanks for posting it!
  11. 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.
  12. zborgerd

    GCC for MSP430 officially out of beta

    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 hammer on it a bit more when I get some time. There are a few issues with shared library links in some of the included binaries in /bin. For example, I've found: zborgerd@katana:~$ msp430-elf-gdb msp430-elf-gdb: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory zborgerd@katana:~$ ldd `which msp430-elf-gdb` | grep libX11 libX11.so.6 => not found I could manually force the link or redirect it, but I guess the libX11 requirement is simply for an optional GUI component of the GDB agent. Ditto for wish and some broken tcl components. I think that someone is going to need to be more careful in packing up these binary builds for end-users, but that's the downside to binaries and shared libraries on lots of different platforms. Beginners should probably stick to MSPGCC for now unless there is an immediate need to upgrade. For me, I'd like to work on the MSP-EXP430FR5969 launchpad without repeatedly having to BSL a bricked micro, so this is probably the most logical progression without patching MSPGCC LTS for new FRAM chips.
  13. zborgerd

    GCC for MSP430 officially out of beta

    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.
  14. 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 using a patched version of mspgcc, such as the version included in Energia. I've had to debrick my board with a BSL flash no less than 5 or 6 times so far, but I'm using the old MSPGCC LTS 20120406 because I still trust it more than RedHat / TI's GCC compiler.
  15. 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
×