gmane.os.ecos.general

Does NetBSD IPv6 honor rmx_expire?

Grant Edwards — 2012-05-24T22:03:32

Does the NetBSD IPv6 implementation honor the  rtm_rmx.rmx_expire
field in an rt_msghdr structure when IPv6 routes are added?

IOW, if the rmx_expre field is non-zero, will the network stack
automatically delete the route after the specified number of seconds?

Help with LwIP in ecos-3.0

Elad Yosef — 2012-05-24T15:27:46

Hi all I get the following Trace by GDB

(gdb) bt
#0  ~Cyg_Mboxt (this=0x80046e10) at
/localhome/cc-views/elady_Mars_SW/vobs/Mars-eCos/Mars-eCos_OS/Mars_eCos_Config_install/include/cyg/kernel/mboxt.inl:105
#1  0x80017255 in ~Cyg_Mbox (this=0x80046e10) at
/localhome/eCos/ecos-3.0/packages/kernel/v3_0/src/sync/mbox.cxx:92
#2  0x80014409 in cyg_mbox_delete (mbox=2147773968) at
/localhome/eCos/ecos-3.0/packages/kernel/v3_0/src/common/kapi.cxx:851
#3  0x80022a41 in sys_mbox_free (mbox=2147773968) at
/localhome/eCos/ecos-3.0/packages/net/lwip_tcpip/v3_0/src/ecos/sys_arch.c:108
#4  0x800282bd in netconn_delete (conn=0x80049b98) at
/localhome/eCos/ecos-3.0/packages/net/lwip_tcpip/v3_0/src/api/api_lib.c:304
#5  0x800222b5 in lwip_close (s=<value optimized out>) at
/localhome/eCos/ecos-3.0/packages/net/lwip_tcpip/v3_0/src/api/sockets.c:268

