Zynq Ethernet driver

[Davide Viti]

Hi,
I'm a RTEMS newbie and I've recently experimented with RTEMS on a microzed
board.
I did some basic testing with the provided examples, and I'm now interested
to know more about the support for the Ethernet; this is what I figured out
so far:

   - the RTEMS page on the xilinx site (http://www.wiki.xilinx.com/RTEMS)
   lists "Etherne" among the supported devices - it is wrong and misleading
   - there's no support for the Ethernet in the current source tree
   - back in 2013, a patch adding support for the Ethernet driver was
   submitted (https://lists.rtems.org/pipermail/devel/2013-April/002915.html)
   but not included upstream. I depends on some sources which must be obtained
   from Xilinx
   - current u-boot supports the Eternet device with GPL licensed code

I'm giving a go at resurrecting the patch which must fit the latest RTEMS
sources and the most recent version of the BIST code I've obtained from
Xilinx. I got to the point where I can compile the BSP and a simple
application using the ethernet driver: I got there workarounding and
postponing the problems I stepped into.

the application hangs after doing some device initialization, in particular
in the middle of a routine initializing dma.
The comments before the offending code say: /* Allocate a 1 MB MMU page
aligned to 1 MB boundary for the BDs.*/
/ The BDs need to be allocated in uncached memory. Hence the 1 MB address
* range just allocated is made uncached by setting appropriate attributes *
in the translation table.
*/

It turns out that xilinx code relies on a MMUTable declared as "extern u32"
and handled in the linker script as follows:

.mmu_tbl (ALIGN(16384)) : {

*mmu_tbl_start = .; *(.mmu_tbl) *mmu_tbl_end = .;
} > ps7_ddr_0_S_AXI_BASEADDR

Can I get some help on handling such memory area with current RTEMS linker
script?

thanx so much in advance

Davide
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20151125/3f0a341a/attachment.html>