Re: [ECOS] Testing eCos 3.0 beta 1 on STM3210E-EVAL board.

[Sergei Gavrikov <sergei.gavrikov@gmail.com>]

On Tue, Feb 24, 2009 at 05:23:33PM +0000, Chris Holgate wrote:
> All the following STM32 tests worked as expected - although I had to use
> the 'net' template because 'all' wouldn't fit into RAM!

This is. Most of the targets have a few RAM to build tests for 'all'
template. Just to be sure that all compile itself for my targets I use
this trick

    sed -i "/ram : .*LENGTH/s/$/0/" install/lib/target.ld
    make tests

Same way I multiply RAM's length on 16 and "get" 16M instead 1M in my
case. At the least I knew that all compiled. Yes, it was surprise for me
that even hal basic test built for 'all' template do not fit into 1M

arm-eabi-size install/tests/hal/common/v3_0b1/tests/basic
   text	   data	    bss	    dec	    hex	filename
 433973	      0	 653480	1087453	 1097dd	install/tests/hal/common/v3_0b1/tests/basic

> 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?

I did meat same errors when I did try to run tests using configtool, but
I though that is because I use rare communication port /dev/ttyUSB0. I
think what if your environment is Linux, you can dig it using 'lsof':

    lsof /dev/ttyS0

Regards,

Sergei

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