From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: u-boot-flasher fails with current u-boot Date: Tue, 6 Jun 2017 23:36:38 +0000 Message-ID: <84tw3sk7sq.wl-Peter.Chubb@data61.csiro.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-Language: en-US Content-ID: <3728F29185C0224A9D7488DC679C01D2-uXK74I8fpZ0@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org, sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org List-Id: linux-tegra@vger.kernel.org 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 --=20 Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group Data61 (formerly NICTA)=