public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Curt Brune <curt@cumulusnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB Device Identification -- non-removable USB NAND flash
Date: Wed, 17 Apr 2013 21:33:29 -0700 (PDT)	[thread overview]
Message-ID: <1699553972.803992.1366259609100.JavaMail.root@cumulusnetworks.com> (raw)
In-Reply-To: <1958288758.803909.1366258865033.JavaMail.root@cumulusnetworks.com>

Hi - 

Looking for suggestions on how to identify a particular USB mass storage device on my platform.

My platform has a P2020 SoC.  The SoC USB controller is connected to an on board USB hub.  The hub has 3 connections as follows:

+---------+
|         |--->[USB flash controller, fronting a 2GB NAND flash]
| USB Hub |--->[front panel USB connector]
|         |--->[front panel USB connector]
+---------+

My uImage is stored on the NAND in a raw partition. I have been using the usbboot command just fine.  Something like this:

  uboot> usbboot $loadaddr 0:0 && bootm $loadaddr

That boots from storage device 0, partition 0.  That works great.

The problem is when I *also* have a USB memory stick plugged into one of the front panel ports.  In that case my boot device no longer shows up as device "0", but rather "1".

I'm guessing this problem is not unique.

Is there a way to "fix" the device number for the non-removable flash to always be 0?

Alternatively is there a way to figure out at run time (in a script) what device corresponds to my internal flash?

I started hacking on common/usb.c and I see how I can make it work, but that solution seemed wrong.  There's got to be a better way.

Any suggestions are much appreciated.

Cheers,
Curt

       reply	other threads:[~2013-04-18  4:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1958288758.803909.1366258865033.JavaMail.root@cumulusnetworks.com>
2013-04-18  4:33 ` Curt Brune [this message]
2013-04-18  6:25   ` [U-Boot] USB Device Identification -- non-removable USB NAND flash Albert ARIBAUD

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=1699553972.803992.1366259609100.JavaMail.root@cumulusnetworks.com \
    --to=curt@cumulusnetworks.com \
    --cc=u-boot@lists.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