My quickie guide for setting up mspgcc for ez430-cc2500

Comments

6 responses to “My quickie guide for setting up mspgcc for ez430-cc2500”

1. 

   Jason

   9/20/2009

   Your writeup seems great (I stumbled upon it while realizing I needed make as well. After installing everything though, neither cygwin, nor the standard DOS prompt understands me saying “make”, am I missing another step?? THanks.

2. 

   jeff

   9/25/2009

   THANK YOU for the msp430-jtag syntax. I appreciate what the mspgcc team is doing but I wish their msp430-downloader utility would support spy-bi-wire.

   I’ll be looking into the GDB proxy now. Unfortunately, none of the three “msp430” options it provides can connect to my USB key, ie it’s lacking the –lpt=USBFET option.

   Or have you already found a solution to this?

   JASON: It’s because MinGW installs mingw32-make.exe instead of make. You could just copy the file and rename it to make.exe while keeping it in the same folder (normally under linux I’d say “ln” it)

3. 

   jeff

   9/25/2009

   Sorry for the double post: found it!

   first of all create the file gdb.ini in the bin folder and add
   set remoteaddresssize 64
   set remotetimeout 999999
   target remote localhost:2000

   then run the following command:

   msp430-gdbproxy msp430 –spy-bi-wire USBFET

   And you can now use GDB at port 2000.

4. 

   Jason

   10/25/2009

   Sorry, I didn’t see the response until now, installing MSYS seemed to fix the issue for me, so I am golden. What are you using to debug the code? That is my next step!
   Thanks for the great site!

5. 

   Tim

   12/10/2009

   @Jason et al: under Windoze, if you install software such as ‘make’ after opening a CMD prompt, only the stuff available before you opened it will show up. Under Win32, the installers for most programs such as make intended to be used from anywhere will add themselves to your PATH= system variable, so that Windows can find them without explicitly specifying their location every time. If this does not happen, try closing and opening a new command prompt (Start -> run “cmd”) to see if it exists now… if not, you will need to explicitly add them to Windows’ path.

   if ‘make’ (or ‘mingw32-make’, etc. still is not found even though they have been installed, you need to add the path to them into the Windows PATH= system environment variable. To do this, open Start -> Settings -> Control Panel -> System -> Advanced tab, click on “environment variables”, and in the “system variables” window, find the ‘Path’ variable. It contains a long list of paths where important programs are located, such as e.g. C:\Windows\System32 (etc.) separated by semicolons;… to enable mingw32-make to work from any location, add its path to this list. Eg. change the ‘Path’ variable so that it reads ‘C:\Windows\system32;C:\important\crap\;…(more crap)…;C:\mingw\ (or wherever it is located). After you have added its path, close and re-open any command prompts and it should work. Same goes for any other important programs or script interpreters, e.g. perl, python, etc….

6. 

   Bruce

   5/21/2010

   THANK YOU for the msp430-jtag syntax. I appreciate what the mspgcc team is doing but I wish their msp430-downloader utility would support spy-bi-wire.

   I’ll be looking into the GDB proxy now. Unfortunately, none of the three “msp430” options it provides can connect to my USB key, ie it’s lacking the –lpt=USBFET option.

   Or have you already found a solution to this?

   JASON: It’s because MinGW installs mingw32-make.exe instead of make. You could just copy the file and rename it to make.exe while keeping it in the same folder (normally under linux I’d say “ln” it)