[En-Nut-Discussion] ethernut on display3000 board
Philipp Brüll
phil at outofsync.de
Tue May 15 14:04:21 CEST 2007
There is a 16Mhz xtal connect to the chip. but this shouldn't be a
problem, because during the configuration I set NUT_CPU_FREQ to 16000000
and I'm not using the usart or anything else related to a baud rate.
anyway - thanks for the idea
Philipp
David Armstrong schrieb:
> just a thought
> dependant on your configuration Ethernut expects a 32Khz xtal to be fitted
> for the auto baud rate
> if you do not have the xtal fitted you need to set the options for your cpu
> xtal
>
> Dave
>
> ----- Original Message -----
> From: "Philipp Brüll" <phil at outofsync.de>
> To: <en-nut-discussion at egnite.de>
> Sent: Tuesday, May 15, 2007 11:05 AM
> Subject: [En-Nut-Discussion] ethernut on display3000 board
>
>
>> Hello,
>>
>> currently I'm trying to run the latest (4.2.1) nut/os version on a
>> display3000 board (www.display3000.com). The display board is just a
>> simple board with a display and an atmega128 chip. It isn't a problem to
>> compile and upload a simple application that turn a led on and of.
>> Without ethernut it's working fine, but if I just link the ethernut
>> libs, nothing is happened any more. Compile, upload (via avrdude) is ok,
>> but no blinking led :-(
>> I turned off any optimisation. I think it's a problem either with the
>> nutinit or the linking of the main() method. Does someone know under
>> which circumstances the ethernut initialisation is not running through?
>>
>> Maybe someone who has experience with running ethernut on
>> not-original-ethernut-hardware can help me?
>>
>> Regards
>> Philipp
>> _______________________________________________
>> 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