From: Rommel G Custodio <sessyargc+u-boot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 10/10] board/t104xrdb: Add support of NAND, SD, SPI boot for T1040RDB
Date: Tue, 1 Apr 2014 06:50:25 +0000 (UTC) [thread overview]
Message-ID: <loom.20140401T083759-578@post.gmane.org> (raw)
In-Reply-To: 533A20D2.2060603@freescale.com
Dear Prabhakar Kushwaha,
Prabhakar Kushwaha <prabhakar <at> freescale.com> writes:
>
>
> On 4/1/2014 4:40 AM, Rommel G Custodio wrote:
> > Dear Prabhakar Kushwaha,
> >
> > Prabhakar Kushwaha <prabhakar <at> freescale.com> writes:
> >
8>< snipped ><8
> >> +#Flush PBL data
> >> +091380c0 000FFFFF
> > That's a "Wait" command.
> > Unless the "Flush" was command (that is in most PBI files I've read,
> > Flush/Wait pait) was inadvertantly deleted.
> >
>
> Flush command only work for CCSRBAR address space. It should not be used
> for CPC-SRAM.
>
> This is the reason, it has been removed.
Does this affect all mpc85xx cores?
I've noticed this same weird behavior on a T1040QDS.
A simple write to CPC-SRAM before a Flush command causes the LEDs to report
an error.
i.e
89ffff00 4bfff004
09138000 00000000
091380c0 00000001
After putting the CPC-SRAM write after the Flush the write was successful
(as verified by a BDI-3000).
i.e
09138000 00000000
091380c0 00000001
89ffff00 4bfff004
091380c0 00000001
BUT it seems this does not occur on the P5040DS. The P5040DS_SPIFLASH
creates a u-boot that has Flush commands and it boots correctly.
[local]$ xxd -g4 obj-P5040DS_SPIFLASH/u-boot.pbl
:
00cc0a0: ffffffff 81ffffc0 ffffffff ffffffff ................
00cc0b0: ffffffff ffffffff ffffffff ffffffff ................
00cc0c0: ffffffff ffffffff ffffffff ffffffff ................
00cc0d0: ffffffff ffffffff ffffffff ffffffff ................
00cc0e0: ffffffff 4bfff004 09138000 00000000 ....K...........
00cc0f0: 091380c0 00000000 08138040 aa69eb89 ........... at .i..
On another note, if this affects all mpc85xx cores then I guess
tools/pblimage.c needs updating. The add_end_cmd() always adds a Flush
command prior to a CRC check (CONT=0) command.
>
> Regards,
> Prabhakar
>
All the best,
Rommel
prev parent reply other threads:[~2014-04-01 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:05 [U-Boot] [PATCH 10/10] board/t104xrdb: Add support of NAND, SD, SPI boot for T1040RDB Prabhakar Kushwaha
2014-03-31 23:10 ` Rommel G Custodio
2014-03-31 23:44 ` Rommel G Custodio
2014-04-01 2:17 ` Prabhakar Kushwaha
2014-04-01 2:13 ` Prabhakar Kushwaha
2014-04-01 6:50 ` Rommel G Custodio [this message]
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=loom.20140401T083759-578@post.gmane.org \
--to=sessyargc+u-boot@gmail.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