USB Host support on mpc 8313

USB Host support on mpc 8313

[Joaquin Luna]

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

Is there anyone out there who has tried getting usb to work under the
2.6.27 kernel?  I am using the Freescale MPC831x RDB platform and when I
enable "Support for Freescale on-chip EHCI USB controller"
(USB_EHCI_FSL) I get stuck during boot up.  The last two lines of my
boot log are:

 

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

 

 

With the 2.6.20 kernel I had usb working and my boot log looked like:

 

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 38, io base 0xe0023000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004

 

 

I did notice that there were a few usb bug fixes that went into 2.6.27.7
so I updated to the latest version, but it did not help.  Any idea how
or where I can begin looking for a solution?

 

Cheers,

Joaquin Luna


[-- Attachment #2: Type: text/html, Size: 4250 bytes --]

RE: USB Host support on mpc 8313

[Li Yang]

> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.org=20
> [mailto:linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.o
> rg] On Behalf Of Joaquin Luna
> Sent: Monday, November 24, 2008 11:24 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: USB Host support on mpc 8313
>=20
> Is there anyone out there who has tried getting usb to work=20
> under the 2.6.27 kernel?  I am using the Freescale MPC831x=20
> RDB platform and when I enable "Support for Freescale on-chip=20
> EHCI USB controller" (USB_EHCI_FSL) I get stuck during boot=20
> up.  The last two lines of my boot log are:
>=20
> =20
>=20
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
>=20
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
>=20
> =20
>=20
> =20
>=20
> With the 2.6.20 kernel I had usb working and my boot log looked like:
>=20
> =20
>=20
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
>=20
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
>=20
> fsl-ehci fsl-ehci.0: irq 38, io base 0xe0023000
>=20
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
>=20
> =20
>=20
> =20
>=20
> I did notice that there were a few usb bug fixes that went=20
> into 2.6.27.7 so I updated to the latest version, but it did=20
> not help.  Any idea how or where I can begin looking for a solution?


There are two settings of the board (USB internal PHY/ USB external
PHY).  They are described in the board UM.

Is the phy_type property in DTS matching the board setting?
utmi_wide for internal PHY
ulpi for external PHY

- Leo

Regarding MPC5200

[Naveen Kumar]

HI,
I am using the MPc5200 processor(TQM5200) board with stk5200 base board for
porting embedded Linux kernel 2.4.25 denx distribution with U-boot loader.
Am trying to compile the drivers for my atheroes chipset AR5006x series with
madwifi able to load the driver and see the wireless interface by ifconfig
command and do self ping but unavle to connect to the Access point or the
other wlan module.
What might be the problem help in this regard is highly appreciated
Regards
Naveen

Re: Regarding MPC5200

[Grant Likely]

On Mon, Nov 24, 2008 at 12:37 AM, Naveen Kumar
<naveenkumar_v@infotechsw.com> wrote:
> HI,
> I am using the MPc5200 processor(TQM5200) board with stk5200 base board for
> porting embedded Linux kernel 2.4.25 denx distribution with U-boot loader.
> Am trying to compile the drivers for my atheroes chipset AR5006x series with
> madwifi able to load the driver and see the wireless interface by ifconfig
> command and do self ping but unavle to connect to the Access point or the
> other wlan module.

Is there any particular reason that you're using a 2.4 kernel?
Current 2.6 kernels have much better MPC5200 support, including
support for the TQM5200.  As for your question you'd probably be
better off asking on either the wireless or Madwifi mailing lists
where people are more familiar with wireless issues.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

Re: Regarding MPC5200

[Wolfgang Denk]

Dear Naveen Kumar,

In message <200811240740.mAO7eS4X013348@mail.infotechsw.com> you wrote:
>
> I am using the MPc5200 processor(TQM5200) board with stk5200 base board for
> porting embedded Linux kernel 2.4.25 denx distribution with U-boot loader.

There is full support for the TQM5200 / STK5200 in mainline. Please
use a recent 2.6 kernel for any current work.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Never underestimate the bandwidth of a station wagon full of tapes.
                                -- Dr. Warren Jackson, Director, UTCS

NMI and AMD8131/8111 on Maple board

[Benjamin Walsh]

Hi all,

I've written EDAC support for the AMD8131/8111 chips that are present on a
Maple board (PPC970FX with IBM CPC925 memory controller/bridge), currently
running in poll mode. I am now trying to get this to work in interrupt mode.
These two chipsets have a feature that enables triggering an NMI when an
error is detected (PERR and SERR). How can this be hooked into the interrupt
system on a PPC board ?

>From what I understand from the doc for these chipsets, the NMI will
delivered as a HT message to the CPC925 on this board. What I don't get is
how will this be delivered to the CPU, and on what interrupt line ? The HT
message sent to the CPC925 is the following:

MT = NMI
TM = edge
DM = physical
INTRDEST = 'hFF (all)
VECTOR = 'h00 (does not matter)

Any help appreciated.

Thanks,
Ben

Re: NMI and AMD8131/8111 on Maple board

[tiejun.chen]

Benjamin Walsh wrote:
> Hi all,
> 
> I've written EDAC support for the AMD8131/8111 chips that are present on a
> Maple board (PPC970FX with IBM CPC925 memory controller/bridge), currently
> running in poll mode. I am now trying to get this to work in interrupt mode.
> These two chipsets have a feature that enables triggering an NMI when an
> error is detected (PERR and SERR). How can this be hooked into the interrupt
> system on a PPC board ?
> 
>>From what I understand from the doc for these chipsets, the NMI will
> delivered as a HT message to the CPC925 on this board. What I don't get is
> how will this be delivered to the CPU, and on what interrupt line ? The HT
> message sent to the CPC925 is the following:
> 
> MT = NMI
> TM = edge
> DM = physical
> INTRDEST = 'hFF (all)
> VECTOR = 'h00 (does not matter)
> 

The AMD8131/8130 can generate an NMI to the CPC925. There is an interrupt
controller resided in the CPC925. And you know the CPC925 is attached the
PowerPC PPC970FX. The interrupt controller collects and distributes system
interrupts from the PCI Express and HyperTransport blocks. So you should get the
map connection based on the system in detail. Often these information should be
defined in the corresponding dtc.

Best Regards
Tiejun

> Any help appreciated.
> 
> Thanks,
> Ben
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

RE: NMI and AMD8131/8111 on Maple board

[Benjamin Walsh]

> The AMD8131/8130 can generate an NMI to the CPC925. There is 
> an interrupt
> controller resided in the CPC925. And you know the CPC925 is 
> attached the
> PowerPC PPC970FX. The interrupt controller collects and 
> distributes system
> interrupts from the PCI Express and HyperTransport blocks. So 
> you should get the
> map connection based on the system in detail. Often these 
> information should be
> defined in the corresponding dtc.

The only DTS I have is the one I extracted from a running target. This is
part of the entry for the 8111:

        ht@0 {  
                ranges = <0x81000000 0x0 0x0 0x0 0xf4000000 0x0 0x400000
0x82000000 0x0 0x80000000 0x0 0x80000000 0x0 0x70000000>;
                reg = <0x0 0xf2000000 0x3000000>;
                device_type = "ht";
                bus-range = <0x0 0x5>;
                compatible = "u3-ht";
                interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
                interrupt-map = <
                        0x0900 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x1100 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x1900 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x2100 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x3000 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x3200 0x0 0x0 0x4 0x6103fa00 0x19 0x1
                        0x3300 0x0 0x0 0x0 0x6103fa00 0x00 0x1
                        0x3400 0x0 0x0 0x3 0x6103fa00 0xff 0x1
                        0x3500 0x0 0x0 0x2 0x6103fa00 0x17 0x1
                        0x3600 0x0 0x0 0x2 0x6103fa00 0x17 0x1
                        0x3700 0x0 0x0 0x0 0x6103fa00 0x00 0x1>;
                #address-cells = <0x3>;
                linux,phandle = <0x61043600>;
                name = "ht";
                #interrupt-cells = <0x1>;
                #size-cells = <0x2>; 

And this is the CPC925, with its interrupt controller:

        hostbridge@f8000000 {
                reg = <0xf8000000 0x1000000>;
                device_type = "memory-controller";
                compatible = "u3";
                #address-cells = <0x1>;
                linux,phandle = <0x61044000>;
                name = "hostbridge";
                #size-cells = <0x1>;

                dart@f8033000 {
                        reg = <0xf8033000 0x7000>;
                        device_type = "dart";
                        compatible = "u3-dart", "dart";
                        linux,phandle = <0x61045e00>;
                        name = "dart";
                };

                interrupt-controller@f8040000 {
                        reg = <0xf8040000 0x40000>;
                        device_type = "open-pic";
                        interrupt-controller;
                        compatible = "open-pic";
                        big-endian;
                        built-in;
                        #address-cells = <0x0>;
                        linux,phandle = <0x6103fa00>;
                        name = "interrupt-controller";
                        clock-frequency = <0x0>;
                        #interrupt-cells = <0x2>;
                };

And I think this is the part of the LPC bridge entry:

                isa@6 { 
                        min-grant = <0x0>;
                        ranges = <0x1 0x0 0x1003000 0x0 0x0 0x10000>;
                        reg = <0x3000 0x0 0x0 0x0 0x0>;
                        device_type = "isa";
                        revision-id = <0x5>;
                        66mhz-capable;
                        max-latency = <0x0>;
                        class-code = <0x60100>;
                        vendor-id = <0x1022>;
                        linux,phandle = <0x610dfa00>;
                        name = "isa";
                        device-id = <0x7468>;

The LPC bridge is supposed to be able to generate an NMI on error. Am I
right in saying that the 0x3000 entry in the ht@0 interrupt-map corresponds
to the LPC bridge ? If so, the mapping I can read from there is 0->0. 0 is
an internal interrupt of the CPC925, so this does not make sense. Or I am
reading this wrong.

Any insights ?

Thanks,
Ben

RE: USB Host support on mpc 8313

[Joaquin Luna]

That was exactly my problem.  You guys at freescale rock.

- Joaquin Luna

-----Original Message-----
From: Li Yang [mailto:LeoLi@freescale.com]=20
Sent: Monday, November 24, 2008 2:12 AM
To: Joaquin Luna; linuxppc-embedded@ozlabs.org
Subject: RE: USB Host support on mpc 8313

> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.org=20
> [mailto:linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.o
> rg] On Behalf Of Joaquin Luna
> Sent: Monday, November 24, 2008 11:24 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: USB Host support on mpc 8313
>=20
> Is there anyone out there who has tried getting usb to work=20
> under the 2.6.27 kernel?  I am using the Freescale MPC831x=20
> RDB platform and when I enable "Support for Freescale on-chip=20
> EHCI USB controller" (USB_EHCI_FSL) I get stuck during boot=20
> up.  The last two lines of my boot log are:
>=20
> =20
>=20
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
>=20
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
>=20
> =20
>=20
> =20
>=20
> With the 2.6.20 kernel I had usb working and my boot log looked like:
>=20
> =20
>=20
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
>=20
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
>=20
> fsl-ehci fsl-ehci.0: irq 38, io base 0xe0023000
>=20
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
>=20
> =20
>=20
> =20
>=20
> I did notice that there were a few usb bug fixes that went=20
> into 2.6.27.7 so I updated to the latest version, but it did=20
> not help.  Any idea how or where I can begin looking for a solution?


There are two settings of the board (USB internal PHY/ USB external
PHY).  They are described in the board UM.

Is the phy_type property in DTS matching the board setting?
utmi_wide for internal PHY
ulpi for external PHY

- Leo