From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot fails with new versatile PB (lead-free version)
Date: Sat, 03 Feb 2007 12:30:40 -0500 [thread overview]
Message-ID: <45C4C6C0.7090605@comcast.net> (raw)
In-Reply-To: <8783212.post@talk.nabble.com>
T S Rajesh wrote:
> A bit more info..
>
> When i type "List Area" from the boot monitor code, i get
>
> Base Area Size Blocks Block Size
> --------- --------------- ------------ ----------------
> 0x34000000 256k 4 64k
> 0x34040000 65280k 255 256k
> 0x30000000 256k 4 64k
> 0x30040000 65280k 255 256k
>
> whereas in the older boards, i used to get
>
> Base Area Size Blocks Block Size
> --------- --------------- ------------ ----------------
> 0x34000000 64M 256 256k
>
> Thanks & Regards
> Rajesh
>
>
> T S Rajesh wrote:
>> Hi All,
>>
>> I tried with the latest versatile PB926EJ-S (Lead Free Version). The
>> failure i get is:
>> DRAM: 0kb
>> Flash: 0kb
>> Whereas in the old boards, it used to say
>> DRAM: 0kb
>> Flash: 64M
>>
>> And after that, in the new board, when I try to do a saveenv, it fails
>> with a
>> "start/end address not on sector boundary".
>> The same image works perfectly in the older boards (purchased last year).
>> Anyone came across this problems? Any help on this is greatly appreciated.
>>
>> Thanks & Regards
>> Rajesh
Hi Rajesh,
It looks like your memory part is different: the original flash has 256
equal size blocks, the new flash is "bottom boot" with four 64K blocks
in the lowest 256K area. You probably need to do some configuration
(rebuild) u-boot for the different parts.
Beyond this general information I'm afraid I don't have enough knowledge
to help.
Best regards,
gvb
next prev parent reply other threads:[~2007-02-03 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 15:20 [U-Boot-Users] U-boot fails with new versatile PB (lead-free version) T S Rajesh
2007-02-03 15:35 ` T S Rajesh
2007-02-03 17:30 ` Jerry Van Baren [this message]
2007-02-06 2:20 ` T S Rajesh
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=45C4C6C0.7090605@comcast.net \
--to=gerald.vanbaren@comcast.net \
--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