<div dir="ltr">I meant the patch has the link truncated</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 1, 2013 at 10:31 PM, luke.leighton <span dir="ltr"><<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">talk to joe ok? really busy martin. rev3 pcb, doing the routing<br>
myself (1st board. scarey!)<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Nov 1, 2013 at 10:01 PM, martin brook<br>
<<a href="mailto:martin.brook100@googlemail.com">martin.brook100@googlemail.com</a>> wrote:<br>
> Luke Hi,<br>
><br>
> Has the text been truncated there?<br>
> "<a href="http://www.gplsquared.com/eoma_boot/script.fex_2013_09_17" target="_blank">http://www.gplsquared.com/eoma_boot/script.fex_2013_09_17</a>"<br>
><br>
><br>
> On Fri, Nov 1, 2013 at 9:22 PM, luke.leighton <<a href="mailto:luke.leighton@gmail.com">luke.leighton@gmail.com</a>><br>
> wrote:<br>
>><br>
>> good enough, martin - thank you :)<br>
>><br>
>> diff --git a/allwinner/a20/boot.mdwn b/allwinner/a20/boot.mdwn<br>
>> index 541a69b..d3b0c70 100644<br>
>> --- a/allwinner/a20/boot.mdwn<br>
>> +++ b/allwinner/a20/boot.mdwn<br>
>> @@ -1,6 +1,9 @@<br>
>> # config files<br>
>><br>
>> <a href="./script.fex">script.fex</a><br /><br>
>> +<br>
>> +I had more luck with this fex,<br>
>> <a href="http://www.gplsquared.com/eoma_boot/script.fex_2" target="_blank">http://www.gplsquared.com/eoma_boot/script.fex_2</a><br>
>> +<br>
>> <a href="./eoma68-a20-3.3-config">eoma68-a20-3.3-config</a> <br /><br>
>> <a href="./eoma68-a20-3.4-config">eoma68-a20-3.4-config</a> <br /><br>
>><br>
>> On Wed, Oct 30, 2013 at 2:05 PM, luke.leighton <<a href="mailto:luke.leighton@gmail.com">luke.leighton@gmail.com</a>><br>
>> wrote:<br>
>> > great, martin - can you add that to the wiki plese? anyhow you can.<br>
>> > thanks<br>
>> ><br>
>> > On Wed, Oct 30, 2013 at 6:35 AM, martin brook<br>
>> > <<a href="mailto:martin.brook100@googlemail.com">martin.brook100@googlemail.com</a>> wrote:<br>
>> >> I had more luck with this .fex<br>
>> >> <a href="http://www.gplsquared.com/eoma_boot/script.fex_2013_09_17" target="_blank">http://www.gplsquared.com/eoma_boot/script.fex_2013_09_17</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> On Wed, Oct 30, 2013 at 6:00 AM, luke.leighton<br>
>> >> <<a href="mailto:luke.leighton@gmail.com">luke.leighton@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> On Wed, Oct 30, 2013 at 2:08 AM, Ryan Mullen <<a href="mailto:rmmullen@gmail.com">rmmullen@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>> > Hi,<br>
>> >>> ><br>
>> >>> > I am booting an eoma68-a20 using the script.fex (converted to<br>
>> >>> > script.bin with sunxi-tools' fex2bin) found here:<br>
>> >>> ><br>
>> >>> > <a href="http://rhombus-tech.net/allwinner/a20/boot/script.fex" target="_blank">http://rhombus-tech.net/allwinner/a20/boot/script.fex</a><br>
>> >>> ><br>
>> >>> > I have run the instructions found on that page under the subtitle<br>
>> >>> > "setup boot instructions for booting directly off of sd/mmc" and all<br>
>> >>> > seems well.<br>
>> >>> ><br>
>> >>> > However, my kernel (linux-sunxi 3.4 with some custom config options)<br>
>> >>> > tells me this when booting:<br>
>> >>> ><br>
>> >>> > [ 1.663649] [mmc-msg] sw_mci_init<br>
>> >>> > [ 1.667156] [mmc-msg] get mmc1's IO(det) failed<br>
>> >>> > [ 1.671684] [mmc-msg] Not using mmc1 due to script.bin parse<br>
>> >>> > failure<br>
>> >>> > [ 1.678123] [mmc-msg] MMC host used card: 0x9, boot card: 0x0,<br>
>> >>> > io_card 8<br>
>> >>> > [ 1.685471] [mmc-msg] sdc0 set round clock 400000, src 24000000<br>
>> >>> > [ 1.691708] [mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V<br>
>> >>> > width 1 timing LEGACY(SDR12) dt B<br>
>> >>> > [ 1.702062] [mmc-msg] sdc0 Probe: base:0xf0034000 irq:64<br>
>> >>> > sg_cpu:ffdfb000(4fc00000) ret 0.<br>
>> >>> > [ 1.710382] [mmc-msg] sdc3 set round clock 400000, src 24000000<br>
>> >>> > [ 1.716717] [mmc-msg] sdc3 set ios: clk 0Hz bm OD pm OFF vdd 3.3V<br>
>> >>> > width 1 timing LEGACY(SDR12) dt B<br>
>> >>> > [ 1.726839] [mmc-msg] sdc3 Probe: base:0xf0036000 irq:67<br>
>> >>> > sg_cpu:ffdfa000(4fc01000) ret 0.<br>
>> >>> ><br>
>> >>> > After I boot an initrd, there are no /dev/mmcblk0 entries in my dev<br>
>> >>> > filesystem. However, I can make it appear if I do the following:<br>
>> >>> ><br>
>> >>> > echo 1 > /proc/driver/sunxi-mmc.3/insert<br>
>> >>> ><br>
>> >>> > This causes the card to be registered at /dev/mmcblk0 as expected.<br>
>> >>> ><br>
>> >>> > Digging deeper, it would seem that the script.fex sets the<br>
>> >>> > card-detect<br>
>> >>> > mode for mmc0 and mmc1 both to 1, which is CARD_DETECT_BY_GPIO. The<br>
>> >>> > failure in the kernel log occurs when the script.bin parser tries to<br>
>> >>> > read the "sdc_det" key and doesn't get a valid value describing the<br>
>> >>> > GPIO it should be using, I assume. mmc3 doesn't have that problem<br>
>> >>> > because script.fex sets the card-detect mode to 4, which is manual<br>
>> >>> > mode - this requires me to write a 1 to the control node in the<br>
>> >>> > procfs<br>
>> >>> > as I experienced.<br>
>> >>> ><br>
>> >>> > Is the script.fex incomplete?<br>
>> >>><br>
>> >>> almost certainly!<br>
>> >>><br>
>> >>> > What's going on here?<br>
>> >>><br>
>> >>> we're reliant on you to help diagnose that! can you please check the<br>
>> >>> GPIO line when the card is inserted, by using the gpio kernel module<br>
>> >>> (use 3.4 it's easier) flipping it to input and reading the entry? it<br>
>> >>> could be that the manual-soldering of the mmc card slot was done<br>
>> >>> poorly.<br>
>> >>><br>
>> >>> l.<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
>> >>> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>> >>> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
>> >> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>> >> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
>><br>
>> _______________________________________________<br>
>> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
>> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
<br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</div></div></blockquote></div><br></div>