AW: [En-Nut-Discussion] EtherNUT-3.3.0 Example Problems - EtherNUT Newbie

Oliver Schulz olischulz at web.de
Wed Oct 15 20:46:28 CEST 2003


Right!

Alls calls to _ioctl on device devDebug0 or devDebug1 do nothing but
return -1. The speed of devDebug0 is set in device initialization fixed to
115.200 baud.

Oliver.

-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-admin at egnite.de
[mailto:en-nut-discussion-admin at egnite.de]Im Auftrag von Axel Zöllich
Gesendet: Mittwoch, 15. Oktober 2003 19:00
An: en-nut-discussion at egnite.de
Betreff: Re: [En-Nut-Discussion] EtherNUT-3.3.0 Example Problems -
EtherNUT Newbie


> 2> Major problem is Serial output seems to be corrupted. For example on
> loading the httpserv.hex - "make burn" verifies OK, but the following
> appears on the terminal screen. Note my IP addr is 10.10.10.99
>
> N++/OS 3.3.0.1 HTTP D#+ÄÅ...10.10.10.99 _#<
> [1] CÄÅÅ+, 23461 <+_ °_
>
> The other program exhibit the same problems. The original
> basmon worked without any uart problems but after re programming
> EtherNUT I haven't been successful in getting the UART0 to work
> reliably.

    /* this doesn't work */
    _ioctl(_fileno(stdout), UART_SETSPEED, &baud);

    /*
     * The NUT-OS debugcode doesn't set the baudrate on my atmega103.
     * therefor setting the hard way on 57600 baud.
     */
    outp(3, UBRR);

I have had the same problem. At the moment help myself with outp...

axel
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo/en-nut-discussion




More information about the En-Nut-Discussion mailing list