A possible way to handle this (at least on chips where the USB ram is right 
before and not behind the 'normal' ram) would be to have the USB-related
includes in a separate header file that needs to be included manually.
Within the header file, the USB ram is allocated as a fixed-address
non-initialized buffer.

This way, it would be placed there if the header is included and the ram would
be free for the rest if not.
Since the USB ram is before the normal ram, there is no need for a separate
linker file, as the stack pointer init would be the same. The USB ram would
just be normal ram in the memory map.

But I'm not 100% sure whether you need to access the USB registers (and
therefore include the USB header) just to send the USB part in lowest power
state after power-up. I never worked with USB.

JMGross

----- Ursprüngliche Nachricht -----
Von: Peter Bigot
An: Mathias K.
Gesendet am: 09 Okt 2011 18:11:30
Betreff: Re: [Mspgcc-users] MSP430F5510 - USB RAM

Found an old related ticket at
https://sourceforge.net/tracker/?func=detail&aid=3113886&group_id=42303&atid=432701

I've asked TI to provide the information necessary to support the solution
described below in the next msp430mcu release.

Peter

On Sat, Oct 8, 2011 at 6:38 AM, Peter Bigot <big...@acm.org> wrote:

> I don't believe so.
>
> One fairly simple solution would be to augment msp430mcu to detect
> chips with USB RAM and to provide two MCU descriptions for them.
> Viz., msp430f5510 which would reserve USB memory and msp430f5510nousb
> which would combine it with RAM (assuming the two are contiguous).
> The only difference would be in linker flags and the memory map.
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to