[ECOS] Linux synthetic target build errors

[ECOS] Linux synthetic target build errors

[Aziz Bodal]

I am trying to build a linux synthetic target using the default
package configuration however I am getting the following build errors.
I have an Ubuntu 9.10 build.

Any help would be much appreciated.

Thank you.
Aziz

sh -c "export PATH=/usr/bin:$PATH; unset GDBTK_LIBRARY; unset
GCC_EXEC_PREFIX; export
ECOS_REPOSITORY=/home/ecos/ecos/ecos-3.0/packages; make -j1
--directory /home/ecos/ecos/ecos-3.0/tools/bin/test4_build"

make: Entering directory `/home/ecos/ecos/ecos-3.0/tools/bin/test4_build'
make -r -C hal/common/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/common/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/common/v3_0'
make -r -C io/common/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/common/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/common/v3_0'
make -r -C io/serial/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/serial/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/serial/v3_0'
make -r -C infra/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/infra/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/infra/v3_0'
make -r -C kernel/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/kernel/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/kernel/v3_0'
make -r -C services/memalloc/common/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make -r -C isoinfra/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/isoinfra/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/isoinfra/v3_0'
make -r -C language/c/libc/common/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/common/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/common/v3_0'
make -r -C language/c/libc/i18n/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/i18n/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/i18n/v3_0'
make -r -C language/c/libc/setjmp/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/setjmp/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/setjmp/v3_0'
make -r -C language/c/libc/signals/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/signals/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/signals/v3_0'
make -r -C language/c/libc/startup/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/startup/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/startup/v3_0'
make -r -C language/c/libc/stdio/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/stdio/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/stdio/v3_0'
make -r -C language/c/libc/stdlib/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/stdlib/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/stdlib/v3_0'
make -r -C language/c/libc/string/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/string/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/string/v3_0'
make -r -C language/c/libc/time/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/time/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libc/time/v3_0'
make -r -C language/c/libm/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libm/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/language/c/libm/v3_0'
make -r -C io/wallclock/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/wallclock/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/wallclock/v3_0'
make -r -C error/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/error/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/error/v3_0'
make -r -C hal/synth/arch/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/synth/arch/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/synth/arch/v3_0'
make -r -C hal/synth/i386linux/v3_0 headers
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/synth/i386linux/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/synth/i386linux/v3_0'
headers finished
make -r -C services/memalloc/common/v3_0 heapgeninc.tcl
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make[1]: `heapgeninc.tcl' is up to date.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make -r -C services/memalloc/common/v3_0 heaps.cxx
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make[1]: `heaps.cxx' is up to date.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/services/memalloc/common/v3_0'
make -r -C hal/common/v3_0 build
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/common/v3_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/hal/common/v3_0'
make -r -C io/common/v3_0 build
make[1]: Entering directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/common/v3_0'
gcc -c  -I/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include
-I/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0
-I/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src
-I/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/tests -I.
-I/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src/
-finline-limit=7000 -Wall -Wpointer-arith  -Wundef
-Woverloaded-virtual -Wno-write-strings -g -O2 -ffunction-sections
-fdata-sections -fno-rtti -fno-exceptions -Wp,-MD,src/ioinit.tmp -o
src/io_common_ioinit.o
/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src/ioinit.cxx
In file included from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/kernel/kapidata.h:84,
                 from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/kernel/kapi.h:673,
                 from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/drv_api.h:73,
                 from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/io/devtab.h:59,
                 from
/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src/ioinit.cxx:53:
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_intr.h:168:5:
warning: "CYGINT_HAL_FRV_MEM_REAL_REGION_TOP" is not defined
In file included from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_tables.h:61,
                 from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/io/devtab.h:60,
                 from
/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src/ioinit.cxx:53:
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_arch.h:59:5:
warning: "CYGINT_HAL_FRV_ARCH_FR500" is not defined
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_arch.h:62:7:
warning: "CYGINT_HAL_FRV_ARCH_FR400" is not defined
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_arch.h:66:2:
error: #error No architecture defined?
In file included from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_tables.h:61,
                 from
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/io/devtab.h:60,
                 from
/home/ecos/ecos/ecos-3.0/packages/io/common/v3_0/src/ioinit.cxx:53:
/home/ecos/ecos/ecos-3.0/tools/bin/test4_install/include/cyg/hal/hal_arch.h:126:
error: ‘_NGPR’ was not declared in this scope
make[1]: Leaving directory
`/home/ecos/ecos/ecos-3.0/tools/bin/test4_build/io/common/v3_0'
make[1]: *** [src/ioinit.o.d] Error 1
make: Leaving directory `/home/ecos/ecos/ecos-3.0/tools/bin/test4_build'
make: *** [build] Error 2

--
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: Linux synthetic target build errors

[John Dallaway]

Hi Aziz

Aziz Bodal wrote:

> I am trying to build a linux synthetic target using the default
> package configuration however I am getting the following build errors.
> I have an Ubuntu 9.10 build.
> 
> Any help would be much appreciated.

Firstly, your build tree looks confused. You have some references to the
FR-V architecture lying around. I suggest you start by saving your eCos
configuration under a new name within the eCos Configuration Tool (File
-> Save As...).

Secondly, for correct operation of the synthetic target with eCos 3.0
sources on recent Ubuntu installations, you will need to add the
"-fno-stack-protector" compiler switch to the list of switches in the
CYGBLD_GLOBAL_CFLAGS configuration option (Configuration -> Global build
options -> Global compiler flags). This is no-longer necessary with the
current eCos CVS sources.

I hope this helps...

John Dallaway
eCos maintainer

-- 
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] Building redboot without Ethernet fails

[Mikhail Matusov]

Hi all,

I've started with redboot template in the configuration tool and disabled 
everything related to Ethernet I could find, however CYGPKG_IO_ETH_DRIVERS 
is still enabled and produces errors because other things are now missing. 
Is there a way to make CYGPKG_IO_ETH_DRIVERS undefined through the 
configuration tool?

Thanks,
/Mikhail 


-- 
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] Building redboot without Ethernet fails

[Mikhail Matusov]

Figured it out myself. Right click on the Common Ethernet Support package in 
the configuration tool and Unload.

/Mikhail



> Hi all,
>
> I've started with redboot template in the configuration tool and disabled 
> everything related to Ethernet I could find, however CYGPKG_IO_ETH_DRIVERS 
> is still enabled and produces errors because other things are now missing. 
> Is there a way to make CYGPKG_IO_ETH_DRIVERS undefined through the 
> configuration tool?
>
> Thanks,
> /Mikhail
>
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
> 


-- 
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: Linux synthetic target build errors

[Aziz Bodal]

I went by your recommendations, and got the Linux synthetic target it
to work. Your advise was right on the mark, thank!

I am writing a paper for a Real-time OS class on comparing the
scheduling algorithms of two real-time operating systems. The RTOS
systems I am comparing are eCOS and FreeRTOS. I need to run a
multi-threaded application and compare some statistics.

I am a newbie at this so please excuse my ignorance. I am looking for
a good emulator so that I can compare these two operating systems. I
have basically set up an Ubuntu virtual environment on my Windows
machine. I am trying to use QEMU as my emulator, but I don't
know/understand how to push the eCos on to it. I have tried using GDB
from Ubuntu to connect to QEMU with little success. I don't quite
understand how to make an image of eCOS OS to that I can have it run
on QEMU (or any other system). The command for using GDB on QEMU is
"qemu.exe -s -S -L . -m 128 -hda linux.img -M pc %*" however this
looks like it using a Linux image.

I basically need some guidance on:

1- What is a good emulator I can use with eCOS
2- How to push eCOS onto the emulator

Thanks!
Aziz

On Mon, Apr 26, 2010 at 9:23 AM, John Dallaway <john@dallaway.org.uk> wrote:
> Hi Aziz
>
> Aziz Bodal wrote:
>
>> I am trying to build a linux synthetic target using the default
>> package configuration however I am getting the following build errors.
>> I have an Ubuntu 9.10 build.
>>
>> Any help would be much appreciated.
>
> Firstly, your build tree looks confused. You have some references to the
> FR-V architecture lying around. I suggest you start by saving your eCos
> configuration under a new name within the eCos Configuration Tool (File
> -> Save As...).
>
> Secondly, for correct operation of the synthetic target with eCos 3.0
> sources on recent Ubuntu installations, you will need to add the
> "-fno-stack-protector" compiler switch to the list of switches in the
> CYGBLD_GLOBAL_CFLAGS configuration option (Configuration -> Global build
> options -> Global compiler flags). This is no-longer necessary with the
> current eCos CVS sources.
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
>

-- 
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: Linux synthetic target build errors

[Grant Edwards]

On 2010-05-01, Aziz Bodal <azizbodal@gmail.com> wrote:

> I am writing a paper for a Real-time OS class on comparing the
> scheduling algorithms of two real-time operating systems. The RTOS
> systems I am comparing are eCOS and FreeRTOS. I need to run a
> multi-threaded application and compare some statistics.
>
> I am a newbie at this so please excuse my ignorance. I am looking for
> a good emulator so that I can compare these two operating systems.

Qemu works nicely for eCos.

I found the easiest way to to it was to create a bootable CD ISO image
and then tell Qemu to boot from that.

Build your application using "grub" startup mode.

Then you can use the shellscript below to run it.  The script creates
the bootable CD containing the grub bootloader and the eCos
application specified on the commandline.  Then it runs Qemu using
that CD image.

------------------------------runit.sh------------------------------
#!/bin/bash
#set -x

# a shell script to run in the Qemu PC emulator an eCos
# application that's been built with "Grub" startup mode for the
# pc_rltk8239 target.
#
# The program to be run is $1.  It runs Qemu with the no-graphics
# option and with a single serial port connected to a telnet
# server socket.
#
# An instance of the "aterm" X11 terminal emulator is started with
# telnet command to connect to that virtual serial port.
#
# TUN/TAP networking is used to create a point-to-point Ethernet link
# to the virtual machine.  The host end is 172.16.0.1, so you should
# configure the eCos build to use a static 172.16.0.x network address.
#
# The script could be modified to bridge the virtual TAP interface 
# with a physcial interface if you want to make the virtual machine
# accessible from other hosts.  Or you could start a DHCP server on 
# the TAP interface so that you don't have to build apps with static
# IP configurations.

# set this to point to your grub el torito stage 2 file
ElToritoStage2=/lib/grub/i386-pc/stage2_eltorito

function StartQemu {
  # create a TAP interface belonging to the user
  User=$USER
  TAP=$(sudo /usr/bin/tunctl -b -u $User)
  sudo /sbin/ifconfig $TAP 172.16.0.1 promisc up
  # try to load the kqemu module to speed up emulation
  sudo /sbin/modprobe kqemu
  # start the emulator using the TAP interface we created above
  qemu -net nic,model=rtl8139  -net tap,ifname=$TAP,script=no -nographic $*
  # remove the TAP interface
  sudo /usr/bin/tunctl -d $TAP
  }

test -f $ElToritoStage2 || { echo "grub el torito stage 2 file not found"; exit 1; }

test -z "$TEMP" && TEMP=/tmp

# create a bootable ISO image with Grub configured to load the program

ProgPath="$1"
Prog=$(basename "$ProgPath")
Iso=$TEMP/grub-$$.iso
Tree=$TEMP/grub-$$-tree

# we want to end up with an ISO image with this structure:
#
# /
# |-- boot
# |   `-- grub
# |       |-- menu.lst
# |       `-- stage2_eltorito
# `-- eCosApplication

# create the empty directry "tree" (only has the one branch)
mkdir -p $Tree/boot/grub

# copy Grub stage2 file
cp $ElToritoStage2 $Tree/boot/grub

# create Grub configuration file that loads program
cat >$Tree/boot/grub/menu.lst <<EOF
serial --unit=0 --speed=115200
terminal --timeout=2 serial console
default 0
timeout 1
title  /$Prog
kernel /$Prog
EOF

# application goes in "root" directory, and stripping it will
# speed up loading
cp $ProgPath $Tree
strip $Tree/$Prog 

# create the bootable ISO9660 image
mkisofs -quiet -R -b boot/grub/stage2_eltorito -no-emul-boot \
   -boot-load-size 4 -boot-info-table -o $Iso $Tree
   
# done with the tree
rm -rf $Tree

# start a terminal that will telnet to the virtual machine's serial port
(sleep 0.5; aterm -title "eCos Serial 0" -name "eCos Serial 0" -e telnet localhost 9876)&

# start the emulator
StartQemu -boot cdrom -cdrom $Iso -serial telnet:localhost:9876,server

# clean up
rm -rf $Iso
--------------------------------------------------------------------


-- 
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: Linux synthetic target build errors

[Aziz Bodal]

I think I have most of the pieces in place (grub, qemu, kqemu, etc).

