From: Brian Swetland <swetland@google.com>
To: Chetan Kapoor <chetan.kapoor@flextronicssoftware.com>
Cc: Linux-omap-open-source@linux.omap.com,
linux-omap-open-source-bounces@linux.omap.com
Subject: Re: Trasnferring u-boot to P2 730
Date: Fri, 7 Apr 2006 09:29:38 -0700 [thread overview]
Message-ID: <20060407162938.GA9920@localhost.localdomain> (raw)
In-Reply-To: <OF252DA920.39024BFA-ON65257149.004C9463-65257149.004F0E12@flextronicssoftware.com>
[Chetan Kapoor <chetan.kapoor@flextronicssoftware.com>]
> Hello
>
> I am also working on the P2 board and having similar problems with u-boot
> download onto the board.
>
> Can we not use OST Tools - a TI application, for downloading the
> u-boot.bin onto the P2 board RAM/FLASH, OST seems to have flexibility
> between downloading & executing images from RAM AND downloading/burning
> images to flash.
>
> I was able to download the u-boot.bin (the raw binary) as well as u-boot
> (ELF image) to P2's RAM using OST Tools over a serial line (COM1). I has
> success in downloading u-boot to the specific address in RAM, but the
> image doesn't seem to execute/run. ALso, there is a provision of
> downloading images over the USB connection to the target, but in my case
> my Windows PC does not detect the P2 board as a USB device when I connect
> the board to the host PC with a USB cable. Rather, the charging LED on the
> board blinks for a second.
There is a bug in P2 (some combination of an on-die rom bug and a board
design issue, iirc) that prevents USB download from working.
Brian
next prev parent reply other threads:[~2006-04-07 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 13:18 Trasnferring u-boot to P2 730 Kipisz, Steven
2006-04-07 14:23 ` Chetan Kapoor
2006-04-07 16:29 ` Brian Swetland [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-07 7:15 Ola Helm
2006-04-07 16:47 ` Trasnferring " Todd Poynor
2006-04-07 16:58 ` Kevin Hilman
2006-04-10 8:54 ` Ola Helm
2006-03-29 9:07 Ola Helm
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=20060407162938.GA9920@localhost.localdomain \
--to=swetland@google.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=chetan.kapoor@flextronicssoftware.com \
--cc=linux-omap-open-source-bounces@linux.omap.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