Jump to content


  • Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    WethaGuy got a reaction from abecedarian in Well... crap.   
    I'm in the process of moving and have one packed away in a moving box somewhere around here.  I'm not going to have a chance to mess with it for a few months, at least.  You're welcome to it (if I can find the box it's in, hmmm..).
  2. Like
    WethaGuy reacted to Emeryth in USB mass storage bootloader   
    I wanted to share a bootloader I wrote for the Stellaris Launchpad (and other boards/chips if you change it up a bit).
    The bootloader acts as a mass storage device, and allows for software update by simply moving a file to the device. No software or drivers needed!
    It's inspired by the bootloader found on some NXP LPC microcontrollers.
    The project was surprisingly easy thanks to the awesome Stellaris USB Library.
    Grab the source here: https://github.com/Emeryth/Stellaris-mass-storage-bootloader
    Pleas report any issues you encounter.
  3. Like
    WethaGuy reacted to olivluca in Energia slow to start with TI Launchpad connected, Ubuntu 12.04   
    Download the zip file from the page linked by Rickta59
    Unzip it somewhere
    cd where_you_unzipped_it
    cd linux-3.0/cdcacm-0.1/
    make clean
    This should produce a cdcacm.ko file
    sudo modprobe -r cdc_acm (just in case it's been already loaded)
    sudo insmod ./cdcacm.ko
  4. Like
    WethaGuy reacted to Rickta59 in clean install Linux Mint - MSP430 works, StellarPad "no ICDI" error   
    > First thing to do is make sure the device is being recognized by the linux kernel. Open a terminal window and try the lsusb command:
    # lsusb -d 1cbe:00fd Bus 003 Device 022: ID 1cbe:00fd Luminary Micro Inc.  the lsusb command is used to list usb devices. If you see an entry for the VID:PID (1cbe:00fd) then your linux kernel has enumerated your device.  So that is a good first step
    > Next, did you setup a udev entry? This changes the permissions on the usb device so non-root users can read and write it. I named my entry /etc/udev/rules.d/61-stellapad.rules:
    # This file allows non-root access to TI stellaris launchpad # See udev(7) for syntax. # SUBSYSTEM=="usb",ATTRS{idVendor}=="1cbe",ATTRS{idProduct}=="00fd",MODE="0666" # When you add the entry you need to restart udev or just unplug your launchpad, wait, then replug. While you are doing this you can do a 'tail -f /var/log/syslog' ( or multiple dmesg commands ) to see the kernel messages. You should look for any suspicious errors.
    > Next step is to see if you can use lm4flash. The lm4flash program is in your Energia install directory:
    $ ls -l energia-0101E0009/hardware/tools/lm4f/bin/lm4flash $ energia-0101E0009/hardware/tools/lm4f/bin/lm4flash /tmp/build4630516746846355870.tmp/Blink_blue.cpp.bin !Success I turned on verbose in the Energia IDE and using a simple blink step I ran the "Verify" aka compile button. It puts the .bin file in a /tmp/buildxxxxx/ directory. You will have to substitute the name used on your compile. If that works you can then try the Energia IDE. It should be working at this point.
    > Next if steps above didn't work it could be that the libusb I used to compile lm4flash isn't working with your linux. Try downloading compiling lm4flash from source. https://github.com/RickKimball/lm4tools Follow the steps listed there to get a working lm4flash and try it with the /tmp/buildxxx/*.bin file you created. Note: my version is based on an earlier version of lm4flash from https://github.com/utzig/lm4tools Mine is bare bones. You might try that later version if you have problems with mine.
    If none of the steps there work, then someone else has suggested that you try a different usb port. If that doesn't work, you'll have to explain more about the errors you are seeing.
    In any case, let us know how it works out for you. This is our first release of the stellarpad Energia, there are bound to be glitches.
  • Create New...