Menu
▾
▴
Re: [Gumstix-users] u-boot-2010.12 broken on early rev omaps?
|
From: Steve S. <sa...@gm...> - 2011-03-25 04:04:16
|
Ah, I see you already copied him on the original email :-) Steve On Thu, Mar 24, 2011 at 9:01 PM, Steve Sakoman <sa...@gm...> wrote: > On Thu, Mar 24, 2011 at 6:21 PM, Frank Agius <ft...@ya...> wrote: >> I have various vintages of overo's, some purchased fairly recently and >> others more than 18 months old. I've been systematically upgrading >> u-boot on all boards to u-boot-2010-.12. On the newer boards, the >> process has gone smoothly, but on the older boards (all with OMAP >> revision 2.1), u-boot fails to load as follows: >> >> Hiy key to stop autoboot: 0 >> reading boot.scr >> >> 212 bytes read >> Running bootscript from mmc ... >> ## Executing script at 82000000 >> Testing >> reading uImage >> mmc_send_cmd: timedout waiting for cmddis! >> mmc fail to send stop cmd >> mmc_send_cmd: timedout waiting for cmddis! >> Invalid FAT entry >> >> 743424 bytes read >> Wrong Image Format for bootm command >> ERROR: can't get kernel image! >> >> I did some debug and found that the problem was introduced into >> u-boot-2010.12.rc3 with a checkin that added multiblock read support to >> the mmc driver. According to the TI docs, multiple block read transfer >> does not work correctly in CPU revisions 2.1 and earlier (TI advisory >> 2.1.1.128). I think that a potential fix is the check the cpu revision >> in mmc code that does the block read and only attempt multiblock if the >> revision is > 2.1. > > I'll ping the author of the multi-block read patch and see if he has > any ideas on how best to implement this. > > Steve > |