dlucas 0 Posted April 4, 2012 Share Posted April 4, 2012 Are you using the mspdebug version installed on your system or the packaged version I provide for msp430eclipse ? I have been using the version packaged by you. I purposely removed all reference to the system versions. I will double check that this is in fact the case ... Quote Link to post Share on other sites
dlucas 0 Posted April 10, 2012 Share Posted April 10, 2012 Are you using the mspdebug version installed on your system or the packaged version I provide for msp430eclipse ? I have been using the version packaged by you. I purposely removed all reference to the system versions. I will double check that this is in fact the case ... Yes in fact I am using the mspdebug binaries supplied by you installer. I notice that there is a mspdebug-wrapper script in the directory. Does this need to setup as the executable version somewhere? If so where? Thanks again, David Quote Link to post Share on other sites
xpg 127 Posted April 10, 2012 Author Share Posted April 10, 2012 Yes in fact I am using the mspdebug binaries supplied by you installer. I notice that there is a mspdebug-wrapper script in the directory. Does this need to setup as the executable version somewhere? If so where? The wrapper script is only there to ensure that the output from mspdebug is not buffered. However, as pointed out by gordon, this is not needed for newer mspdebug releases. The packaged version of the tools automatically uses the wrapper script (it's specified by the tools.info-file). An interesting thing is that I ran into this issue yesterday. I will see if I can reproduce it tonight. Cheers, Paul Quote Link to post Share on other sites
dlucas 0 Posted April 18, 2012 Share Posted April 18, 2012 An interesting thing is that I ran into this issue yesterday. I will see if I can reproduce it tonight. Any luck reproducing the problem? Quote Link to post Share on other sites
xpg 127 Posted April 18, 2012 Author Share Posted April 18, 2012 Any luck reproducing the problem? Unfortunately not yet. I have a suspicion which I cannot try out before tonight: It might be caused by whitespaces in the path to either the source or binary files. I'll check tonight and let you know how it goes. Cheers, Paul Quote Link to post Share on other sites
robomotic 1 Posted May 4, 2012 Share Posted May 4, 2012 Hello fantastic job! I am trying to install your plugin on my Eclipse installation however I get this error: Cannot complete the install because some dependencies are not satisfiable dk.xpg.msp430eclipse.toolchain.linux32.feature.feature.group [1.0.2.1] cannot be installed in this environment because its filter is not applicable. Could it be related to the fact that I have installed from ubuntu oneiric the msp430 toolchain? My Eclipse version is Version: 3.7.0 Build id: I20110613-1736 Quote Link to post Share on other sites
xpg 127 Posted May 4, 2012 Author Share Posted May 4, 2012 Hello fantastic job!I am trying to install your plugin on my Eclipse installation however I get this error: Cannot complete the install because some dependencies are not satisfiable dk.xpg.msp430eclipse.toolchain.linux32.feature.feature.group [1.0.2.1] cannot be installed in this environment because its filter is not applicable. Could it be related to the fact that I have installed from ubuntu oneiric the msp430 toolchain? My Eclipse version is Version: 3.7.0 Build id: I20110613-1736 Hmm.. Strange. What system are you running a 32-bit Linux? and which distribution? /Paul Quote Link to post Share on other sites
robomotic 1 Posted May 7, 2012 Share Posted May 7, 2012 Hello I have managed to solve the issue by installing a fresh Indigo from the web and the plugin was installed correctly. It compiled the blinky and now trying to debug on a launchpad. Quote Link to post Share on other sites
xpg 127 Posted May 7, 2012 Author Share Posted May 7, 2012 Hello I have managed to solve the issue by installing a fresh Indigo from the web and the plugin was installed correctly.It compiled the blinky and now trying to debug on a launchpad. Thank you very much for that update. I'm happy to hear that things are working for you. Cheers, Paul Quote Link to post Share on other sites
robomotic 1 Posted May 7, 2012 Share Posted May 7, 2012 Oky in the Debug Configuration I don't see the mspdebug tool from the list. I made a screenshot, basically it finds the variable you describe but it doesn't find the mspdebug. I have tried a workaround by launching mspdebug rf2500 gdb on shell console but I then get another error: Error while launching command: gdbmsp430-gdb --version this happens regardless if port 2000 is listening or not. Hmmmm anyway to find the issue? PS The udev rule is fine as I am able to download the blinky demo on the board although with some problem: fet: FET returned error code 4 (Could not find device (or device not supported))fet: command C_IDENT1 failed fet: identify failed MSPDebug version 0.16 - debugging tool for MSP430 MCUs Trying to open interface 1 on 007 Initializing FET... FET protocol version is 30001000 Configured for Spy-Bi-Wire Set Vcc: 3000 mV Trying again... Initializing FET... FET protocol version is 30001000 Configured for Spy-Bi-Wire Sending reset... Set Vcc: 3000 mV Device ID: 0xf201 Device: MSP430G2231 Code memory starts at 0xf800 Number of breakpoints: 1 Erasing... Programming... Writing 142 bytes to f800... Writing 32 bytes to ffe0... Quote Link to post Share on other sites
xpg 127 Posted May 7, 2012 Author Share Posted May 7, 2012 Oky in the Debug Configuration I don't see the mspdebug tool from the list.I made a screenshot, basically it finds the variable you describe but it doesn't find the mspdebug. Hmm... things have changed slightly. Instead of using the hardware debug group, use the "MSP430 Debug" group. See (at 4:50). PS The udev rule is fine as I am able to download the blinky demo on the board although with some problem: fet: FET returned error code 4 (Could not find device (or device not supported))fet: command C_IDENT1 failed fet: identify failed MSPDebug version 0.16 - debugging tool for MSP430 MCUs Trying to open interface 1 on 007 Initializing FET... FET protocol version is 30001000 Configured for Spy-Bi-Wire Set Vcc: 3000 mV Trying again... Initializing FET... FET protocol version is 30001000 Configured for Spy-Bi-Wire Sending reset... Set Vcc: 3000 mV Device ID: 0xf201 Device: MSP430G2231 Code memory starts at 0xf800 Number of breakpoints: 1 Erasing... Programming... Writing 142 bytes to f800... Writing 32 bytes to ffe0... That is perfectly alright. I know it looks strange, but it is ok. Quote Link to post Share on other sites
robomotic 1 Posted May 7, 2012 Share Posted May 7, 2012 O yeah that works now but I have to use the trick to launch the mspdebug on the console. Note that I care but just to let you know of a potential bug in the interface. I am quite pleased is working now and I hope you can improve it more. :clap: Quote Link to post Share on other sites
xpg 127 Posted May 8, 2012 Author Share Posted May 8, 2012 O yeah that works now but I have to use the trick to launch the mspdebug on the console. Strange. Do you get any error messages? Are you using the packaged toolchain or the one in the system path? Note that I care but just to let you know of a potential bug in the interface. I am quite pleased is working now and I hope you can improve it more. :clap: Thank you for letting me know. I appreciate all feedback. Thanks, Paul Quote Link to post Share on other sites
robomotic 1 Posted May 8, 2012 Share Posted May 8, 2012 Hello I am using the pre-compiled ones and if I follow the video I get this: Failed to start debug session gdb: can't bind to port 2000: Address already in use rf2500: warning: can't detach kernel driver: No data available fet: FET returned NAK gdb: can't bind to port 2000: Address already in use gdb: can't bind to port 2000: Address already in use gdb: can't bind to port 2000: Address already in use rf2500: warning: can't detach kernel driver: No data available fet: FET returned NAK gdb: can't bind to port 2000: Address already in use Quote Link to post Share on other sites
xpg 127 Posted May 8, 2012 Author Share Posted May 8, 2012 Hello I am using the pre-compiled ones and if I follow the video I get this: Failed to start debug session gdb: can't bind to port 2000: Address already in use rf2500: warning: can't detach kernel driver: No data available fet: FET returned NAK gdb: can't bind to port 2000: Address already in use gdb: can't bind to port 2000: Address already in use gdb: can't bind to port 2000: Address already in use rf2500: warning: can't detach kernel driver: No data available fet: FET returned NAK gdb: can't bind to port 2000: Address already in use May I guess that this is the second attempt? The first attempt did not work either, but gave different error messages? I currently have an outstanding issue, which I fail to reproduce where mspdebug is started but eclipse fails to connect to it, leaving mspdebug hanging occupying the port. Could you try to do a "killall mspdebug" from a console and try again to see if debugging works? Thanks, Paul Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.