public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Chris Holgate <chris@zynaptic.com>
To: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Testing eCos 3.0 beta 1 on STM3210E-EVAL board.
Date: Tue, 24 Feb 2009 17:23:00 -0000	[thread overview]
Message-ID: <49A42D15.3040008@zynaptic.com> (raw)
In-Reply-To: <49A2910C.30707@zynaptic.com>

All the following STM32 tests worked as expected - although I had to use
the 'net' template because 'all' wouldn't fit into RAM!

The automated install worked for me, as did the configtool package
import and the built-in help which told me how to implement it.

The one configtool quirk I did notice was that while trying to run the
tests from the GUI, they would occasionally fail with 'file not found'.
 This is all new to me, since i usually use GDB from the command line.
The only file I can think of which 'comes and goes' in this way would be
/dev/ttyS0 - or more specifically the lock on it - so I was wondering if
this behaviour may be caused by GDB not releasing /dev/ttyS0 properly
between tests.  Is this something anyone else has seen?

Chris.

Chris Holgate wrote:
> Hi folks,
> 
> I'm just about to grab the beta release to test on the STM3210E-EVAL
> target.  My host OS is OpenSuse 11.0 (x86-64).  I plan to run all the
> standard tests via remote serial GDB using the RAM memory layout and a
> new Redboot build generated from the beta release code.
> 
> In addition to running the standard tests I plan to do the following
> board specific tests:
> 
> 1) Simple SPI loopback tests for SPI bus 2 and SPI bus 3.
> 2) M25Pxx SPI flash soak test using SPI bus 1.
> 3) Test external interrupts (single pin only) using a custom add-on
> board which I happen to have.
> 
> In addition, I've been working on a USB driver which obviously wasn't
> ready for this release.  Since the obvious thing to do is release it as
> an add-on package when it is ready, I'm going to try and package up what
> I've currently got to test the following:
> 
> 4) The configtool package import flow.
> 5) The USB register map in the proposed release.
> 6) My ability to understand the instructions on how to create a new
> package(!).
> 
> Chris.
> 


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

  reply	other threads:[~2009-02-24 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 12:05 Chris Holgate
2009-02-24 17:23 ` Chris Holgate [this message]
2009-02-24 18:42   ` Sergei Gavrikov
2009-03-09 16:31   ` [ECOS] File not found when running tests [ was Re: Testing eCos 3.0 beta 1 on STM3210E-EVAL board. ] John Dallaway
2009-03-09 17:24     ` Sergei Gavrikov
2009-03-09 19:38       ` [ECOS] Re: File not found when running tests John Dallaway
2009-03-09 20:18         ` Sergei Gavrikov
2009-03-10  9:28           ` Sergei Gavrikov
2009-03-10 10:58         ` Chris Holgate
2009-03-10 11:22           ` John Dallaway

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A42D15.3040008@zynaptic.com \
    --to=chris@zynaptic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).