STK5200 pci_enable_device problem

STK5200 pci_enable_device problem

[Mustafa Cayır]

Hi all,

I am working on TQ STK52000 development board with TQM5200-AB cpu =
module. I am trying to use PCI bus and Local Plus Bus together. SM501, =
video chip is located on local plus bus and PLX9030 based pci device is =
on pci bus.

My pci driver is able to scan pci bus and find succesfully the pci =
device. After this point, pci_enable_device function returns following =
error:

PCI:  Device 00:18.0 not available because of resource collisions

Any help is appreciated.

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Hi Mustafa,

> Hi all,
> 
[...]
> 
> My pci driver is able to scan pci bus and find succesfully the pci
> device. After this point, pci_enable_device function returns
> following error:
> 
> PCI:  Device 00:18.0 not available because of resource collisions
> 

Which ELDK and kernel do you use? I had the same problem on this board 
with a PLX9054 based PCI card on a 2.4.25 kernel. I switched to the 2.6 
kernel and the 4.1 ELDK and the card was scanned correctly.
But keep in mind that the linux PLX drivers do not work out of the box 
with a big endian platform like the MPC5200. Although there is a 
BIG_ENDIAN flag in the makefiles there are still some places left in the 
driver code which have to be patched (the parts with int64 adresses).
It's not so easy to compile the PLX drivers on the 4.1 ELDK because of 
missing headers in the ppc architecture. I managed to build the drivers 
for the 2.6.19 kernel and I was able to work with the card except the 
DMA routines (still working on this issue).

Hope this helps. Bye,

-- 
Dipl. Ing. Oliver Rutsch

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <7B9A8FF57DBB524190E98CABF6E56F078FAE4E@itri.bte.mam.gov.tr> you wrote:
> 
> I am working on TQ STK52000 development board with TQM5200-AB cpu module. I am trying to use PCI bus and Local Plus Bus together. SM501, video chip is located on local plus bus and PLX9030 based pci device is on pci bus.
> 
> My pci driver is able to scan pci bus and find succesfully the pci device. After this point, pci_enable_device function returns following error:
> 
> PCI:  Device 00:18.0 not available because of resource collisions

Did you try the linux-2.6-denx repo on our server? Note  that  you'll
need a somewhat recent version of U-Boot for device tree support.

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
PLEASE NOTE: Some Quantum Physics Theories Suggest That When the Con-
sumer Is Not Directly Observing This Product, It May Cease  to  Exist
or Will Exist Only in a Vague and Undetermined State.

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <46CD3618.70801@sympatec.com> you wrote:
>
> Which ELDK and kernel do you use? I had the same problem on this board 
> with a PLX9054 based PCI card on a 2.4.25 kernel. I switched to the 2.6 
> kernel and the 4.1 ELDK and the card was scanned correctly.
> But keep in mind that the linux PLX drivers do not work out of the box 
> with a big endian platform like the MPC5200. Although there is a 
> BIG_ENDIAN flag in the makefiles there are still some places left in the 
> driver code which have to be patched (the parts with int64 adresses).
> It's not so easy to compile the PLX drivers on the 4.1 ELDK because of 
> missing headers in the ppc architecture. I managed to build the drivers 
> for the 2.6.19 kernel and I was able to work with the card except the 
> DMA routines (still working on this issue).

WHy don't you use the arch/powerpc configuration, then? Note that the
STK5200 has never been supported in a  2.6  kernel  with  a  arch/ppc
configuration.

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
"When the only  tool  you  have  is  a  hammer,  you  tend  to  treat
everything as if it were a nail."                    - Abraham Maslow

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Hi,

[...]

 >> It's not so easy to compile the PLX drivers on the 4.1 ELDK because of
 >> missing headers in the ppc architecture. I managed to build the drivers
 >> for the 2.6.19 kernel and I was able to work with the card except the
 >> DMA routines (still working on this issue).
 >
 > WHy don't you use the arch/powerpc configuration, then? Note that the
 > STK5200 has never been supported in a  2.6  kernel  with  a  arch/ppc
 > configuration.
 >

