[En-Nut-Discussion] nut/os-timer-PORTA-problem

Ernst Stippl ernst at stippl.org
Wed Apr 2 22:53:13 CEST 2008


Hi Ajit!

As far as I understand nutinit.c, removing the definitions of NUTXMEM_SIZE =
"28416" and NUTXMEM_START = "0x1100" completely from the .conf file seems
right for me to disable external memory. 
How do you actually figure out it's NutSleep which does not return?
How many threads do you have running?
Does the board lock up completely or are some parts of the SW still running.

Regards
Ernst


-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Ajit Ratnaparkhi
Gesendet: Dienstag, 01. April 2008 23:23
An: Ethernut User Chat (English)
Betreff: Re: [En-Nut-Discussion] nut/os-timer-PORTA-problem

Hi Ernst,

thanks a lot for your help. Will try this to check whether external memmory
is really disabled or not. Actually to disable external memmory I just
removed external memmory related declarations from the configuration file
like,
NUTXMEM_SIZE = "28416"
NUTXMEM_START = "0x1100"
I removed above two declarations from the configuration file. can you tell
me any other way to disable external memmory if there is any?
your help is valuable.

thanx and regards,
-ajit.

On Wed, Apr 2, 2008 at 2:28 AM, Ernst Stippl <ernst at stippl.org> wrote:

> Hi Ajit!
>
> Besides setting the values to disable usage of external memory, have you
> tried to prove that your application does not use it?
> A way to do this would be to call NutHeapAvailable() and display the
> result.
> It must not be larger than 4096 (in any case, because this is the size of
> the internal memory), actually it must be considerable less: 4096 minus
> the
> stack size of (384 for "idle" plus 768 for "main") minus stack size of app
> threads minus variables allocated from heap minus some global vars.
>
> Regards
> Ernst
>
> -----Ursprüngliche Nachricht------discussion-bounces at egnite.de] Im Auftrag
> von Ajit Ratnaparkhi
> Gesendet: Dienstag, 01. April 2008 22:30
> An: Ethernut User Chat (English)
> Betreff: Re: [En-Nut-Discussion] nut/os-timer-PORTA-problem
>
> Hi,
> I am using Ethurnut2, ATmega128, and I am not using external memmory, I
> have
> set configuration file accordingly, also I have not defined
> NUTMEM_STACKHEAP
> in configuration file. Do I need to include this? And what is the solution
> to make timer work while using PORTA simultaneously?
> Mime-Version: 1.0
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain; charset=iso-8859-1
> Content-Disposition: inline
>
> thanks and regards,
> -ajit
> On Wed, Apr 2, 2008 at 1:42 AM, Ernst Stippl <ernst at stippl.org> wrote:
>
> > Hi!
> >
> > Which Ethernut board do you use?
> > If it is Ehternut 1 or 2 or compatible using the ATmega128 CPU, this is
> an
> > excerpt from the ATmega128 data sheet:
> >
> > Alternate Functions of Port A
> > The Port A has an alternate function as the address low byte and data
> > lines
> > for the External Memory Interface.
> >
> > So, if you external memory, port A is needed for it.
> >
> > Regards
> > Ernst
> > -----Urspr=FCngliche Nachricht-----
> > Von: en-nut-discussion-bounces at egnite.de
> > [mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Ajit
> > Ratnaparkhi
> > Gesendet: Dienstag, 01. April 2008 22:01
> > An: en-nut-discussion at egnite.de
> > Betreff: [En-Nut-Discussion] nut/os-timer-PORTA-problem
> >
> > Hi all,
> >
> > I am using nut/os for development of an embeded application as a course
> > assignment.
> > I am facing problem while using timer functions,
> > The problem is,
> >
> > Whenever I output some value on PORTA, all the timer functions stop
> > working
> > like NutSleep(). NutSleep(ms) makes the program to sleep forever,
> instead
> > of
> > 'ms' amount of time. Some motors are connected to PORTA of the embedded
> > device which I am working on. So to operate those motors I have to set
> > PORTA
> > to some value other than 0x00, and as soon as I change the value the
> > timers
> > stop working.
> >
> > Somebody please tell me what might be the problem, and what is the
> > solution
> > for it?
> >
> >
> > Thanks and regards,
> > - Ajit.
> > _______________________________________________
> > http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> >
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.519 / Virus Database: 269.22.3/1354 - Release Date:
> > 01.04.2008
> > 05:38
> >
> >
> > _______________________________________________
> > http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> >
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.519 / Virus Database: 269.22.3/1354 - Release Date:
> 01.04.2008
> =
> 05:38
>
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion



-- 
No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.519 / Virus Database: 269.22.3/1354 - Release Date: 01.04.2008
05:38





More information about the En-Nut-Discussion mailing list