From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] about flashing the u-boot
Date: Thu, 15 Dec 2011 13:31:29 -0600 [thread overview]
Message-ID: <4EEA4B11.50705@freescale.com> (raw)
In-Reply-To: <ACB6D0C0104CFF42A45A5D82A0DD4F3D018C2F@039-SN2MPN1-011.039d.mgd.msft.net>
On 12/14/2011 09:01 PM, Aggrwal Poonam-B10812 wrote:
>
>
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
>> On Behalf Of ?rico Porto
>> Sent: Thursday, December 15, 2011 8:14 AM
>> To: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] about flashing the u-boot
>>
>> Got a USB TAP, but unfortunately it is supposed to be used with Code
>> Warrior. Any software that allows me to use it to flash a ppc?
>>
>> ?rico V. Porto
>>
>>
>> On Wed, Dec 14, 2011 at 2:10 PM, ?rico Porto
>> <ericoporto2008@gmail.com>wrote:
>>
>>> Hello!
>>>
>>> Is it possible to flash a ppc board, that already has an older u-boot
>>> version, without using a jtag interface? I mean, I know I can write
>>> the filesystem using tftpboot, is it possible to also use it to write
>>> over u-boot? If no, is there any alternative to use jtag?
>>>
> You can use tftp to reflash the bootloader onto the ppc board.
Just be aware that if the new image doesn't work, you'll need jtag (or
an alternative boot source such as NAND) to recover.
-Scott
next prev parent reply other threads:[~2011-12-15 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 16:10 [U-Boot] about flashing the u-boot Érico Porto
2011-12-15 2:44 ` Érico Porto
2011-12-15 3:01 ` Aggrwal Poonam-B10812
2011-12-15 19:31 ` Scott Wood [this message]
2011-12-15 22:29 ` Érico Porto
2011-12-15 22:34 ` Scott Wood
2011-12-20 0:43 ` Érico Porto
2011-12-20 19:17 ` Scott Wood
2011-12-22 12:30 ` Érico Porto
2011-12-22 12:40 ` Érico Porto
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=4EEA4B11.50705@freescale.com \
--to=scottwood@freescale.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