From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukasz Majewski Date: Sat, 23 Mar 2019 22:29:05 +0100 Subject: [U-Boot] Fixing dfu_alt_info field after DM conversion In-Reply-To: References: Message-ID: <20190323222905.5dbb11f1@jawa> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Fabio, > Hi Lukasz, > > Myself and Joris have been working on DM conversion of pico-mx7 and > the the latest patches are available at: > https://github.com/jorisoffouga/u-boot/commits/pico-imx7d/convert-dm > > Things are working well so far, except eMMC flashing via DFU. > > The following error is seen we flash u-boot-dtb.img: > > => dfu 0 mmc 0 > Request would exceed designated area! > #Deferred dfu_flush() failed!=> > > Joris found a way to fix this problem by doing: > > #define CONFIG_DFU_ENV_SETTINGS \ > "dfu_alt_info=" \ > "spl raw 0x2 0x400;" \ > - "u-boot raw 0x8a 0x400;" \ > + "u-boot raw 0x8a 0x1000;" \ The change is as follows: It defines the DFU alt setting "u-boot" to be "raw" (LBA addressed) - starting from 0x8a LBA and with 0x400 * 512B = 512 KiB. Probably your u-boot is larger than 512 KiB, so you need to increase the "size" of the alt setting to be written to eMMC. In short - yes this is an acceptable fix. > "/boot/zImage ext4 0 1;" \ > "/boot/imx7d-pico-hobbit.dtb ext4 0 1;" \ > "/boot/imx7d-pico-pi.dtb ext4 0 1;" \ > > Is this an acceptable fix? > > What does the last field in dfu_alt_info mean? > > Thanks, > > Fabio Estevam Best regards, Lukasz Majewski -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: