Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++

ocm_spi_mmu problem with NEEK

Altera_Forum
Honored Contributor II
1,231 Views

Hi 

 

I'm newbie and I want to make my NEEK working with MMU. I follow the tutorial in the NIOS wiki for the toolchain installation (I have Fedora 10). 

I succeded with my first project starting from scratch (only cpu and UART), so the toolchain is working and now I want to implement ethernet.  

 

I look at the Ethernet page on the wiki and for testing I download the ocm design for neek (neek_ocm_spi_mmu.zip). I take directly the custom_fpga and I try to configure the drivers (make menuconfig) and I have some difficulties to choose the drivers. I look at the thread "Avalon OpenCores MAC 10/100 + µClinux" thread 18390 and I configure the drivers accordingly. Anyway when I do "make" I have the following error : 

 

/home/phil/nios2-linux/linux-2.6/drivers/net/open_eth.c: In function 'oeth_phymac_synch': 

/home/phil/nios2-linux/linux-2.6/drivers/net/open_eth.c:757: error: 'PHY_ADDRESS' undeclared (first use in this function) 

/home/phil/nios2-linux/linux-2.6/drivers/net/open_eth.c:757: error: (Each undeclared identifier is reported only once 

 

Why this error? 

 

Antoher question more generic: where to find the driver to configure with the sopc modules I implement? I mean when I looked at the ip eth_ocm documentation I can't find the relevant options to cross in the "make menuconfig" 

 

Finally, I looked at the sopc configuration for the ocm_spi_mmu project and I'm wondering about the IRQ0 for the sys_clock_timer ??? I thought it as forbidden ??? 

 

Thanks
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
516 Views

please use ethoc for nios2mmu branch. The open_eth in nios2mmu branch is not updated yet. 

 

sys timer can use irq0. 

 

Please check nios wiki for driver info. 

 

- Hippo
0 Kudos
Altera_Forum
Honored Contributor II
516 Views

Thanks Hippo, it's now working.  

 

Anyway I have the same issue as other people, with RX : overrun and packet dropped. I use ethoc in static IP, with route and gateway configured. What is amazing is that overrun and packet dropped messages appear only when I connect the NEEK to my lab network. When I use only a ethernet "cross" cable between my pc and the neek, this error disappears !!!! Any idea ? 

 

Another issue is now to configure the framebuffer. I use the Framebuffer wiki page and I guess the fb0 is working because the neek screen as color bars. But if I want to use Microwindow and specially nanox, I have the jpeg error: 

 

/usr/lib/libjpeg.so: could not read symbols: File in wrong format 

collect2: ld returned 1 exit status 

make[5]: *** [/home/phil/nios2-linux/uClinux-dist/user/microwin/src/bin/nano-X] Error 1 

make[5]: Leaving directory `/home/phil/nios2-linux/uClinux-dist/user/microwin/src/nanox' 

I looked at the jpeg library and it's automatically selected.  

 

I tried to not use jpeg (png for instance) and I have a equivalent problem. 

 

I'm stucked.
0 Kudos
Reply