Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-06 Thread M. Andree
Am 04.09.2010 01:40, schrieb Arturo Gurrola:
   Error while installing insight:
 
 config.status: creating po/Makefile
 make[1]: Leaving directory 
 '/cygdrive/c/mspgcc4-inst/build/insight-6.8-1-build'
 make: *** [all] Error 2
 
 And then it just exists.

And there's surely a lot of logging before - last time I checked because Tcl
tried things that the Cygwin headers no longer support.

 The command in the script is: sh do-gdb.sh /cygdrive/c/mspgcc4/ 
 6.8-1 http://ftp.uni-kl.de; build insight
 This is, of course, before installing gdb (as stated in the new buildgcc 
 perl script).
 
 Any solution?

Not to my knowledge.  Insight builds its own Tcl/Tk libraries, and that fails
since Cygwin reached 1.7.X earlier this year.  It has been discussed on and off
on the Insight mailing list, to no avail, and I personally lack the time and
interest to look into that.  Insight looks unmaintained.

You might succeed with Cygwin 1.7.7, and possibly by removing the
tcl/tk/itcl/itk libraries and installing those system-wide from the Insight
sources between unpacking and configuring Insight, and possibly also tweaking
configure options a bit. No guarantees though that that will work.

Good luck
MA



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-04 Thread Mark J. Blair

On Sep 3, 2010, at 11:59 AM, Peter Bigot wrote:
 We could also use a downstream packager for OSX, so people won't have to
 fight with the build process.  (Ubuntu and Windows, too; I think Rob
 Spanton's doing Fedora/RedHat, though we haven't coordinated the release
 processes yet: that should be done with the return to mspgcc.)

Maybe a good way to provide MSPGCC4 (and related stuff) to the Mac users would 
be to feed releases into  one of the existing open source porting and 
distribution channels for the Mac, such as Fink or MacPorts. I previously used 
Fink (which provides for both source and binary distribution), but I presently 
use MacPorts (which I think just distributes source) be because it seems to 
stay more up-to-date.

While a new Mac user of MSPGCC4 would still need to build a huge pile of 
software if it was distributed via MacPorts, installation would be reduced to 
installing the base MacPorts installer package and then typing sudo port 
install mspgcc4 (or something like that). The difficult task of getting the 
all of the necessary tools and pre-requisites in place prior to building 
MSPGCC4 would then be mostly automated, and it would fall upon the downstream 
packager person to submit new releases into MacPorts and do whatever patching, 
hacking, pre-requisite definition, etc. that's necessary to make things 
painless for the end users.

In case you're not already familiar with MacPorts, you can take a quick peek 
here to get an idea of what it's about:

http://www.macports.org/



