Re: TI AM35xx support

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

Hello, panu.

(2013/01/12 17:41), panu.finnila%iki.fi@localhost wrote:
> Hi Jeff,
>
> Thanks for the reply. I already tried, but it seems that AM35xx is
> much closer to OMA3530 than AM335x. Can't boot BEAGLEBONE kernel
> on AM35xx because every single peripheral register has different
> address.
>
> Also the AM35xx Ethernet controller is different from one that is
> used at AM33xx but I hope there are some similar registers.
>
> http://processors.wiki.ti.com/index.php/OMAP35x_to_AM35x_Hardware_Migration_Guide
> http://processors.wiki.ti.com/index.php/AM35x_To_AM335x_Hardware_Migration_Guide
>
> --
> -panu
>
> Jeff Rizzo writes:
>  > On 1/11/13 11:47 AM, panu.finnila%iki.fi@localhost wrote:
>  > > Hello all,
>  > >
>  > > Anyone tried NetBSD on TI AM35xx based board? I'm able to run current
>  > > BEAGLEBOARD kernel with 6.0 userland without any source changes.
>  > > It runs relatively well on SD card. It halts after couple of minutes
>  > > running idle but it's ok for now.
>  > >
>  > > But the Ethernet driver is missing... To enable Ethernet controller
>  > > it would need a new memory region (IPSS, 0x5C000000 - 0x5EFFFFFF) to
>  > > be added into the omap2_obio driver. Is this legal?
>  > >
>  > > # dmesg | grep ^obio
>  > > obio0 at mainbus0 base 0x48000000-0x48ffffff: On-Board IO
>  > > obio1 at mainbus0 base 0x48300000-0x4833ffff: On-Board IO
>  > > obio2 at mainbus0 base 0x49000000-0x490fffff: On-Board IO
>  > > obio3 at mainbus0 base 0x54000000-0x547fffff: On-Board IO
>  > > obio4 at mainbus0 base 0x5c000000-0x5effffff: On-Board IO
>  > >
>  > > I tweaked BEAGLEBONEs if_cpsw driver a little. Now it's able to
>  > > correctly read the MAC address without crashing, no more:
>  > >
>  > > cpsw0 at obio4 addr 0x5c000000-0x5c007fff intrbase 67: TI CPSW Ethernet
>  > > cpsw0: Ethernet address 00:50:c2:1e:af:fa
>  > > cpsw0: no PHY found!
>  > >
>  > > # ifconfig cpsw0
>  > > cpsw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>  > >          address: 00:50:c2:1e:af:fa
>  > >          media: Ethernet manual (none)
>  > >
>  >
>  > The BEAGLEBONE kernel (in -current) works on, well, the BeagleBone,
>  > which has an AM355x in it.  You might want to start there...  It's
>  > missing a few things (USB), but is getting there.
>  >
>  > +j

 This problem might be fixed by today's commit by ozaki-r. Do you still have
the board?


> Module Name:    src
> Committed By:   ozaki-r
> Date:           Wed Feb 26 03:58:33 UTC 2014
>
> Modified Files:
>         src/sys/arch/arm/omap: if_cpsw.c if_cpswreg.h
>
> Log Message:
> Make cpsw driver work without uboot support
>
> On some eval boards such as BeagleBone, the cpsw device is initialized
> rightly by the uboot of the boards so that the cpsw driver doesn't need
> to do some initializations but works fine.
>
> The patch adds initializations to make the driver work solely. It also
> adds support for 1000BaseT (RGMII) PHY that is equipped on some boards,
> e.g., CKB-3352.
>
> Reviewed by christos@
>
>
> To generate a diff of this commit:
> cvs rdiff -u -r1.4 -r1.5 src/sys/arch/arm/omap/if_cpsw.c
> cvs rdiff -u -r1.1 -r1.2 src/sys/arch/arm/omap/if_cpswreg.h


--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)