Because I found at least a lite5200 configuration in the 4.1 ELDK 
(2.6.19.2 kernel) in the ARCH/ppc architecure. With ARCH/powerpc I only 
had a few configurations for other modules and I wasn't able to build a 
running kernel for the TQM5200 (maybe my fault).
Is there support for the TQM5200 and the STK5200 with ARCH/powerpc in 
newer kernels? I'm still using the 3.1.1 ELDK for the TQM5200 as it have 
everything I need and I don't need to use the PLX card in this board 
(although it would have been nice if I got it working...).

Bye,

-- 
Dipl. Ing. Oliver Rutsch

RE: STK5200 pci_enable_device problem

[Mustafa Cayir]

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

Hi ,
i use 2.4.25 kernel and eldk 3.1.1 on TQM5200 board. i tried denx 2.6.19 kernel to port on TQM5200 but i couldn't.
Did you port 2.6 kernel on TQM5200? Did pci device start working succesfully after porting 2.6 kernel to TQM5200 board.





-----Original Message-----
From: linuxppc-embedded-bounces+mustafa.cayir=bte.mam.gov.tr@ozlabs.org on behalf of Oliver Rutsch
Sent: Thu 8/23/2007 10:24 AM
To: linuxppc-embedded@ozlabs.org
Subject: Re: STK5200 pci_enable_device problem
 
Hi Mustafa,

> Hi all,
> 
[...]
> 
> My pci driver is able to scan pci bus and find succesfully the pci
> device. After this point, pci_enable_device function returns
> following error:
> 
> PCI:  Device 00:18.0 not available because of resource collisions
> 

Which ELDK and kernel do you use? I had the same problem on this board 
with a PLX9054 based PCI card on a 2.4.25 kernel. I switched to the 2.6 
kernel and the 4.1 ELDK and the card was scanned correctly.
But keep in mind that the linux PLX drivers do not work out of the box 
with a big endian platform like the MPC5200. Although there is a 
BIG_ENDIAN flag in the makefiles there are still some places left in the 
driver code which have to be patched (the parts with int64 adresses).
It's not so easy to compile the PLX drivers on the 4.1 ELDK because of 
missing headers in the ppc architecture. I managed to build the drivers 
for the 2.6.19 kernel and I was able to work with the card except the 
DMA routines (still working on this issue).

Hope this helps. Bye,

-- 
Dipl. Ing. Oliver Rutsch
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


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

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <46D26E3F.8040309@sympatec.com> you wrote:
> 
>  >> It's not so easy to compile the PLX drivers on the 4.1 ELDK because of
>  >> missing headers in the ppc architecture. I managed to build the drivers
>  >> for the 2.6.19 kernel and I was able to work with the card except the
>  >> DMA routines (still working on this issue).
>  >
>  > WHy don't you use the arch/powerpc configuration, then? Note that the
>  > STK5200 has never been supported in a  2.6  kernel  with  a  arch/ppc
>  > configuration.
>  >
> 
> Because I found at least a lite5200 configuration in the 4.1 ELDK 
> (2.6.19.2 kernel) in the ARCH/ppc architecure. With ARCH/powerpc I only 

You will find many completely unsupported board configurations in the
kernel.org tree, too. The fact that somethign  is  present  does  not
mean anything.

> Is there support for the TQM5200 and the STK5200 with ARCH/powerpc in 
> newer kernels? I'm still using the 3.1.1 ELDK for the TQM5200 as it have 
> everything I need and I don't need to use the PLX card in this board 
> (although it would have been nice if I got it working...).

