latest au1000 updates

latest au1000 updates

[Pete Popov]

James,

I pushed the latest au1000 code. I had to add a new vec0 handler for the au1000 
in head.S, much like the other vec0 ones. I also checked in the vr41xx patch. 
Jun indicated that he and/or Ralf reworked some of the 41xx so the 41xx will 
probably have to be updated again, but at least the kernel compiles.


To compile the code right at this moment, you need to make this local change in 
kernel/Makefile:

[ppopov@zeus linux-dev]$ diff ../stock/kernel/Makefile  kernel/Makefile
14c14
< obj-y     = sched.o dma.o fork.o exec_domain.o panic.o printk.o \
---
 > obj-y     = sched.o fork.o exec_domain.o panic.o printk.o \
17a18,21
 >
 > ifndef CONFIG_MIPS_AU1000
 > obj-y	 += dma.o
 > endif

and, this local change in drivers/net/Space.c:

diff ../stock/drivers/net/Space.c drivers/net/Space.c
103a104,105
 > extern int gt96100_probe(struct net_device *);
 > extern int au1000_probe(struct net_device *dev);
382a385,390
 > #endif
 > #ifdef CONFIG_MIPS_GT96100ETH
 > 	{gt96100_probe, 0},
 > #endif
 > #ifdef CONFIG_MIPS_AU1000_ENET
 > 	{au1000_probe, 0},


The Space.c patch really needs to go to Alan. I'll see if he'll take it. The 
kernel/Makefile patch probably needs to be reworked so that we don't have to 
touch kernel/Makefile.

I tested the kernel and it seems to work fine, so I think I got everything. 
However, I haven't tested the fb driver, pcmcia, usb, etc, etc with this kernel. 
Also, note that if anyone needs usb on this board or any other au1000 board, 
we'll need to send a local usb patch for non-pci devices. Steve already had most 
of his work accepted in the usb tree, but the non-pci patch wasn't accepted 
because the usb code is going through some reorg right now. So, without this usb 
patch which is only in the MontaVista tree at the moment, usb is not usable on 
this board.

There are Au1000 customers showing up all over the place, so having the latest 
code in sourceforge is a good thing.  Now I have to find the time to create a 
patch against the oss tree...

Pete

usb-problems with Au1000

[Wolfgang Heidrich]

Hello,

I have following configuration:

- mips-Au1000-processor (PB1000-board from Alchemy-Semiconductor)
-  _no_  USB-devices connected
- linux from the Montavista-Tree (downloaded in December from
     www.alchemysemi.com)(Kernel "2.4.2_hhl20") 
- prebuilt crosscompiler from Montavista (downloaded in December from
     www.alchemysemi.com)

During booting the kernel initalizes the usb-device-driver and 
a little later prints "USB device not accepting new address...":

>>>>
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-ohci.c: USB OHCI at membase 0xb0100000, IRQ 26
usb-ohci.c: usb-builtin, non-PCI OHCI
usb.c: new USB bus registered, assigned bus number 1
Product: USB OHCI Root Hub
SerialNumber: b0100000
hub.c: USB hub found
hub.c: 2 ports detected
usb-ohci.c: v5.2 Roman Weissgaerber <weissg@vienna.at>, David Brownell
usb-ohci.c: USB OHCI Host Controller Driver
usb.c: registered new driver hid
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 192.168.65.17, my address is
192.168.65.240
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Serial driver version 1.01 (2001-02-08) with no serial options enabled
ttyS00 at 0xb1100000 (irq = 0) is a 16550
ttyS01 at 0xb1200000 (irq = 1) is a 16550
ttyS02 at 0xb1300000 (irq = 2) is a 16550
ttyS03 at 0xb1400000 (irq = 3) is a 16550
Looking up port of RPC 100003/2 on 192.168.65.17
Looking up port of RPC 100005/2 on 192.168.65.17
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device not accepting new address=2 (error=-145)  
<---------????
VFS: Mounted root (nfs filesystem) readonly.
Freeing unused kernel memory: 64k freed
Algorithmics/MIPS FPU Emulator v1.5a
hub.c: USB new device connect on bus1/1, assigned device number 3
usb.c: USB device not accepting new address=3 (error=-145)
<---------????
<<<<

I wonder what I could have done wrong. The switches on the board
are set accordingly the Montavista-faq.txt. I could verify these
settings
with the schematics of the board.
After booting, when I plug in an USB-device, the same error messages
are repeated.

As far as I know USB should work with this kernel. So maybe this
is a hardware failure ? I reduced the CPU-frequency from 396MHz to
120MHz,
but this didn't help, too. The same messages appear, when I plug the
device
in the other USB-connector on the board. It's no problem with the power,
because I could verify that there are 5Volt on the USB-connector.

Probably someone already knows the solution, because this is not a
special
configuration.

Thanks in advance

-- 
Wolfgang

Re: usb-problems with Au1000

[Pete Popov]

On Thu, 2002-01-10 at 09:40, Wolfgang Heidrich wrote:
> Hello,
> 
> I have following configuration:
> 
> - mips-Au1000-processor (PB1000-board from Alchemy-Semiconductor)
> -  _no_  USB-devices connected
> - linux from the Montavista-Tree (downloaded in December from
>      www.alchemysemi.com)(Kernel "2.4.2_hhl20") 
> - prebuilt crosscompiler from Montavista (downloaded in December from
>      www.alchemysemi.com)
> 
> During booting the kernel initalizes the usb-device-driver and 
> a little later prints "USB device not accepting new address...":

Which LSP version do you have? Do an "rpm -qa | grep hhl- | grep lsp".

There was a hardware errata in the usb controller, but a software fix is
already in the kernel (assuming you have a late enough kernel).  Also,
the usb switches, S4, should be set to:

1-4 off
5-6 on
7-8 off

Pete
 
> >>>>
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-ohci.c: USB OHCI at membase 0xb0100000, IRQ 26
> usb-ohci.c: usb-builtin, non-PCI OHCI
> usb.c: new USB bus registered, assigned bus number 1
> Product: USB OHCI Root Hub
> SerialNumber: b0100000
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb-ohci.c: v5.2 Roman Weissgaerber <weissg@vienna.at>, David Brownell
> usb-ohci.c: USB OHCI Host Controller Driver
> usb.c: registered new driver hid
> mice: PS/2 mouse device common for all mice
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 4096 bind 4096)
> Sending BOOTP requests.... OK
> IP-Config: Got BOOTP answer from 192.168.65.17, my address is
> 192.168.65.240
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Serial driver version 1.01 (2001-02-08) with no serial options enabled
> ttyS00 at 0xb1100000 (irq = 0) is a 16550
> ttyS01 at 0xb1200000 (irq = 1) is a 16550
> ttyS02 at 0xb1300000 (irq = 2) is a 16550
> ttyS03 at 0xb1400000 (irq = 3) is a 16550
> Looking up port of RPC 100003/2 on 192.168.65.17
> Looking up port of RPC 100005/2 on 192.168.65.17
> hub.c: USB new device connect on bus1/1, assigned device number 2
> usb.c: USB device not accepting new address=2 (error=-145)  
> <---------????
> VFS: Mounted root (nfs filesystem) readonly.
> Freeing unused kernel memory: 64k freed
> Algorithmics/MIPS FPU Emulator v1.5a
> hub.c: USB new device connect on bus1/1, assigned device number 3
> usb.c: USB device not accepting new address=3 (error=-145)
> <---------????
> <<<<
> 
> I wonder what I could have done wrong. The switches on the board
> are set accordingly the Montavista-faq.txt. I could verify these
> settings
> with the schematics of the board.
> After booting, when I plug in an USB-device, the same error messages
> are repeated.
> 
> As far as I know USB should work with this kernel. So maybe this
> is a hardware failure ? I reduced the CPU-frequency from 396MHz to
> 120MHz,
> but this didn't help, too. The same messages appear, when I plug the
> device
> in the other USB-connector on the board. It's no problem with the power,
> because I could verify that there are 5Volt on the USB-connector.
> 
> Probably someone already knows the solution, because this is not a
> special
> configuration.
> 
> Thanks in advance
> 
> -- 
> Wolfgang

Re: usb-problems with Au1000

[Wolfgang Heidrich]

Hello Pete,

Pete Popov wrote:
> 
> On Thu, 2002-01-10 at 09:40, Wolfgang Heidrich wrote:
> > Hello,
> >

> > During booting the kernel initalizes the usb-device-driver and
> > a little later prints "USB device not accepting new address...":
> 
> Which LSP version do you have? Do an "rpm -qa | grep hhl- | grep lsp".

hhl-cross-mips_fp_le-lsp-mips-malta-2.4.2_hhl20-hhl2.0.2
hhl-cross-mips_fp_le-lsp-alchemy-pb1000-2.4.2_hhl20-hhl2.0.2

> 
> There was a hardware errata in the usb controller, but a software fix is
> already in the kernel (assuming you have a late enough kernel).  Also,
> the usb switches, S4, should be set to:
> 
> 1-4 off
> 5-6 on
> 7-8 off

I used these settings. But as far as I know these settings are only
relevant for the second USB.

Thanks in advance
-- 
Wolfgang

Re: usb-problems with Au1000

[Pete Popov]

On Thu, 2002-01-10 at 10:48, Wolfgang Heidrich wrote:
> Hello Pete,
> 
> Pete Popov wrote:
> > 
> > On Thu, 2002-01-10 at 09:40, Wolfgang Heidrich wrote:
> > > Hello,
> > >
> 
> > > During booting the kernel initalizes the usb-device-driver and
> > > a little later prints "USB device not accepting new address...":
> > 
> > Which LSP version do you have? Do an "rpm -qa | grep hhl- | grep lsp".
> 
> hhl-cross-mips_fp_le-lsp-mips-malta-2.4.2_hhl20-hhl2.0.2
> hhl-cross-mips_fp_le-lsp-alchemy-pb1000-2.4.2_hhl20-hhl2.0.2
 
That LSP is old.  Get the _hhl20_hhl2.0.3 release. Alchemy should have
it on their ftp site by now.  Let me know if you still have problems
with 2.0.3.

Pete
 
> > There was a hardware errata in the usb controller, but a software fix is
> > already in the kernel (assuming you have a late enough kernel).  Also,
> > the usb switches, S4, should be set to:
> > 
> > 1-4 off
> > 5-6 on
> > 7-8 off
> 
> I used these settings. But as far as I know these settings are only
> relevant for the second USB.
> 
> Thanks in advance
> -- 
> Wolfgang

Re: usb-problems with Au1000

[Kunihiko IMAI]

Hi,

I'm trying SGI version of kernel-2.2.17.
And I get same message,

At Thu, 10 Jan 2002 18:40:24 +0100,
Wolfgang Heidrich wrote:

> hub.c: USB new device connect on bus1/1, assigned device number 3
> usb.c: USB device not accepting new address=3 (error=-145)

when connect some device.


I checked in some cases:

- Some devices are recognized, some are not.
	A joystick device (sanwa supply) works fine.
	A mouse device (century corp.) works too.
	But another mouse (Logitech Mini Wheel Mouse) doesn't work and
		I got message like above.

- When connected via USB hub device, Logitech mouse works fine.

I think USB root HUB doesn't work properly.


By the way:

today, I got a errata document from the chip dealer.  This document
reports some USB errata.
I read the report and source code, then  I found a bug in
arch/mips/au1000/pb1000/setup.c.


The errata report says workaround method:
- set the CPU clock is 384MHz
- set the source of USB host controller is CPU clcck.

And the code:

        /*
         * Setup 48MHz FREQ2 from CPUPLL for USB Host
         */
        /* FRDIV2=3 -> div by 8 of 384MHz -> 48MHz */
        sys_freqctrl |= ((3<<22) | (1<<21) | (0<<20));
        outl(sys_freqctrl, FQ_CNTRL_1);

Comment says "Setup FREQ2" but the code set FREQ5.

        outl(sys_freqctrl, FQ_CNTRL_1);

should be 

        outl(sys_freqctrl, FQ_CNTRL_0);

Also formar line:

	sys_freqctrl = inl(FQ_CNTRL_1);

should be

	sys_freqctrl = inl(FQ_CNTRL_0);


Thanks.
_._. __._  _ . ... _  .___ ._. _____ _... ._ _._ _.._. .____  _ . ... _

                                                          Kunihiko IMAI

Re: usb-problems with Au1000

[Pete Popov]

On Thu, 2002-01-17 at 02:36, Kunihiko IMAI wrote:
> Hi,
> 
> I'm trying SGI version of kernel-2.2.17.
> And I get same message,
> 
> At Thu, 10 Jan 2002 18:40:24 +0100,
> Wolfgang Heidrich wrote:
> 
> > hub.c: USB new device connect on bus1/1, assigned device number 3
> > usb.c: USB device not accepting new address=3 (error=-145)

I'm surprised the sgi kernel works with usb at all.  We did a patch for
non-pci usb devices which was not accepted by the usb project at that
time because they were working on a different solution.
 
> when connect some device.
> 
> 
> I checked in some cases:
> 
> - Some devices are recognized, some are not.
> 	A joystick device (sanwa supply) works fine.
> 	A mouse device (century corp.) works too.
> 	But another mouse (Logitech Mini Wheel Mouse) doesn't work and
> 		I got message like above.
> 
> - When connected via USB hub device, Logitech mouse works fine.
> 
> I think USB root HUB doesn't work properly. 
 
> By the way:
> 
> today, I got a errata document from the chip dealer.  This document
> reports some USB errata.
> I read the report and source code, then  I found a bug in
> arch/mips/au1000/pb1000/setup.c.
> 
> 
> The errata report says workaround method:
> - set the CPU clock is 384MHz
> - set the source of USB host controller is CPU clcck.
> 
> And the code:
> 
>         /*
>          * Setup 48MHz FREQ2 from CPUPLL for USB Host
>          */
>         /* FRDIV2=3 -> div by 8 of 384MHz -> 48MHz */
>         sys_freqctrl |= ((3<<22) | (1<<21) | (0<<20));
>         outl(sys_freqctrl, FQ_CNTRL_1);
> 
> Comment says "Setup FREQ2" but the code set FREQ5.

It's the comment that's wrong, not the code. The code works and has been
tested.  Alchemy makes available the Linux Support Package (LSP) which
we did. That kernel has been tested with all peripherals so I would
recommend that you get that from them.  Also,make sure your jumpers are
setup correctly (S4).

I do have a better USB workaround which checks the CPU silicon rev, but
I haven't had time to send Ralf an updated patch. The current setup.c
should work though.  Get the latest LSP from Alchemy, check the S4
jumpers (1-4 off, 5-6 on, 7-8 off), and let me know if it still doesn't
work for you.

Pete

Re: usb-problems with Au1000

[Kunihiko IMAI]

Hi,

At 17 Jan 2002 11:02:03 -0800,
Pete Popov wrote:
> 
> On Thu, 2002-01-17 at 02:36, Kunihiko IMAI wrote:
> > Hi,
> > 
> > I'm trying SGI version of kernel-2.2.17.
> > And I get same message,
> > 
> > At Thu, 10 Jan 2002 18:40:24 +0100,
> > Wolfgang Heidrich wrote:
> > 
> > > hub.c: USB new device connect on bus1/1, assigned device number 3
> > > usb.c: USB device not accepting new address=3 (error=-145)
> 
> I'm surprised the sgi kernel works with usb at all.  We did a patch for
> non-pci usb devices which was not accepted by the usb project at that
> time because they were working on a different solution.

Of course, I patched usb-ohci code with memory mapped I/O support.
It is very ugly code, so Linux USB stuff will not accept, I think.

About two years ago, I ported USB OHCI to StrongARM SA1111 CPU and
SA1111 companion chip.  At that time, I suggested to the author of
usb-ohci.c that it should be better to support of memory mapped I/O
device, but it was not accepted.  On StrongARM, it has DMA memory
coherency problem, too. (Au1000 has bus snoop function, so this is not
a problem.)

> > The errata report says workaround method:
> > - set the CPU clock is 384MHz
> > - set the source of USB host controller is CPU clcck.
> > 
> > And the code:
> > 
> >         /*
> >          * Setup 48MHz FREQ2 from CPUPLL for USB Host
> >          */
> >         /* FRDIV2=3 -> div by 8 of 384MHz -> 48MHz */
> >         sys_freqctrl |= ((3<<22) | (1<<21) | (0<<20));
> >         outl(sys_freqctrl, FQ_CNTRL_1);
> > 
> > Comment says "Setup FREQ2" but the code set FREQ5.
> 
> It's the comment that's wrong, not the code. The code works and has been
> tested.  Alchemy makes available the Linux Support Package (LSP) which
> we did. That kernel has been tested with all peripherals so I would
> recommend that you get that from them.  Also,make sure your jumpers are
> setup correctly (S4).

In the source code:

	sys_clksrc |= ((4<<12) | (0<<11) | (0<<10));

	(snip...)

	outl(sys_clksrc, CLOCK_SOURCE_CNTRL);

This code sets the clock source of USB host controller is FREQ2.  So
FREQ5 clock source doesn't affect to USB host controller.


And I found HHL version of kernel source code in Pb1000 CD-ROM.  I'll
read it.


> I do have a better USB workaround which checks the CPU silicon rev, but
> I haven't had time to send Ralf an updated patch. The current setup.c
> should work though.  Get the latest LSP from Alchemy, check the S4
> jumpers (1-4 off, 5-6 on, 7-8 off), and let me know if it still doesn't
> work for you.

OK.  I checked S4 DIP SW, it was setted same config.
# Pb1000 documentation doesn't clearly explain at this configration.
# So I looked schematics of Pb1000.

This switch affects only J24 connector setting.  J2 connector is not
affected by S4.

Thanks.
_._. __._  _ . ... _  .___ ._. _____ _... ._ _._ _.._. .____  _ . ... _

                                                          Kunihiko IMAI

Re: usb-problems with Au1000

[Pete Popov]

> Of course, I patched usb-ohci code with memory mapped I/O support.
> It is very ugly code, so Linux USB stuff will not accept, I think.

I think the work we did was clean, but it wasn't accepted anyway.
Although, Steve L.'s initial work on mips usb did get accepted and that
gave us usb on the it8172 system controller.
 
> About two years ago, I ported USB OHCI to StrongARM SA1111 CPU and
> SA1111 companion chip.  At that time, I suggested to the author of
> usb-ohci.c that it should be better to support of memory mapped I/O
> device, but it was not accepted.  On StrongARM, it has DMA memory
> coherency problem, too. (Au1000 has bus snoop function, so this is not
> a problem.)
> 
> > > The errata report says workaround method:
> > > - set the CPU clock is 384MHz
> > > - set the source of USB host controller is CPU clcck.
> > > 
> > > And the code:
> > > 
> > >         /*
> > >          * Setup 48MHz FREQ2 from CPUPLL for USB Host
> > >          */
> > >         /* FRDIV2=3 -> div by 8 of 384MHz -> 48MHz */
> > >         sys_freqctrl |= ((3<<22) | (1<<21) | (0<<20));
> > >         outl(sys_freqctrl, FQ_CNTRL_1);
> > > 
> > > Comment says "Setup FREQ2" but the code set FREQ5.
> > 
> > It's the comment that's wrong, not the code. The code works and has been
> > tested.  Alchemy makes available the Linux Support Package (LSP) which
> > we did. That kernel has been tested with all peripherals so I would
> > recommend that you get that from them.  Also,make sure your jumpers are
> > setup correctly (S4).
> 
> In the source code:
> 
> 	sys_clksrc |= ((4<<12) | (0<<11) | (0<<10));
> 
> 	(snip...)
> 
> 	outl(sys_clksrc, CLOCK_SOURCE_CNTRL);
> 
> This code sets the clock source of USB host controller is FREQ2.  So
> FREQ5 clock source doesn't affect to USB host controller.
 
