This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: issue about porting ecos on new target board


oops sorry,
i have miss read the cpu name ...
so  S3C4510 and  KS32C50100 are the same (e7t)
and KS32C41000 should not be the same...
apologies,

Aurelien Francillon
 
On Wed, 16 Apr 2003, Robert Cragie wrote:

> I have found data sheet on S3C44B0X which is a similar part to the one you
> mention and, yes, you're right, it's quite different.
> 
> In this case, you would still be wise to start from an ARM7TDMI core based
> port, so 'e7t' or 'snds' would still be appropriate. However, you will need
> to consider all aspects of the port - the cache control, UART, system
> configuration, memory map, clock configuration etc. when doing the port. I
> would suggest buying Anthony Massa's book 'Embedded Software Development
> with eCos' (ISBN 0-13-035473-2) - this has a whole chapter on porting.
> 
> Robert Cragie, Design Engineer
> _______________________________________________________________
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
> http://www.jennic.com  Tel: +44 (0) 114 281 2655
> _______________________________________________________________
> 
> > -----Original Message-----
> > From: P_CHING_KUANG [mailto:p_ching_kuang at ms10 dot url dot com dot tw]
> > Sent: 16 April 2003 11:59
> > To: rcc at jennic dot com
> > Subject: [ECOS] issue about porting ecos on new target board
> >
> >
> > Dear,
> > Thanks for replying.
> > I think it is not similar with the S3C4510/S3C4530.
> >
> > You can find this process at below website:
> > http://www.samsungusa.com/cgi-
> > bin/nabc/semiconductors/system_lsi/32_bit_arm_based_risc_mpu/pda/k
> > s32c41000/
> > ks32c41000.jsp
> >
> > Hope to hear your reply, thanks.
> >
> > Regards,
> > Steve
> >
> > ____________________Original Message_____________________
> >
> > I can't find any information about your processor on the Samsung website
> > (http://www.samsung.com/Products/Semiconductor/). However, it
> > sounds like it
> > might be similar to the S3C4510/S3C4530 used in ARM's E7T or Samsung's
> > SNDS100, so the 'e7t' or 'snds' targets would probably be your
> > best starting
> > point for a port.
> >
> > Robert Cragie, Design Engineer
> > _______________________________________________________________
> > Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
> > http://www.jennic.com  Tel: +44 (0) 114 281 2655
> > _______________________________________________________________
> >
> > > -----Original Message-----
> > > From: ecos-discuss-owner at sources dot redhat dot com
> > > [mailto:ecos-discuss-owner at sources dot redhat dot com]On Behalf Of P_CHING_KUANG
> > > Sent: 16 April 2003 04:45
> > > To: ecos-discuss at sources dot redhat dot com
> > > Subject: [ECOS] issue about porting ecos on new target board
> > >
> > >
> > > Dear,
> > >
> > > I am new for ecos project, and I want to port it on Samsung KS32C41000
> > > ARM7TDMI CPU.
> > > Do you have some suggestion?  Which process supported by ecos is similar
> > > with this process ?
> > >
> > > Regards,
> > > Steve
> > >
> > >
> > > ------------------------------------------
> > > 台灣最物超所值的大眾化虛擬郵件主機
> > > http://mymailer.url.com.tw
> > >
> > >
> > >
> > > --
> > > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > > and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> > >
> > >
> >
> >
> > ------------------------------------------
> > 台灣最物超所值的大眾化虛擬郵件主機
> > http://mymailer.url.com.tw
> >
> >
> >
> 
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 
> 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]