[En-Nut-Discussion] Problems sending 0x0D data to a remote server.

[Matthias Ringwald]

hi

this called cooked-mode and it converts 0x0d into 0x0d 0x0a, at least for the UARTs. You can disable it with an ioctl somehow (grep for cooked)

best
 Mathias

On Mar 25, 2010, at 12:40 PM, Javier Longares wrote:

> Hi all,
> 
> We have a system composed of an ethernut which sends and receives commands
> and events from another board.  Each of these commands and events are
> composed by headers, CRCs, etc.  When an event is received by the ethernut,
> it must to check if the CRC is OK and then retransmit it to a remote socket
> server. The problem has appeared when an event has the byte 0x0D, because in
> this case the remote socket server receives 0x0A despite 0x0D.
> 
> We've checked our code and if the data is sent though a serial port the data
> is transmitted OK.  So, as far as I know, the Internet Protocol has some
> stuffing with the CARRIER and LINEFEED bytes (0x0d and 0x0a),  If this is
> the problem I would know if this stuffing can be avoided indicating that
> we're sending data bytes (binary) despite text or not.
> 
> Best regards,
> Javier
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion