[En-Nut-Discussion] Nut/OS configuration utility

[Marc Wetzel]

Hi Hugo,

I just had something similar to your problem with a custom board I made
recently. What helped me was just sending many A's out of one uart and
inspecting this signal with an oscilloscope, and then I saw that my
frequency setting was completely wrong. I thought I had set the fuses to
external but they weren't. They still were set to internal oscillator.

Regards
/Marc

> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de [mailto:en-nut-discussion-
> bounces at egnite.de] On Behalf Of Adam Baran
> Sent: Saturday, July 10, 2004 6:50 PM
> To: Ethernut User Chat (English)
> Subject: Re: [En-Nut-Discussion] Nut/OS configuration utility
> 
> Just a hint: 3.4.2 release has spoiled timer initialisation when
> NUT_CPU_FREQ is defined if You are using this release You should apply a
> patch.
> If You are using other release just don't bother, maybe someone other can
> help.
> 
> 
> badam
> 
> 
> 
> ----- Original Message -----
> From: "Hugo Simon" <hugo.simon at gmx.de>
> To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
> Sent: Saturday, July 10, 2004 6:34 PM
> Subject: Re: [En-Nut-Discussion] Nut/OS configuration utility
> 
> 
> > I just tried that. I edited the makedefs and makedefs.gcc to uncomment
> the
> > NUT_CPU_FREQ line.
> > Then I did an "make clean" and an "make all". But it doesnot help.
> >
> > Is that the wrong place to do the definition? I also uncommented the
> > NUT_DEBUG definition, but the debug messages did not appear.
> >
> > Then I tried flashing the basemon into my hardware, works fine.
> >
> > Any furter ideas?
> >
> > Thanks
> > Thorsten
> 
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion