[En-Nut-Discussion] Fw: Using AT91SAM7

Angel Sanchez angelsp at aumat.es
Tue Nov 27 10:44:31 CET 2007


Thanks for the replies

I am going to investigate a bit more.

When I have the port working, I will made it public

----- Original Message ----- 
From: "Thiago A. Corrêa" <thiago.correa at gmail.com>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Monday, November 26, 2007 5:40 PM
Subject: Re: [En-Nut-Discussion] Using AT91SAM7


> One could be created on the wiki *hint* :)
>
>
> On Nov 26, 2007 12:53 PM, Dave Warren <dwarren at luescher.com> wrote:
>> Hi Angel,
>>
>> There is not a supported port to CrossWorks, just a small number of 
>> people
>> who use it and make a few 'hacks' to get it working.
>>
>> I think the problem with interrupts is in NutEnterCritical. I use the
>> ..\nut\include\arch\arm\atom.h from 4.2.1 then interrupt works.
>>
>> I think it would help if we had a page on the website discribing how to 
>> use
>> Ethernut with Crossworks
>>
>> regards
>>
>> Dave Warren
>>
>>
>> ----- Original Message -----
>> From: "Angel Sanchez" <angelsp at aumat.es>
>> To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
>> Sent: Monday, November 26, 2007 1:08 PM
>> Subject: [En-Nut-Discussion] Using AT91SAM7
>>
>>
>> > Hello
>> >
>> > I am using Ethernut 4.4.0 with AT91SAM7XC256, compiling both Ethernut 
>> > and
>> > my application with Rowley CrossWorks
>> >
>> > My main is only a loop calling NutSleep (100);
>> >
>> > I have the following problems:
>> > - The main loop is executed only the first entry.
>> > - Tracing the code, I find IRQ interupts disabled permanently
>> > - Forcing an initial enable, in some point from inside the kernel the
>> > interrupt are disabled again
>> > - In anoter test, including the compiler option -f omit-frame-pointer, 
>> > the
>> > application crash, and seem be a erroneus implementation of
>> >   NutEnterCritical  (It push the saved csr in stack, changing the 
>> > offsets
>> > to paremeters an local variables)
>> >
>> > I am very surprised by this problem, because reading the discussion 
>> > list,
>> > the port seem work correctly.
>> >
>> > Can somebody give me some hint about this problems?
>> >
>> > Thanks in advance
>> >
>> > Angel Sanchez
>> > _______________________________________________
>> > http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>> >
>>
>> _______________________________________________
>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion 




More information about the En-Nut-Discussion mailing list