Discussions among eCos developers

Evgeniy Dushistov | 6 Nov 2008 19:23

Picon

at91sam9263ek

Hi,  

I want to see working ecos on at91sam9263ek board.  
As far as I know, there is no freely available source code of ecos port on  
this hardware, am I right? (I know about ecoscentric, but it is not  
freely available).  

May be anybody is working on such kind of port?  

Right now I'm reading docs about cdl language, and stuck on which
variant to choose: create directory at91sam9 in  
packages/hal/arm/arm9 and write hal package from scratch  
or use packages/hal/arm/at91 stuff, at91sam9263ek is very similar  
to at91sam7s, but  
packages/hal/arm/at91/var/current/cdl/hal_arm_at91.cdl  
contain things like "implements CYGINT_HAL_ARM_ARCH_ARM7",  
may be someone, who has more experience than I (i.e. > 0) with ecos  
configuration framework, could suggest which solution to choose? 

--

-- 
/Evgeniy

Andrew Lunn | 10 Nov 2008 10:20

Picon

Re: at91sam9263ek

On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
> Hi,  
>  
> I want to see working ecos on at91sam9263ek board.  
> As far as I know, there is no freely available source code of ecos port on  
> this hardware, am I right? (I know about ecoscentric, but it is not  
> freely available).  
>  
> May be anybody is working on such kind of port?  
>  
> Right now I'm reading docs about cdl language, and stuck on which
> variant to choose: create directory at91sam9 in  
> packages/hal/arm/arm9 and write hal package from scratch  
> or use packages/hal/arm/at91 stuff, at91sam9263ek is very similar  
> to at91sam7s, but  
> packages/hal/arm/at91/var/current/cdl/hal_arm_at91.cdl  
> contain things like "implements CYGINT_HAL_ARM_ARCH_ARM7",  
> may be someone, who has more experience than I (i.e. > 0) with ecos  
> configuration framework, could suggest which solution to choose? 

