Date: Tue, 20 May 2014 23:42:45 +0900 (JST) From: SAITOU Toshihide <toshi@ruby.ocn.ne.jp> To: madis555@hot.ee Cc: freebsd-arm@freebsd.org Subject: Re: BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz) Message-ID: <20140520.234245.38709064.toshi@ruby.ocn.ne.jp> In-Reply-To: <537B62D1.4090901@hot.ee> References: <20140520.191001.03109216.toshi@ruby.ocn.ne.jp> <20140520.212003.232778263.toshi@ruby.ocn.ne.jp> <537B62D1.4090901@hot.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <537B62D1.4090901@hot.ee>
"Sulev-Madis Silber (ketas)" <madis555@hot.ee> writes:
> On 2014-05-20 15:20, SAITOU Toshihide wrote:
>> In message: <20140520.191001.03109216.toshi@ruby.ocn.ne.jp>
>> SAITOU Toshihide <toshi@ruby.ocn.ne.jp> writes:
>>> In message: <537ACDB2.9080808@hot.ee>
>>> "Sulev-Madis Silber (ketas)" <madis555@hot.ee> writes:
>>>>
>>>> Actually I guess many people might think like me... "HELL, optimizing
>>>> boot time of 1min?! I have more important tasks to do than this".
>>>
>>> If you have ``device sdhci'' line in conf/BEAGLEBONE, is there any
>>> differences by changing mmchs to sdhci in am335x.dtsi and
>>> beaglebone-black.dts? And also remove ``status = "disabled"''
>
> Don't edit am335x.dtsi
>
> And beaglebone-black.dts already has proper config.
In this case, how does ``device sdhci'' driver know the register address?
I thought that there is an inconsistency in BEAGLEBONE config and
dts file for the SD/MMC driver.
>>> It's needed for me to detect eMMC, and the perfomance is
>>> better: http://lists.freebsd.org/pipermail/freebsd-arm/2013-August/006332.html
>>>
>>> But I don't success to boot from eMMC yet with u-boot-2014.04. I need
>>> to change u-boot.
>>
>> It was booted from eMMC, though it failed sometimes.
>
> Are you sure it booted from eMMC? Like, I can't find eMMC in loader
> (ubldr). So I need SD to complete this part of boot.
>
> Not sure what I need to patch, probably loader? Hopefully the old uboot
> can be used as well. Version check or something...
Yes sure, because SD card is detached. The pach is for u-boot.
>> u-boot-2014.04.tar.bz2
>>
>> patch
>>
>> 1. apply these patches:
>>
>> http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007922.html
>> ~/crochet-freebsd/board/BeagleBone/files/uboot-2013.04_api_api_storage.c.patch
>> ~/crochet-freebsd/board/BeagleBone/files/uboot-2013.04_drivers_mmc_mmc.c.patch
>>
>> patch -p1 or edit.
>>
>> 2. add followings to include/configs/am335x_evm.h:
>>
>> #ifndef CONFIG_SPL_BUILD
>> #define CONFIG_CMD_ELF
>> #define CONFIG_API
>> #define CONFIG_SYS_MMC_MAX_DEVICE 2
>> #endif
>>
>> 3. comment WATCHDOG in include/configs/ti_am335x_common.h:
>>
>> #define CONFIG_HW_WATCHDOG
>> #define CONFIG_OMAP_WATCHDOG
>>
>> #define CONFIG_SPL_WATCHDOG_SUPPORT
>>
>> build
>>
>> gmake CROSS_COMPILE=arm-eabi- am335x_boneblack_config
>> gmake CROSS_COMPILE=arm-eabi-
>>
>>
>> uEnv.txt
>>
>> bootdelay=2
>> fdtaddr=0x80000100
>> loadaddr=0x88000000
>> loaderdev=disk
>> fdtfile=beaglebo.dtb
>> bootdir=
>> bootfile=ubldr
>> mmcdev=1
>> mmcloados=mmc rescan
>> loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
>> importbootenv=env import -t $loadaddr $filesize
>> findfdt=setenv fdtfile beaglebo.dtb
>> loadimage=fatload mmc ${mmcdev} ${loadaddr} ${bootfile}
>> loadfdt=fatload mmc ${mmcdev} ${fdtaddr} ${fdtfile}; fdt addr ${fdtaddr}
>> mmcboot=bootelf ${loadaddr}
>> nandboot=run mmcboot
>>
>> Please ignore ``Card did not respond to voltage select!'' message.
>>
>
> Crochet already has all those patches, so I use uboot from there.
Yes, I use patches of crochet for u-boot-2014.04.
--
SAITOU Toshihide
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140520.234245.38709064.toshi>