Hi Robert,
You still haven't said which version you are using. Is this the current
Windows installer at the mspgcc web site? If so, it may be this does not
have the current patch for the 1610, 1611, and 1612. When this support
was first added there were some errors, but that should have been sorted
out a long time ago.
The error will be in the files in the ldscripts directory. These are the
ones defining the memory map. We need to get a new installer built, if
the current one is not up to date.
Chris,
Can we have a new Windows installer built? I use a recent version of
binutils from sources.redhat.com without any problems.
Regards,
Steve
Robert Carlsson wrote:
Hi
Dmitriy
Thanks for your reply. I forgot to mention that I'm using mspgcc for
cygwin on windows. My knowledge of the GNU-toolchain is rather limited
but if I understand things correctly I would not be able to use the
binutils patch, and I would not need it since the cygwin-port of
binutils (and msp430-gdbproxy) already have support for
msp430x1611. I just thought I should share this
info with others, and maybe get a confirmation from someone who can
verify my claims.
I should correct myself by the way. In my post I claimed that the RAM
address range placement is incorrect, but it seems it's only the start
value of the stack register that's incorrect. All variables are placed
starting at address 0x1100 as they should.
I'm sorry that I wasted your time by not specifying what system I'm using.
Best regards,
Robert
