From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lokesh Vutla Date: Fri, 30 Oct 2020 11:41:31 +0530 Subject: Using USB Mass Storage on AM335X In-Reply-To: <36da80a3-e644-3551-9850-a4a07c5c80c6@denx.de> References: <36da80a3-e644-3551-9850-a4a07c5c80c6@denx.de> Message-ID: <00eed1c0-520a-e1ff-4a23-c4e70cc9148e@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de + Pratyush On 30/10/20 11:36 am, Heiko Schocher wrote: > Hello Otavio, > > Am 29.10.2020 um 23:19 schrieb Otavio Salvador: >> Hi, >> >> I am working on porting mainline U-Boot to a custom AM335X board that >> only has eMMC as the boot medium. >> >> I can load U-Boot via serial boot and flash MLO and u-boot.img into >> the eMMC using DFU. Then the board boots successfully via eMMC. >> >> Now I want to run the "ums" command to be able to mount the eMMC on >> the host. The problem I am getting is that when I select >> CONFIG_CMD_USB_MASS_STORAGE=y the board no longer boots. >> >> Does anyone know why selecting CONFIG_CMD_USB_MASS_STORAGE=y causes >> the board to not boot anymore? > > Not really ... I cannot see, which impact activating this command > has with not booting ... > > May some problem with image size? Early malloc space, some addresses > which now overlap? Good point. Just to avoid this scenario, can you make sure UMS is enabled only in U-Boot and not in SPL? or you can try with old MLO with new U-Boot :). As Heiko already asked, can you provide more details in the failing scenario? Thanks and regards, Lokesh