The Mac is just different enough from the mainstream open source build 
platforms (i.e., various Linuxes) that installing stuff through MacPorts is 
often much easier than trying to port Linux-centric source distributions. Even 
when I choose to build something from the original source distribution instead 
of an available MacPort package (i.e., to get bleeding-edge code releases that 
haven't been ported yet), I try to get as much of my build environment and 
pre-requisite libraries as possible through MacPorts.

I might be willing to take on the task of feeding MSPGCC4 stuff into MacPorts 
at some point, but I'm still wallowing in build issues and learning-curve stuff 
too much to commit to that just yet.

-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.







Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-03 Thread Mark J. Blair

On Sep 2, 2010, at 12:16 PM, Baruch Siach wrote:
 A fully open-source implementation exists, it's called mspdebug  
 (http://mspdebug.sourceforge.net/). And the protocol is not a USB one, it's a 
 serial protocol over a USB-to-serial chip (the TI3410). So, all you need is a 
 driver for the TI3410 for your OS, and you're done.

Thank you for the hint! With only minor pain, I got mspdebug to build on my 
Mac, found and installed the serial port driver from TI and configured it to 
recognize my eZ430 dongle and MSP430-UIF device, and successfully programmed a 
simple LED-blinker program into the MSP430F2012 from my original eZ430 kit. 
Hooray!

With my eZ430-RF2500, I found it to be necessary to use the --fet-force-id 
option to get mspdebug to correctly identify the chip type and program it 
properly. Otherwise, it seems to work ok.

I am very pleased that I now have a no-code-size-limitation, open-source 
toolchain for the MSP430, and that I can build for and program the devices on 
my Mac without needing to bring up another OS in a virtual machine. It took 
some minor pain to get everything up and running, but I think it was well worth 
the effort.

Woohoo!

BTW, I also tried the FET-Pro430 Lite program, and it worked just fine on my 
virtual WinXP machine.

-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.







Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-03 Thread M. Andree
Am 02.09.2010 20:38, schrieb Mark J. Blair:
 
 On Sep 2, 2010, at 10:52 AM, Arturo Gurrola wrote:
 try184.c:1:20: error: curses.h: No such file or directory and then 
 Note that you must have libcurses developer headers installed. Abort..
 
 
 I'm also installing MSPGCC4 under Cygwin right now, and I ran into the same 
 problem. I have libncurses-devel installed, which provides 
 ncurses/curses.h, but MSPGCC4's do-gdb.sh script looks for curses.h and 
 doesn't find it. Since the compilation runs so terribly slowly for me (I'm 
 running WinXP in a virtual machine on my Mac, and the compilation is easily 
 an order of magnitude slower than it was when doing it natively under OSX), 
 and buildgcc.pl does a brute-force compilation which will rebuild gcc before 
 it even gets around to choking on gdb... I decided to try skipping do-gdb.sh 
 and instead compile gdb manually.

Sorry for that, I've done that quick hack as an assistance to newbies, but
evidently it backfires on recent Cygwin and some Solaris versions.

I have now figured that finding curses.h reliably and portably is a major
undertaking (way more time that I can spend), and will anyways not necessarily
match what ./configure digs out later, so let's just remove the check.

As a quick fix, remove the exit 1 line related to the curses.h complain from
do-gdb.sh before running buildgcc.pl.

I'm submitting a series of fixes to Peter, including a fix for this, for review.

Best regards
MA



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-03 Thread Mark J. Blair

On Sep 3, 2010, at 7:33 AM, M. Andree wrote:
 Sorry for that, I've done that quick hack as an assistance to newbies, but
 evidently it backfires on recent Cygwin and some Solaris versions.
 
 I have now figured that finding curses.h reliably and portably is a major
 undertaking (way more time that I can spend), and will anyways not necessarily
 match what ./configure digs out later, so let's just remove the check.

Don't feel too bad... making any complex package build portably can be very 
difficult!

I'm up and running with MSPGCC4 and mspdebug under OSX now, and I'm really 
happy that this fully open and complete toolchain exists. I hope that I'll be 
able to contribute in some small way towards its growth and improvement, 
because I believe that it's beneficial for development tools to be free in 
order to enable and stimulate creation of new and better things.

-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.







Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-03 Thread Peter Bigot
MA: Thanks.  The patches look good, and I've merged them to the next
branch of the git repository.

MB: Help is certainly welcome.  Wiki pages with updated instructions,
especially how to build (especially on windows) would address the biggest
problems; perhaps, having recently succeeded, you could document what you
did?

As we're moving back to putting everything under mspgcc, and we have to keep
mspgcc4 somewhat stable due to external references to its content by the
WASP project, I'd suggest that be done on the existing mspgcc wiki at:
https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=MSPGCC_Wiki

If you need somebody to give you write access, contact me directly with your
sourceforge userid.  Just mark the stuff that's currently only relevant to
mspgcc4; I don't think we're going to change the existing mspgcc
infrastructure, just supersede it.  I'm hoping for a new release under the
mspgcc project within a couple weeks, with my updates that eliminate all the
specialized hard-coded chip-specific addresses and assumptions.
Unfortunately, real work has started to interfere again, so it's already
later than I'd intended.

We could also use a downstream packager for OSX, so people won't have to
fight with the build process.  (Ubuntu and Windows, too; I think Rob
Spanton's doing Fedora/RedHat, though we haven't coordinated the release
processes yet: that should be done with the return to mspgcc.)

Peter

On Fri, Sep 3, 2010 at 10:45 AM, Mark J. Blair n...@nf6x.net wrote:


 On Sep 3, 2010, at 7:33 AM, M. Andree wrote:
  Sorry for that, I've done that quick hack as an assistance to newbies,
 but
  evidently it backfires on recent Cygwin and some Solaris versions.
 
  I have now figured that finding curses.h reliably and portably is a major
  undertaking (way more time that I can spend), and will anyways not
 necessarily
  match what ./configure digs out later, so let's just remove the check.

 Don't feel too bad... making any complex package build portably can be very
 difficult!

 I'm up and running with MSPGCC4 and mspdebug under OSX now, and I'm really
 happy that this fully open and complete toolchain exists. I hope that I'll
 be able to contribute in some small way towards its growth and improvement,
 because I believe that it's beneficial for development tools to be free in
 order to enable and stimulate creation of new and better things.

 --
 Mark J. Blair, NF6X n...@nf6x.net
 Web page: http://www.nf6x.net/
 GnuPG public key available from my web page.






 --
 This SF.net Dev2Dev email is sponsored by:

 Show off your parallel programming skills.
 Enter the Intel(R) Threading Challenge 2010.
 http://p.sf.net/sfu/intel-thread-sfd
 ___
 Mspgcc-users mailing list
 Mspgcc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-03 Thread Mark J. Blair

On Sep 3, 2010, at 11:59 AM, Peter Bigot wrote:
 MB: Help is certainly welcome.  Wiki pages with updated instructions,
 especially how to build (especially on windows) would address the biggest
 problems; perhaps, having recently succeeded, you could document what you
 did?

I'd rather document what I did on the Mac side... my whole goal is to eliminate 
my need to ever touch Windows, and I was only building there because I didn't 
know yet that I could flash and debug chips under OS X with mspdebug!

 We could also use a downstream packager for OSX, so people won't have to
 fight with the build process.  (Ubuntu and Windows, too; I think Rob
 Spanton's doing Fedora/RedHat, though we haven't coordinated the release
 processes yet: that should be done with the return to mspgcc.)

I'm not sure if I know how to do that (particularly, capturing any needed 
prerequisites from MacPorts or Fink), but I might look into that if somebody 
more experienced in that area doesn't grab the task first. It took a bit of 
pain to build the compiler toolchain, build mspdebug, find-patch-install needed 
kernel extensions and so forth, and it'd be really nice if future Mac users 
could just drag a folder out of a .dmg or double-click a .pkg!

I'm still not quite at the finish line, since Insight wouldn't build for me and 
I decided to put off debugging that until I got the other stuff basically 
working.



-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.







[Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Arturo Gurrola

 Hello everyone,

I'm installing MSPGCC4 through Cygwin on windows (command: perl 
buildgcc.pl).


BinUtils, GCC and Libc have installed correctly so far.

But then when it comes to GDB (command in the script: bash do-gdb.sh 
/cygdrive/c/mspgcc4/ 7.1 http://ftp.uni-kl.de; build gdb), and 
after Unpacking gdb... and a bunch of patching file ..., I get 
try184.c:1:20: error: curses.h: No such file or directory and then 
Note that you must have libcurses developer headers installed. Abort..
Now, I do have the package Libs (and a bunch of others) which contains 
some libncurses... files in my Cygwin installation. And I do have the 
file curses.h somewhere in my mspgcc4 directory.
Should I install a specific package for Cygwin? Or should I copy 
curses.h to a specific directory?


Thanks in advance.



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Peter Bigot
Not a cygwin user, so I'm reaching here, but there may be a package
libcurses-devel (or libncurses-devel) that you need in order to get the
headers.  This is generally the fix for this problem when it arises under
Linux.

Unless you're sure the curses.h you found matches the libncurses library, I
do not recommend copying it into the gdb source area.  You'll probably just
find that there's another header that's missing too.

Peter

On Thu, Sep 2, 2010 at 12:52 PM, Arturo Gurrola
mgurr...@gdl.cinvestav.mxwrote:

  Hello everyone,

 I'm installing MSPGCC4 through Cygwin on windows (command: perl
 buildgcc.pl).

 BinUtils, GCC and Libc have installed correctly so far.

 But then when it comes to GDB (command in the script: bash do-gdb.sh
 /cygdrive/c/mspgcc4/ 7.1 http://ftp.uni-kl.de; build gdb), and
 after Unpacking gdb... and a bunch of patching file ..., I get
 try184.c:1:20: error: curses.h: No such file or directory and then
 Note that you must have libcurses developer headers installed. Abort..
 Now, I do have the package Libs (and a bunch of others) which contains
 some libncurses... files in my Cygwin installation. And I do have the
 file curses.h somewhere in my mspgcc4 directory.
 Should I install a specific package for Cygwin? Or should I copy
 curses.h to a specific directory?

 Thanks in advance.


 --
 This SF.net Dev2Dev email is sponsored by:

 Show off your parallel programming skills.
 Enter the Intel(R) Threading Challenge 2010.
 http://p.sf.net/sfu/intel-thread-sfd
 ___
 Mspgcc-users mailing list
 Mspgcc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Mark J. Blair

On Sep 2, 2010, at 10:52 AM, Arturo Gurrola wrote:
 try184.c:1:20: error: curses.h: No such file or directory and then 
 Note that you must have libcurses developer headers installed. Abort..


I'm also installing MSPGCC4 under Cygwin right now, and I ran into the same 
problem. I have libncurses-devel installed, which provides ncurses/curses.h, 
but MSPGCC4's do-gdb.sh script looks for curses.h and doesn't find it. Since 
the compilation runs so terribly slowly for me (I'm running WinXP in a virtual 
machine on my Mac, and the compilation is easily an order of magnitude slower 
than it was when doing it natively under OSX), and buildgcc.pl does a 
brute-force compilation which will rebuild gcc before it even gets around to 
choking on gdb... I decided to try skipping do-gdb.sh and instead compile gdb 
manually.

What I've done so far is:

  cd build/gdb-7.1
  ./configure --prefix=/opt/msp430-gcc-4.4.4 --target=msp430 --disable-werror
  make

It failed to find libz and choked on the compilation, so I'm not there just yet.

I plan to use the compiler under OSX, but I'm still trying to build it under 
WinXP so that I can try to use gdb + gdbproxy to download code with my eZ430 
dongle or MSP-FET430UIF, which aren't supported under OSX yet.

I wouldn't mind using IAR or CCC to download code built by msp430-gcc, but it 
seems that they want the code in a .d43 format which I don't know how to create 
with msp430-gcc.

-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.







Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Peter Bigot
Go to http://www.elprotronic.com and download FET-Pro430.  The Lite (free)
version has done everything I needed.

Use msp430-objcopy to convert the elf output from mspgcc to Intel hex and
program with FET-Pro430.  You may need to name the file something.hex to get
FET-Pro430 to recognize it.

Best solution I found prior to mspdebug working under Linux.

Peter

On Thu, Sep 2, 2010 at 1:38 PM, Mark J. Blair n...@nf6x.net wrote:


 On Sep 2, 2010, at 10:52 AM, Arturo Gurrola wrote:
  try184.c:1:20: error: curses.h: No such file or directory and then
  Note that you must have libcurses developer headers installed. Abort..


 I'm also installing MSPGCC4 under Cygwin right now, and I ran into the same
 problem. I have libncurses-devel installed, which provides
 ncurses/curses.h, but MSPGCC4's do-gdb.sh script looks for curses.h and
 doesn't find it. Since the compilation runs so terribly slowly for me (I'm
 running WinXP in a virtual machine on my Mac, and the compilation is easily
 an order of magnitude slower than it was when doing it natively under OSX),
 and buildgcc.pl does a brute-force compilation which will rebuild gcc
 before it even gets around to choking on gdb... I decided to try skipping
 do-gdb.sh and instead compile gdb manually.

 What I've done so far is:

  cd build/gdb-7.1
  ./configure --prefix=/opt/msp430-gcc-4.4.4 --target=msp430
 --disable-werror
  make

 It failed to find libz and choked on the compilation, so I'm not there just
 yet.

 I plan to use the compiler under OSX, but I'm still trying to build it
 under WinXP so that I can try to use gdb + gdbproxy to download code with my
 eZ430 dongle or MSP-FET430UIF, which aren't supported under OSX yet.

 I wouldn't mind using IAR or CCC to download code built by msp430-gcc, but
 it seems that they want the code in a .d43 format which I don't know how to
 create with msp430-gcc.

 --
 Mark J. Blair, NF6X n...@nf6x.net
 Web page: http://www.nf6x.net/
 GnuPG public key available from my web page.






 --
 This SF.net Dev2Dev email is sponsored by:

 Show off your parallel programming skills.
 Enter the Intel(R) Threading Challenge 2010.
 http://p.sf.net/sfu/intel-thread-sfd
 ___
 Mspgcc-users mailing list
 Mspgcc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Peter Bigot
