From: Peter.Chubb at data61.csiro.au <Peter.Chubb@data61.csiro.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-flasher fails with current u-boot
Date: Thu, 8 Jun 2017 01:12:30 +0000 [thread overview]
Message-ID: <84vao7uvsz.wl-Peter.Chubb@data61.csiro.au> (raw)
In-Reply-To: <848tl430qh.wl-Peter.Chubb@data61.csiro.au>
>>>>> "Peter" == Peter Chubb <Peter.Chubb@data61.csiro.au> writes:
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
Simon> Oh dear. I cannot find my board but will see if I can repeat
Simon> this on a beaver.
Peter> If there's any additional logging you'd like me to collect on
Peter> the Jetson, let me know.
I tried to reproduce this this morning. Today, even trying to exec
the U-Boot without flashing fails.
So,
./tegra-uboot-flasher exec jetson-tk1
with a current u-boot gives an inoperative eMMC.
In the boot header I see:
U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
TEGRA124
Model: NVIDIA Jetson TK1
Board: NVIDIA Jetson TK1
DRAM: 2 GiB
MMC: sdhci at 700b0400: 1, sdhci at 700b0600: 0
Then:
Tegra124 (Jetson TK1) # mmc rescan
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
Peter C
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
next prev parent reply other threads:[~2017-06-08 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84tw3sk7sq.wl-Peter.Chubb@data61.csiro.au>
2017-06-07 3:13 ` [U-Boot] u-boot-flasher fails with current u-boot Simon Glass
2017-06-07 4:01 ` Peter.Chubb at data61.csiro.au
2017-06-08 1:12 ` Peter.Chubb at data61.csiro.au [this message]
2017-06-08 3:11 ` Simon Glass
2017-06-08 4:00 ` Peter.Chubb at data61.csiro.au
2017-06-09 12:28 ` Simon Glass
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=84vao7uvsz.wl-Peter.Chubb@data61.csiro.au \
--to=peter.chubb@data61.csiro.au \
--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