I'll take a look at it, thanks.

 
> And I found HHL version of kernel source code in Pb1000 CD-ROM.  I'll
> read it.

I don't think you have the latest CDROM. That one you have probably has
an older version of the LSP.
 
> 
> > I do have a better USB workaround which checks the CPU silicon rev, but
> > I haven't had time to send Ralf an updated patch. The current setup.c
> > should work though.  Get the latest LSP from Alchemy, check the S4
> > jumpers (1-4 off, 5-6 on, 7-8 off), and let me know if it still doesn't
> > work for you.
> 
> OK.  I checked S4 DIP SW, it was setted same config.
> # Pb1000 documentation doesn't clearly explain at this configration.
> # So I looked schematics of Pb1000.
> 
> This switch affects only J24 connector setting.  J2 connector is not
> affected by S4.

The CDROM you have is most definitely old and might not have the latest
usb code.  Try the latest LSP from Alchemy. The rpms should have
"hhl2.0.3" or later in the string.

Pete

Re: usb-problems with Au1000

[Pete Popov]

> > It's the comment that's wrong, not the code. The code works and has been
> > tested.  Alchemy makes available the Linux Support Package (LSP) which
> > we did. That kernel has been tested with all peripherals so I would
> > recommend that you get that from them.  Also,make sure your jumpers are
> > setup correctly (S4).
> 
> In the source code:
> 
> 	sys_clksrc |= ((4<<12) | (0<<11) | (0<<10));
> 
> 	(snip...)
> 
> 	outl(sys_clksrc, CLOCK_SOURCE_CNTRL);
> 
> This code sets the clock source of USB host controller is FREQ2.  So
> FREQ5 clock source doesn't affect to USB host controller.

After looking into it, both the comment and code are correct. From
include/asm-mips/au1000.h:

#define FQ_CNTRL_1                0xB1900020
#define FQ_CNTRL_2                0xB1900024

So FQ_CNTRL_1 corresponds to what is now sys_freqctrl0. In other words,
the update to the databook has not been incorporated into the Au1000
files. The names of the registers were updated after I had done all the
core work. I need to update the code so the names of the registers
correspond to the latest Au1000 manual.

Since the boards we have do work with USB and there were some usb
hardware glitches, please check with Alchemy on what the problem might
be with your board. 

Pete

Re: usb-problems with Au1000

[Kunihiko IMAI]

Hi,

At 18 Jan 2002 11:49:09 -0800,
Pete Popov wrote:
> 
> 
> > > It's the comment that's wrong, not the code. The code works and has been
> > > tested.  Alchemy makes available the Linux Support Package (LSP) which
> > > we did. That kernel has been tested with all peripherals so I would
> > > recommend that you get that from them.  Also,make sure your jumpers are
> > > setup correctly (S4).
> > 
> > In the source code:
> > 
> > 	sys_clksrc |= ((4<<12) | (0<<11) | (0<<10));
> > 
> > 	(snip...)
> > 
> > 	outl(sys_clksrc, CLOCK_SOURCE_CNTRL);
> > 
> > This code sets the clock source of USB host controller is FREQ2.  So
> > FREQ5 clock source doesn't affect to USB host controller.
> 
> After looking into it, both the comment and code are correct. From
> include/asm-mips/au1000.h:
> 
> #define FQ_CNTRL_1                0xB1900020
> #define FQ_CNTRL_2                0xB1900024
> 
> So FQ_CNTRL_1 corresponds to what is now sys_freqctrl0. In other words,
> the update to the databook has not been incorporated into the Au1000
> files. The names of the registers were updated after I had done all the
> core work. I need to update the code so the names of the registers
> correspond to the latest Au1000 manual.

