public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Need help to get u-boot running on the taskit stamp9g20
Date: Thu, 12 Jul 2012 11:28:13 +0200	[thread overview]
Message-ID: <4FFE98AD.7070107@gmail.com> (raw)
In-Reply-To: <CAGws1Ttp+LsKa18DpmWz-Q4d94sEeM84rOJZ+9=kS_YnGx0-Dw@mail.gmail.com>

Dear Markus Hubig,

On 11.07.2012 21:28, Markus Hubig wrote:
> Hello @all,
> 
> as part of my bachelor thesis I'm working with the stamp9g20 / portuxg20
> board from taskit (http://www.taskit.de/produkte/stamp9g20/index.htm). I
> have a patch for a older version (2010.somewhat) of u-boot to get it running
> on this board, but this patch is not working anymore.

well, there where a lot of architectural changes (renames, drop of old
code, ...) in at91 around 2011. This is still work in progress, however
nothing happened since Reinhard gave up. I hope to bring this to an end
this year.

> Now I'm in the process of adapting this patch to the new u-boot. Up to now
> I can compile a u-boot.bin and download it to the board. But after starting up
> the new u-boot I just see this on the serial port
> 
> ---8<------------------------------------------
> U-Boot 2012.04.01-00001-gadcb359-dirty (Jul 11 2012 - 19:24:58)
> 
> CPU: AT91SAM9G20
> Crystal frequency:   18.432 MHz
> CPU clock        :  396.288 MHz
> Master clock     :  132.096 MHz
> DRAM:  64 MiB
> WARNING: Caches not enabled
> NAND:  RomBOOT
> ---8<------------------------------------------

So something went wrong in nand_init()? Two things you should do:
 a) as Wolfgung suggested previously: disable the Watchdog
 b) check for the 'NAND Ready' Pin (use some oscilloscope);
    alternatively just remove the CONFIG_SYS_NAND_READY_PIN R/B should
    be handled by the nand_base driver in another way then.

> and the board is rebooting every some seconds. I'm not able to give it some
> input via the keyboard. I think maybe there are just some small bits missing
> but I'm a bit lost now ... maybe some of you can have a look and can give me
> some advice. ;-)

enable debug for all the drivers/mtd/nand files, put in some more debug
printouts where necessary.

> I include the old patch (portuxg20.patch) and the three patches I made in this
> email. My patches are based on u-boot v2012.04.01.

Please send the patches in line, Wolfgang already sent a pointer
describing ho to achieve this.

Another not related question: What is your Bachelor thesis about? Is
there some space to implement some basic SPL for u-boot on at91?

I'm looking forward to get proper patches for the stamp9g20 to have this
device mainlined. Unfortunately Taskit has not tried to bring their
devices to mainline in the past. Therefore I think this would be your
task if you (or the company you working for) want this device supported
by u-boot mainline code. I don't want to summarize all the advantages,
you just hit one problem of out of tree code ...


Best regards

Andreas Bie?mann

  parent reply	other threads:[~2012-07-12  9:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 19:28 [U-Boot] Need help to get u-boot running on the taskit stamp9g20 Markus Hubig
2012-07-12  6:07 ` Wolfgang Denk
2012-07-12 15:53   ` Markus Hubig
2012-07-12  9:28 ` Andreas Bießmann [this message]
2012-07-12 15:49   ` Markus Hubig
2012-07-12 23:04     ` Andreas Bießmann
2012-07-18 13:21       ` Markus Hubig
2012-07-20 13:08         ` Markus Hubig
2012-07-20 14:26           ` Markus Hubig
2012-07-21 22:03             ` Wolfgang Denk
2012-07-24 15:43               ` Markus Hubig
2012-07-27  8:59                 ` [U-Boot] [SOLVED] " Markus Hubig

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=4FFE98AD.7070107@gmail.com \
    --to=andreas.devel@googlemail.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