Re: [microblaze-uclinux] uCLinux cannot allocate EMAClite interrupt

[Jean-Yves Ouellet <jouellet7@xxxxxxxxxxxx>]

John,

Thanks. uCLinux is now running on my microblaze.

However, when I issue the command microblaze-uclinux-gdb in RedHat 9.0, 
I always get the GDB command line mode. According to the Petalinux User 
Guide (Debugging User Applications), I should get the GDB GUI.

[jouellet@jy-compaq jouellet]$ microblaze-uclinux-gdb
GNU gdb 5.3Xilinx EDK 8.1.01 Build EDK_I.19.4
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu 
--target=microblaze-uclinux".
(gdb)


J-Y

John Williams wrote:
> Hi,
>
> Jean-Yves Ouellet wrote:
>
> > I can compile and boot uCLinux (without networking support) on 
> > MicroBlaze without Flash and EMAClite. However, if I add networking 
> > support to uCLinux and EMAClite to MicroBlaze, I get the following 
> > error:
>
> [snip]
>
> > Microblaze UARTlite serial driver version 1.00
> > ttyS0 at 0x40600000 (irq = 2) is a Microblaze UARTlite
>
> [snip]
>
> > eth0: using fifo mode.
> > eth0: No PHY detected.  Assuming a PHY at address 0.
> > eth0: Xilinx EMACLite #0 at 0x40E00000 mapped to 0x40E00000, irq=2
>
> [snip]
>
> eth0: Could not allocate interrupt 2.
>
> > It looks like interrupt 2 cannot be allocated to EMAClite because it 
> > is already allocated to UARTlite. But according to auto-config.in 
> > (see the attached file), interrupt 3 (instead of interrupt 2) should 
> > be allocated to UARTlite.
>
> After you copied the auto-config.in file across, you must do
>
> $ yes "" | make oldconfig
> $ make dep all
>
> The petalinux-copy-autoconfig script does this as part of its 
> operation - if you aren't using it you need to do it manually.
>
> In reality if you are changing the hardware like adding a new 
> peripheral, it's probably a good idea to do a "make linux-2.4.x_clean" 
> as well, to force a complete rebuild of the kernel.
>
> This should get things consistent again.
>
> Regards,
>
> John
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/