Don't have Mac OS X, but mspdebug allows me to use the FETUIF-430 under
Fedora 13 on Linux.  Infinitely nicer than an ssh terminal under Windows and
a shared disk drive.  See mspdebug.sourceforge.net.

http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Mac_OS_X#Installing_mspdebug_under_Mac_OS_X

On Thu, Sep 2, 2010 at 2:02 PM, Mark J. Blair n...@nf6x.net wrote:


 On Sep 2, 2010, at 11:57 AM, Peter Bigot wrote:
  Go to http://www.elprotronic.com and download FET-Pro430.  The Lite
 (free)
  version has done everything I needed.

 Thanks for the suggestion! I'll give that a try.

 I hope that someday I'll be able to use the TI USB programmers under Mac OS
 X, without needing to pop up WinXP on a virtual machine. Has anybody looked
 into reverse-engineering the USB protocols for those programmers so that a
 fully open-source implementation that supports them can be created?

 --
 Mark J. Blair, NF6X n...@nf6x.net
 Web page: http://www.nf6x.net/
 GnuPG public key available from my web page.






 --
 This SF.net Dev2Dev email is sponsored by:

 Show off your parallel programming skills.
 Enter the Intel(R) Threading Challenge 2010.
 http://p.sf.net/sfu/intel-thread-sfd
 ___
 Mspgcc-users mailing list
 Mspgcc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Baruch Siach
Hi Mark,

On Thu, Sep 02, 2010 at 12:02:48PM -0700, Mark J. Blair wrote:
 On Sep 2, 2010, at 11:57 AM, Peter Bigot wrote:
  Go to http://www.elprotronic.com and download FET-Pro430.  The Lite (free)
  version has done everything I needed.
 
 Thanks for the suggestion! I'll give that a try.
 
 I hope that someday I'll be able to use the TI USB programmers under Mac OS 
 X, without needing to pop up WinXP on a virtual machine. Has anybody looked 
 into reverse-engineering the USB protocols for those programmers so that a 
 fully open-source implementation that supports them can be created?

A fully open-source implementation exists, it's called mspdebug  
(http://mspdebug.sourceforge.net/). And the protocol is not a USB one, it's a 
serial protocol over a USB-to-serial chip (the TI3410). So, all you need is a 
driver for the TI3410 for your OS, and you're done.

baruch


-- 
 ~. .~   Tk Open Systems
=}ooO--U--Ooo{=
   - bar...@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -



Re: [Mspgcc-users] problem while installing GDB of MSPGCC4

2010-09-02 Thread Mark J. Blair
I'll look at mspdebug today. I was under the impression that the USB-based TI 
programmers (including the eZ430 dongles) were only supported under Windows 
(using TI DLLs) and Linux (using pre-compiled libraries based on proprietary TI 
code).

-- 
Mark J. Blair, NF6X n...@nf6x.net
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.