Jump to content

bi0tech

Members
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    2

Reputation Activity

  1. Like
    bi0tech reacted to username in DAC GUI V2   
    Hey all,
     
    Round 2: This extends the peripherals of the MSP430 to a UART based ascii AT command set. For example, send "AT+GET_ADC" over the USB->Serial bridge to get all the ADC values returned. Since I released my first GUI there have been a couple others like it. You will find that this version's strength is that the underlying C driver set is my personal driver set which is quite powerful XD . I then wrote a C# GUI as a wrapper around this command set.
     
    Features Implemented: Digital IO, Analog I, PWM, SPI

     
    PWM Example:

     
    Steps to use:
    1. Download code & .exe file here: https://github.com/NateZimmer/ICBM
    2. Import C code into CCSV5.1 (haven't tested with other versions) and flash to launchpad.
    3. Ensure UART jumpers on the MSP430 Launchpad are set to Hardware based UART on a msp430g2553 launchpad Rev 1.5
    4. Run GUI and connect to launchpad.
    5. Enjoy!
     
    Skip to 10:35 for setup instructions:
     
     


     
    Todo:
    Implement DCO Calibration for better CLK accuracy
    Implement I2C
    Implement Graphing/Logging
    Implement more flexible spi chip select features
     
    Please let me know if this does not work for you
  2. Like
    bi0tech got a reaction from roadrunner84 in advice on mounting a launchpad?   
    This seems relevant so Ill throw in a few pics of my msp430 franken'pad.
     
    I wanted a zif and drop in breadboard capability, so I picked up a few knockoff texttool 28 pin zifs (largest size I saw in narrow format, the extra pins don't pose an issue and allow use with a few other chips).  Desoldering the carrier socket was moderately painful, but doable with just some braid/fine tip.  (full disclosure I'm not the worlds worst at soldering, now 2nd worst is still to be determined).  Added in stacker headers in place of the carrier to give me drop in breadboarding and to clear the board surface level / leave room for the crystal.  A little hot glue to keep things in place (and hold a flywire from where I lifted a pad) and a 5 minute router job with some scrap wood as a puck stand.
     

  3. Like
    bi0tech got a reaction from tripwire in advice on mounting a launchpad?   
    This seems relevant so Ill throw in a few pics of my msp430 franken'pad.
     
    I wanted a zif and drop in breadboard capability, so I picked up a few knockoff texttool 28 pin zifs (largest size I saw in narrow format, the extra pins don't pose an issue and allow use with a few other chips).  Desoldering the carrier socket was moderately painful, but doable with just some braid/fine tip.  (full disclosure I'm not the worlds worst at soldering, now 2nd worst is still to be determined).  Added in stacker headers in place of the carrier to give me drop in breadboarding and to clear the board surface level / leave room for the crystal.  A little hot glue to keep things in place (and hold a flywire from where I lifted a pad) and a 5 minute router job with some scrap wood as a puck stand.
     

  4. Like
    bi0tech got a reaction from enl in advice on mounting a launchpad?   
    This seems relevant so Ill throw in a few pics of my msp430 franken'pad.
     
    I wanted a zif and drop in breadboard capability, so I picked up a few knockoff texttool 28 pin zifs (largest size I saw in narrow format, the extra pins don't pose an issue and allow use with a few other chips).  Desoldering the carrier socket was moderately painful, but doable with just some braid/fine tip.  (full disclosure I'm not the worlds worst at soldering, now 2nd worst is still to be determined).  Added in stacker headers in place of the carrier to give me drop in breadboarding and to clear the board surface level / leave room for the crystal.  A little hot glue to keep things in place (and hold a flywire from where I lifted a pad) and a 5 minute router job with some scrap wood as a puck stand.
     

  5. Like
    bi0tech got a reaction from energia in Programming MSP-EXP430G2 Launchpad using Energia on Linux OS   
    I figured I'd have to deal with this sooner or later myself so I hooked up my launchpad and tested a kernel module patch I'd seen around a few places.  In very brief testing it does seem that it eliminates the extended hang when serial data is passed to ttyACM* before there is a reciever on the host.
     
    The patch to cdc-acm I used was for arch and has been since abandoned but it's easy enough to use/modify:

    Grab the tarball here: https://aur.archlinux.org/packages.php?ID=63769 The only file you need from it is the cdc-acm.patch, extract it somewhere like /usr/src/cdcacm-msp430 Grab the source for your kernel version.  (either from vendor site or kernel.org) Pull the cdc-acm.c & cdc-acm.h files from the kernel source into /usr/src/cdcacm-msp430 sudo apt-get install kernel-headers build-essential (or similar for non-deb distros) cd /usr/src/cdcacm-msp430/ Rename the cdc-acm.c to cdc-acm.c.orig Either use the patch file (/usr/src/cdcacm-msp430/patch < cdc-acm.patch) or manually edit the changes from the .patch into cdc-acm.c.orig Save the result file as cdcacm.c Save the below text into /usr/src/cdcacm-msp430/Makefile make sudo cp /usr/src/cdcacm-msp430/cdcacm.ko /lib/modules/`uname -r`/kernel/drivers/usb/class/ echo "blacklist cdc-acm" > blacklist-MSP430.conf sudo cp blacklist-MSP430.conf /etc/modprobe.d/ sudo depmod -a reboot (or manually unload the old "cdc-acm" and insmod the new "cdcacm") generic kernel module Makefile:
    obj-m := cdcacm.o KVERSION := $(shell uname -r) all: $(MAKE) --debug=v -C /lib/modules/$(KVERSION)/build M=$(PWD) modules clean: $(MAKE) --debug=v -C /lib/modules/$(KVERSION)/build M=$(PWD) clean  You can also go the dkms route but I had issues with it (and I'm not overly fond of it).  Using dkms you won't need to rebuild when switching kernels (in theory). 
     
    To revert back to cdc-acm:

    sudo rm /etc/modprobe.d/blacklist-MSP430.conf sudo rm /lib/modules/`uname -r`/kernel/drivers/usb/class/cdcacm.ko sudo depmod -a reboot
  6. Like
    bi0tech got a reaction from spirilis in Energia + Linux ?   
    For Mint/*buntu at least you can also skip the udev rules by simply adding the user to the ownership group of the device file, in this case 'dialout'.
     
    Show device permissions: (for the default ACM0):

    ls -al /dev/ttyA* crw-rw-r-- 1 root dialout 166, 0 May  1 10:19 /dev/ttyACM0
     
     
    Show current group members:

    cat /etc/group | grep <groupname>
    cat /etc/group | grep dialout dialout:x:20:<username>
     
     
    Add existing user to the group (as secondary group membership):

    sudo usermod -a -G <group> <user>
    sudo usermod -a -G dialout username *After changes to user permissions you will need to logout and back in to establish a session with the new permissions.  (or just reboot)
     
     
×
×
  • Create New...