RE: [ECOS] why only this address in pci

RE: [ECOS] why only this address in pci

[sumanth.kondlada]

 Hi Stewart

           I have some douobts still, have you changed the address of
the start
       
           location in the .mlt file which was sugessted by Mr andrew by
which

           I am able to proceed upto this location ,

           have you done any cahnges other than this please help me also
so that

           I can also proceed.

           Even I am getting problem at hal_if_init if I directly say a
go but
     
           working when single stepping,

           are there any pointers for this type of problem and can you
tell me

           changes can be made for the free flow of execution atleast up
to this point

Thanks & regards,
Sumanth.  


-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Stewart
Heitmann
Sent: Friday, March 03, 2006 4:04 AM
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] why only this address in pci

Hi Sumanth,
you are not alone. I am having similar problems on a board based on the
IXDPG425 (Montejade) eval board.
Unfortunately I have no answers and am only getting very odd results
that I cannot make sense of.

At first I was bombing out at the next line from you, at
   HAL_PCI_CFG_WRITE_UINT32(0, 0, CYG_PCI_CFG_BAR_2, 0x02000000); This
was using the ixdpg425 redboot ROM configuration (without network NPE)
shipped with redboot-intel-ixp4xx-050425.

Thinking I had a problem with the PCI bus (my board has the PCI bus
disabled in hardware) I hacked out most of the platform specific code
relating to the PCI bus.
During this work I did manage to see some PCI debug messages on the
console, so I thought I was making progress.

Since then I have lost the console again and am getting even weirder
results. Moreover, the weird stuff happens before any of the code that I
hacked gets executed!

I am now finding the call to hal_xscale_core_init (from ixp425_misc.c)
doesn't jump t the correct address.
	5000ac0c:   eb004ffa   bl 5001ebfc <hal_xscale_core_init>
It ends up jumping to 0x5001_ac14 instead of the intended 0x5000_ebfc
address!!!! I have no idea why that happens!
--
Stewart Heitmann




On Thursday 02 March 2006 10:51 pm, sumanth wrote:
>
> Hi all,
>
>              We are porting ecos for ixp425 evalution board, we are
> using the grg
>              for the purpose ,
>               now we are able to go up to plf_hardware_init
>
>               we are strucking up at cyg_hal_plf_pci_init
>  
> in pci  it is using this address  are there any specific reasons
>
> *IXP425_PCI_PCIMEMBASE = 0x48494A4B
> *IXP425_PCI_AHBMEMBASE = 0x00010203
>
> i am strucking at
>
> HAL_PCI_CFG_WRITE_UINT32(0, 0, CYG_PCI_CFG_BAR_1, 0x01000000);
>
> can any one help me what is the reason or any pointers at this stage
> of porting
>
>
>
> thanks & regards,
> Sumanth


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.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

Re: [ECOS] why only this address in pci

[Stewart Heitmann]

> have you changed the address of the start location in the .mlt file

No. I'm using the standard ixdpg425 settings.
They work on my eval board, so saw no reason to change them.

> Even I am getting problem at hal_if_init if I directly say a
> go but working when single stepping

Sorry but I don't understand what you mean.
Do you mean you have no problem when single stepping?
If so, then it sounds like a timing issue and you may
need to allow your hardware more time to settle after
initialising it.

 
> are there any pointers for this type of problem

Not that I know of. I think we are on our own.


> and can you tell me changes can be made for the free flow of
> execution at least up to this point

I got as far as cyg_hal_plf_pci_init() just using the default settings.
No changes required.

-- 
Stewart Heitmann <stewart@heitmann.id.au>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] why only this address in pci

[Stewart Heitmann]

Hi Sumanth,
you are not alone. I am having similar problems on a board based on
the IXDPG425 (Montejade) eval board.
Unfortunately I have no answers and am only getting very odd
results that I cannot make sense of.

At first I was bombing out at the next line from you, at
   HAL_PCI_CFG_WRITE_UINT32(0, 0, CYG_PCI_CFG_BAR_2, 0x02000000); 
This was using the ixdpg425 redboot ROM configuration (without
network NPE) shipped with redboot-intel-ixp4xx-050425.

Thinking I had a problem with the PCI bus (my board has the PCI
bus disabled in hardware) I hacked out most of the platform
specific code relating to the PCI bus.
During this work I did manage to see some PCI debug messages
on the console, so I thought I was making progress.

Since then I have lost the console again and am getting
even weirder results. Moreover, the weird stuff happens before
any of the code that I hacked gets executed!

I am now finding the call to hal_xscale_core_init (from ixp425_misc.c)
doesn't jump t the correct address.
	5000ac0c:   eb004ffa   bl 5001ebfc <hal_xscale_core_init>
It ends up jumping to 0x5001_ac14 instead of the intended 0x5000_ebfc
address!!!! I have no idea why that happens!
--
Stewart Heitmann




On Thursday 02 March 2006 10:51 pm, sumanth wrote:
> 
> Hi all, 
> 
>              We are porting ecos for ixp425 evalution board, we are using
> the grg 
>              for the purpose , 
>               now we are able to go up to plf_hardware_init 
> 
>               we are strucking up at cyg_hal_plf_pci_init 
>   
> in pci  it is using this address  are there any specific reasons 
> 
> *IXP425_PCI_PCIMEMBASE = 0x48494A4B 
> *IXP425_PCI_AHBMEMBASE = 0x00010203 
> 
> i am strucking at 
> 
> HAL_PCI_CFG_WRITE_UINT32(0, 0, CYG_PCI_CFG_BAR_1, 0x01000000); 
> 
> can any one help me what is the reason or any pointers at this stage of
> porting 
> 
> 
> 
> thanks & regards, 
> Sumanth 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] why only this address in pci

[sumanth]

Hi all, 

             We are porting ecos for ixp425 evalution board, we are using
the grg 
             for the purpose , 
              now we are able to go up to plf_hardware_init 

              we are strucking up at cyg_hal_plf_pci_init 
  
in pci  it is using this address  are there any specific reasons 

*IXP425_PCI_PCIMEMBASE = 0x48494A4B 
*IXP425_PCI_AHBMEMBASE = 0x00010203 

i am strucking at 

HAL_PCI_CFG_WRITE_UINT32(0, 0, CYG_PCI_CFG_BAR_1, 0x01000000); 

can any one help me what is the reason or any pointers at this stage of
porting 



thanks & regards, 
Sumanth 



--
View this message in context: http://www.nabble.com/why-only-this-address-in-pci-t1211193.html#a3200940
Sent from the Sourceware - ecos-discuss forum at Nabble.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