You could change this. Do something like

    cdl_option CYGHWR_HAL_ARM_AT91_ARM7 {
        display  "ARM7 core"
        no_define
        calculated { is_substring("R40807 R40008 M42800A M55800A JTST AT91SAM7S", CYGHWR_HAL_ARM_AT91) }
        implements  CYGINT_HAL_ARM_ARCH_ARM7
    } 

    cdl_option CYGHWR_HAL_ARM_AT91_ARM9 {

(Continue reading)

Jonathan Larmour | 18 Nov 2008 17:37

Re: at91sam9263ek

Andrew Lunn wrote:
> On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
>> Hi,  
>>  
>> I want to see working ecos on at91sam9263ek board.  
>> As far as I know, there is no freely available source code of ecos port on  
>> this hardware, am I right? (I know about ecoscentric, but it is not  
>> freely available).  
>>  
>> May be anybody is working on such kind of port?  
>>  
>> Right now I'm reading docs about cdl language, and stuck on which
>> variant to choose: create directory at91sam9 in  
>> packages/hal/arm/arm9 and write hal package from scratch  
>> or use packages/hal/arm/at91 stuff, at91sam9263ek is very similar  
>> to at91sam7s,

I don't think it's that similar. At least, it seems similar at a
high-level, but differs in most of the details once you get into it. The
register layouts differ in many places between the SAM9 variants even. I
think you'd end up with huge amounts of ifdefs.

I recommend the former approach. If there is anything that can sensibly be
shared, perhaps it could be broken out into a separate package.

>> but  
>> packages/hal/arm/at91/var/current/cdl/hal_arm_at91.cdl  
>> contain things like "implements CYGINT_HAL_ARM_ARCH_ARM7",  
>> may be someone, who has more experience than I (i.e. > 0) with ecos  
>> configuration framework, could suggest which solution to choose?

(Continue reading)

Evgeniy Dushistov | 25 Nov 2008 21:50

Picon

Re: at91sam9263ek

On Tue, Nov 18, 2008 at 04:37:33PM +0000, Jonathan Larmour wrote:
> Andrew Lunn wrote:
> > On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
> >> Hi,  
> >>  
> >> I want to see working ecos on at91sam9263ek board.  
> >> As far as I know, there is no freely available source code of ecos port on  
> >> this hardware, am I right? (I know about ecoscentric, but it is not  
> >> freely available).  
> >>  
> >> May be anybody is working on such kind of port?  
> >>  
> >> Right now I'm reading docs about cdl language, and stuck on which
> >> variant to choose: create directory at91sam9 in  
> >> packages/hal/arm/arm9 and write hal package from scratch  
> >> or use packages/hal/arm/at91 stuff, at91sam9263ek is very similar  
> >> to at91sam7s,
> 
> I don't think it's that similar. At least, it seems similar at a
> high-level, but differs in most of the details once you get into it. The
> register layouts differ in many places between the SAM9 variants even. I
> think you'd end up with huge amounts of ifdefs.
> 

Can you, please, give, example of such defence?
I compared  at91sam7s and at91sam9263ek datasheets, the base addresses
on which IP blocks are mapped sometimes different,
but layouts of the registers the same, here what I compare:

- gpio controller

(Continue reading)

Jonathan Larmour | 25 Nov 2008 23:57

Re: at91sam9263ek

Evgeniy Dushistov wrote:
> On Tue, Nov 18, 2008 at 04:37:33PM +0000, Jonathan Larmour wrote:
> 
>>Andrew Lunn wrote:
>>
>>>On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
>>>
>>>>Hi,  
>>>> 
>>>>I want to see working ecos on at91sam9263ek board.  
>>>>As far as I know, there is no freely available source code of ecos port on  
>>>>this hardware, am I right? (I know about ecoscentric, but it is not  
>>>>freely available).  
>>>> 
>>>>May be anybody is working on such kind of port?  
>>>> 
>>>>Right now I'm reading docs about cdl language, and stuck on which
>>>>variant to choose: create directory at91sam9 in  
>>>>packages/hal/arm/arm9 and write hal package from scratch  
>>>>or use packages/hal/arm/at91 stuff, at91sam9263ek is very similar  
>>>>to at91sam7s,
>>
>>I don't think it's that similar. At least, it seems similar at a
>>high-level, but differs in most of the details once you get into it. The
>>register layouts differ in many places between the SAM9 variants even. I
>>think you'd end up with huge amounts of ifdefs.
> 
> Can you, please, give, example of such defence?

Well I had flicked through our own SAM926x implementation to see the

(Continue reading)

Evgeniy Dushistov | 11 Nov 2008 19:50

Picon

Re: [PATCH] [RFC] at91sam9263ek support

On Mon, Nov 10, 2008 at 10:20:57AM +0100, Andrew Lunn wrote:
> On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
> You could change this. Do something like

Thanks for suggestion.

Here is patch for initial support of atmel at91sam9263ek
against current cvs tree.

Using this patch it is possible to get redboot console
on dbgu port if you load it into memory via sam-ba or jtag.

Any comments about this patch?

The next step I think will be implement booting from flash
memory.
But at91sam9263k board has limitations for
the "the first level" application, it size should be < 72K,
or it should consists of several parts when one load another.

So how do you think is it possible to build redboot with
nand,nor and serial usb support and image size less
then 72K? Another option may be usage of
"the first level" bootloader from atmel(at91bootstrap),
but this solution has its own disadvantages.

--

-- 
/Evgeniy

(Continue reading)

Evgeniy Dushistov | 11 Nov 2008 19:50

Picon

Re: [PATCH] [RFC] at91sam9263ek support

On Mon, Nov 10, 2008 at 10:20:57AM +0100, Andrew Lunn wrote:
> On Thu, Nov 06, 2008 at 09:23:28PM +0300, Evgeniy Dushistov wrote:
> You could change this. Do something like

Thanks for suggestion.

Here is patch for initial support of atmel at91sam9263ek
against current cvs tree.

Using this patch it is possible to get redboot console
on dbgu port if you load it into memory via sam-ba or jtag.

Any comments about this patch?

The next step I think will be implement booting from flash
memory.
But at91sam9263k board has limitations for
the "the first level" application, it size should be < 72K,
or it should consists of several parts when one load another.

So how do you think is it possible to build redboot with
nand,nor and serial usb support and image size less
then 72K? Another option may be usage of
"the first level" bootloader from atmel(at91bootstrap),
but this solution has its own disadvantages.

--

-- 
/Evgeniy

(Continue reading)

roberto.lavarini | 26 Nov 2008 16:05

Picon

Re: [PATCH] [RFC] at91sam9263ek support


Hi,

I've try to follow your patch but I have some problems during compiling
phase. Can you tell me the directory that you used to create the others two
directory at91sam9 and at91sam9263ek? I used at91sam7s folder for both.

Thank you.
--

-- 
View this message in context: http://www.nabble.com/at91sam9263ek-tp20367309p20702652.html
Sent from the Sourceware - ecos-devel mailing list archive at Nabble.com.

Evgeniy Dushistov | 27 Nov 2008 20:09

Picon

Re: [PATCH] [RFC] at91sam9263ek support

On Wed, Nov 26, 2008 at 07:05:54AM -0800, roberto.lavarini wrote:
> 
> Hi,
> 
> I've try to follow your patch but I have some problems during compiling
> phase. Can you tell me the directory that you used to create the others two
> directory at91sam9 and at91sam9263ek? I used at91sam7s folder for both.
> 

I don't undesntand you, you need only apply patch, and that's all,
no need copy something somewhere, just apply patch, run configtool
choose template, hardware at91sam9263ek, package redboot,
and build.

--

-- 
/Evgeniy

roberto.lavarini | 28 Nov 2008 12:03

Picon

Re: [PATCH] [RFC] at91sam9263ek support

Thanks for your answer.

 In your patch seems to miss the files mlt_arm_at91sam9263ek_rom.h and
mlt_arm_at91sam9263ek_rom.ldi. So I obtain an error if I try to start
"RedBoot" from ROM. Can you complete your patch? I consider it very useful.
Thanks for your support.

Roberto

Evgeniy Dushistov wrote:
> 
> On Wed, Nov 26, 2008 at 07:05:54AM -0800, roberto.lavarini wrote:
>> 
>> Hi,
>> 
>> I've try to follow your patch but I have some problems during compiling
>> phase. Can you tell me the directory that you used to create the others
>> two
>> directory at91sam9 and at91sam9263ek? I used at91sam7s folder for both.
>> 
> 
> I don't undesntand you, you need only apply patch, and that's all,
> no need copy something somewhere, just apply patch, run configtool
> choose template, hardware at91sam9263ek, package redboot,
> and build.
> 
> -- 
> /Evgeniy
>

(Continue reading)

Return

Return to gmane.os.ecos.devel.

Project Web Page

Discussions among eCos developers

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane