All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Evade Flow <evadeflow-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Flash Yocto-built kernel on Tegra2 T20?
Date: Wed, 31 Oct 2012 22:47:38 -0600	[thread overview]
Message-ID: <5091FEEA.3050905@wwwdotorg.org> (raw)
In-Reply-To: <CAMAb8ZN3m2Vj1o0gJaRSE5xbu2e2ih84YF_8UP1o-ztPfmj7KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 10/31/2012 04:46 PM, Evade Flow wrote:
...
> The old system's burnflash.sh script is executing the following
> commands:
...
> With the flash.sh script from NVIDIA, I'm seeing this:
...
> The differences that jump out are:
...
> 4. diffs boils down to contents of .cfg and .bct files
> 5. also pass different --odmdata args

BCT files and ODMDATA are board-specific. You should certainly use the
values from the script that's specific to your board.

Apart from that, all I can really suggest is to get the flashing process
working with the exact kernel source for the kernel binary you have that
already works. Then, once you've worked out those kinks, you could try
using a different kernel source base.

BTW, I have no idea if the L4T kernel you're trying to use has support
for p852; did you check or explicitly add it? It doesn't seem that
surprising it won't work, since the the L4T kernel is likely separate
from any kernel used by the embedded/automotive team.

My suggestion would be to try to get mainline U-Boot and Linux working
instead. You would need board schematics for that (or a working kernel
as a reference). If you have some specific need to run the downstream
L4T kernel instead, it'd be best to talk to your support contacts at NVIDIA.

  parent reply	other threads:[~2012-11-01  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 18:29 Flash Yocto-built kernel on Tegra2 T20? Evade Flow
     [not found] ` <CAMAb8ZNts=SB2rhD8BU+_wAQ84S3tOzwGazr5hnTveMt-BdwGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-31 22:46   ` Evade Flow
     [not found]     ` <CAMAb8ZN3m2Vj1o0gJaRSE5xbu2e2ih84YF_8UP1o-ztPfmj7KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-31 23:04       ` Evade Flow
2012-11-01  4:47       ` Stephen Warren [this message]
2012-10-31 23:06   ` Stephen Warren
     [not found]     ` <5091AEE4.6080907-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-01 21:24       ` Evade Flow

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=5091FEEA.3050905@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=evadeflow-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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.