linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adish Kuvelker <adish.kuvelker@gmail.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PPC 405 EX USB Development
Date: Wed, 25 Feb 2009 18:15:15 +0530	[thread overview]
Message-ID: <d9c5f2890902250445j784bc66fp605740e86647ca12@mail.gmail.com> (raw)
In-Reply-To: <d9c5f2890902250439u58c819a5pbd4a1bdda11d1dc4@mail.gmail.com>

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

Hi Stefan,

Also in the SETUP stage where I have set my packet size as 1, as I treat
each of this 3 stages (SETUP, DATA and STATUS) as three different
stages/transactions,  I find that the "Non-Periodic Transmit FIFO/Queue
Status Register" read as soon as I write to the "Non-Periodic Transmit FIFO
Size Register" as "0x10500fa". Before writing the value is "0x80100". Is it
fine that the bit 7 which defines the termination of channel a right thing
to happen? Secondly since i am writing 2 bytes to the FIFO why should the
"Non-periodic TxFIFO Space Avail (NPTxFSpcAvail)" bits of USB0_GNPTXSTS be
0xfa?

The FIFO to which I write:
*USB0_GRXFSIZ - 0x213            USB0_GNPTXFSIZ - 0x1000213*
The above setting mean that my Non-Periodic Transmit register starts at
0x213. So I write my data (8 byte SETUP Token Data) in the following way:
-    Write the first 4 bytes to the starting adress of  0x1000 since I am
using Channel 0  --- (*(volatile unsigned  *)(DHc->base + 0x1000 + (bEnd *
0x1000) + 0x213 + fifo_address_offset))=*((volatile       unsigned
*)pSrcBuf);
-   Then increment the "fifo_adress_offset" by 4 and write the next 4 bytes.


I think that there is some problem in the SETUP (Token) Stage. Can you
please pass any pointers over this?

Regards;
Aadish

On Wed, Feb 25, 2009 at 6:09 PM, Adish Kuvelker <adish.kuvelker@gmail.com>wrote:

> Hi Stefan,
>
> I am working on the internal OTG controller. The synopsys DWC.
>
> Regards;
> Aadish
>
>
> On Wed, Feb 25, 2009 at 5:57 PM, Stefan Roese <sr@denx.de> wrote:
>
>> On Wednesday 25 February 2009, Adish Kuvelker wrote:
>> > I am developing a Host Controller Driver for the PPC405EX based board. I
>> > have a OTG controller on it, which I have to configure as Host
>> Controller
>> > and thus I am witting a HCD for the same. I am stuck at the Control
>> stage
>> > wherein although my SETUP stage seems to be going through I get a STALL.
>> >
>> > Can anyone help me in this regard as to where would I get a reference
>> code
>> > for this?
>>
>> Are you talking about the 405EX internal USB OTG controller (Synopsys DWC)
>> or
>> some other OTG controller?
>>
>> Best regards,
>> Stefan
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2979 bytes --]

  parent reply	other threads:[~2009-02-25 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  9:15 PPC 405 EX USB Development Adish Kuvelker
2009-02-25 12:27 ` Stefan Roese
     [not found]   ` <d9c5f2890902250439u58c819a5pbd4a1bdda11d1dc4@mail.gmail.com>
2009-02-25 12:45     ` Adish Kuvelker [this message]
2009-02-25 12:45   ` Stefan Roese
2009-03-03 21:18     ` Felix Radensky

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=d9c5f2890902250445j784bc66fp605740e86647ca12@mail.gmail.com \
    --to=adish.kuvelker@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    /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 NNTP newsgroup(s).