[ECOS] AT91RM9200 chip select

[ECOS] AT91RM9200 chip select

[pippo]

Hi,
I'm using eCosPro with a AT91RM9200-EK board and I'm trying to set up 
a connection with a radio module mapped at CS4 (Host Interface) and CS5 
(DCI). For the moment my attempt is to see both CS4 and CS5 activated 
on my scope. On my code I firstly configure the external bus:

HAL_WRITE_UINT32(_EBI_CFGR, (AT91C_EBI_DBPUC & 0x00) | 
(AT91C_EBI_EBSEN & 0x00));

but when I try to assign the CSs my application stops

HAL_WRITE_UINT32(_EBI_CSA, _EBI_CSA & ~(_EBI_CSA_CS4A));

I thought that maybe is an MMU problem, but I don't know what I should 
modify to get the application running, could someone help me? I've 
already been spending some time looking for a similar problem and I 
noticed that on the file hal_platform_setup.h some initialisations are 
done. In particular I saw that the CS0 is assigned to flash before the 
MMU is enabled, should I do the same thing with CS4 and CS5?
Thanks.

Michele


Naviga e telefona senza limiti con Tiscali     
Scopri le promozioni Tiscali adsl: navighi e telefoni senza canone Telecom

http://abbonati.tiscali.it/adsl/


-- 
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] AT91RM9200 chip select

[Gary Thomas]

pippo@pippo.it wrote:
> Hi,
> I'm using eCosPro with a AT91RM9200-EK board and I'm trying to set up 

Then you should be asking them for support, I'm afraid...

> a connection with a radio module mapped at CS4 (Host Interface) and CS5 
> (DCI). For the moment my attempt is to see both CS4 and CS5 activated 
> on my scope. On my code I firstly configure the external bus:
> 
> HAL_WRITE_UINT32(_EBI_CFGR, (AT91C_EBI_DBPUC & 0x00) | 
> (AT91C_EBI_EBSEN & 0x00));
> 
> but when I try to assign the CSs my application stops
> 
> HAL_WRITE_UINT32(_EBI_CSA, _EBI_CSA & ~(_EBI_CSA_CS4A));
> 
> I thought that maybe is an MMU problem, but I don't know what I should 
> modify to get the application running, could someone help me? I've 
> already been spending some time looking for a similar problem and I 
> noticed that on the file hal_platform_setup.h some initialisations are 
> done. In particular I saw that the CS0 is assigned to flash before the 
> MMU is enabled, should I do the same thing with CS4 and CS5?
> Thanks.


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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] AT91RM9200 chip select

[miguelon]

pippo@pippo.it wrote:

       Hi,
       I'm using eCosPro with a AT91RM9200-EK board and I'm trying to 
set up 

       Then you should be asking them for support, I'm afraid...

We managed to have eCosPro for a lower price without having support, 
that's why I'm asking here...
I thought that it was a general problem not related to the version of 
eCos. Thanks anyway.

Michele


Naviga e telefona senza limiti con Tiscali     
Scopri le promozioni Tiscali adsl: navighi e telefoni senza canone Telecom

http://abbonati.tiscali.it/adsl/


-- 
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] AT91RM9200 chip select

[Andrew Lunn]

On Mon, Aug 14, 2006 at 02:12:48PM +0200, miguelon@tiscali.it wrote:
> We managed to have eCosPro for a lower price without having support, 
> that's why I'm asking here...
>
> I thought that it was a general problem not related to the version of 
> eCos. Thanks anyway.

Well, if it is an MMU problem, it will be specific to the MMU setup
code for that particular platform. And since we don't have access to
that code, it is hard for us to help you. 

     Andrew

-- 
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] AT91RM9200 chip select

[Daniel Morris]

On Mon, Aug 14, 2006 at 02:12:48PM +0200, miguelon@tiscali.it wrote:
> pippo@pippo.it wrote:
> 
>        Hi,
>        I'm using eCosPro with a AT91RM9200-EK board and I'm trying to 
> set up 
> 
>        Then you should be asking them for support, I'm afraid...
> 
> We managed to have eCosPro for a lower price without having support, 
> that's why I'm asking here...

That's strange, we don't offer eCosPro for that platform without support
and don't have any authorised resellers.

 Daniel

%<----------------------------------------------------------------------
  Daniel Morris - Sales & Marketing Director
  eCosCentric - The eCos and RedBoot experts
  Tel: +44 1223 245 571 - info@eCosCentric.com
  DDI: +44 1269 591 171 - danielm@eCosCentric.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] AT91RM9200 chip select

[miguelon]

On Mon, Aug 14, 2006 at 02:12:48PM +0200, miguelon@tiscali.it wrote:
> > We managed to have eCosPro for a lower price without having 
support, 
> > that's why I'm asking here...
> >
> > I thought that it was a general problem not related to the version 
of 
> > eCos. Thanks anyway.

> Well, if it is an MMU problem, it will be specific to the MMU setup
> code for that particular platform. And since we don't have access to
> that code, it is hard for us to help you. 

>     Andrew

I finally found a package on the CVS repository 
(packages/hal/arm/arm9/aaed2000/) which is similar to mine, at least as 
for the MMU setup. As I understood from other threads the file which 
has to be modified is /include/hal_platform_setup.h but in this case 
the code calls a function (hal_mmu_init) to create MMU tables. I've 
found the code for this function in /src/aaed2000_misc.c and actually 
it defines a MMU table using the macro X_ARM_MMU_SECTION. The first 
thing that comes into my head is to modify directly the source file 
adding the mapping for my device but maybe there's a more elegant way 
to do it. I hope to have provided all the information you need to help 
me, I'm at the beginning with eCos. Thanks a lot.

Michele


Naviga e telefona senza limiti con Tiscali     
Scopri le promozioni Tiscali adsl: navighi e telefoni senza canone Telecom

http://abbonati.tiscali.it/adsl/


-- 
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] AT91RM9200 chip select

[Andrew Lunn]

> I finally found a package on the CVS repository 
> (packages/hal/arm/arm9/aaed2000/) which is similar to mine, at least as 
> for the MMU setup. As I understood from other threads the file which 
> has to be modified is /include/hal_platform_setup.h but in this case 
> the code calls a function (hal_mmu_init) to create MMU tables. I've 
> found the code for this function in /src/aaed2000_misc.c and actually 
> it defines a MMU table using the macro X_ARM_MMU_SECTION. The first 
> thing that comes into my head is to modify directly the source file 
> adding the mapping for my device but maybe there's a more elegant way 
> to do it. I hope to have provided all the information you need to help 
> me, I'm at the beginning with eCos. Thanks a lot.

It might be possible to call the X_ARM_MMU_SECTION macro in
"application" space. I've done with with the EBSA285 target when i
needed to map an external bus into memory. Doing it this way you have
less trouble in the future if eCosCentric gives you an update. No need
to move your patches between trees.

   Andrew

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