Hans Kester | 1 Mar 10:28 2004
Picon

MicroWindows test fails to build

When I 
1. choose the NET template for an x86 PC
2. add the MicroWindows package
3. enable CYGBLD_MICROWINDOWS_ECOS_APP
4. build the eCos library
5. build the tests

I get the following error messages:

[snip]
make[1]: Leaving directory `/ecos-e/cygwin/ecos/workdir/eCos/demo_build/io/pci/current'
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_srvmain.o):
In function `SVR_GrBell':
make: Leaving directory `/ecos-e/cygwin/ecos/workdir/eCos/demo_build'
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/nanox/srvmain.c:902:
undefined reference to `gettimeofday'
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_srvfunc.o):
In function `SVR_GrSetPortraitMode':
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/nanox/srvfunc.c:2945:
undefined reference to `strdup'
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_devtimer.o):
In function `time_to_expiry':
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
(Continue reading)

Retallack, Mark (Siemens | 1 Mar 10:46 2004
Picon

Suggested version of GCC

Good morning (UK time). 

I am currently using GCC version 2.95.2 and feel it is time to upgrade to
one of the 3.x versions. I am using Cygwin to compile to a powerpc-eabi
target. On the ecos/Sourceware site it suggests version 3.2.1, is this the
best version to use? 

Also which version of Insight is best under Cygwin for the powerpc-eabi
target? (I can see 5.x and 6.0 are available).

Thanks in advanced.

Mark Retallack
Embedded Software Engineer
Siemens Traffic Controls 
Sopers Lane, Poole, Dorset. BH17 7ER. UK.
Tel: 01202 782844
Fax: 01202 782545
www.siemenstraffic.com

Committed to quality traffic solutions and service excellence

Siemens Traffic Controls is a division of Siemens plc. Registered No.
727817, England. 
Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ. 

This communication contains information which is confidential and 
may also be privileged. It is for the exclusive use of the addressee. 
If you are not the addressee please note that any distribution, 
reproduction, copying, publication or use of this communication 
(Continue reading)

Andrew Lunn | 1 Mar 10:57 2004
Picon

Re: MicroWindows test fails to build

On Mon, Mar 01, 2004 at 10:28:31AM +0100, Hans Kester wrote:
> When I 
> 1. choose the NET template for an x86 PC
> 2. add the MicroWindows package
> 3. enable CYGBLD_MICROWINDOWS_ECOS_APP
> 4. build the eCos library
> 5. build the tests
> 
> I get the following error messages:
> 
> [snip]
> make[1]: Leaving directory `/ecos-e/cygwin/ecos/workdir/eCos/demo_build/io/pci/current'
> /ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_srvmain.o):
In function `SVR_GrBell':
> make: Leaving directory `/ecos-e/cygwin/ecos/workdir/eCos/demo_build'
> /ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/nanox/srvmain.c:902:
undefined reference to `gettimeofday'
> /ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_srvfunc.o):
In function `SVR_GrSetPortraitMode':
> /ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/nanox/srvfunc.c:2945:
undefined reference to `strdup'
>
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(services_gfx_mw_devtimer.o):
In function `time_to_expiry':
> /ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
> /ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
> /ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/engine/devtimer.c:211:
undefined reference to `gettimeofday'
(Continue reading)

Hans Kester | 1 Mar 11:55 2004
Picon

RE: MicroWindows test fails to build

Now I seem to have two of them. I had to include SNMP agent as well,
otherwise it complaint about a missing header file.

make -r -C services/gfx/mw/current
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/bin/ecos_mw.elf
make[1]: Entering directory
`/ecos-e/cygwin/ecos/workdir/eCos/demo_build/services/gfx/mw/current'
i386-elf-gcc -c  -I/ecos-e/cygwin/ecos/workdir/eCos/demo_install/include
-I/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current
-I/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src
-I/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/tests -I.
-Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
-fno-rtti -fno-exceptions
-I/ecos-e/cygwin/ecos/workdir/eCos/demo_install/include/microwin
-D__ECOS=1 -DMSDOS=0 -DELKS=0 -D__rtems__=0 -D_MINIX=0 -DNOTYET=0
-DUNIX=1 -DHAVE_FILEIO -DHAVE_BMP_SUPPORT=1 -DHAVE_PNM_SUPPORT=1
-DHAVE_XPM_SUPPORT=1 -DxHAVE_JPEG_SUPPORT=1 -DHAVESELECT=1
-DMWPIXEL_FORMAT=MWPF_TRUECOLOR0888 -o
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/ecos_app.o
/ecos-e/cygwin/ecos/ecos/packages/services/gfx/mw/current/src/ecos/ecos_
app.c
i386-elf-gcc -g -nostdlib -Wl,--gc-sections -Wl,-static
-L/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib -Ttarget.ld -o
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/bin/ecos_mw.elf
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/ecos_app.o
make[1]: Leaving directory
`/ecos-e/cygwin/ecos/workdir/eCos/demo_build/services/gfx/mw/current'
/ecos-e/cygwin/ecos/workdir/eCos/demo_install/lib/libtarget.a(net_snmp_l
ib_system.o): In function `get_uptime':
(Continue reading)