Oh, I see.  I'm sorry for my misunderstanding.

Now the relations are like this:

Au1000 manual	Linux Header
-----------------------------------
sys_freqctl0	FQ_CNTRL_1
sys_freqctl1	FQ_CNTRL_2
-----------------------------------

Then it's correct setup.

Thanks.
_._. __._  _ . ... _  .___ ._. _____ _... ._ _._ _.._. .____  _ . ... _

                                                          Kunihiko IMAI

Re: usb-problems with Au1000

[Wolfgang Heidrich]

(I just repeat my last message with corrected subject)

Hi Bob,

>Hi Wolfgang,
>Have you been successful in getting the latest files?
>Thanks,
>Bob

Yes, thank you very much, now I really have Beta6 and Beta5.
But USB still doesn't work, I still get the message
"usb.c: USB device not accepting new address=3 (error=-145)"
everytime I plug in a USB device in J2. The same happens with J24.

Only one thing changed (look my Email in the newsgroup from January 10):
With Beta4-Version I always was getting the message
>>>
hub.c: USB new device connect on bus1/1, assigned device number 3
usb.c: USB device not accepting new address=3 (error=-145)
<<<
already during booting of the kernel, although there were no USB 
devices connected.
But with Beta6-Version I just get it when plugging in a device after
booting:
>>>
usb.c: USB device not accepting new address=2 (error=-145)
usb.c: USB device not accepting new address=3 (error=-145)
<<<

The version of the LSP is now
hhl-cross-mips_fp_le-lsp-alchemy-pb1000-2.4.2_hhl20-mb011105.2

The Pb1000 Board Serial Number is 5070.
Maybe you can tell me that the reason is just a buggy Au1000,
and perhaps USB is going to work, when we get our own Au1000-boards
with newer versions of the Au1000.

Thanks in advance

-- 
Wolfgang

Re: usb-problems with Au1000

[Pete Popov]

On Tue, 2002-01-22 at 01:56, Kunihiko IMAI wrote:
> Hi,
> 
> At 18 Jan 2002 11:49:09 -0800,
> Pete Popov wrote:
> > 
> > 
> > > > It's the comment that's wrong, not the code. The code works and has been
> > > > tested.  Alchemy makes available the Linux Support Package (LSP) which
> > > > we did. That kernel has been tested with all peripherals so I would
> > > > recommend that you get that from them.  Also,make sure your jumpers are
> > > > setup correctly (S4).
> > > 
> > > In the source code:
> > > 
> > > 	sys_clksrc |= ((4<<12) | (0<<11) | (0<<10));
> > > 
> > > 	(snip...)
> > > 
> > > 	outl(sys_clksrc, CLOCK_SOURCE_CNTRL);
> > > 
> > > This code sets the clock source of USB host controller is FREQ2.  So
> > > FREQ5 clock source doesn't affect to USB host controller.
> > 
> > After looking into it, both the comment and code are correct. From
> > include/asm-mips/au1000.h:
> > 
> > #define FQ_CNTRL_1                0xB1900020
> > #define FQ_CNTRL_2                0xB1900024
> > 
> > So FQ_CNTRL_1 corresponds to what is now sys_freqctrl0. In other words,
> > the update to the databook has not been incorporated into the Au1000
> > files. The names of the registers were updated after I had done all the
> > core work. I need to update the code so the names of the registers
> > correspond to the latest Au1000 manual.
> 
> Oh, I see.  I'm sorry for my misunderstanding.

It's OK, one of these days I'll have time to rename all the registers to
match the last data book.

Pete
 
> Now the relations are like this:
> 
> Au1000 manual	Linux Header
> -----------------------------------
> sys_freqctl0	FQ_CNTRL_1
> sys_freqctl1	FQ_CNTRL_2
> -----------------------------------