[En-Nut-Discussion] Porting Ethernut 1.3-Rev. G to my hardware

Harald Kipp harald.kipp at egnite.de
Tue Oct 31 16:09:54 CET 2006


1. Missing 32kHz crystal
Setting NUT_CPU_FREQ to the main crystal frequency of your
board (e.g. 14745600 for Ethernut 1).

2. EEPROM Emulation
Earlier Ethernut 1.3 revisions do not have this either.
http://www.ethernut.de/pdf/enut13e-s3.pdf
See ethernut13f.conf and compare this with ethernut13g.conf.

3. Realtek connected to GPIO
You need to re-write arch/avr/dev/nicrtl.c. Probably, more has
to be done than just modifying the I/O macros. If the changes
are minor, please send the updated file (or a diff) to my
egnite email address or just info at egnite dot de. If more
changes are required, you may prefer to create a new source
file.

If your hardware will be available to others, you may want
to publish your own .conf file as well.

If you are familar with CVS, you may also apply for CVS write
access. In this case contact me directly.

Harald


At 18:58 29.10.2006 -0200, you wrote:
>Thanks to Harald, I understood the Nut/os configurator.
>
>Now I am trying to port the code to my hardware.
>I analyse ethernut 1.3-Rev G, and saw that my hardware has 3 majors 
>diferences from Rev G.
>one is that rtl8019 it is not memory mapped, I use portF and port b to 
>deal to it, second is that I do not have 32768 crystal, third I do not 
>have the conections to do an eeprom emulation to rtl8019, so I have 
>doubts, one of them is about the low level function to read and write to 
>rlt8019, I saw into the code that in file nicrtl.c has 2 macros (NICOUTB 
>and NICINB) that do low level read and write to rtl8019, my questions is:
>Are these functions the only one low level to deal with rtl8019? As they 
>read and write byte, I think the ethernut does not read word or etc?
>About crystal 32768, has ethernut another way to bypass it or I must 
>provide this crystal.?
>Last but not least,does the ethernut provide another way to config rtl8019 
>without an eeprom or eeprom emulation?
>
>When these changes stay stable, how is the way to public them to ethernut 
>users?
>
>regards
>
>Zach.




More information about the En-Nut-Discussion mailing list