public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* Re: [ECOS] Compile USB Host Application
       [not found] <20071211055518.7F44B19500D2@mail.chez-thomas.org>
@ 2007-12-11  8:08 ` Gary Thomas
  2007-12-11 12:12   ` Navya S Kamath
  2007-12-13  3:25   ` [ECOS] fis list hong zhang
  0 siblings, 2 replies; 7+ messages in thread
From: Gary Thomas @ 2007-12-11  8:08 UTC (permalink / raw)
  To: Navya S Kamath; +Cc: ecos-discuss

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: [ECOS] Compile USB Host Application
  2007-12-11  8:08 ` [ECOS] Compile USB Host Application Gary Thomas
@ 2007-12-11 12:12   ` Navya S Kamath
  2007-12-13  3:25   ` [ECOS] fis list hong zhang
  1 sibling, 0 replies; 7+ messages in thread
From: Navya S Kamath @ 2007-12-11 12:12 UTC (permalink / raw)
  To: 'Gary Thomas'; +Cc: ecos-discuss

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [ECOS] fis list
  2007-12-11  8:08 ` [ECOS] Compile USB Host Application Gary Thomas
  2007-12-11 12:12   ` Navya S Kamath
@ 2007-12-13  3:25   ` hong zhang
  2007-12-13  9:53     ` Gary Thomas
  1 sibling, 1 reply; 7+ messages in thread
From: hong zhang @ 2007-12-13  3:25 UTC (permalink / raw)
  To: ecos-discuss

List,

"fis list" returns something like

Name             flash addr  Mem addr   Length   Entry
point
RedBoot         0xA0000000  0xA0000000 0x020000
0x80000000
RedBoot[backup] 0xA0020000  0x8C010000 0x020000
0x8C010000
RedBoot config  0xA0FC0000  0xA0FC0000 0x020000
0x00000000
FIS directory   0xA0FE0000  0xA0FE0000 0x020000
0x00000000
RedBoot>

What is real meaning Mem addr and Entry point? I read
redboot manual but no answer.

----henry



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-- 
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 raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] fis list
  2007-12-13  3:25   ` [ECOS] fis list hong zhang
@ 2007-12-13  9:53     ` Gary Thomas
  0 siblings, 0 replies; 7+ messages in thread
From: Gary Thomas @ 2007-12-13  9:53 UTC (permalink / raw)
  To: hong zhang; +Cc: ecos-discuss

hong zhang wrote:
> List,
> 
> "fis list" returns something like
> 
> Name             flash addr  Mem addr   Length   Entry
> point
> RedBoot         0xA0000000  0xA0000000 0x020000
> 0x80000000
> RedBoot[backup] 0xA0020000  0x8C010000 0x020000
> 0x8C010000
> RedBoot config  0xA0FC0000  0xA0FC0000 0x020000
> 0x00000000
> FIS directory   0xA0FE0000  0xA0FE0000 0x020000
> 0x00000000
> RedBoot>
> 
> What is real meaning Mem addr and Entry point? I read
> redboot manual but no answer.

'Mem Addr' is the address that this image will be loaded to RAM
if you execute 'fis load' with no memory options.  This can always
be overridden using the '-b' option.

'Entry Point' is the default address if you were to execute the
code, via the 'go' command.

-- 
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 raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Compile USB Host Application
       [not found] <20071211062402.A14A5260003@tymora.bartv.net>
@ 2007-12-11 22:19 ` Bart Veer
  0 siblings, 0 replies; 7+ messages in thread
From: Bart Veer @ 2007-12-11 22:19 UTC (permalink / raw)
  To: Navya S Kamath; +Cc: ecos-discuss

>>>>> "Navya" == Navya S Kamath <navya@coreel.com> writes:

    Navya> Hi All,
    Navya> I'm trying to compile the USB host application on a RedHat
    Navya> Enterprise Linux, I get following errors

    Navya> usbhost.o(.text+0xb4): In function `usb_scan_devices':
    Navya> : undefined reference to `__fgetc_unlocked'
    Navya> usbhost.o(.text+0x197): In function `usb_scan_devices':
    Navya> : undefined reference to `__fgetc_unlocked'
    Navya> usbhost.o(.text+0x207): In function `usb_scan_devices':
    Navya> : undefined reference to `__fgetc_unlocked'
    Navya> usbhost.o(.text+0x163d): In function `run_test_bulk_out':
    Navya> : undefined reference to `__glibc_strerror_r'
    Navya> usbhost.o(.text+0x1e4b): In function `run_test_bulk_in':
    Navya> : undefined reference to `__glibc_strerror_r'
    Navya> usbhost.o(.text+0x2807): In function `run_test_control_in':
    Navya> : undefined reference to `__glibc_strerror_r'

    Navya> I include file /usr/local/include/stdio.h has these
    Navya> definitions.Anybody faced such errors before? Please help

It is not clear that usbhost is going to compile easily on any current
Linux system due to incompatible changes in the Linux world. For
example my Fedora 7 system no longer has a <linux/usb.h> header,
instead there is a <linux/usb/ch9.h> header which appears much to have
the same contents.

However I think that your immediate problem is that the build is
picking up the wrong header files. I do not know where
/usr/local/include/stdio.h comes from, but the usbhost build should be
using the official header files from /usr/include.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.

-- 
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 raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Compile USB Host Application
       [not found] <200712110712.1j23Ym59t3Nl3qW0@watson.mail.atl.earthlink.net>
@ 2007-12-11 14:01 ` Frank Pagliughi
  0 siblings, 0 replies; 7+ messages in thread
From: Frank Pagliughi @ 2007-12-11 14:01 UTC (permalink / raw)
  To: Navya S Kamath; +Cc: 'Gary Thomas', ecos-discuss

Navya S Kamath wrote:
> 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.
>
>
>   
There is a USB host application in the eCos sources that you compile on 
a desktop Linux and use to help test the USB slave device that you 
create with eCos. You don't *need* the host app to create a USB slave 
device with eCos. It just helps you debug one if you do have it.

-- 
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 raw reply	[flat|nested] 7+ messages in thread

* [ECOS] Compile USB Host Application
@ 2007-12-11  5:55 Navya S Kamath
  0 siblings, 0 replies; 7+ messages in thread
From: Navya S Kamath @ 2007-12-11  5:55 UTC (permalink / raw)
  To: ecos-discuss

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

Regards,
Navya 



-- 
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 raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2007-12-13  8:07 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20071211055518.7F44B19500D2@mail.chez-thomas.org>
2007-12-11  8:08 ` [ECOS] Compile USB Host Application Gary Thomas
2007-12-11 12:12   ` Navya S Kamath
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

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