public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Navya S Kamath" <navya@coreel.com>
To: "'Gary Thomas'" <gary@mlbassoc.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Compile USB Host Application
Date: Tue, 11 Dec 2007 12:12:00 -0000	[thread overview]
Message-ID: <20071211121200.iq0Wwa0MlvH8RbnabNJmnc7IIdfpCe1dzpMvTDsMgio@z> (raw)
In-Reply-To: <475E44EE.4050300@mlbassoc.com>

Hi,

Could you please elaborate on how to compile the host application? The
ECOS_REPOSITROY has been installed on the host Linux machine. I use this
repository for compiling the target bootloader along with the USB slave
application.

How can I invoke the target application from the bootloader "Redboot"
prompt? 

If the USB host application has to be compiled on ecos environment, how can
it be executed on Linux?

I am new to ecos environment, please help.

Regards,
Navya

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Gary Thomas
Sent: Tuesday, December 11, 2007 1:36 PM
To: Navya S Kamath
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Compile USB Host Application

Navya S Kamath wrote:
> Hi All,
> 
> I'm trying to compile the USB host application on a RedHat Enterprise
Linux,
> I get following errors
> 
> usbhost.o(.text+0xb4): In function `usb_scan_devices':
> : undefined reference to `__fgetc_unlocked'
> usbhost.o(.text+0x197): In function `usb_scan_devices':
> : undefined reference to `__fgetc_unlocked'
> usbhost.o(.text+0x207): In function `usb_scan_devices':
> : undefined reference to `__fgetc_unlocked'
> usbhost.o(.text+0x163d): In function `run_test_bulk_out':
> : undefined reference to `__glibc_strerror_r'
> usbhost.o(.text+0x1e4b): In function `run_test_bulk_in':
> : undefined reference to `__glibc_strerror_r'
> usbhost.o(.text+0x2807): In function `run_test_control_in':
> : undefined reference to `__glibc_strerror_r'
> 
> I include file /usr/local/include/stdio.h has these definitions.Anybody
> faced such errors before? Please help

It looks like you're trying to use things that are outside of eCos
(no eCos application should ever need to use 'standard' include files,
only the ones provided)

The public version of eCos doesn't support USB host operations.  I
believe that this can be obtained from eCosCentric.


-- 
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

  reply	other threads:[~2007-12-11 12:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071211055518.7F44B19500D2@mail.chez-thomas.org>
2007-12-11  8:08 ` Gary Thomas
2007-12-11 12:12   ` Navya S Kamath [this message]
2007-12-13  3:25   ` [ECOS] fis list hong zhang
2007-12-13  9:53     ` Gary Thomas
     [not found] <20071211062402.A14A5260003@tymora.bartv.net>
2007-12-11 22:19 ` [ECOS] Compile USB Host Application Bart Veer
     [not found] <200712110712.1j23Ym59t3Nl3qW0@watson.mail.atl.earthlink.net>
2007-12-11 14:01 ` Frank Pagliughi
2007-12-11  5:55 Navya S Kamath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071211121200.iq0Wwa0MlvH8RbnabNJmnc7IIdfpCe1dzpMvTDsMgio@z \
    --to=navya@coreel.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).