All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Puls <appu@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot 2012.10 PXA270 - saveenv / Kernel issue
Date: Tue, 13 Nov 2012 07:51:54 +0100	[thread overview]
Message-ID: <20121113065154.85000@gmx.net> (raw)
In-Reply-To: <201211130204.04871.marex@denx.de>

Dear Marek,

> Betreff: Re: [U-Boot] U-Boot 2012.10 PXA270 - saveenv / Kernel issue

> Dear Andreas Puls,
> 
> you have much better chance of getting a proper reply if you Cc 
> custodian/maintainer (see MAINTAINERS) file.
Im sorry, will do it next time. Thnaks you for the hint.

> > [...]
> > 1.  unprotect and erase the hole flash.
> > 2.  copy the latest u-boot.bin to flash
> > 2.1 usb start
> > 2.2 fatload usb 0:1 0xa0000000 u-boot.bin
> > 2.3 protect off 0x0 0x3ffff
> 
> You mean protect off 0 0x40000 ? (0x3ffff makes no sense)
When i try to use the 0x40000 address i got the following message:
Error: end address not on sector boundary

and flinfo shows all sectors are RO

> > 2.4 erase 0x0 0x3ffff
> > 2.5 cp.b 0xa0000000 0x0 $filesize
> > 3   reset to look the u-boot is installed
> > 3.1 see that CRC is bad (normal behavier couse no defaults are written)
> > 3.2 savenv and powercyle
> > 4.  all fine
> > 5.  copy kernel image to flash
> > 5.1 usb start
> > 5.2 fatload usb 0:1 0xa0000000 uimage-2.6.35.9-toradex-pxa270v22b
> > 5.3 protect off 0xc0000 0x47ffff
> > 5.4 erase 0xc0000 0x47ffff
> > 5.5 cp.b 0xa0000000 0xc0000 $filesize
> > 6.  check the uImage
> > 6.1 iminfo 0xC00000 - OK
> > 7.  hard reset (power cycle)
> > 
> > Now comes the part that i dosen't understand
> > The U-Boot loader sayes again that the CRC is bad and using default
> values.
> 
> Did you not overwrite the env? The env is at 0x40000 in the flash.
Yep i did. That was the problme which Vasily and Rommel are pointed out.

> 163 #define CONFIG_SYS_MONITOR_BASE         0x0
> 164 #define CONFIG_SYS_MONITOR_LEN          0x80000
> 165 
> 166 #define CONFIG_ENV_ADDR                 \
> 167                         (CONFIG_SYS_MONITOR_BASE +
> CONFIG_SYS_MONITOR_LEN)
> 168 #define CONFIG_ENV_SIZE                 0x40000
> 169 #define CONFIG_ENV_SECT_SIZE            0x40000
> 170 #define CONFIG_ENV_ADDR_REDUND          (CONFIG_ENV_ADDR + 
> CONFIG_ENV_SECT_SIZE)
> 171 #define CONFIG_ENV_SIZE_REDUND          (CONFIG_ENV_SIZE)
> 
> 
> Best regards,
> Marek Vasut

Kind regards
  Andreas

      reply	other threads:[~2012-11-13  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 19:10 [U-Boot] U-Boot 2012.10 PXA270 - saveenv / Kernel issue Andreas Puls
2012-11-11 20:58 ` Vasily Khoruzhick
2012-11-11 22:35   ` Rommel G Custodio
2012-11-12 12:40     ` Andreas Puls
2012-11-12 17:26     ` Andreas Puls
2012-11-13  1:05       ` Marek Vasut
2012-11-12 12:35   ` Andreas Puls
2012-11-13  1:04 ` Marek Vasut
2012-11-13  6:51   ` Andreas Puls [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=20121113065154.85000@gmx.net \
    --to=appu@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.