public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <bard.shen@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] timing issue - uboot freeze after pringing header
Date: Mon, 18 Feb 2013 11:06:55 +0800	[thread overview]
Message-ID: <51219ACF.9050201@gmail.com> (raw)
In-Reply-To: <1360946736.13529.335.camel@genx>

Hi John,

On 02/16/2013 12:45 AM, John Stile wrote:
> I am trying to move from uboot-1.3.6 to uboot 2013.01, where the old
> works, the new prints this before freezing:
>
>          U-Boot 2013.01 (Feb 14 2013 - 16:24:13)
>
>          CPU: AT91SAM9G20
>          Crystal frequency:   18.432 MHz
>          CPU clock        :  396.288 MHz
>          Master clock     :  132.096 MHz
>
> My board is the at91sam9g20ek_2mmc.
> at91bootstrap-1.1.6 loads uboot.

Please update the at91bootstrap to new version.
You can get the it from: git://github.com/linux4sam/at91bootstrap.git
using tag: v3.5.2
or master branch

For new bootstrap, the memory map for NAND flash has changed. More 
information: 
http://www.at91.com/linux4sam/bin/view/Linux4SAM/GettingStarted#Linux4SAM_NandFlash_demo_Memory

So, you need flash u-boot to 0x40000 address, and change u-boot env as 
the memory map (I will send patches for this later).

Best Regards,
Bo Shen

> I am trying both nandflash and dataflash versions, using
> include/configs/at91sam9260ek.h
>
> Messing with settings I have got it back to a state of not printing
> anything.
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

  reply	other threads:[~2013-02-18  3:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 16:45 [U-Boot] timing issue - uboot freeze after pringing header John Stile
2013-02-18  3:06 ` Bo Shen [this message]
2013-02-19 21:12   ` John Stile

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=51219ACF.9050201@gmail.com \
    --to=bard.shen@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