On Sat, Nov 03, 2012 at 12:31:36AM -0400, Alex Burka wrote:
> Hi Daniel,
> 
> Thanks! Unfortunately, that did not fix the problem. There is a little bit of 
> extra output now when mspdebug starts (in between "Number of breakpoints: 2" 
> and "Chip ID data: 25 53"):
> fet: FET returned NAK
> warning: device does not support power profiling
> 
> 
> But then the behavior is the same as before :(

Sorry, I just had another (more careful) look at the original output you
posted:

    (mspdebug) prog hello_world.elf
    Erasing...
    Programming...
    Writing 208 bytes at c000 [section: .text]...
    Writing 108 bytes at c0d0 [section: .rodata]...
    Writing 50 bytes at c13c [section: .data]...
    Done, 366 bytes total

This program is never going to run, because you aren't writing anything
to the reset vector (2 bytes at 0xfffe).

I notice the Makefile is supplying a lot of options to the linker, which
are probably unnecessary and possibly a problem. You should be able to
compile your program with just a single command:

    msp430-gcc $(CFLAGS) -mmcu=msp430g2553 -o hello_world.elf hello_world.c

Perhaps try compiling just like that first, see what happens, and then
see if you can alter the Makefile to get it working.

Cheers,
Daniel

-- 
Daniel Beer <dlb...@gmail.com>    www.dlbeer.co.nz
IRC: inittab (Freenode)    PGP key: 2048D/160A553B

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to