Radu Cernea | 1 Mar 15:21 2004

2 types of FLASH memory

Hello,

Is it possible, with eCcos, to have a FLASH file system that covers 2 
different FLASH banks?

I have a board that has 2 different banks of FLASH memory. 

One consists in 2 AM20LV040B organized as a 16 bit memory:
-	CYGNUM_FLASH_INTERLEAVE = 2
-	CYGNUM_FLASH_WIDTH = 8
-	CYGNUM_FLASH_SERIES = 1

The 2nd one consists of 4 AM29LV116D) organized as a 32 bit memory:
-	CYGNUM_FLASH_INTERLEAVE = 2
-	CYGNUM_FLASH_WIDTH = 16
-	CYGNUM_FLASH_SERIES = 2

The design idea was to have the possibility to change the program (stored in 
the small 2*AM29LV040B which has a socket), and store a large database in the 
other FLASH bank.

Thank you for your answer,
Radu Cernea

--

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

Winkler Andreas | 1 Mar 16:22 2004
Picon

backup strategy for loading Linux kernel in Redboot FIS ?

Hi,

for a deployable system I need the possibility to load a linux kernel into
the Redboot FIS, to update the system.
This must be possible via ethernet or modem connection (ppp).
Therefore the load and store has to be done by the running Linux system.
Now I am looking for a backup strategy in the case of a fault - e. g. power
failure - during load or writing the kernel.
In that case the linux kernel couldn't be started again.
I am thinking of a second Linux kernel, which could be started in the case,
the load of the first one fails.
How could this be handled?
Or is there a better solution?

Regards
Andreas

--

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

Leandro | 1 Mar 20:53 2004

Keyboard input (i386)

Hello, I'm trying to get input from the keyboard in a POS context, i386 
platform. The only thing I could find in eCos is to open /dev/ttydiag 
and read from there, but for some reason I still can't understand, 
everytime I read a byte from there that same byte is written on the 
screen. If I do not open ttydiag, no echo is shown, and I couldn't find 
where this behaviour takes place inside the code of the kernel. Is there 
any other way to read from the PS/2 keyboard preventing the echo, id 
est, in a raw fashion?
Thank you,

Leandro.

--

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

Richardson, Anthony | 1 Mar 22:14 2004
Picon

RE: Keyboard input (i386)

Leandro wrote:
> Hello, I'm trying to get input from the keyboard in a POS 
> context, i386 
> platform. The only thing I could find in eCos is to open /dev/ttydiag 
> and read from there, but for some reason I still can't understand, 
> everytime I read a byte from there that same byte is written on the 
> screen. If I do not open ttydiag, no echo is shown, and I 
> couldn't find 
> where this behaviour takes place inside the code of the 
> kernel. Is there 
> any other way to read from the PS/2 keyboard preventing the echo, id 
> est, in a raw fashion?

I think there are a couple of ways to do this, but the following
is what I've used in the past:

  hal_virtual_comm_table_t* comm;
  comm = CYGACC_CALL_IF_CONSOLE_PROCS();

  while(1) {
     // Get a character
     c = CYGACC_COMM_IF_GETC(*comm);

     // other stuff here
  }

The input is unbuffered, i.e. you don't have to press
newline to get the character.  Also, there is no echo
of the character to the display.

(Continue reading)

Hiroki Yoshioka | 2 Mar 02:48 2004
Picon

adding a new command to RedBoot

hello,

how do I add a new command to RedBoot?

the post below seems simply adding some `RedBoot_cmd()' macros and
function bodies but that doesn't work for me.
http://ecos.sourceware.org/ml/ecos-discuss/2001-10/msg00402.html

I'm using redboot-intel-xscale-031212 on IXDP425 (an ixp425 evaluation board).

thanks,

hiro

--

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

Sidharth Jandhyala | 2 Mar 05:33 2004

Problem opening second serial port on EB40A

Hello,

I am having trouble using the second serial port on the eb40A. Let me
explain my setup

1)      I have built a configuration using the graphical tool with the
following settings (default package)

CYGDAT_IO_SERIAL_TTY_CONSOLE = "/dev/ttydiag"

CYGDAT_IO_SERIAL_TTY_TTY0_DEV = "/dev/ser0"

CYGDAT_IO_SERIAL_TTY_TTY1_DEV = "dev/ser1"

2)      I have serial A of the board connected to arm-elf-gdb

3)      I have serial B of the board connected to another computer running
hyperterminal

4)      My sample hello world program is shown below

/*-------------------------------------CODE STARTS
HERE---------------------------------*/

#include <stdio.h>                      /* printf */

#include <string.h>                     /* strlen */

#include <cyg/kernel/kapi.h>            /* All the kernel specific stuff */

(Continue reading)


Gmane