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: Samsung SNDS100 Eval. Board...


Thanks, Jay.

Yesterday I also found the problem in PLATFORM_SETUP1 code. After
fixing it, now I can run a ROM version test program very well on my SNDS100
board.

=================
Yao-Lu Tsai
KCodes Corporation

----- Original Message -----
From: "Jay Foster" <jay@systech.com>
To: "'Yao-Lu Tsai'" <ytsai@kcodes.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Thursday, October 17, 2002 12:29 AM
Subject: RE: [ECOS] Samsung SNDS100 Eval. Board...


> I am very new to eCos & RedBoot myself (about 2 weeks).  I have only built
a
> RAM version of the eCos hello world example program, and loaded it using
the
> GDB/Insight debugger.
>
> I selected the "Samsung SNDS" template and the "new_net" package.  Also
make
> sure that the CPU type (CYG_HAL_CPUTYPE) is selected correctly for your
> processor.  The default value of "KS32C5000A" is not right for the
S3C4510B
> that I'm using.  I selected the S3C4510A" selection.  The primary
difference
> between these selections is which register bits the interrupts are
connected
> to.  RedBoot doesn't seem to use the interrupts, so it didn't matter for
> RedBoot, but eCos does.  The other difference is between hardware/software
> CRC in the ethernet driver.
>
> Another thing to check is if the RAM and ROM configuration registers are
> getting configured correctly.  Since I'm using GDB to load my RAM version
of
> the code, I do this with a .gdbinit file before loading the code.  The
> startup code for the ROM version must do this itself.  I noticed that the
> code that does this for the SNDS board only gets included if the GDB stubs
> are compiled in (see the PLATFORM_SETUP1 definition in the
> hal_platform_setup.h file for the snds platform). In fact, I had to
disable
> this code to get the RAM version of the RedBoot package to build (this
code
> can only be executed from ROM, and should only be included in the ROM
> versions).
>
> Jay
>
> -----Original Message-----
> From: Yao-Lu Tsai [mailto:ytsai@kcodes.com]
> Sent: Tuesday, October 15, 2002 6:52 PM
> To: Jay Foster; 'Grant Edwards'
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] Samsung SNDS100 Eval. Board...
>
>
> Hi Jay,
>
> Actually I am trying to run eCos on SNDS100, but still failed until now.
> Maybe you can give me some help. My goal is to build a test program of
> ROM-startup version, which can be burned directly into flash memory. I
> don't need RAM version. If I choose default template for SNDS100
> platform and change startup type to ROM, the application still can not
> run. I guess it is still of RAM-startup version. However, if I choose
> "redboot" template and change startup type to ROM, the binary can run
> well after I directly burn it into the flash memory. But I don't need
> redboot
> and the redboot template doesn't contain eCos kernel. Can you give me some
> hints ?
>
> BTW, the UARTs in S3C4510 just support console. If you need UART with
> full modem functions, you should use S3C4530. It is almost identical to
> S3C4510
> except for UART part. The eval. board using S3C4530 is called "NBC".
>
> Thanks & Regards,
> =================
> Yao-Lu Tsai
> KCodes Corporation
>
> ----- Original Message -----
> From: "Jay Foster" <jay@systech.com>
> To: "'Grant Edwards'" <grante@visi.com>
> Cc: <ecos-discuss@sources.redhat.com>
> Sent: Wednesday, October 16, 2002 4:03 AM
> Subject: RE: [ECOS] Samsung SNDS100 Eval. Board...
>
>
> > I'm beginning a new project with the S3C4510 part and have the SNDS100
> eval
> > board running RedBoot and the hello world eCos application.  My
impression
> > of the processor are that the UARTs are feature poor (we're using
external
> > UARTs instead), but this really depends on the application.
> >
> > My SNDS100 eval board came with NO documentation.  I was able to
download
> a
> > schematic (for the old board) to get some idea of what's on it and how
to
> > configure it.
> >
> > Michael - you stated that you found a few bugs with the KS32C5000.  If
> it's
> > not too much bother could you reply with a short list or point me to the
> > errata (if there is any) on the Samsung web site?
> >
> > Jay Foster
> > jay at systech dot com
> >
> > -----Original Message-----
> > From: Grant Edwards [mailto:grante@visi.com]
> > Sent: Tuesday, October 15, 2002 11:29 AM
> > To: Jones, Michael
> > Cc: eCos Discussion (E-Mail)
> > Subject: Re: [ECOS] Samsung SNDS100 Eval. Board...
> >
> >
> > On Tue, Oct 15, 2002 at 01:58:53PM +0200, Jones, Michael wrote:
> >
> > > Has anybody used the Samsung SNDS100 Eval. Board ?
> >
> > Hi Michael,
> >
> > I've used an older version with a KS32C5000 on it.
> >
> > > Any impressions regarding this processor?
> >
> > We liked the peripheral set, but support from Samsung can be
> > slow and difficult to get.  We've found a few bugs in some of
> > the peripherals that we've been able to work around.
> >
> > Sharp has some new parts out that look pretty nice:
> >
> >  http://smaecom1.sharpsec.com/sma/products/MCUSoC
> >
> > --
> > Grant Edwards
> > grante@visi.com
> >
> > --
> > 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
>
> --
> 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]