What parameter do I need to pass to the shell script (runit.sh) when running it?

Thanks!
Aziz

On Sat, May 1, 2010 at 12:32 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2010-05-01, Aziz Bodal <azizbodal@gmail.com> wrote:
>
>> I am writing a paper for a Real-time OS class on comparing the
>> scheduling algorithms of two real-time operating systems. The RTOS
>> systems I am comparing are eCOS and FreeRTOS. I need to run a
>> multi-threaded application and compare some statistics.
>>
>> I am a newbie at this so please excuse my ignorance. I am looking for
>> a good emulator so that I can compare these two operating systems.
>
> Qemu works nicely for eCos.
>
> I found the easiest way to to it was to create a bootable CD ISO image
> and then tell Qemu to boot from that.
>
> Build your application using "grub" startup mode.
>
> Then you can use the shellscript below to run it.  The script creates
> the bootable CD containing the grub bootloader and the eCos
> application specified on the commandline.  Then it runs Qemu using
> that CD image.
>
> ------------------------------runit.sh------------------------------
> #!/bin/bash
> #set -x
>
> # a shell script to run in the Qemu PC emulator an eCos
> # application that's been built with "Grub" startup mode for the
> # pc_rltk8239 target.
> #
> # The program to be run is $1.  It runs Qemu with the no-graphics
> # option and with a single serial port connected to a telnet
> # server socket.
> #
> # An instance of the "aterm" X11 terminal emulator is started with
> # telnet command to connect to that virtual serial port.
> #
> # TUN/TAP networking is used to create a point-to-point Ethernet link
> # to the virtual machine.  The host end is 172.16.0.1, so you should
> # configure the eCos build to use a static 172.16.0.x network address.
> #
> # The script could be modified to bridge the virtual TAP interface
> # with a physcial interface if you want to make the virtual machine
> # accessible from other hosts.  Or you could start a DHCP server on
> # the TAP interface so that you don't have to build apps with static
> # IP configurations.
>
> # set this to point to your grub el torito stage 2 file
> ElToritoStage2=/lib/grub/i386-pc/stage2_eltorito
>
> function StartQemu {
>  # create a TAP interface belonging to the user
>  User=$USER
>  TAP=$(sudo /usr/bin/tunctl -b -u $User)
>  sudo /sbin/ifconfig $TAP 172.16.0.1 promisc up
>  # try to load the kqemu module to speed up emulation
>  sudo /sbin/modprobe kqemu
>  # start the emulator using the TAP interface we created above
>  qemu -net nic,model=rtl8139  -net tap,ifname=$TAP,script=no -nographic $*
>  # remove the TAP interface
>  sudo /usr/bin/tunctl -d $TAP
>  }
>
> test -f $ElToritoStage2 || { echo "grub el torito stage 2 file not found"; exit 1; }
>
> test -z "$TEMP" && TEMP=/tmp
>
> # create a bootable ISO image with Grub configured to load the program
>
> ProgPath="$1"
> Prog=$(basename "$ProgPath")
> Iso=$TEMP/grub-$$.iso
> Tree=$TEMP/grub-$$-tree
>
> # we want to end up with an ISO image with this structure:
> #
> # /
> # |-- boot
> # |   `-- grub
> # |       |-- menu.lst
> # |       `-- stage2_eltorito
> # `-- eCosApplication
>
> # create the empty directry "tree" (only has the one branch)
> mkdir -p $Tree/boot/grub
>
> # copy Grub stage2 file
> cp $ElToritoStage2 $Tree/boot/grub
>
> # create Grub configuration file that loads program
> cat >$Tree/boot/grub/menu.lst <<EOF
> serial --unit=0 --speed=115200
> terminal --timeout=2 serial console
> default 0
> timeout 1
> title  /$Prog
> kernel /$Prog
> EOF
>
> # application goes in "root" directory, and stripping it will
> # speed up loading
> cp $ProgPath $Tree
> strip $Tree/$Prog
>
> # create the bootable ISO9660 image
> mkisofs -quiet -R -b boot/grub/stage2_eltorito -no-emul-boot \
>   -boot-load-size 4 -boot-info-table -o $Iso $Tree
>
> # done with the tree
> rm -rf $Tree
>
> # start a terminal that will telnet to the virtual machine's serial port
> (sleep 0.5; aterm -title "eCos Serial 0" -name "eCos Serial 0" -e telnet localhost 9876)&
>
> # start the emulator
> StartQemu -boot cdrom -cdrom $Iso -serial telnet:localhost:9876,server
>
> # clean up
> rm -rf $Iso
> --------------------------------------------------------------------
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

--
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: Linux synthetic target build errors

[Aziz Bodal]

I think I have most of the pieces in place (grub, qemu, kqemu, etc).

What parameter do I need to pass to the shell script (runit.sh) when running it?

Thanks!
Aziz

On Sat, May 1, 2010 at 12:32 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2010-05-01, Aziz Bodal <azizbodal@gmail.com> wrote:
>
>> I am writing a paper for a Real-time OS class on comparing the
>> scheduling algorithms of two real-time operating systems. The RTOS
>> systems I am comparing are eCOS and FreeRTOS. I need to run a
>> multi-threaded application and compare some statistics.
>>
>> I am a newbie at this so please excuse my ignorance. I am looking for
>> a good emulator so that I can compare these two operating systems.
>
> Qemu works nicely for eCos.
>
> I found the easiest way to to it was to create a bootable CD ISO image
> and then tell Qemu to boot from that.
>
> Build your application using "grub" startup mode.
>
> Then you can use the shellscript below to run it.  The script creates
> the bootable CD containing the grub bootloader and the eCos
> application specified on the commandline.  Then it runs Qemu using
> that CD image.
>
> ------------------------------runit.sh------------------------------
> #!/bin/bash
> #set -x
>
> # a shell script to run in the Qemu PC emulator an eCos
> # application that's been built with "Grub" startup mode for the
> # pc_rltk8239 target.
> #
> # The program to be run is $1.  It runs Qemu with the no-graphics
> # option and with a single serial port connected to a telnet
> # server socket.
> #
> # An instance of the "aterm" X11 terminal emulator is started with
> # telnet command to connect to that virtual serial port.
> #
> # TUN/TAP networking is used to create a point-to-point Ethernet link
> # to the virtual machine.  The host end is 172.16.0.1, so you should
> # configure the eCos build to use a static 172.16.0.x network address.
> #
> # The script could be modified to bridge the virtual TAP interface
> # with a physcial interface if you want to make the virtual machine
> # accessible from other hosts.  Or you could start a DHCP server on
> # the TAP interface so that you don't have to build apps with static
> # IP configurations.
>
> # set this to point to your grub el torito stage 2 file
> ElToritoStage2=/lib/grub/i386-pc/stage2_eltorito
>
> function StartQemu {
>  # create a TAP interface belonging to the user
>  User=$USER
>  TAP=$(sudo /usr/bin/tunctl -b -u $User)
>  sudo /sbin/ifconfig $TAP 172.16.0.1 promisc up
>  # try to load the kqemu module to speed up emulation
>  sudo /sbin/modprobe kqemu
>  # start the emulator using the TAP interface we created above
>  qemu -net nic,model=rtl8139  -net tap,ifname=$TAP,script=no -nographic $*
>  # remove the TAP interface
>  sudo /usr/bin/tunctl -d $TAP
>  }
>
> test -f $ElToritoStage2 || { echo "grub el torito stage 2 file not found"; exit 1; }
>
> test -z "$TEMP" && TEMP=/tmp
>
> # create a bootable ISO image with Grub configured to load the program
>
> ProgPath="$1"
> Prog=$(basename "$ProgPath")
> Iso=$TEMP/grub-$$.iso
> Tree=$TEMP/grub-$$-tree
>
> # we want to end up with an ISO image with this structure:
> #
> # /
> # |-- boot
> # |   `-- grub
> # |       |-- menu.lst
> # |       `-- stage2_eltorito
> # `-- eCosApplication
>
> # create the empty directry "tree" (only has the one branch)
> mkdir -p $Tree/boot/grub
>
> # copy Grub stage2 file
> cp $ElToritoStage2 $Tree/boot/grub
>
> # create Grub configuration file that loads program
> cat >$Tree/boot/grub/menu.lst <<EOF
> serial --unit=0 --speed=115200
> terminal --timeout=2 serial console
> default 0
> timeout 1
> title  /$Prog
> kernel /$Prog
> EOF
>
> # application goes in "root" directory, and stripping it will
> # speed up loading
> cp $ProgPath $Tree
> strip $Tree/$Prog
>
> # create the bootable ISO9660 image
> mkisofs -quiet -R -b boot/grub/stage2_eltorito -no-emul-boot \
>   -boot-load-size 4 -boot-info-table -o $Iso $Tree
>
> # done with the tree
> rm -rf $Tree
>
> # start a terminal that will telnet to the virtual machine's serial port
> (sleep 0.5; aterm -title "eCos Serial 0" -name "eCos Serial 0" -e telnet localhost 9876)&
>
> # start the emulator
> StartQemu -boot cdrom -cdrom $Iso -serial telnet:localhost:9876,server
>
> # clean up
> rm -rf $Iso
> --------------------------------------------------------------------
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

--
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: Linux synthetic target build errors

[Grant Edwards]

On 2010-05-03, Aziz Bodal <azizbodal@gmail.com> wrote:

> I think I have most of the pieces in place (grub, qemu, kqemu, etc).
>
> What parameter do I need to pass to the shell script (runit.sh) when
> running it?

The filename of the program you want to run:

>> # The program to be run is $1.

-- 
Grant



-- 
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: Linux synthetic target build errors

[Aziz Bodal]

I am able to get the grub to load, however I am not able to get my
program to run. My program is a compiled hello world application.

I see the option of my program (a.out) from GRUB boot loader but when
I select it, I get:

Error 13: Invalid or unsupported executable format.... Press any key
to continue...

Below is the output when I execute runit.sh:

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
QEMU waiting for connection on: telnet:[::1]:9876,server
QEMU 0.11.0 monitor - type 'help' for more information
(qemu) info kvm
kvm support: disabled
(qemu) kvm support enabled
unknown command: 'kvm'
(qemu) lsmod|grep kvm
unknown command: 'lsmod|grep'
(qemu) q
Set 'tap0' nonpersistent

I apologize for my ignorance, but I am not quite clear on how the eCos
operating system gets loaded. Is it compiled into the program? How
does QEMU know what architecture to emulate?

Thanks.
Aziz


On Sun, May 2, 2010 at 10:59 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2010-05-03, Aziz Bodal <azizbodal@gmail.com> wrote:
>
>> I think I have most of the pieces in place (grub, qemu, kqemu, etc).
>>
>> What parameter do I need to pass to the shell script (runit.sh) when
>> running it?
>
> The filename of the program you want to run:
>
>>> # The program to be run is $1.
>
> --
> Grant
>
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

-- 
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: Linux synthetic target build errors

[Grant Edwards]

On 2010-05-04, Aziz Bodal <azizbodal@gmail.com> wrote:

> I am able to get the grub to load,

That's 90% of the battle.

> however I am not able to get my program to run. My program is a
> compiled hello world application.
>
> I see the option of my program (a.out) from GRUB boot loader but when
> I select it, I get:
>
> Error 13: Invalid or unsupported executable format.... Press any key
> to continue...

What format is your application?  It should a statically linked ELF
file:

$ file server.elf
server.elf: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped

> Below is the output when I execute runit.sh:
>
> open /dev/kvm: No such file or directory
> Could not initialize KVM, will disable KVM support
> QEMU waiting for connection on: telnet:[::1]:9876,server
> QEMU 0.11.0 monitor - type 'help' for more information
> (qemu) info kvm
> kvm support: disabled
> (qemu) kvm support enabled
> unknown command: 'kvm'
> (qemu) lsmod|grep kvm
> unknown command: 'lsmod|grep'
> (qemu) q
> Set 'tap0' nonpersistent
>
> I apologize for my ignorance, but I am not quite clear on how the
> eCos operating system gets loaded. Is it compiled into the program?

