public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "m mariga" <ma_ariga@yahoo.co.jp>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Can not compile API file
Date: Wed, 09 Dec 2009 09:32:00 -0000	[thread overview]
Message-ID: <4AB6DC5340C94AFEB5AB2B9A3D00CF98@masahiro> (raw)

[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]

I am very sorry.
I forgot to append file.
Here it is.

> Hello everyone,
>
> I am in a very serious predicament, please help me.
>
> I would like to implement USB driver for my target.
> But by scarce schedule time,I cannot afford to implement it by normal 
> way,which I mean, by using ecos-formal-sample and construct step by step.
> Instead my way is to include others-developed-and-confirmed USB sources 
> that have been developed on other OS.
> I do not use devtab function.
>
> I created \devs\usb\sh7705mod\v3_0\src and inserted next source files.
> DoBulk.c
> DoControl.c
> DoInterrupt.c
> DoRequest.c
> DoRequestPrinterClass.c
> PPOUT.C
> UsbMain.c
> usbs_sh7705mod_data.cxx
>
> All of these except PPOUT.C deal with USB transfer.
> Only PPOUT.C is different.This function is polling USB buffer and if there 
> are data, outputs them to printer port.
> In this file there is a user-calling routine(API). It shares only USB 
> buffer and not calls any other USB functions.
> I defined prototype in proto_ppout.h and enterd it in 
> \devs\usb\sh7705mod\v3_0\include directory.
>
> I included instructions in CDL file to compile these files.
>    cdl_option CYGFUN_DEVS_USB_SH7705MOD_EP0 {
> display       "Support the control endpoint 0"
> default_value CYGINT_IO_USB_SLAVE_CLIENTS
> # And the USB support packages
> requires      CYGPKG_IO_USB CYGPKG_IO_USB_SLAVE
> compile       UsbMain.c DoBulk.c DoControl.c DoRequest.c 
> DoRequestPrinterClass.c PPOUT.C
> compile       -library=libextras.a usbs_sh7705mod_data.cxx
> description "
>     Enable support for endpoint 0. If this support is disabled
>     then the entire USB port is unusable."
>    }
>
> Whenever I build using configtool.exe I cannot compile PPOUT.C.
> Other files are compiled.
> I do not know why only this file cannot be compiled.
> Please help me.
> I append build-log,PPOUT.C,proto_ppout.h,usbs_sh7705mod.cdl.
>
> m mariga
>
> 

[-- Attachment #2: append_files.tar.bz2 --]
[-- Type: application/octet-stream, Size: 7142 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
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:[~2009-12-09  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09  9:32 m mariga [this message]
2009-12-09  9:47 ` Ross Younger
2009-12-11 10:28   ` [ECOS] Does eCOS 2.0/3.0 support CFI ? Ramgopal Kota
2009-12-11 22:51   ` [ECOS] Re: Can not compile API file m mariga
2009-12-14 12:38     ` m mariga
2009-12-14 12:49       ` Edgar Grimberg
2009-12-15 12:47         ` m mariga

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=4AB6DC5340C94AFEB5AB2B9A3D00CF98@masahiro \
    --to=ma_ariga@yahoo.co.jp \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).