[En-Nut-Discussion] Building NUT/OS for Atmega2561

[Thiago A. Corrêa]

As far as I know, from the past posts from Harald and others, it's not yet
supported. The problem is that Atmel renamed many registers and the code
must be changed somehow to support the new names.

I've ordered a few samples to try porting it. It might take a while for them
to get here, but I'm interested in helping the porting effort if someone
wants to start it :)
We need some guidance on how to cope with the register renaming issue :)

On 7/6/06, Josh Arnold <jarnold at atterotech.com> wrote:
>
> Does anyone have step by step experience building NutOS for the Atmel
> Atmega2561.  This seems to be a hard topic to get info on.
>
> Thanks in advance,
> Josh Arnold
>
>
> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de
> [mailto:en-nut-discussion-bounces at egnite.de]On Behalf Of ivesworking
> Sent: Thursday, July 06, 2006 11:59 AM
> To: don at led.com.au; Ethernut User Chat (English)
> Subject: [En-Nut-Discussion] Q1:different on heapalloc and
> malloc]Q2:sprintf problem
>
>
> first, i use the mixture of malloc and nutheapalloc
> anyone can tell me is that different ?
>
>
> another problem is sprintf
> i use it for format my string,
> to avoid create another buffer, i do something like that
> char *temp;    //assume already allocate mem
>
> sprintf(temp,"hello world");
> sprintf(temp,"%s is testing program", temp);    // please assume that i
> will
> do some format on second sprintf
> are this example should work or it will be got problem on time over time.
>
> wfloh
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>