mspdebug

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

mspdebug

Ian Chapman
Hi,
     I have a silly problem.  Mspdebug runs and reports :--
#mspdebug rf2500
MSPDebug version 0.19 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer <[hidden email]>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

usbutil: unable to find a device matching 0451:f432

     but it's okay if I do a su "super user" first.  I'm using
MintDerbian and I've tried adding myself to the admin groups but need a
pointer from a Linux expert.  I guess I can work as a superuser for
now.  Thanks in advance Ian.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: mspdebug

David W. Schultz
On 09/26/2013 08:12 AM, Ian Chapman wrote:
>
> usbutil: unable to find a device matching 0451:f432
>

The first step is to see if anything is there using lsusb. You should
see something like:

Bus 003 Device 002: ID 0451:f432 Texas Instruments, Inc. eZ430
Development Tool

If it is working.

Recently the Launchpad has been giving me fits which is why I pulled out
a JTAG unit. At times the Launchpad works but other times it fails to
enumerate. (use dmesg to view information spit out as it tries to connect)


--
David W. Schultz
http://home.earthlink.net/~david.schultz
Returned for Regrooving



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: mspdebug

Daniel Beer-3
In reply to this post by Ian Chapman
On Thu, Sep 26, 2013 at 09:12:50AM -0400, Ian Chapman wrote:

>      I have a silly problem.  Mspdebug runs and reports :--
> #mspdebug rf2500
> MSPDebug version 0.19 - debugging tool for MSP430 MCUs
> Copyright (C) 2009-2012 Daniel Beer <[hidden email]>
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> usbutil: unable to find a device matching 0451:f432
>
>      but it's okay if I do a su "super user" first.  I'm using
> MintDerbian and I've tried adding myself to the admin groups but need a
> pointer from a Linux expert.  I guess I can work as a superuser for
> now.  Thanks in advance Ian.

Hi Ian,

Not sure why the error message is that one in particular if the problem
is due to permissions (maybe an old bug in 0.19?). Anyway, to allow
normal user access to USB devices, you need to add udev rules. If you
find out where your rules are stored (mine are in /lib/udev/rules.d),
add a file called 99-mspdebug.rules, containing these lines:

ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", MODE="0660", GROUP="plugdev"
ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="plugdev"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0200", MODE="0660", GROUP="plugdev"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0010", MODE="0660", GROUP="plugdev"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0013", MODE="0660", GROUP="plugdev"

Then:

  * run: udevadm control --reload-rules
  * add yourself to the plugdev group
  * log out and in again
  * replug your device

Hopefully you should then be able to use the device as a normal user.
You might need to pick a different group if you don't have a "plugdev"
group -- it doesn't really matter.

Cheers,
Daniel

--
Daniel Beer <[hidden email]>    www.dlbeer.co.nz
IRC: inittab (Freenode)    PGP key: 2048D/160A553B

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: mspdebug

Ian Chapman
On 09/26/2013 04:18 PM, Daniel Beer wrote:

> On Thu, Sep 26, 2013 at 09:12:50AM -0400, Ian Chapman wrote:
>>       I have a silly problem.  Mspdebug runs and reports :--
>> #mspdebug rf2500
>> MSPDebug version 0.19 - debugging tool for MSP430 MCUs
>> Copyright (C) 2009-2012 Daniel Beer <[hidden email]>
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>
>> usbutil: unable to find a device matching 0451:f432
>>
>>       but it's okay if I do a su "super user" first.  I'm using
>> MintDerbian and I've tried adding myself to the admin groups but need a
>> pointer from a Linux expert.  I guess I can work as a superuser for
>> now.  Thanks in advance Ian.
> Hi Ian,
>
> Not sure why the error message is that one in particular if the problem
> is due to permissions (maybe an old bug in 0.19?). Anyway, to allow
> normal user access to USB devices, you need to add udev rules. If you
> find out where your rules are stored (mine are in /lib/udev/rules.d),
> add a file called 99-mspdebug.rules, containing these lines:
>
> ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", MODE="0660", GROUP="plugdev"
> ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="plugdev"
> ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0200", MODE="0660", GROUP="plugdev"
> ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0010", MODE="0660", GROUP="plugdev"
> ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0013", MODE="0660", GROUP="plugdev"
>
> Then:
>
>    * run: udevadm control --reload-rules
>    * add yourself to the plugdev group
>    * log out and in again
>    * replug your device
>
> Hopefully you should then be able to use the device as a normal user.
> You might need to pick a different group if you don't have a "plugdev"
> group -- it doesn't really matter.
>
> Cheers,
> Daniel
>
> Thanks Daniel, that's fixed it and it goes where you said.  I had to be
> su to generate 99-mspdebug.rules.
>
> Just for those trying to figure things out as it may be a bit terse
> these are the details.
>
> id stan
> uid=1001(stan) gid=1001(stan) groups=1001(stan),46(plugdev)
>
> id admin
> uid=1000(admin) gid=1000(admin)
> groups=1000(admin),4(adm),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),113(lpadmin),120(sambashare)
>
> and to add 46(plugdev) to stan use this "usermod -G plugdev stan" as a
> superuser and I had to reboot.  Thanks Ian.
PS. I have to unplug the TI device to be able to boot.  Also worthy of a
mention, my flash drive mounted before I did any of what Daniel
suggested.  Ian.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users