BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz)

[SAITOU Toshihide]

In message: <CADH-AwFWPn6=tRVATAOw=PoGO-0AvF8j-vv4Ko1An=0qqpbhuw at mail.gmail.com>
            Winston Smith <smith.winston.101 at gmail.com> writes:
> On Sat, May 24, 2014 at 7:08 AM, SAITOU Toshihide <toshi at ruby.ocn.ne.jp> wrote:
>>>> > Does it fix the problem to move the ti_prcm_clk_enable() call to be
>>>> > before the USBSS_REVREG read in attach?
>>>>
>>>> I will try ti_prcm_clk_enable() at the weekend. But someone's report
>>>> would be appriciated because I remove the src and svn up now.
> 
> Just to clarify; you applied the ti_prcm_clk_enable() to fix the
> 'non-linefetch abort' (above).

No. I revert back and update the source about two days before, and so
far, I can't reproduce the above failure.


>> BEAGLEBONE config is changed to include beaglebone-black.dts, boot
>> from SD by pressing S2, repeat power cycle and hit enter key randomly
>> when ``Hit [Enter] to boot immediately''.
>>
>> result:
>>
>>   'external non-linefetch abort' was disappeared, and very few
>>   'translation fault' was observed.
>>
>>      vm_fault(0xc092d960, 0, 1, 0) -> 1
>>      Fatal kernel mode data abort: 'Translation Fault (S)'
>>      trapframe: 0xc0a26b30
>>      FSR=00000005, FAR=00000018, spsr=80000193
>>      r0 =c288d380, r1 =00000000, r2 =00000019, r3 =60000193
>>      r4 =00000000, r5 =c288d380, r6 =00000006, r7 =c053e8fc
>>      r8 =c288d380, r9 =c28e928c, r10=c28e70c8, r11=c0a26b90
>>      r12=00000000, ssp=c0a26b80, slr=c055fedc, pc =c0391098
>>
>>      [ thread pid 0 tid 100000 ]
>>      Stopped at      device_delete_child+0x14:       ldr     r1, [r4, #0x018]
> 
> But now you're running into these 'translation fault' traps?

But only very few, plus I may have a bias when operating power cycle
(for expecting the same result).

-- 
SAITOU Toshihide