headers
Neundorf, Alexander | 1 Apr 2005 10:12

probably simple problem: ASSERT in Cyg_StdIostream

Hi,

probably a simple question, but I already searched on the web for an answer but wasn't successful.
So, I added to my working firmware the File IO package, and didn't change anything in the code. Otherwise I
don't use the POSIX compat. (i.e. no pthreads, no main()).
Now, when my program starts I get an assert:

ASSERT FAIL: <8>stream.inl[109]cyg_bool Cyg_StdioStream::trylock_me() Stream
object is not a valid stream!

Some stuff like diag_printf(), sprintf() etc. is used.
I guess I have to prepare something else for the File IO package. 
Any hints ?

Thanks
Alex

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
liu hua | 1 Apr 2005 10:37
Picon
Favicon

Scheduler problem

In the tewothreads example program, if I don't use cyg_thread_delay() in 
the 'simple_program' thread, or if use cyg_thread_delay(0), the two threads 
cannt be scheduled normally.  The result is only one thread can run, and 
another thread is hung. 

thread program:
void simple_program(cyg_addrword_t data)
{
  int message = (int) data;
  int delay;

  printf("Beginning execution; thread data is %d\n", message);

  //cyg_thread_delay(200);

  for (;;) {
    //delay = 0+ (rand() % 0);

    /* note: printf() must be protected by a
       call to cyg_mutex_lock() */
    cyg_mutex_lock(&cliblock); {
      printf("Thread %d: and now a delay of %d clock ticks\n",
	     message, delay);
    }
    cyg_mutex_unlock(&cliblock);
    cyg_thread_delay(0);
  }
}
Output result:
Thread 0: and now a delay of 0 clock ticks
(Continue reading)

Permalink | Reply | 2 comments |
headers
Nickolay | 1 Apr 2005 10:43
Picon

RedBoot FTP and CVS versions

Hello!

I need add IXDP425 NPE support to RedBoot loader.
I download from Intel website next two packages:
Redboot-v1_94-epk.zip
Redboot-v1_94-npe-microcode.zip

I need both these packages to add NPE support to the RedBoot source from 
CVS ?

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
Raghavendar.M | 1 Apr 2005 11:44

ecos installation on 386 PC - regd

Resepcted Sir,

iam final year Master's of Engg. student. i taken my project in eCos.i
have installed eCos config tool using cygwin. after installation i was
not able to set up  bulid and user tools that the configuration Tool
uses to build eCos and RedBoot images.i.e iam able to select the
tools->paths->buildtools from the menu.in order to select  the
d:\cygwin\tools is not avaliable to the cygwin i installed. i have tried
many such links and iam not able to find tools folder. help in this
regd. sir. 

      Sir i have also gone thro' sourceware.ecos .. i need to load eCos
      to an 386 PC. what procedures i need to do. only thro' Config tool
      is it possible or is there any other means.
 i have not created any application. without any application is it
 possible to work on eCos after loading in 386 PC. is there any sample
 application to test. 

 Pl suggest me. 

thanking you
yours faithfully,
M.Raghavendar

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
Nelly Pison | 1 Apr 2005 11:56
Picon

Re: synthetic target serial support