Yes.  eCos is a library that is linked with the application object
files to produce a statically linke executable ELF format file that
includes the OS and application.

> How does QEMU know what architecture to emulate?

That is configured when you build qemu.  If you want to see the list
of machines that your particular build knows about do this:

  $ qemu -M ?
  Supported machines are:
  pc         Standard PC (default)
  isapc      ISA-only PC

Your copy of qemu is emulating the correct machine, otherwise grub
wouldn't run at all.

-- 
Grant Edwards               grant.b.edwards        Yow! UH-OH!!  We're out
                                  at               of AUTOMOBILE PARTS and
                              gmail.com            RUBBER GOODS!


-- 
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: Linux synthetic target build errors

[Grant Edwards]

On Thu, May 06, 2010 at 09:34:33AM -0500, Aziz Bodal wrote:

> My file is statically linked. I ran the command $ file hello.elf and
> I got: hello.elf: ELF 32-bit LSB executable, Intel 80386, version 1
> (SYSV), statically linked, not stripped

I tried your hello.elf program and got the same results you did:

 1) Qemu boots up OK

 2) GRUB runs OK

 3) When GRUB attempts to load hello.elf I get

         Booting '/hello.elf'

       kernel /hello.elf

       Error 13: Invalid or unsupported executable format

       Press any key to continue...

There must be something different in your eCos configuration, but I'm
not sure what to check other than making sure you've set
CYG_HAL_STARTUP to GRUB.

> I am stumped! I appreciate the help.

Probably the next things to try are:

 1) Try my server.elf to verify that your ISO/GRUB combination is
    working (I'm pretty sure it is).

 2) Compare your eCos configuration with mine (or just try using
    my configuration).

You can find the following files at 

 http://www.panix.com/~grante/files/ecos/

  server.elf
  
    A sample application that you can run using runit.sh.  It waits
    for an SSL encrypted connection to TCP port 7654 and then echoes
    data received on that connection.  This application has a
    hard-coded IP address of 172.16.0.99.  Once it's running, you can
    test it by doing:
  
     openssl s_client -connect 172.16.0.99:7654
  
  newtree-pc_8139.sh
   
    The shell script used to configure eCos for use with the above
    application and runit.sh script.
  
  ecos.ecc-pc_8139
  
    The ecos.ecc file created by the newtree-pc_8139.sh script (used
    to build eCos used by server.elf).

The copy of eCos that I used for this is probably almost two years
old, so it could be that something in eCos has changed.

-- 
Grant

-- 
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: Linux synthetic target build errors

[Aziz Bodal]

Thank you, thank you, thank you!

I was able to successfully run your server.elf, which lead me to look
at your newtree-pc_8139.sh
(http://www.panix.com/~grante/files/ecos/newtree-pc_8139.sh)

I noticed that in your shell script, the "cdl_option CYG_HAL_STARTUP
{user_value GRUB}" where as my configuration that was generated using
the default i386 template had the the Startup Type (eCos HAL\i386
architecture\i386 PC Target\Startup type) as RAM". I changed this to
GRUB, rebuild my libraries (Build>Library), rebuild my hello.c
application and that did the trick. I was able to run the runit.sh
file and get QEMU to boot and execute my hello world application.

Now to get some real work done with eCos!

Thank you!


On Thu, May 6, 2010 at 12:24 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On Thu, May 06, 2010 at 09:34:33AM -0500, Aziz Bodal wrote:
>
>> My file is statically linked. I ran the command $ file hello.elf and
>> I got: hello.elf: ELF 32-bit LSB executable, Intel 80386, version 1
>> (SYSV), statically linked, not stripped
>
> I tried your hello.elf program and got the same results you did:
>
>  1) Qemu boots up OK
>
>  2) GRUB runs OK
>
>  3) When GRUB attempts to load hello.elf I get
>
>         Booting '/hello.elf'
>
>       kernel /hello.elf
>
>       Error 13: Invalid or unsupported executable format
>
>       Press any key to continue...
>
> There must be something different in your eCos configuration, but I'm
> not sure what to check other than making sure you've set
> CYG_HAL_STARTUP to GRUB.
>
>> I am stumped! I appreciate the help.
>
> Probably the next things to try are:
>
>  1) Try my server.elf to verify that your ISO/GRUB combination is
>    working (I'm pretty sure it is).
>
>  2) Compare your eCos configuration with mine (or just try using
>    my configuration).
>
> You can find the following files at
>
>  http://www.panix.com/~grante/files/ecos/
>
>  server.elf
>
>    A sample application that you can run using runit.sh.  It waits
>    for an SSL encrypted connection to TCP port 7654 and then echoes
>    data received on that connection.  This application has a
>    hard-coded IP address of 172.16.0.99.  Once it's running, you can
>    test it by doing:
>
>     openssl s_client -connect 172.16.0.99:7654
>
>  newtree-pc_8139.sh
>
>    The shell script used to configure eCos for use with the above
>    application and runit.sh script.
>
>  ecos.ecc-pc_8139
>
>    The ecos.ecc file created by the newtree-pc_8139.sh script (used
>    to build eCos used by server.elf).
>
> The copy of eCos that I used for this is probably almost two years
> old, so it could be that something in eCos has changed.
>
> --
> Grant
>

--
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: Linux synthetic target build errors

[Grant Edwards]

On 2010-05-08, Aziz Bodal <azizbodal@gmail.com> wrote:
> Thank you, thank you, thank you!
>
> I was able to successfully run your server.elf, which lead me to look
> at your newtree-pc_8139.sh
> (http://www.panix.com/~grante/files/ecos/newtree-pc_8139.sh)
>
> I noticed that in your shell script, the "cdl_option CYG_HAL_STARTUP
> {user_value GRUB}" where as my configuration that was generated using
> the default i386 template had the the Startup Type (eCos HAL\i386
> architecture\i386 PC Target\Startup type) as RAM".

Um, that's why I told you twice to build the application using "grub"
startup mode. ;)

> Now to get some real work done with eCos!

Good luck.

-- 
Grant Edwards               grant.b.edwards        Yow! Oh my GOD -- the
                                  at               SUN just fell into YANKEE
                              gmail.com            STADIUM!!


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