* Re: ecos-devel Digest 24 Mar 2006 01:22:59 -0000 Issue 297
[not found] <1143163379.25698.ezmlm@ecos.sourceware.org>
@ 2006-03-24 12:06 ` Ravi modgekar
0 siblings, 0 replies; only message in thread
From: Ravi modgekar @ 2006-03-24 12:06 UTC (permalink / raw)
To: ecos-devel
Hi,
Ok, let me put it clearly.I have a custom board
whose design is based on ADI Coyote reference
board.Now , for this custom board we have a linux
zImage/ramdisk and a redboot binary(we dont have a
source code for this redboot).With this zImage/ramdisk
and redboot binary I can see Linux booting properly on
my custom board without any problems.
Now I have compiled a new redboot image from sources
available from GW2345 refernce board for my custom
board.With this image,I am able to load the same
zImage/ramdisk,but while accessing the PCI device
,Linux reports PCI master abort.Please note that I am
not at all scanning the PCI bus in Redboot.Linux is
doing it for me.
So, the problem seems to be in the newly compiled
redboot and definitely not in Linux as the the same
Linux image works fine with the older Redboot binary
on the custom board.
Regds
Ravi
--- ecos-devel-digest-help@ecos.sourceware.org wrote:
>
> ecos-devel Digest 24 Mar 2006 01:22:59 -0000 Issue
> 297
>
> Topics (messages 931 through 933):
>
> [ECOS] Redboot causes PCI abort in Linux Ixp425
> 931 by: "Daly, Jeffrey" <jeffrey.daly@intel.com>
> 932 by: "Stephen Goadhouse"
> <stephen.goadhouse@adiengineering.com>
>
> Can't start redboot in RAM mode
> 933 by: "EE89 student"
> <s8964016@star.ee.nchu.edu.tw>
>
> Administrivia:
>
> To subscribe to the digest, e-mail:
> ecos-devel-digest-subscribe@ecos.sourceware.org
>
> To unsubscribe from the digest, e-mail:
> ecos-devel-digest-unsubscribe@ecos.sourceware.org
>
> To post to the list, e-mail:
> ecos-devel@ecos.sourceware.org
>
>
>
----------------------------------------------------------------------
> > Subject: RE: [ECOS] Redboot causes PCI abort in
> Linux Ixp425
> Date: Wed, 22 Mar 2006 09:42:09 -0500
> From: "Daly, Jeffrey" <jeffrey.daly@intel.com>
> To: <ecos-devel@sourceware.org>
>
> The situation isn't quite clear to me from your
> original email. Are you
> saying you've got 2 boards, one GW2345 and one
> custom? The GW2345 works
> fine. The custom one works fine with the GW2345
> redboot and linux, but
> doesn't work whith the custom redboot and linux?
> Pls clarify.
>
> Sounds to me like your PCI configuration during
> redboot is wrong (or at
> least is different that what the original does).
> You should dump the
> PCI config of the GW2345 (from redboot, before
> booting linux) and dump
> the PCi config of the custom board (again redboot,
> not linux) and post
> that.
>
> -----Original Message-----
> From: ecos-devel-owner@ecos.sourceware.org
> [mailto:ecos-devel-owner@ecos.sourceware.org] On
> Behalf Of Ravi modgekar
> Sent: Wednesday, March 22, 2006 9:21 AM
> To: Stephen Goadhouse; ecos-devel@sourceware.org;
> ecos-discuss@sourceware.org
> Subject: RE: [ECOS] Redboot causes PCI abort in
> Linux Ixp425
>
> Hi Stephen,
> Data abort exception during PCI scan is ok.But in
> my case, the abort does not happen while scanning
> the
> bus , but it happens while accessing the device!!!!
> Basically Linux does the PCI enumeration at the
> boot time and sets up the device properly.There is
> absolutely no problem while scanning.The abort
> happens
> only when you try to access the PCI device.Now when
> you are trying to access the device , there is no
> question of scanning the bus again.
> I am wondering , if I am missing something else in
> the redboot .I also don't see any need to scan the
> PCI
> bus in the redboot, since linux is re doing it for
> me.what could be wrong.
> By the way, I think even the ADI coyote board does
> not scan the PCI bus in Redboot.
>
> Regds
> Ravi
>
>
> --- Stephen Goadhouse
> <stephen.goadhouse@adiengineering.com> wrote:
>
> >
> > Xscale processors, and perhaps other ARM-based
> > processors, will get a
> > data abort exception while scanning the PCI bus.
> > This is normal. To
> > scan the bus, the system should be trying to read
> > every available PCI
> > configuration slot address to see if a device is
> > there. If no device is
> > there, you'll get a data abort exception because
> > technically the PCI
> > transaction did not complete (no target to handle
> > the PCI configuration
> > read). Typically, this is handled by installing a
> > data abort exception
> > handler prior to scanning the bus that gracefully
> > handles these
> > exceptions during PCI bus scan. Another
> alternative
> > with the IXP425 may
> > be to setup its internal PCI bridge so that it
> > returns 0xFFFFFFFF instead
> > of doing a data abort. I have not looked at the
> > ixp425 manual in a
> > while, but I am fairly certain that it has this
> > ability. I would expect
> > that's what your old RedBoot did to handle this so
> > that Linux would not
> > have to. Receiving 0xFFFFFFFF when reading
> > non-existent PCI slots is
> > what happens in a PC environment and I'm fairly
> > certain that is what
> > Linux typically expects.
> >
> >
> >
>
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> >
> > _/ Stephen Goadhouse Work: (434)
> > 978-2888 x254 _/
> > _/ Senior Staff Engineer
> > stephen.goadhouse@adiengineering.com _/
> > _/ ADI Engineering
> > http://www.adiengineering.com _/
> >
>
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> >
> >
> >
> > > -----Original Message-----
> > > From: ecos-discuss-owner@ecos.sourceware.org
> > > [mailto:ecos-discuss-owner@ecos.sourceware.org]
> On
> > Behalf Of
> > > Ravi modgekar
> > > Sent: Thursday, March 16, 2006 1:04 AM
> > > To: ecos-devel@sourceware.org;
> > ecos-discuss@sourceware.org
> > > Subject: [ECOS] Redboot causes PCI abort in
> Linux
> > Ixp425
> > >
> > > Hi,
> > > I have an IXP425 based board based on
> > Gateworks
> > > GW2345 board.This
> > > board already had a redboot image programmed
> > through which
> > > we could easily load linux and work on it.
> > > Now I have compiled the redboot for our IXP
> > based board
> > > from the Avila redboot sources.With this newly
> > compiled
> > > redboot I am able to
> > > boot linux, but unfortunately the PCI cribs
> and
> > the
> > > linux crashes
> > > with PCI abort. The error message being "!!!
> > > abort_handler addr =
> > > 0x40015000 ,isr = 0x0 , status = 0x22a0".
> > > Interestingly the same Linux
> > > image works fine with the old redboot ,for which
> > we don't
> > > have the source code.
> > > Has anybody in this list faced this problem.Am
> I
> > missing
> > > configuring something in the Redboot which is
> > causing the
> > > PCI abort.I have tried with completely disabling
> > PCI
> > > interface , but I still see this problem.
> > >
> > > any pointers !!!
> > >
> > > Regds
> > > Ravi
> > >
> > >
> __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > protection
> > > around http://mail.yahoo.com
> > >
> > > --
> > > Before posting, please read the FAQ:
> > > http://ecos.sourceware.org/fom/ecos
> > > and search the list archive:
> > > http://ecos.sourceware.org/ml/ecos-discuss
> > >
> > >
> > > __________ NOD32 1.1445 (20060315) Information
> > __________
> > >
> > > This message was checked by NOD32 antivirus
> > system.
> > > http://www.eset.com
> > >
> > >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
> > From: "Stephen Goadhouse"
> <stephen.goadhouse@adiengineering.com>
> To: <ravilm@yahoo.com>,
> <ecos-devel@sourceware.org>,
> <ecos-discuss@sourceware.org>
> Subject: RE: [ECOS] Redboot causes PCI abort in
> Linux Ixp425
> Date: Wed, 22 Mar 2006 12:01:21 -0500
>
> Yes, you are correct about the ADI Coyote board.
> Almost all of our other
> platforms scan PCI devices in RedBoot and Linux
> makes use of the RedBoot
> scan. The opposite is true of Coyote where RedBoot
> does no scanning and
> Linux does the scanning. Because it's the exception
> for us, I often forget
> that.
>
> You may want to try creating a simple data abort
> handler that captures the
> PCI status and the PC of the offending instruction.
> There should be a data
> abort handler for PCI scans in some eCos HALs that
> you can use as an example
> for your case. The PCI status may tell you that you
> are getting a master
> abort or some other type of PCI error or it may have
> no error, in which case
> it could be the address you are using to access the
> device (make sure it's a
> proper virtual address that maps to the correct
> physical address) or perhaps
> some register in the IXP425 is not setup correctly.
>
>
> Stephen Goadhouse
> Senior Staff Engineer
> ADI Engineering (http://www.adiengineering.com)
> (434) 978-2888 x254
>
>
>
> > -----Original Message-----
> > From: Ravi modgekar [mailto:ravilm@yahoo.com]
> > Sent: Wednesday, March 22, 2006 9:21 AM
> > To: Stephen Goadhouse; ecos-devel@sourceware.org;
> > ecos-discuss@sourceware.org
> > Subject: RE: [ECOS] Redboot causes PCI abort in
> Linux Ixp425
> >
> > Hi Stephen,
> > Data abort exception during PCI scan is ok.But
> in my case,
> > the abort does not happen while scanning the bus ,
> but it
> > happens while accessing the device!!!!
> > Basically Linux does the PCI enumeration at the
> boot time
> > and sets up the device properly.There is
> absolutely no
> > problem while scanning.The abort happens only when
> you try to
> > access the PCI device.Now when you are trying to
> access the
> > device , there is no question of scanning the bus
> again.
> > I am wondering , if I am missing something else
> in the
> > redboot .I also don't see any need to scan the PCI
> bus in the
> > redboot, since linux is re doing it for me.what
> could be wrong.
> > By the way, I think even the ADI coyote board
> does not scan
> > the PCI bus in Redboot.
> >
> > Regds
> > Ravi
> >
> >
> > --- Stephen Goadhouse
> > <stephen.goadhouse@adiengineering.com> wrote:
> >
> > >
> > > Xscale processors, and perhaps other ARM-based
> processors,
> > will get a
> > > data abort exception while scanning the PCI bus.
> > > This is normal. To
> > > scan the bus, the system should be trying to
> read every
> > available PCI
> > > configuration slot address to see if a device is
> there. If
> > no device
> > > is there, you'll get a data abort exception
> because technically the
> > > PCI transaction did not complete (no target to
> handle the PCI
> > > configuration read). Typically, this is handled
> by
> > installing a data
> > > abort exception handler prior to scanning the
> bus that gracefully
> > > handles these exceptions during PCI bus scan.
> Another alternative
> > > with the IXP425 may be to setup its internal PCI
> bridge so that it
> > > returns 0xFFFFFFFF instead of doing a data
> abort. I have
> > not looked
> > > at the
> > > ixp425 manual in a
> > > while, but I am fairly certain that it has this
> ability. I would
> > > expect that's what your old RedBoot did to
> handle this so
> > that Linux
> > > would not have to. Receiving 0xFFFFFFFF when
> reading
> > non-existent PCI
> > > slots is what happens in a PC environment and
> I'm fairly
> > certain that
> > > is what
> > > Linux typically expects.
> > >
> > >
> > >
> >
>
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > >
> > > _/ Stephen Goadhouse Work:
> (434)
> > > 978-2888 x254 _/
> > > _/ Senior Staff Engineer
> > > stephen.goadhouse@adiengineering.com _/
> > > _/ ADI Engineering
> > > http://www.adiengineering.com _/
> > >
> >
>
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: ecos-discuss-owner@ecos.sourceware.org
> > > >
> [mailto:ecos-discuss-owner@ecos.sourceware.org] On
> > > Behalf Of
> > > > Ravi modgekar
> > > > Sent: Thursday, March 16, 2006 1:04 AM
> > > > To: ecos-devel@sourceware.org;
> > > ecos-discuss@sourceware.org
> > > > Subject: [ECOS] Redboot causes PCI abort in
> Linux
> > > Ixp425
> > > >
> > > > Hi,
> > > > I have an IXP425 based board based on
> > > Gateworks
> > > > GW2345 board.This
> > > > board already had a redboot image programmed
> > > through which
> > > > we could easily load linux and work on it.
> > > > Now I have compiled the redboot for our IXP
> > > based board
> > > > from the Avila redboot sources.With this newly
> > > compiled
> > > > redboot I am able to
> > > > boot linux, but unfortunately the PCI cribs
> and
> > > the
> > > > linux crashes
> > > > with PCI abort. The error message being "!!!
> > > > abort_handler addr =
> > > > 0x40015000 ,isr = 0x0 , status = 0x22a0".
> > > > Interestingly the same Linux
> > > > image works fine with the old redboot ,for
> which
> > > we don't
> > > > have the source code.
> > > > Has anybody in this list faced this
> problem.Am I
> > > missing
> > > > configuring something in the Redboot which is
> > > causing the
> > > > PCI abort.I have tried with completely
> disabling
> > > PCI
> > > > interface , but I still see this problem.
> > > >
> > > > any pointers !!!
> > > >
> > > > Regds
> > > > Ravi
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam? Yahoo! Mail has the best spam
> > > protection
> > > > around http://mail.yahoo.com
> > > >
> > > > --
> > > > Before posting, please read the FAQ:
> > > > http://ecos.sourceware.org/fom/ecos
> > > > and search the list archive:
> > > > http://ecos.sourceware.org/ml/ecos-discuss
> > > >
> > > >
> > > > __________ NOD32 1.1445 (20060315) Information
> > > __________
> > > >
> > > > This message was checked by NOD32 antivirus
> > > system.
> > > > http://www.eset.com
> > > >
> > > >
> > >
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection
> > around http://mail.yahoo.com
>
> > From: "EE89 student"
<s8964016@star.ee.nchu.edu.tw>
> To: ecos-devel@sourceware.org
> Subject: Can't start redboot in RAM mode
> Date: Fri, 24 Mar 2006 09:21:56 +0800
>
> Hi
> i have a modified ixdp425 board and redboot can run
> on it with ROM and ROMRAM mode
> but after i load the redboot[RAM].bin into memory
> and trying to execute "go"
> ,then crash.
>
> here is how i generate the bin file
> ./ecosconfig new ${Board}_npe redboot
> ./ecosconfig import
>
${ECOS_REPOSITORY}/hal/arm/xscale/${Board}/current/misc/redboot_RAM.ecm
> ./ecosconfig import
>
${ECOS_REPOSITORY}/hal/arm/xscale/${Board}/current/misc/no_eeprom.ecm
> ./ecosconfig tree
>
> make
>
>
> and i already change the settings in
>
packages/hal/arm/xscale/ixdp425/current/include/pkgconf/
> to fit my board
> is the crash resulted from my wrong settings? but it
> works on ROM and ROMRAM mode.
>
> best regards
> Blair
>
>
>
--------------------------------------------------------------------------------------
> Trying NPE-B...success. Using NPE-B with PHY 0.
> Ethernet eth0: MAC address 00:03:47:df:32:a8
> IP: 10.12.7.221/255.255.255.0, Gateway: 10.12.7.254
> Default server: 10.12.7.17
>
> RedBoot(tm) bootstrap and debug environment [ROMRAM]
> Red Hat certified release, version 2.01 - built
> 19:31:44, Mar 22 2006
>
> Platform: IXDP425 Development Platform (XScale) BE
> Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat,
> Inc.
>
> RAM: 0x00000000-0x04000000, [0x000266f0-0x03fc1000]
> available
> FLASH: 0x50000000 - 0x51000000, 128 blocks of
> 0x00020000 bytes each.
> RedBoot> load -r -v -b 0x03000000 redboot[RAM].bin
> Using default protocol (TFTP)
> -
> Raw file loaded 0x03000000-0x03049c8b, assumed entry
> at 0x03000000
> RedBoot> go
>
$T050f:01000040;0d:03fc0fec;#dc$T050f:01000040;0d:03fc0fec;#dc$T050f:01000040;0c
>
> --
> NCHUEE (http://www.ee.nchu.edu.tw)
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [flat|nested] only message in thread