OK, I have installed it on my linux with the ecos repository, make what 
is indicated in the readme (except for the pseudo ttys that I don't need) .
Then with configTool I create an ecc with the  template "Linux synthetic 
target"
and I try to add the package "Synthetic target serial driver" but 
configTool refuse with the error message :
 " Add and Remove hardware packages by selecting a new hardware template"
What is the problem?
Note : I saw that in the synthserial.cdl file the parent is 
CYGPKG_IO_SERIAL_DEVICES and I don't find it in the ecos.db file

Thanks for any help

>On Wed, Mar 23, 2005 at 09:06:20AM +0100, Nelly Pison wrote:
>  
>
>>Hello,
>>
>>I need to use a serial port on the linux synthetic target running on a 
>>PC that is able to send messages and to receive messages (finished by 
>>the character 0x0D)
>>Can someone give me advices for :
>>- where I can found  the good software
>>- how to configure and use it in the lst
>>- how is the interface between it and my software
>>    
>>
>
>http://ecos.sourceware.org/ml/ecos-devel/2003-08/msg00000.html
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Andrew Lunn | 1 Apr 2005 12:12
Picon

Re: synthetic target serial support

On Fri, Apr 01, 2005 at 11:56:29AM +0200, Nelly Pison wrote:
> OK, I have installed it on my linux with the ecos repository, make what 
> is indicated in the readme (except for the pseudo ttys that I don't need) .
> Then with configTool I create an ecc with the  template "Linux synthetic 
> target"
> and I try to add the package "Synthetic target serial driver" but 
> configTool refuse with the error message :
> " Add and Remove hardware packages by selecting a new hardware template"
> What is the problem?

The config tool has a "feature" that it wont add/remove hardware
packages. ecosconfig, the CLI tool is more flexiable and will do
this. The other option is to edit the

target linux {
        alias           { "Linux synthetic target" i386linux }
        packages        { CYGPKG_HAL_SYNTH

and just add the serial device driver package.

> Note : I saw that in the synthserial.cdl file the parent is 
> CYGPKG_IO_SERIAL_DEVICES and I don't find it in the ecos.db file

This is not a package, its a component. Its defined in the
CYGPKG_IO_SERIAL package. Most templates include this package, so all
you need to do is enable the option CYGPKG_IO_SERIAL_DEVICES.

        Andrew

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nickolay | 1 Apr 2005 13:34
Picon

RedBoot and semaphore

Hallo!

What last ecos version, that successfuly builded with IXP425 NPE support 
from Intel?
I did try build last ecos version from CVS with Intel's 
CYGPKG_DEVS_ETH_INTEL_NPE and
CYGPKG_DEVS_ETH_ARM_IXDP425_NPE. But when compile, has some error:

In file included from 
/home/nickolay/ecos/build1/install/include/os_datatypes.h:168,
                 from 
/home/nickolay/ecos/build1/install/include/ix_ossl.h:170,
                 from 
/home/nickolay/ecos/packages/devs/eth/intel/npe/v1_4/src/if_npe.c:72:
/opt/montavista/previewkit/arm/xscale_le/target/usr/include/asm/semaphore.h:20: 
error: parse error before "wait_queue_head_t"

But wait_queue_head_t really defined only with -D__KERNEL__, but ecos 
compile without this flag.

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 1 comment |
headers
Nelly Pison | 1 Apr 2005 15:31
Picon

Re: synthetic target serial support

You are very rapid to answer: Thanks

I have build the library now. But when I start a simple program using 
the lst (make only printf) with option --io  (as I see for the synthetic 
erthernet driver) I have the following  error: "unable to find the I/O 
auxiliary program on the current search PATH. Please install the 
appropriate host-side tools"

In fact I don't know use the synth. serial driver :
- have you a source example
- is there any documentation about it
- is there host tools necessary for that (like rawether for ethernet) 
and where if yes

Thanks a lot for your help

> OK, I have installed it on my linux with the ecos repository, make 
> what is indicated in the readme (except for the pseudo ttys that I 
> don't need) .
> Then with configTool I create an ecc with the  template "Linux 
> synthetic target"
> and I try to add the package "Synthetic target serial driver" but 
> configTool refuse with the error message :
> " Add and Remove hardware packages by selecting a new hardware template"
> What is the problem?
> Note : I saw that in the synthserial.cdl file the parent is 
> CYGPKG_IO_SERIAL_DEVICES and I don't find it in the ecos.db file
>
> Thanks for any help
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andrew Lunn | 1 Apr 2005 15:45
Picon

Re: synthetic target serial support

On Fri, Apr 01, 2005 at 03:31:17PM +0200, Nelly Pison wrote:
> You are very rapid to answer: Thanks
> 
> I have build the library now. But when I start a simple program using 
> the lst (make only printf) with option --io  (as I see for the synthetic 
> erthernet driver) I have the following  error: "unable to find the I/O 
> auxiliary program on the current search PATH. Please install the 
> appropriate host-side tools"
> 
> In fact I don't know use the synth. serial driver :
> - have you a source example
> - is there any documentation about it
> - is there host tools necessary for that (like rawether for ethernet) 
> and where if yes
> 
> Thanks a lot for your help

The following explains a lot:

http://ecos.sourceware.org/docs-latest/ref/hal-synth-arch.html

It will be looking for the executable ecosynth. If you have done an
install from the prebuild binaries this normally lives in

/opt/ecos/libexec/ecos/hal/synth/arch/v2_0/ecosynth

It finds this be using the PATH variable, which in this case needs to
include /opt/ecos/bin. It knows how to get from the bin directory to
the correct subdirectory under libexec.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Salter | 1 Apr 2005 15:47
Picon
Favicon

Re: RedBoot and semaphore

On Fri, 2005-04-01 at 15:34 +0400, Nickolay wrote:
> Hallo!
> 
> What last ecos version, that successfuly builded with IXP425 NPE support 
> from Intel?
> I did try build last ecos version from CVS with Intel's 
> CYGPKG_DEVS_ETH_INTEL_NPE and
> CYGPKG_DEVS_ETH_ARM_IXDP425_NPE. But when compile, has some error:
> 
> In file included from 
> /home/nickolay/ecos/build1/install/include/os_datatypes.h:168,
>                  from 
> /home/nickolay/ecos/build1/install/include/ix_ossl.h:170,
>                  from 
> /home/nickolay/ecos/packages/devs/eth/intel/npe/v1_4/src/if_npe.c:72:
> /opt/montavista/previewkit/arm/xscale_le/target/usr/include/asm/semaphore.h:20: 
> error: parse error before "wait_queue_head_t"
> 
> But wait_queue_head_t really defined only with -D__KERNEL__, but ecos 
> compile without this flag.

The problem seems to be that you are using a linux toolchain. This won't
work because the NPE software sees the __linux__ define and thinks its
building for linux, not RedBoot. You really need to use an xscale-elf
or arm-elf toolchain, not a toolchain meant to build linux apps.

--Mark

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
(Continue reading)

Permalink | Reply | 0 comments |

Gmane