Thierry Varidel | 2 Jul 14:23 2013
Picon

MSP430F5659, msp430mcu-20130321, Windows

Hi all,

I want to use mspgcc with the MSP430F5659 and I've seen that the header
files for this microcontroller have been made available in
msp430-mcu-20130321.zip.

I'm working with Windows 8 and I was secretely hoping that it was as simple
as copying the .x and .h files of the MCU in the mingw32 prebuilt package
include and bin folders but if I do that, I have the following error when
linking :

memory.x(20): error : nonconstant expression for length

I've spent a lot of time altavisting for this and it seems that I'm the
only guy in the world using this MCU with MSPGCC. I couldn't find any clue
on how to put the mcu-20130321 in my mspgcc distribution.

I'm using mspgcc 4.6.3 for now but I plan to update to 4.7.0 for large
memory support.

Can anybody give me some information on how to achieve that?

Thanks in advance!

TV
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

(Continue reading)

Peter Bigot | 2 Jul 14:55 2013
Picon

Re: MSP430F5659, msp430mcu-20130321, Windows

> Can anybody give me some information on how to achieve that?

Not really.  In some cases you can mix versions of the component packages
of mspgcc and they'll probably work; in this case you can't.  See:
http://www.mail-archive.com/mspgcc-users <at> lists.sourceforge.net/msg11556.html

In short, the new FRAM chip headers require a compiler patch and are
unsupported in released mspgcc at this time.  An entity that may pay for
mspgcc maintenance is caught up on an internal matter that must be resolved
before they can fund a new release that includes the fix for this.  I have
no ability to influence that process, and at this time do not plan to
donate the necessary release packaging/testing effort myself (especially
since I have no boards using these new chips).

Peter

On Tue, Jul 2, 2013 at 7:23 AM, Thierry Varidel <thierry_varidel <at> sensimed.ch
> wrote:

> Hi all,
>
> I want to use mspgcc with the MSP430F5659 and I've seen that the header
> files for this microcontroller have been made available in
> msp430-mcu-20130321.zip.
>
> I'm working with Windows 8 and I was secretely hoping that it was as simple
> as copying the .x and .h files of the MCU in the mingw32 prebuilt package
> include and bin folders but if I do that, I have the following error when
> linking :
>
(Continue reading)

Thierry Varidel | 2 Jul 15:08 2013
Picon

Re: MSP430F5659, msp430mcu-20130321, Windows

Hello Peter,

Thank you for answering.

I have seen the mailing list entry you mentioned before.

In it, you said that the release 20130321 of msp430mcu is not working with
FRAM chips but the F5659 is not using FRAM this is why I was thinking that
it was feasible to use its headers from 20130321-msp430mcu with previous
builds. So is it supposed to work with this non FRAM chip?

Best regards,

TV

2013/7/2 Peter Bigot <bigotp <at> acm.org>

> > Can anybody give me some information on how to achieve that?
>
> Not really.  In some cases you can mix versions of the component packages
> of mspgcc and they'll probably work; in this case you can't.  See:
> http://www.mail-archive.com/mspgcc-users <at> lists.sourceforge.net/msg11556.html
>
> In short, the new FRAM chip headers require a compiler patch and are
> unsupported in released mspgcc at this time.  An entity that may pay for
> mspgcc maintenance is caught up on an internal matter that must be resolved
> before they can fund a new release that includes the fix for this.  I have
> no ability to influence that process, and at this time do not plan to
> donate the necessary release packaging/testing effort myself (especially
> since I have no boards using these new chips).
(Continue reading)

Peter Bigot | 2 Jul 15:32 2013
Picon

Re: MSP430F5659, msp430mcu-20130321, Windows

Sorry; I misread that as the FR5969.

In short, the only combinations that are supposed to work are the ones that
are in mspgcc releases.  The 20120406 mspgcc release you're using will
probably not work with 20130321 msp430mcu, but the 20120911 mspgcc release
probably would except for the risk of damaging FRAM chips if it was used
for them.

Peter

On Tue, Jul 2, 2013 at 8:08 AM, Thierry Varidel <thierry_varidel <at> sensimed.ch
> wrote:

> Hello Peter,
>
> Thank you for answering.
>
> I have seen the mailing list entry you mentioned before.
>
> In it, you said that the release 20130321 of msp430mcu is not working with
> FRAM chips but the F5659 is not using FRAM this is why I was thinking that
> it was feasible to use its headers from 20130321-msp430mcu with previous
> builds. So is it supposed to work with this non FRAM chip?
>
> Best regards,
>
> TV
>
>
> 2013/7/2 Peter Bigot <bigotp <at> acm.org>
(Continue reading)

Thierry Varidel | 2 Jul 15:57 2013
Picon

Re: MSP430F5659, msp430mcu-20130321, Windows

I found the problem!

There was a typo in the memory.x file at this line :

  ram_mirror (wx)  : ORIGIN = 0xfc000, LENGTH = 0x-f5c00

instead of :

  ram_mirror (wx)  : ORIGIN = 0xfc000, LENGTH = 0xf5c00

Now it compiles with mspgcc 4.7.0!

TV

2013/7/2 Peter Bigot <bigotp <at> acm.org>

> Sorry; I misread that as the FR5969.
>
> In short, the only combinations that are supposed to work are the ones
> that are in mspgcc releases.  The 20120406 mspgcc release you're using will
> probably not work with 20130321 msp430mcu, but the 20120911 mspgcc release
> probably would except for the risk of damaging FRAM chips if it was used
> for them.
>
> Peter
>
>
>
> On Tue, Jul 2, 2013 at 8:08 AM, Thierry Varidel <
> thierry_varidel <at> sensimed.ch> wrote:
(Continue reading)

Peter Bigot | 2 Jul 16:01 2013
Picon

Re: MSP430F5659, msp430mcu-20130321, Windows

That's almost certainly not the right correction, but as long as you don't
use the ram_mirror section it won't matter.

Thanks for following up; I'll add a ticket so if there's another release it
gets fixed.

Peter

On Tue, Jul 2, 2013 at 8:57 AM, Thierry Varidel <thierry_varidel <at> sensimed.ch
> wrote:

> I found the problem!
>
> There was a typo in the memory.x file at this line :
>
>   ram_mirror (wx)  : ORIGIN = 0xfc000, LENGTH = 0x-f5c00
>
> instead of :
>
>   ram_mirror (wx)  : ORIGIN = 0xfc000, LENGTH = 0xf5c00
>
> Now it compiles with mspgcc 4.7.0!
>
> TV
>
>
> 2013/7/2 Peter Bigot <bigotp <at> acm.org>
>
>> Sorry; I misread that as the FR5969.
>>
(Continue reading)

Cody Kemp | 3 Jul 00:06 2013

mspgcc Red Hat release

Hello everyone,

I have reached a point where I am needing to use upper memory in a project.
I am currently using version 20110716, and I would like to migrate the
project to the new Red Hat version if it will be arriving soon.  If not, I
will need to migrate to the newest LTS release. Is there an estimated
release date?

Thank you for your help,

Cody Kemp

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

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
Peter Bigot | 3 Jul 00:23 2013
Picon

Re: mspgcc Red Hat release

I don't follow the status of Red Hat's port, but if you need 20-bit support
you need 20120911 which is not an LTS release.

Peter

On Tue, Jul 2, 2013 at 5:06 PM, Cody Kemp <cody <at> houston-radar.com> wrote:

> Hello everyone,
>
> I have reached a point where I am needing to use upper memory in a project.
> I am currently using version 20110716, and I would like to migrate the
> project to the new Red Hat version if it will be arriving soon.  If not, I
> will need to migrate to the newest LTS release. Is there an estimated
> release date?
>
> Thank you for your help,
>
> Cody Kemp
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users <at> lists.sourceforge.net
(Continue reading)

Brendan Conoboy | 3 Jul 00:29 2013
Picon

Re: mspgcc Red Hat release

On 07/02/2013 03:06 PM, Cody Kemp wrote:
> Hello everyone,
>
> I have reached a point where I am needing to use upper memory in a project.
> I am currently using version 20110716, and I would like to migrate the
> project to the new Red Hat version if it will be arriving soon.  If not, I
> will need to migrate to the newest LTS release. Is there an estimated
> release date?

Essentially everything is upstream at this point except for gcc.  If you 
wanted to build up a current version of binutils, gdb, and gcc with the 
current patch set (http://patchwork.ozlabs.org/patch/252490/), you'd be 
good to go.

--

-- 
Brendan Conoboy / Red Hat, Inc. / blc <at> redhat.com

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

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
Sergei Sharonov | 3 Jul 00:51 2013

Re: mspgcc Red Hat release

Brendan Conoboy <blc <at> redhat.com> writes:
> Essentially everything is upstream at this point except for gcc.  If you 
> wanted to build up a current version of binutils, gdb, and gcc with the 
> current patch set (http://patchwork.ozlabs.org/patch/252490/), you'd be 
> good to go.
Will it build cleanly under Cygwin or Mingw? Are there any instructions on
doing so?
Regards,
Sergei 

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

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

Gmane