[U-Boot-Users] Looking for Info on Marvell Libertas 88w8510 WLAN/88E606 switch chipset, AP32/52 SDK or reference design

[Jeff Strickrott]

Hello U-boot forum:

I am searching for some more concrete information on the Marvell Libertas
88w8510 wireless lan and 88E6060 switch. In particular something that
describes the internal registers for memory mapping, interrupts, switch
registers, etc. Better still would be the documentation and the SDK from the
Marvell AP52/32 reference designs. I am writing because I have seen post in
the past from groups with access to the Marvell's SDK. Marvell supplies a
SDK for eCOS or uClinux.



I have been trying to reverse engineer the Netgear WGR614v4 wireless access
based upon the 88W8510 and its associated switch chip. This is almost
identical in design to the AP52 reference design. I have however been
hampered by the lack of documentation.



Here is what I have been able to do on my own:



1.      I have built a JTAG interface and can run C code on the ARM 946
processor and communicate via the serial interface (see 2 below).

2.      I currently have source for the  firmware boot loader code which was
a port of U-boot done by Marvell around 2003. The code was available through
ASUS GPL code for the WL530g but has been pulled. (now only listed on
http://files.wl500g.info/asus/wl530g/gpl/) The memory model between the
Netgear and ASUS product are different.

3.      I have not been able to get the U-boot Ethernet code to work. This
could be due to:

a.       Improper setup of the memory controller on the 88W8510,

b.      Improper setup of interrupt controller,

c.       Improper setup of the WLAN and switch.

4.      I have disassembled the existing Netgear code and can load and run
this from ram, but I have not had the time to understand how and what
registers the commercial code is initializing for the Ethernet controller
and how this is different from Marvell's port of the U-boot code. My
suspicion is that the U-boot code does not know about the switch and I am
not setting it up correctly so the Arp packets I send are never actually
written to the physical layer.

5.       Netgear supplies only limited header files and just object code for
its GPL release (no source) so I am still missing details.



Could anyone shed any more details?



Thanks in advance for the help.

Regards,

--Jeff Strickrott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060802/5fca8604/attachment.htm