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

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

[Chris Holgate]

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

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

[Chris Holgate]

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

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

[Sergei Gavrikov]

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

[ECOS] File not found when running tests [ was Re: Testing eCos 3.0 beta 1 on STM3210E-EVAL board. ]

[John Dallaway]

Chris Holgate wrote:

> 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 have been testing against target pc_i82559 with a CentOS 5 host and
have not observed this issue. Has anyone else seen this?

John Dallaway

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

Re: [ECOS] File not found when running tests [ was Re: Testing eCos 3.0 beta 1 on STM3210E-EVAL board. ]

[Sergei Gavrikov]

John Dallaway wrote:
> Chris Holgate wrote:
> 
> > 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 have been testing against target pc_i82559 with a CentOS 5 host and
> have not observed this issue. Has anyone else seen this?

I noticed same sporadic messages on Ununtu 8.04.02. Target olpch2294,
GDB port was /dev/ttyUSB0. But when I tried same build and same
configtool on Ubuntu 7.10 I never got the errors. I think that my 8.04
disto has mixed C++ environment. I need (and it is istalled) both
libstdc++ (5 and 6) packages. And my old Ubuntu 7.10 uses libstdc++.so.5
only.

In my environment on Ubuntu 8.04.02 I've got the dependences

~$ ldd /opt/ecos/ecos-3.0b1/tools/bin/configtool | grep stdc++
	libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xb795e000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb73c4000)

~$ ldd /opt/ecos/ecos-3.0b1/tools/bin/ecosconfig | grep stdc++
	libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xb7e5a000)

I thought that old release has not the issue that it uses more even
environment. But this is just a guesswork.

CLI GDB session via serial connection work just fine on both distos.


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

[ECOS] Re: File not found when running tests

[John Dallaway]

Hi Sergei

Sergei Gavrikov wrote:

> John Dallaway wrote:
>> Chris Holgate wrote:
>> 
>>> 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 have been testing against target pc_i82559 with a CentOS 5 host and
>> have not observed this issue. Has anyone else seen this?
> 
> I noticed same sporadic messages on Ununtu 8.04.02. Target olpch2294,
> GDB port was /dev/ttyUSB0. But when I tried same build and same
> configtool on Ubuntu 7.10 I never got the errors. I think that my 8.04
> disto has mixed C++ environment. I need (and it is istalled) both
> libstdc++ (5 and 6) packages. And my old Ubuntu 7.10 uses libstdc++.so.5
> only.

That is interesting. Chris Holgate was using openSUSE 11.0 which is also
very recent. Could you try running some eCos tests using configtool
under strace on Ubuntu 8.04? The strace output may reveal more about the
nature of this problem.

John Dallaway

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

Re: [ECOS] Re: File not found when running tests

[Sergei Gavrikov]

On Mon, Mar 09, 2009 at 05:08:18PM +0000, John Dallaway wrote:
> Hi Sergei
> 
> Sergei Gavrikov wrote:
> 
> > John Dallaway wrote:
> >> Chris Holgate wrote:
> >> 
> >>> 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 have been testing against target pc_i82559 with a CentOS 5 host and
> >> have not observed this issue. Has anyone else seen this?
> > 
> > I noticed same sporadic messages on Ununtu 8.04.02. Target olpch2294,
> > GDB port was /dev/ttyUSB0. But when I tried same build and same
> > configtool on Ubuntu 7.10 I never got the errors. I think that my 8.04
> > disto has mixed C++ environment. I need (and it is istalled) both
> > libstdc++ (5 and 6) packages. And my old Ubuntu 7.10 uses libstdc++.so.5
> > only.
> 
> That is interesting. Chris Holgate was using openSUSE 11.0 which is also
> very recent. Could you try running some eCos tests using configtool
> under strace on Ubuntu 8.04? The strace output may reveal more about the
> nature of this problem.

John, thank you for the tip. Tonight I'll try to trace a run and then
report about my diggs.

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

Re: [ECOS] Re: File not found when running tests

[Sergei Gavrikov]

On Mon, Mar 09, 2009 at 07:23:57PM +0200, Sergei Gavrikov wrote:
> On Mon, Mar 09, 2009 at 05:08:18PM +0000, John Dallaway wrote:
> > Hi Sergei
> > 
> > Sergei Gavrikov wrote:
> > 
> > > John Dallaway wrote:
> > >> Chris Holgate wrote:
> > >> 
> > >>> 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 have been testing against target pc_i82559 with a CentOS 5 host and
> > >> have not observed this issue. Has anyone else seen this?
> > > 
> > > I noticed same sporadic messages on Ununtu 8.04.02. Target olpch2294,
> > > GDB port was /dev/ttyUSB0. But when I tried same build and same
> > > configtool on Ubuntu 7.10 I never got the errors. I think that my 8.04
> > > disto has mixed C++ environment. I need (and it is istalled) both
> > > libstdc++ (5 and 6) packages. And my old Ubuntu 7.10 uses libstdc++.so.5
> > > only.
> > 
> > That is interesting. Chris Holgate was using openSUSE 11.0 which is also
> > very recent. Could you try running some eCos tests using configtool
> > under strace on Ubuntu 8.04? The strace output may reveal more about the
> > nature of this problem.
> 
> John, thank you for the tip. Tonight I'll try to trace a run and then
> report about my diggs.

My guesswork aboud libstdc++ was wrong. I am/was sure that all arm gnu
tools in my PATH, but 'arm-eabi-gdb' does not run itself in configtool

21668 execve("arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q", "/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such file or directory)
21668 execve("/bin/arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q", "/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such file or directory)
21668 execve("/usr/bin/arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q", "/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such file or directory)
21668 write(2, "exec error - No such file or dir"..., 39) = 39
...

Why I was sure? I sourced /opt/ecos/ecosenv.sh before to run configtool.
The 'which' found arm-eabi-gdb. I checked it.

... Just for fun I did fulfil

sudo ln -f -s /opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb /usr/bin

then re-run configtool... and the problem went away.

Then I did remove that symlink and reduce my PATH variable to a classic
path

export PATH=/usr/sbin:/usr/bin:/sbin:/bin
. /opt/ecos/ecosenv.sh

echo $PATH
/opt/ecos/gnutools/i386-elf/bin:/opt/ecos/gnutools/arm-eabi/bin:/opt/ecos/ecos-3.0b1/tools/bin:/usr/sbin:/usr/bin:/sbin:/bin

which arm-eabi-gdb
/opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb

which configtool 
/opt/ecos/ecos-3.0b1/tools/bin/configtool

strace -f -o trace /opt/ecos/ecos-3.0b1/tools/bin/configtool

and the tests ran under configtool:

22084 execve("/opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q", "/opt/testing/untitled_install/te"...], [/* 39 vars */]) = 0
22084 brk(0)                            = 0x8324000

Hmm. Is it possible that my original PATH too long?

/home/sg/bin:/home/sg/ecos/gnutools/arm-eabi/bin:/home/sg/ecos/gnutools/i386-elf/bin:/home/sg/ecos/tools/bin:/opt/TclDevKit-5.0/bin:/opt/ActiveTcl-8.5/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

Once again, I sourced 'ecosenv.sh' before to run 'configtool'. I have no
ecos stuff under /usr/local. The same tools are placed under my
~/ecos/gnutools directory. And I am/was? sure that 'ecosenv.sh'
overwrites it.

My conclusion, configtool _has_no_bug_. IMHO, it should work on the
fresh-installed systems. Now, I wonder, What's about openSuSE?

Regards,

Sergei

P.S.

Once again I did think about non-existing eCos 3.0 vmware appliance for
linux. It would justify the results :-)

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

Re: [ECOS] Re: File not found when running tests

[Chris Holgate]

John Dallaway wrote:

> That is interesting. Chris Holgate was using openSUSE 11.0 which is also
> very recent. Could you try running some eCos tests using configtool
> under strace on Ubuntu 8.04? The strace output may reveal more about the
> nature of this problem.

I ran configtool under strace on openSUSE 11.0 and have seen similar
behaviour to that reported by Sergei.  My PATH environment variable is
set up using the "ecosenv.sh" script which places the path to the ARM
tools at the front - as shown:

PATH=/zynaptic/projects/eCos/beta1/gnutools/arm-eabi/bin:/zynaptic/projects/eCos/beta1/ecos-3.0b1/tools/bin:/home/chris/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin

Tests which run successfully are exec'ed as follows:

execve("/zynaptic/projects/eCos/beta1/gnutools/arm-eabi/bin/arm-eabi-gdb",
["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = 0

Which is what I'd expect to see.

Tests which failed are exec'ed like this:

execve("arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)

execve("/bin/arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)

execve("/usr/bin/arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)

write(2, "exec error - No such file or dir"..., 39) = 39

Not only does this not start with the expected path, but the paths that
are tried do not seem to correspond to my PATH environment variable in
any way - for example I don't have the CWD in my path, but it is the
first place being searched.  All very odd.

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

[ECOS] Re: File not found when running tests

[John Dallaway]

Chris and Sergei

John Dallaway wrote:

> That is interesting. Chris Holgate was using openSUSE 11.0 which is also
> very recent. Could you try running some eCos tests using configtool
> under strace on Ubuntu 8.04? The strace output may reveal more about the
> nature of this problem.

Thank you both for your feedback. I have generated a Bugzilla issue and
attached your comments:

  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716

Chris, if you would care to create a Bugzilla account, I can add you to
the CC list for this issue.

John Dallaway

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