public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuno Santos <nuno.m.santos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: NVFlash hangs when flashing U-Boot on Tegra2 board
Date: Mon, 23 Jul 2012 08:45:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120723T101555-779@post.gmane.org> (raw)

Hi

I have a Tegra2 based board (Harmony) running Linux. It is currently booting 
using the fastboot.bin bootloader shipped with NVIDIA's SDK Developer Kit, but 
I need to replace it for U-Boot, because U-Boot is open source.

So far I've been able to successfully deploy U-Boot on the device using nvflash 
and U-Boot actually runs. However, nvflash hangs waiting for the bootloader to 
finish initializing and therefore flashing won't happen. Apparently nvflash is 
expecting the bootloader to follow some protocol, which U-Boot apparently
is not aware of.

I'd really appreciate any help on this and I'm sorry in advance if this is not
the right forum to publish this question. It has been really hard to find 
information on the web about this. Furthermore, I haven't been able to find
nvflash source code anywhere, which could help tremendously to investigate
what's going on; if at least someone could point me to where I can download
I'd be deeply grateful.

So, this is what I'm using to flash the bootloader:

sudo ./nvflash --bct flash.bct --setbct --configfile flash.cfg --create 
    --bl u-boot-dtb.bin --go

(I've updated the file name of the bootloader in flash.cfg, but apparently it 
doen't affect the outcome)

The output is this:

----------------------------------------
Nvflash v1.1.54599 started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 2
   chip sku: 0x8
   chip uid: 0x161c10c541006317
   macrovision: disabled
   hdcp: enabled
   sbk burned: false
   dk burned: false
   boot device: nand
   operating mode: 3
   device config strap: 0
   device config fuse: 0
   sdram config strap: 0

sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: u-boot-dtb.bin
/ 244122/244122 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
----------------------------------------

And it hangs while U-Boot has actually started executing in the device. If I
reset the board, nvflash  unblocks and prints out the following output:

----------------------------------------
usb read error (71): Protocol error
bootloader failed NvError 0x0
command failure: bootloader download failed 
----------------------------------------


Many thanks in advance!
--Nuno

             reply	other threads:[~2012-07-23  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  8:45 Nuno Santos [this message]
     [not found] ` <loom.20120723T101555-779-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2012-07-23  9:54   ` NVFlash hangs when flashing U-Boot on Tegra2 board Alex Courbot
     [not found]     ` <500D1F5C.1060603-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-23 15:11       ` Nuno Santos
     [not found]         ` <500D698B.3040405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-23 19:07           ` Stephen Warren

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=loom.20120723T101555-779@post.gmane.org \
    --to=nuno.m.santos-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox