[En-Nut-Discussion] Re: En-Nut-Discussion Digest, Vol 12, Issue 24

[Diamantopoulos Georgios]

en-nut-discussion-request at egnite.de wrote:

>Send En-Nut-Discussion mailing list submissions to
>	en-nut-discussion at egnite.de
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>or, via email, send a message with subject or body 'help' to
>	en-nut-discussion-request at egnite.de
>
>You can reach the person managing the list at
>	en-nut-discussion-owner at egnite.de
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of En-Nut-Discussion digest..."
>
>
>Today's Topics:
>
>   1. Re: RAW packets transmission (Pavel Chromy)
>   2. Compatibility Problem Between Rev. F and Rev. G
>      (Diamantopoulos Georgios)
>   3. Re: Compatibility Problem Between Rev. F	and Rev. G (Harald Kipp)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 18 Oct 2004 15:22:40 +0200
>From: Pavel Chromy <chromy at asix.cz>
>Subject: Re: [En-Nut-Discussion] RAW packets transmission
>To: Igor Fedorchuk <bel at micran.ru>,	"Ethernut User Chat (English)"
>	<en-nut-discussion at egnite.de>
>Message-ID: <4173C3A0.6040401 at asix.cz>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
>Igor Fedorchuk wrote:
>
>  
>
>>I want to make bridge from Ethernut to RS232 and back from RS232 to
>>EtherNut.
>>    
>>
>
>No a good idea. You have to at least recognize packet beginning/end.
>
>  
>
>>But I dont want use IP routines but want use RAW packets as
>>is, i.e. simple receive packets from LAN, store its to memory and next
>>send it to UART.
>>    
>>
>
>Those things running there and back on the LAN are not packets but rather _frames_.
>It seems to me to be much better idea to capture IP packets (strip off MAC header)
>with simple check of IP header and use SLIP on RS232.
>
>  
>
>>What sort of API functions should I use?  I thing
>>that I should create event to RX and TX events but I  not for a while
>>yet know what it do.
>>Thanks. :)
>>    
>>
>
>I'm afraid there are no API functions as this is not a typical use of a network interface.
>Have a look at the sources net/ ethin.c ethout.c ipin.c ipout.c
>Practically everything you need is in there.
>
>Pavel
>
>
>------------------------------
>
>Message: 2
>Date: Mon, 18 Oct 2004 16:26:39 +0300
>From: Diamantopoulos Georgios <gnagiag at yahoo.gr>
>Subject: [En-Nut-Discussion] Compatibility Problem Between Rev. F and
>	Rev. G
>To: en-nut-discussion at egnite.de
>Message-ID: <4173C48F.4070308 at yahoo.gr>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Hello to everyone,
>
>I have been developing a program (which runs on ethernut 1.3 Rev. F)  
>for the company that I work. This program makes full use of the UART, 
>LAN and all the I/O (Digital and analog). I have produced a Hex  file 
>which when uploaded to an ethernut board Rev. F works just fine but when 
>uploaded to Rev. G it does not work (I cannot use the ethernet to 
>communicate with the board) . To be even more precise when my program 
>start its execution for the first time I am using a socket connection 
>(to a predefined IP) in order  to program the ethernut with some initial 
>values (such as IP, Device Number etc.), a step which works just fine 
>with Rev. F  as I have already mentioned, but does not work when the 
>board is of  Rev. G.
>- First of all I do want to ask if anyone has any kind of Idea why this 
>is happening ?, and
>- If the Rev. F will be a discontinued version?
>
>Thank you all in advance.
>
>
>
>------------------------------
>
>Message: 3
>Date: Mon, 18 Oct 2004 17:05:47 +0200
>From: Harald Kipp <harald.kipp at egnite.de>
>Subject: Re: [En-Nut-Discussion] Compatibility Problem Between Rev. F
>	and Rev. G
>To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
>Message-ID: <5.1.1.6.0.20041018164735.04938830 at egnite.de>
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>Hello Diamantopoulos,
>
>the main difference is EEPROM emulation, which is new to Rev-G.
>There are several options:
>
>1. Hardware modification
>Take a look to schematic page 3. Removing R7 and mounting
>R37 (on the bottom side) makes the board Rev-F compatible.
>
>2. Software upgrade
>Download version 3.9.2 from
>http://www.ethernut.de/en/download.html
>Choose ethernut13g.conf with the Configurator
>http://www.ethernut.de/en/nutconf/index.html
>to build the new system. This will work with
>Rev-F and Rev-G boards.
>
>3. Software modification
>Replace dev/nicrtl.c with
>http://cvs.sourceforge.net/viewcvs.py/*checkout*/ethernut/nut/dev/nicrtl.c?rev=1.8
>in the Nut/OS version you are currently using.
>Again, this will work with Rev-F and Rev-G
>
>The advantage with Rev-G and the new software is, that
>the RTL8019 will run in half duplex mode, which makes
>Ethernet transfers much more reliable with standard
>switches.
>
>egnite will not continue Rev-F, but in case you refuse to change
>your software or do the hardware mod yourself, you can order modified
>Rev-G boards with R37 mounted and R7 removed.
>
>Harald
>
>
>At 16:26 18.10.2004 +0300, you wrote:
>  
>
>>Hello to everyone,
>>
>>I have been developing a program (which runs on ethernut 1.3 Rev. F)
>>for the company that I work. This program makes full use of the UART, LAN 
>>and all the I/O (Digital and analog). I have produced a Hex  file which 
>>when uploaded to an ethernut board Rev. F works just fine but when 
>>uploaded to Rev. G it does not work (I cannot use the ethernet to 
>>communicate with the board) . To be even more precise when my program 
>>start its execution for the first time I am using a socket connection (to 
>>a predefined IP) in order  to program the ethernut with some initial 
>>values (such as IP, Device Number etc.), a step which works just fine with 
>>Rev. F  as I have already mentioned, but does not work when the board is 
>>of  Rev. G.
>>- First of all I do want to ask if anyone has any kind of Idea why this is 
>>happening ?, and
>>- If the Rev. F will be a discontinued version?
>>
>>Thank you all in advance.
>>    
>>
>
>
>
>------------------------------
>
>_______________________________________________
>En-Nut-Discussion mailing list
>En-Nut-Discussion at egnite.de
>http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>
>
>End of En-Nut-Discussion Digest, Vol 12, Issue 24
>*************************************************
>
>  
>

Hello Harald, 

I want to thank you for your responce. I will discuss the choices that you suggested 
with my boss to choose which best suits in  our case, and then I will try to implement it.

Georgios