My connect fails (due to wrong IP, but that's O.k by me) so I close
the TCP socket and get the ASSERT from mboxt.inl:105
deleting mbox with messages.

How bad is it? can I ignore it?

Elad

DSR interruptible by scheduler + memory barriers

Martin Laabs — 2012-05-22T18:01:34

Hello,

unfortunately I couldn't find the answer in the documentation. If the 
scheduler runs a DSR. Can this DSR become interrupted by an other thread or 
another DSR? (Of cause an ISR can interrupt it)

The background is that I wanna share data between a thread an a DSR and 
want to know whether I have to call cyg_(un)lock_scheduler when changing 
the data.

And another question about that - how are memory barriers implemented in 
eCos? (Are they implemented at all?)
Background: I have - for example - a status bit field that is copied to a 
(ISR/DSR) shared variable in the ISR. Now - if the compiler decides to put 
this variable into a register (in the ISR function) the DSR will get the 
wrong data. I could of cause declare the variable as volatile but this 
might be a performance issue in other cases where more data is affected.

Best regards,
  Martin Laabs

Test microwindows nano-x

medamine — 2012-05-22T10:58:18

Hello every one,

I'm a new user of the microwindows library.
I used the STM3240G-EVAL. I added the framebuffer driver and it's work 
correctly

So, i try to test the nano-x librairie. I followed the procedure in this 
link. I added the framebuffer driver, linux netand the microwindows 
library in the configuration with the corresponding changes.

http://www.open-etech.com/RTOS/Debugging/index.php?page=mw

and I tried to build eCos and test the tetris demo but I got these errors

make[1]: Entering directory 
`/home/st/config_Fatfs/mw_config_build/language/c/libc/setjmp/current'
arm-eabi-gcc -c -I/home/st/config_Fatfs/mw_config_install/include 
-I/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current 
-I/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current/src 
-I/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current/tests 
-I. 
-I/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current/src/ 
-finline-limit=7000 -Wall -Wpointer-arith -Wundef -Woverloaded-virtual 
-Wno-write-strings -mcpu=cortex-m3 -mthumb -g -O2 -ffunction-sections 
-fdata-sections -fno-rtti -fno-exceptions -Wp,-MD,src/longjmp.tmp -o 
src/language_c_libc_setjmp_longjmp.o 
/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current/src/longjmp.cxx
make[1]: Leaving directory 
`/home/st/config_Fatfs/mw_config_build/language/c/libc/setjmp/current'
In file included from 
/home/st/config_Fatfs/mw_config_install/include/setjmp.h:69,
make: Leaving directory `/home/st/config_Fatfs/mw_config_build'
from 
/home/st/ecos/ecos-3.0/packages/language/c/libc/setjmp/current/src/longjmp.cxx:72:

/home/st/config_Fatfs/mw_config_install/include/cyg/posix/sigsetjmp.h:73: error: 
‘sigset_t’ does not name a type
make[1]: *** [src/longjmp.o.d] Error 1
make: *** [build] Error 2

It seams an error in the POSIX package.

If any one have any idea about the problem and what should i do?

Great Thanks.

cine castiga

2012-05-21T17:50:47

http://www.youtube.com/watch?feature=youtu.be&hl=ro&v=_Sl3Ox7RMnE
 To unsubscribe please send email to unsubscribe< at >cc.psd-prahova.ro

zImage write from Busybox

Mukund — 2012-05-16T13:18:19

Hello All,

I am facing some issue when I flash kernel from busybox and try to boot 
from redboot console.
The same kernel work correctly when I write it using "fis write" 
command. Below are the steps:

1.load kernel + ramdisk from tftp by using below commands :
 > load -r -b 0x100000 zImage -h 10.100.4.78
2.Boot with above kernel using 'exec' command
3.Write zImage from busybox console by using below commands:
 > dd if=zImage of=/dev/block/mtdblock0 bs=128k
4. reboot busybox
5. Stop on redboot
6. load kernel with the help of following command :
 > fis load nx1
 > exec

Redboot stuck while uncompressing linux.
================================================
RedBoot> fis load qnx1
... Read from 0x07ee0000-0x07eff000 at 0x0ffa0000: ..
... Read from 0x00100000-0x00900000 at 0x00540000: 
.................................................................
RedBoot> exec
entry=0x80008000, target=0x80008000
Using base address 0x00100000 and length 0x00800000
Uncompressing Linux.............
================================================

Here is my mtd partitions :
~ # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00800000 00020000 "nx1"
mtd1: 07520000 00020000 "fs1"
mtd2: 00800000 00020000 "nx2"
mtd3: 07520000 00020000 "fs2"
mtd4: 0001f000 00020000 "FIS directory"
mtd5: 00001000 00020000 "RedBoot config"

Help with pthread_cond_timedwait

Graves, Daniel (GE Healthcare — 2012-05-15T15:33:48

Hello,

I've been developing some communication software that needs to wait for a message over a serial port.  I implemented it using pthread_cond_timedwait under Linux using 2.6.34 kernel.  Basically when a message comes over the serial port the pthread_cond_timedwait is signaled.  It waits for 200ms if it is not signaled in time.  This code has worked really well in Linux, but I needed to port it over to eCos.  At that point the exact same code would timeout immediately even though the serial messages were signaling it on time.  The error 360 for ETIMEDOUT was reporting and it was clear that it wasn't waiting long enough.  As a last desperate attempt to get this to work I changed the code to use cyg_cond_timed_wait and cyg_cond_mutex from eCos.  That worked for me and timeouts were no longer occurring.  However, I would like to know what is wrong with pthread_cond_timedwait, because it seems like there is a bug.  But after looking at the code for each function they both basically end up calling Cyg_Condition_Variable's wait methods.  Below is a snippet of the code I'm referring to.  I've searched through this mailing list for any similar topics.  There was one but that one focused on clock_gettime.  Unfortunately I do not know which version of eCos I'm using as I have just joined the project where we're using eCos.  I will try to find that out.

.....
  struct timespec waittime;
  struct timeval abstime;
.....

    gettimeofday(&abstime,NULL);
   //we want to wait 200 msec before declaring timeout
    abstime.tv_usec += 2000000;

    if(abstime.tv_usec >= 1000000)
    {
      abstime.tv_sec += 1;
      abstime.tv_usec = abstime.tv_usec % 1000000;
    }
    waittime.tv_sec = abstime.tv_sec;
    waittime.tv_nsec = abstime.tv_usec*1000;
    int cond_result = pthread_cond_timedwait(&ackcond,&readlock,&waittime);
    if ( cond_result != 0 )
    {
        printf("SerialComm:Failed to set the conditional variable, error = %d\n", cond_result);
    }
    else
    {
        #if DEBUG
        printf("SerialComm:Successfully set conditional variable ackcond\n");
        #endif
    }

......

Thanks,

Daniel P Graves

Tools or commands for eCos to test footprint, startup time, and response time

Jianmei Guo — 2012-05-04T14:02:42

Hi,

Is there any tool or command available for ECOS to test footprint, 
startup time, and response time (or any other performance metrics) 
conveniently when eCos is running on different hardware platforms (e.g., 
i386 vs. Powerpc) and/or different software configurations (e.g., 2 cpu 
vs. 4 cpu)?

Another question is about the simulation of many different hardware 
platform. Now I just have several i386 PC and Apple MacBook...

Any help or suggestion would be appreciable. Thanks!


Best Regards,

Jianmei Guo, PhD
Postdoctoral Fellow
University of Waterloo
http://gsd.uwaterloo.ca/gjm

simple redboot package donot build for i386!

abhishek srivastava — 2012-05-04T03:36:55


hi
it seems that in my last post i was not clear with my question so no one responded !
just repeating the question with detailed error

i am trying to generate package "redboot" for i386 (vmware) hardware.
i have also imported "redboot_FLOOPY.ecm", made no change and tried to build library.
i got error !!! why?

the output i got after building library--


make -j4 --directory "/opt/ecos/ecos-3.0/work/redboot_build"

make: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build'
make -r -C hal/i386/arch/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/arch/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/arch/v3_0'
make -r -C hal/i386/generic/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/generic/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/generic/v3_0'
make -r -C hal/i386/pc/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/pc/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/pc/v3_0'
make -r -C hal/i386/pcmb/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/pcmb/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/pcmb/v3_0'
make -r -C io/pci/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/io/pci/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/io/pci/v3_0'
make -r -C devs/eth/amd/lancepci/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/devs/eth/amd/lancepci/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/devs/eth/amd/lancepci/v3_0'
make -r -C devs/eth/i386/pc/lancepci/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/devs/eth/i386/pc/lancepci/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/devs/eth/i386/pc/lancepci/v3_0'
make -r -C hal/common/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/common/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/common/v3_0'
make -r -C infra/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/infra/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/infra/v3_0'
make -r -C redboot/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/redboot/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/redboot/v3_0'
make -r -C isoinfra/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/isoinfra/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/isoinfra/v3_0'
make -r -C language/c/libc/string/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/language/c/libc/string/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/language/c/libc/string/v3_0'
make -r -C services/crc/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/services/crc/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/services/crc/v3_0'
make -r -C io/eth/v3_0 headers
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/io/eth/v3_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/io/eth/v3_0'
headers finished
make -r -C hal/i386/arch/v3_0 build
make[1]: Entering directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/arch/v3_0'
i386-elf-gcc -c  -I/opt/ecos/ecos-3.0/work/redboot_install/include -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0 -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/tests -I. -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src/ -finline-limit=7000 -Wall -Wpointer-arith -Wstrict-prototypes -Wundef  -Wno-write-strings -g -O2 -ffunction-sections -fdata-sections  -fno-exceptions -Wp,-MD,src/hal_misc.tmp -o src/hal_i386_arch_hal_misc.o /opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src/hal_misc.c
i386-elf-gcc -c  -I/opt/ecos/ecos-3.0/work/redboot_install/include -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0 -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/tests -I. -I/opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src/ -finline-limit=7000 -Wall -Wpointer-arith -Wstrict-prototypes -Wundef  -Wno-write-strings -g -O2 -ffunction-sections -fdata-sections  -fno-exceptions -Wp,-MD,src/redboot_linux_exec.tmp -o src/hal_i386_arch_redboot_linux_exec.o /opt/ecos/ecos-3.0/packages/hal/i386/arch/v3_0/src/redboot_linux_exec.c
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:89: recipe for target `src/hal_misc.o.d' failed
sed: can't read src/hal_misc.tmp: No such file or directory
make[1]: *** [src/hal_misc.o.d] Error 2
make[1]: *** Waiting for unfinished jobs....
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:89: recipe for target `src/redboot_linux_exec.o.d' failed
sed: can't read src/redboot_linux_exec.tmp: No such file or directory
make[1]: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build/hal/i386/arch/v3_0'
make[1]: *** [src/redboot_linux_exec.o.d] Error 2
makefile:15: recipe for target `build' failed
make: *** [build] Error 2
make: Leaving directory `/opt/ecos/ecos-3.0/work/redboot_build'



i have checked that i have all the files in "D:\cygwin\opt\ecos\ecos-3.0\packages\hal\i386\arch\v3_0\src" named "hal_misc.c,hal_syscall.c, i386_stub.c,redboot_linux_exe.c" 

any help would be appreciable


Abhishek

error in building redboot for i386

abhishek srivastava — 2012-05-02T18:29:50

i get these errors while building for package "redboot", for target i386pc (vmware). what's actually missing? it seems some file are not available for building.how to rectify it?


sed: can't read src/hal_misc.tmp: No such file or directory
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:89: recipe for target `src/hal_misc.o.d' failed
make[1]: *** [src/hal_misc.o.d] Error 2
make[1]: *** Waiting for unfinished jobs....
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:119: recipe for target `src/context.o.d' failed
sed: can't read src/context.tmp: No such file or directory
make[1]: *** [src/context.o.d] Error 2
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:89: recipe for target `src/i386_stub.o.d' failed
sed: can't read src/i386_stub.tmp: No such file or directory
make[1]: *** [src/i386_stub.o.d] Error 2
/opt/ecos/ecos-3.0/packages/pkgconf/rules.mak:89: recipe for target `src/hal_syscall.o.d' failed
sed: can't read src/hal_syscall.tmp: No such file or directory
make[1]: Leaving directory `/work/redboot_build/hal/i386/arch/v3_0'
make[1]: *** [src/hal_syscall.o.d] Error 2
makefile:15: recipe for target `build' failed
make: *** [build] Error 2
make: Leaving directory `/work/redboot_build'

 

Abhishek

Spital nou de pediatrie

2012-05-02T13:57:44

http://www.youtube.com/watch?feature=player_embedded&v=phjGxHn3uKU
 To unsubscribe please send email to unsubscribe< at >cc.psd-prahova.ro

eCos host tools for Cygwin - 120425 snapshot builds

John Dallaway — 2012-04-27T19:05:22

The prebuilt eCos host tools for Cygwin provided within the eCos 3.0
release do not work with recent Cygwin installations due to their
reliance on tcl84.dll. In response to this, I have generated new builds
of the tools which use libtcl8.5.dll. The new tools are built from
current eCos CVS sources and should otherwise exhibit the same behaviour
as the previous snapshot builds of 2011-02-09.

The new snapshot builds for Cygwin can be downloaded from the eCos ftp
site and are located in the "anoncvs" directory:

  anoncvs/ecos-tools-bin-120425.cygwin.tar.bz2

Please use a mirror site in your own geographical region to access these
files. Sites which mirror the eCos ftp area are listed at:

  http://ecos.sourceware.org/mirror.html

The eCos host tools may be extracted into the current working directory
from the downloaded archive file by using the following command at a
bash prompt:

  tar jxvf ecos-tools-bin-120425.cygwin.tar.bz2

If you are using an older Cygwin installation which does not include
libtcl8.5.dll, you should stick with the eCos host tools provided with
eCos 3.0 or with the snapshot builds of 2011-02-09.

Feedback on any remaining compatibility issues is welcome. Please report
any issues at:

  http://bugs.ecos.sourceware.org

John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john

Problem building redboot image - missing cyg/io/io.h when building fileio.c

Graeme — 2012-04-25T17:45:03

Hi all, only recently started working with Redboot/eCos.

Looks like this could be an interesting project (I have several Olimex 
LPC boards in my drawers).

I am currently working on a bootloader using a Triton TX53 dev board. 
This uses a Freescale iMX53 system on chip.
I have a version of eCos that has the TX53 SOC added to allow RedBoot to 
load and run a windows CE image.

However, this image does NOT currently have support for updating the CE 
image from external media (eg. USB stick or SD-Card).


I am trying to add support for a FAT filesystem into this image but Im 
running into problems.
Ive been through all the documentation and Ive now added what I think 
are the relevant packages (doing this from home so I dont have the list 
of packages here - eg. CYGPKG_IO_FLASH, MMC, FAT, etc).


My problems seem to start when building - when the compile reaches 
fileio.c it goes looking to include 'cyg/io/io.h' but fails to find it.
There are other missing includes (all 4 of the files in this directory).

I thought it was an issue with the eCos stuff I have (from the Triton 
reseller, based on V2.0) so I pulled the latest V3.0 on Monday and 
created a clean project using the LPC2294 dev board. Ive come up against 
the same problem - namely cyg/io/io.h is missing. I can find the 
'missing' files but Im assuming the paths should be sorted out as part 
of the configure stage.

Can anyone point me in the right direction as to where my problem might be.
I will try to follow up tomorrow with grabs from the compile output 
(which shows all the include paths).


Thanks in advance and sorry for waffling on this first post.


Graeme

tcl84.dll missing after ecos installation

abhishek srivastava — 2012-04-20T16:34:12

after cygwin and ecos installation,while opening configtool, tcl84.dll is missing.how to acquire it or can it be installed by installing any package from cygwin setup? i have already installed tcl-tk package.
i have also downloaded tcl84.dll from internet but when i place it in cygwin/bin directory, and try to open configtool,it cannot find the root of the ecos repository tree even though ecos.db is available under D:\cygwin\opt\ecos\ecos-3.0\packages. why it is happening this way??

any possible solutions??

thank you 



regards
Abhishek

installation error

abhishek srivastava — 2012-04-15T17:51:36

hi all

please check this installation error and tell me about its possible solution:

sh ecos-instll.tcl


Please select a directory for installation
[Default /opt/ecos]: /opt/ecos
---------------------------------------------------------
Available prebuilt GNU tools:


*** ecos-install.tcl error: *** ecos-install.tcl error: can't read "ecos_install::toolchains(CYGWIN_NT-6.1)": no such element in array



thank you

regards 

Abhishek kumar Srivastava

Problems installing on Windows 7 x64

Andrew Hannam — 2012-04-13T23:32:45

When trying to install on Windows 7 x64 I got the following message after
picking the distribution site and the install directory...

Available prebuilt GNU tools:

*** ecos-install.tcl error: *** ecos-install.tcl error: can't read
"ecos_install::toolchains(CYGWIN_NT-6.1-WOW64)": no such element in array

What do I need to do to resolve this?
PS. Searched Archives but couldn't find anything similar.

Meet up at S.E.E. - Scandinavian Electronic Event, Stockholm 17-19 April 2012

Ilija Kocho — 2012-04-12T11:59:52

eCos colleagues

During the S.E.E. - Scandinavian Electronic Event, 17-19 April, I will be in Stockholm area. If somebody is visiting S.E.E. it would be a nice opportunity for meeting. If you are interested please contact me directly.

Ilija

POSIX layer and pthread:Unable to make the application

medamine — 2012-04-11T14:12:18

Hi every one,

I use
Hardware: ST STM3210E EVAL board
Packages: posix
in the section:POSIX threads

POSIX pthread implementation header Enabled=True Value=0
POSIX mutex/cond var implementation header Enabled=True Value=0

and I got the pthread.h :

#ifndef CYGONCE_ISO_PTHREAD_H
#define CYGONCE_ISO_PTHREAD_H
/*===========================================
//
// pthread.h
//
// POSIX pthread functions
//
//===========================================

/* CONFIGURATION */

#include <pkgconf/isoinfra.h> /* Configuration header */

/* INCLUDES */

#ifdef CYGINT_ISO_PTHREAD_IMPL
# ifdef CYGBLD_ISO_PTHREAD_IMPL_HEADER
# include CYGBLD_ISO_PTHREAD_IMPL_HEADER
# endif
#endif

#ifdef CYGINT_ISO_PTHREAD_MUTEX
# ifdef CYGBLD_ISO_PTHREAD_MUTEX_HEADER
# include CYGBLD_ISO_PTHREAD_MUTEX_HEADER
# endif
#endif

#endif /* CYGONCE_ISO_PTHREAD_H multiple inclusion protection */

/* EOF pthread.h */

After that, i wrote this application using thread

#include <pthread.h>
#include <stdio.h>
#define NUM_THREADS 5

void *PrintHello(void *threadid)
{
long tid;
tid = (long)threadid;
printf("Hello World! It's me, thread #%ld!\n", tid);
pthread_exit(NULL);
}

int main (int argc, char *argv[])
{
pthread_t threads[NUM_THREADS];
int rc;
long t;
for(t=0; t<NUM_THREADS; t++){
printf("In main: creating thread %ld\n", t);
rc = pthread_create(&threads[t], NULL, PrintHello, (void *)t);
if (rc){
printf("ERROR; return code from pthread_create() is %d\n", rc);
exit(-1);
}
}

/* Last thing that main() should do */
pthread_exit(NULL);
}

but when i build the application withe eCos library, i got these errors

/STM3240G/fork$ make hello
arm-eabi-gcc -c -o hello.o 
-I/home/st/config/standard_Posix_install/include -Wall -Wpointer-arith 
-Wstrict-prototypes -Wundef -Woverloaded-virtual -Wno-write-strings 
-mcpu=cortex-m3 -mthumb -g -O2 -ffunction-sections -fdata-sections 
-fno-rtti -fno-exceptions hello.c
cc1: warning: command line option "-Woverloaded-virtual" is valid for 
C++/ObjC++ but not for C
cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ 
but not for C
hello.c: In function ‘PrintHello’:
hello.c:10: warning: implicit declaration of function ‘pthread_exit’
hello.c: In function ‘main’:
hello.c:15: error: ‘pthread_t’ undeclared (first use in this function)
hello.c:15: error: (Each undeclared identifier is reported only once
hello.c:15: error: for each function it appears in.)
hello.c:15: error: expected ‘;’ before ‘threads’
hello.c:20: warning: implicit declaration of function ‘pthread_create’
hello.c:20: error: ‘threads’ undeclared (first use in this function)
hello.c:23: warning: implicit declaration of function ‘exit’
hello.c:23: warning: incompatible implicit declaration of built-in 
function ‘exit’
make: *** [hello.o] Error 1

First view is that the thread functions doesn't exist in the header 
thread.h, the configtool generate uncompleted headers,

Please i need your help.

Thanks a lot.

Using mutex.owner to detect re-entry

Tom Schouten — 2012-04-10T17:27:58

Hi List,

Is it safe to use the following approach to use a mutex to detect re-entry?
( i.e. to avoid thread-local variables to keep an entry counter.)


static int re_entry(cyg_mutext_t *m) {
     return (m->owner == (void*)cyg_thread_self());
}

As used in the following fragment:

cyg_mutex_t m;

int some_call() {
   if (re_entry(&m)) {
     /* Break off recursion. */
     return error_re_entry;
   }
   else {
     cyg_mutex_lock(&m);
     int err = re_entry_protected_call();   /* Might call some_call(), 
which should then return error_re_entry */
     cyg_mutex_unlock(&);
     return err;
   }
}

Rationale: This is safe because (see mutex.cpp)

- If it's not self it's either NULL or the value of another thread, but 
if this is the case it can never become self due to a race condition.
I.e. we're sure this is not a re-entrant call

- It's self if and only if it's a re-entrant call.


Cheers,
Tom

ST STM3210E EVAL board and the POSIX layer

medamine — 2012-04-05T13:58:11

Hi every body,

we use the STM32F1, so i upload the template ST STM3210E EVAL board

when I tried to build the system with the configuration tool. I included 
all the functionnality of the ISO C and POSIX infrastructure especially 
for Limits. But, i got these errors

In file included from 
/home/st/ecos/ecos-3.0/packages/infra/current/src/diag.cxx:63:
/home/st/config/POSIX_all_install/include/limits.h:175:11: error: 
#include expects "FILENAME" or <FILENAME>
/home/st/config/POSIX_all_install/include/limits.h:183:11: error: 
#include expects "FILENAME" or <FILENAME>
/home/st/config/POSIX_all_install/include/limits.h:191:11: error: 
#include expects "FILENAME" or <FILENAME>
/home/st/config/POSIX_all_install/include/limits.h:199:11: error: 
#include expects "FILENAME" or <FILENAME>
make[1]: Leaving directory `/home/st/config/POSIX_all_build/infra/current'
make[1]: *** [src/diag.o.d] Error 1
make: Leaving directory `/home/st/config/POSIX_all_build'
make: *** [build] Error 2

If some one has an idea for the source of these errors.

Starting with eCos : i386 target and hello application

2012-03-30T14:18:46

Hello everybody,

this is my first question to the list. I’m not able to run the ‘hello’ 
application sampled in Ecos v3.0. I’m working with a standard i386 PC as 
target 
on which I successfully installed GRUB and REDBOOT. When Redboot starts it 
shows:

Platform: PC (I386)
RAM: 0x00100000-0x040F0000 [0x00195130-0x01000000]

I built eCos using the “i386 PC target with RTL8139 ethernet” template and 
then the hello application from the examples.
When I try to download via TFTP the ‘hello’ image, I got “Can’t load ELF File 
– program headers out of order”.
While investigating, I realized the start address of the Redboot and of Hello 
are the same : 0x0108000.

Here I’m confused. May I load the hello code everywhere in the available RAM ?
Just to try, I loaded the image at 0x0208000 and the expected “Raw file 
loaded…:” show up.
But when I gave the GO command nothing happened. 

Before to continue, am I doing right ?

Thanks in advance.

Fab