From: <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org
Subject: u-boot-flasher fails with current u-boot
Date: Tue, 6 Jun 2017 23:36:38 +0000 [thread overview]
Message-ID: <84tw3sk7sq.wl-Peter.Chubb@data61.csiro.au> (raw)
Recent changes to U-Boot have broken u-boot-flasher. I now see,
after
./tegra-uboot-flasher flash jetson-tk1
on the serial port:
>>> Selecting MMC device...
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
and nothing is flashed to the MMC.
I can do
./tegra-uboot-flasher exec jetson-tk1
and everything works as expected. The running-from-RAM u-boot can
access the MMC.
The patch in U-Boot that causes the problems (found by git-bisect) is
0e513e788f tegra: convert MMC to use driver model for operations
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
next reply other threads:[~2017-06-06 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 23:36 Peter.Chubb-RgbkMxAV74wUb6iz2VnApA [this message]
[not found] ` <84tw3sk7sq.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
2017-06-07 3:13 ` u-boot-flasher fails with current u-boot Simon Glass
2017-06-07 4:01 ` Peter.Chubb
2017-06-08 1:12 ` Peter.Chubb
[not found] ` <84vao7uvsz.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
2017-06-08 3:11 ` Simon Glass
[not found] ` <CAPnjgZ3GhGGq8SrtXNOQyh5V7Xm2X_pfKcrrbHkyVNXcfvWCjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-08 4:00 ` Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
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=84tw3sk7sq.wl-Peter.Chubb@data61.csiro.au \
--to=peter.chubb-rgbkmxav74wub6iz2vnapa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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