The TQM5200 / STK5200 are supported in our linux-2.6-denx  tree  with
an  arch/powerpc  configuration; also lite5200b. Note that - like all
MPC5200 support in the 2.6 kernel - this is all work in progress.

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
It is dangerous to be right on a subject  on  which  the  established
authorities are wrong.                                    -- Voltaire

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <7B9A8FF57DBB524190E98CABF6E56F070B927E@itri.bte.mam.gov.tr> you wrote:
> 
> i use 2.4.25 kernel and eldk 3.1.1 on TQM5200 board. i tried denx 2.6.19
> kernel to port on TQM5200 but i couldn't.
> Did you port 2.6 kernel on TQM5200? Did pci device start working
> succesfully after porting 2.6 kernel to TQM5200 board.

Current top-of-tree in our git repo has been tested with a Intel
EEPRO100 network card in the ST5200's PCI slot. It's working.

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
Unsichtbar macht sich die Dummheit, indem sie immer  größere  Ausmaße
annimmt.                             -- Bertold Brecht: Der Tui-Roman

RE: STK5200 pci_enable_device problem

[Mustafa Cayir]

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

Hi,

i build Linux-2.6.22-gbcfc8d37 kernel lastest kernel from denx git for the board (STK5200 with TQM5200-AB).
ELDK 4.1 version is used.

make mrproper
export ARCH=powerpc
make tqm5200_defconfig
make uImage

It hangs on after  following line
  Uncompressing Kernel Image ... OK

Our u-boot version : U-Boot 1.1.3 (Apr  7 2005 - 14:42:37)

Any idea will be appreciated.

Regards.

done
Bytes transferred = 1454056 (162fe8 hex)
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.22-gbcfc8d37
   Created:      2007-08-28  19:41:27 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1453992 Bytes =  1.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK




-----Original Message-----
From: Wolfgang Denk [mailto:wd@denx.de]
Sent: Mon 8/27/2007 10:14 PM
To: Mustafa Cayir
Cc: Oliver Rutsch; linuxppc-embedded@ozlabs.org
Subject: Re: STK5200 pci_enable_device problem
 
In message <7B9A8FF57DBB524190E98CABF6E56F070B927E@itri.bte.mam.gov.tr> you wrote:
> 
> i use 2.4.25 kernel and eldk 3.1.1 on TQM5200 board. i tried denx 2.6.19
> kernel to port on TQM5200 but i couldn't.
> Did you port 2.6 kernel on TQM5200? Did pci device start working
> succesfully after porting 2.6 kernel to TQM5200 board.

Current top-of-tree in our git repo has been tested with a Intel
EEPRO100 network card in the ST5200's PCI slot. It's working.

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
Unsichtbar macht sich die Dummheit, indem sie immer  größere  Ausmaße
annimmt.                             -- Bertold Brecht: Der Tui-Roman


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

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Hi Mustafa,

> Hi,
> 
> i build Linux-2.6.22-gbcfc8d37 kernel lastest kernel from denx git for 
> the board (STK5200 with TQM5200-AB).
> ELDK 4.1 version is used.
> 
> make mrproper
> export ARCH=powerpc
> make tqm5200_defconfig
> make uImage
> 
> It hangs on after  following line
>   Uncompressing Kernel Image ... OK
> 

I encountered exactly the same problem. Using U-Boot 1.2 with Kernel 
Linux-2.6.22-gef92f1d7 and a TQM5200S-BD module on the STK52000. I tried 
to modify some kernel settings but it always stopped booting at the 
"Uncompressing Kernel Image ... OK" line.

Bye,
-- 
Dipl. Ing. Oliver Rutsch

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <46D50C0B.80402@sympatec.com> you wrote:
> 
> > i build Linux-2.6.22-gbcfc8d37 kernel lastest kernel from denx git for 
> > the board (STK5200 with TQM5200-AB).
> > ELDK 4.1 version is used.
> > 
> > make mrproper
> > export ARCH=powerpc
> > make tqm5200_defconfig
> > make uImage
> > 
> > It hangs on after  following line
> >   Uncompressing Kernel Image ... OK

Probably it does not hang, but you just don't see any console output.
Eventually  you  just  forgot  to  set  the  correct  console  device
(/dev/ttyPSC0) or console speed.

Also, you need a recent version of U-Boot (for  example  99c2fdab  or
later).

Try something like this:

=> tftp 200000 /tftpboot/tqm5200/uImage
=> tftp 400000 /tftpboot/tqm5200/tqm5200.dtb
=> setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.1:/opt/eldk/ppc_6xx ip=192.168.160.4:192.168.1.1:::tqm5200:eth0:off console=ttyPSC0,115200
=> bootm 200000 - 400000
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.22-gab27a987
   Created:      2007-08-05   8:24:43 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1454249 Bytes =  1.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using flat device tree at 0x400000
Using tqm5200 machine description
Linux version 2.6.22-gab27a987 (wd@pollux.denx.de) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #1 Sun Aug 5 10:24:37 MEST 2007
Zone PFN ranges:
  DMA             0 ->    16384
  Normal      16384 ->    16384
early_node_map[1] active PFN ranges
    0:        0 ->    16384
Built 1 zonelists.  Total pages: 16256
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.1:/opt/eldk/ppc_6xx ip=192.168.160.4:192.168.1.1:::tqm5200:eth0:off panic=1 console=ttyPSC0,115200
MPC52xx PIC is up and running!
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 61704k/65536k available (2872k kernel code, 3772k reserved, 132k data, 142k bss, 156k init)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
MPC52xx BestComm inited
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
...

etc.


> I encountered exactly the same problem. Using U-Boot 1.2 with Kernel 
> Linux-2.6.22-gef92f1d7 and a TQM5200S-BD module on the STK52000. I tried 
> to modify some kernel settings but it always stopped booting at the 
> "Uncompressing Kernel Image ... OK" line.

Please note that the device tree we have at the  moment  is  for  the
TQM5200 only and does not include support for the TQM5200S.

But probably you just had the same problem - missing or  bad  console
device specification.

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
That's their goal, remember, a goal that's really contrary to that of
the programmer or administrator. We just want to get our  jobs  done.
$Bill  just  wants  to  become  $$Bill. These aren't even marginallly
congruent.
         -- Tom Christiansen in <6jhtqk$qls$1@csnews.cs.colorado.edu>

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Hi,


> 
> Probably it does not hang, but you just don't see any console output.
> Eventually  you  just  forgot  to  set  the  correct  console  device
> (/dev/ttyPSC0) or console speed.

I checked this. I think the TQM5200 is really hanging after the ...OK 
because I have activated the telnet server and normally I'm able to 
connect to the device after booting via ethernet. No ping, no telnet. 
With an older 2.6.19.2 kernel this was O.K.

> 
> Also, you need a recent version of U-Boot (for  example  99c2fdab  or
> later).

I'm using U-Boot 1.2.0-gbc2b9c33-dirty (Feb 22 2007 - 09:53:14). Is that 
recent enough? (I don't know exactly what you mean with "99c2fdab", is 
this the second number after "1.2.0-"?)
> 
> Try something like this:
> 
> => tftp 200000 /tftpboot/tqm5200/uImage
> => tftp 400000 /tftpboot/tqm5200/tqm5200.dtb

Maybe the problem is the missing tqm5200.dtb file. I have booted the 
kernel without it (just bootm 200000). Does the kernel need this file? I 
found a tqm5200.dts file the the kernel sources, but the device tree 
compiler (dtc) seems not to be in the 4.1 ELDK. Do I have to install 
this compiler and build the appropriate dtb file?


> 
> Please note that the device tree we have at the  moment  is  for  the
> TQM5200 only and does not include support for the TQM5200S.
> 
> But probably you just had the same problem - missing or  bad  console
> device specification.
> 

In older kernels it was O.K. just to uncheck the SM501 drivers in the 
kernel configuration. Has this changed?

Thanks and bye,

-- 
Dipl. Ing. Oliver Rutsch

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <46D56C25.3020702@sympatec.com> you wrote:
> 
> > Also, you need a recent version of U-Boot (for  example  99c2fdab  or
> > later).
> 
> I'm using U-Boot 1.2.0-gbc2b9c33-dirty (Feb 22 2007 - 09:53:14). Is that 
> recent enough? (I don't know exactly what you mean with "99c2fdab", is 
> this the second number after "1.2.0-"?)

No, that is *way* too old.

The number after the "-g" is the (initial 8 digits of the) git commit
ID. You can use this to identify  a  spoecific  version  in  the  git
repository.

> Maybe the problem is the missing tqm5200.dtb file. I have booted the 
> kernel without it (just bootm 200000). Does the kernel need this file? I 

Yes. An arch/powerpc kernel will not run without a proper device tree.

> found a tqm5200.dts file the the kernel sources, but the device tree 
> compiler (dtc) seems not to be in the 4.1 ELDK. Do I have to install 
> this compiler and build the appropriate dtb file?

Yes, this is correct. dtc will be included with ELDK 4.2.

> In older kernels it was O.K. just to uncheck the SM501 drivers in the 
> kernel configuration. Has this changed?

As mentioned above, with arch/powerpc you always need a  device  tree
blob.

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
I express preference for a chronological  sequence  of  events  which
precludes a violence.   - Terry Pratchett, _The Dark Side of the Sun_

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Hi again,

> 
> As mentioned above, with arch/powerpc you always need a  device  tree
> blob.
> 
> Best regards,
> 
> Wolfgang Denk
> 

Thanks, Wolfang, now it's booting fine!
I've updated u-boot to the newest git version, builded the device tree 
file and now everything's working.

Bye,

-- 
Dipl. Ing. Oliver Rutsch

RE: STK5200 pci_enable_device problem

[Mustafa Cayir]

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

Hello Oliver,

My problems continue, could you summarize your steps to bring up the board?
which u-boot version is used?
how build tqm5200.dts file?
did you test pci bus?

Thanks.


-----Original Message-----
From: linuxppc-embedded-bounces+mustafa.cayir=bte.mam.gov.tr@ozlabs.org on behalf of Oliver Rutsch
Sent: Thu 8/30/2007 12:19 PM
To: linuxppc-embedded@ozlabs.org
Subject: Re: STK5200 pci_enable_device problem
 
Hi again,

> 
> As mentioned above, with arch/powerpc you always need a  device  tree
> blob.
> 
> Best regards,
> 
> Wolfgang Denk
> 

Thanks, Wolfang, now it's booting fine!
I've updated u-boot to the newest git version, builded the device tree 
file and now everything's working.

Bye,

-- 
Dipl. Ing. Oliver Rutsch
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


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

Re: STK5200 pci_enable_device problem

[Wolfgang Denk]

In message <46D68BA6.4020102@sympatec.com> you wrote:
> 
> Thanks, Wolfang, now it's booting fine!
> I've updated u-boot to the newest git version, builded the device tree 
> file and now everything's working.

I'm glad to hear that. Happy hacking!


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
Yes, it's a technical challenge, and  you  have  to  kind  of  admire
people  who go to the lengths of actually implementing it, but at the
same time you wonder about their IQ...
         --  Linus Torvalds in <5phda5$ml6$1@palladium.transmeta.com>

RE: STK5200 pci_enable_device problem

[Mustafa Cayır]

Hi,

i get the latest kernel sources and u-boot sources directly=20
from the git archives from www.denx.de.

My kernel version is Linux-2.6.23-rc5-gaa8ddd08
u-boot version is U-Boot 1.2.0-ge251e00d-dirty

i use dtc compiler with following command:
dtc -O dtb -o tqm5200.dtb -b 0 tqm5200.dts

TQM5200 doesn't boot and gives following error. Any help would be =
approciated.

Thanks a lot.

=3D> run net_nfs_fdt
Using FEC ETHERNET device
TFTP from server 10.18.2.83; our IP address is 10.18.5.44
Filename 'uImage'.
Load address: 0x200000
Loading: =
#################################################################
         ###################################
done
Bytes transferred =3D 1461683 (164db3 hex)
Using FEC ETHERNET device
TFTP from server 10.18.2.83; our IP address is 10.18.5.44
Filename 'tqm5200.dtb'.
Load address: 0x400000
Loading: #
done
Bytes transferred =3D 3507 (db3 hex)
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.23-rc5-gaa8ddd08
   Created:      2007-09-14   6:44:52 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1461619 Bytes =3D  1.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using the fdt at 0x400000
WARNING: could not create /chosen FDT_ERR_NOSPACE.
ERROR: /chosen node create failed - must RESET the board to recover.
                                                                         =
          =20




-----Original Message-----
From: Oliver Rutsch [mailto:orutsch@sympatec.com]=20
Sent: Friday, August 31, 2007 12:35 PM
To: Mustafa Cay=FDr
Subject: Re: STK5200 pci_enable_device problem

Hi Mustafa,

> Hello Oliver,
>=20
> My problems continue, could you summarize your steps to bring up the =
board?
> which u-boot version is used?
> how build tqm5200.dts file?
> did you test pci bus?
>=20
> Thanks.

You should get the latest kernel sources and u-boot sources directly=20
from the git archives from www.denx.de.
Only use the native git protocol, not the HTTP git protocol.
E.g. "git-clone git://www.denx.de/git/linux-2.6-denx linux-2.6-denx"
Build u-boot with the configuration for your board. If your card is NOT=20
a 66 MHz PCI-card, then undefine CFG_PCICLK_EQUALS_IPBCLK_DIV2 in the=20
u-boot configuration to get a 33 MHz PCI bus.
Build u-boot and flash it to the module. Then install the dtc compiler=20
from the git archive (git://www.jdl.com/software/dtc.git). Do NOT use=20
the tar archive on the web, it is out of date. Compile a dtb file out of =

the tqm5200.dts file you find in the kernel sources.
Build the kernel with tqm5200_defconfig.
Boot your module and load the kernel and the dtb file in u-boot. E.g.=20
"tftp 200000 mykernel" and "tftp 400000 mydevicetree.dtb".
Don't forget to change the serial console output. On the 2.4 kernel the=20
internal mpc5200 uarts had the name ttyS0/ttyS1/ttyS2. On the 2.6 they=20
are called ttyPSC0 up to ttyPSC2. So type in u-boot
"set addcons 'setenv bootargs ${bootargs} =
console=3DttyPSC0,${baudrate}'"
"save" (don't forget the single quotes in line above!).
Boot now with "bootm 200000 - 400000".
Now it should boot fine.
I've tested a Korenix Jetcard 1404 (Oxford 16mPCI954 chip) with this=20
kernel and it runs fine. I had no luck with the 2.4 kernel as it failed=20
to give the card an interrupt.

Bye,

--=20
Dipl. Ing. Oliver Rutsch
EMail: orutsch@sympatec.com =B7 Tel.:+49 5323 717514
Sympatec GmbH =B7 Am Pulverhaus 1 =B7 D-38678 Clausthal-Zellerfeld =B7 =
Germany
Geschaeftsfuehrer: Dr.-Ing. E.h. Stephan Roethele =B7 Handelsregister:=20
Amtsgericht Braunschweig, HRB 110809

Re: STK5200 pci_enable_device problem

[Oliver Rutsch]

Mustafa,

It would have been nice, if you would *NOT* repost my private mails I'd 
send to you on the mailing list. At least you could have cut off my 
footer from your mail!
As I thought that it is not of general interest I wrote directly to you 
- but not too see my mails back again on the list. That's really bad style.

Bye,

-- 
Dipl. Ing. Oliver Rutsch