On Fri, 2015-03-20 at 14:39 +0000, Ian Campbell wrote: > I'm going to triple check my remote recovery procedures and then do > some experiments on one of the problematic boards.
Actually, I remember I could use mw.l on the u-boot prompt to fiddle with the register values, so no need for the recovery procedure (but, still good to have). I did some quick experiments with tx delay set to 0, 1, 2 and 3 on one of the problematic boards: 0: mw.l 0x1c20164 0x006 1 -- t/o in 4/5 tftp runs 1: mw.l 0x1c20164 0x406 1 -- t/o in 1/5 tftp runs 2: mw.l 0x1c20164 0x806 1 -- t/o in 1/5 tftp runs 3: mw.l 0x1c20164 0xc06 1 -- t/o many times in first tftp run For 0, 1 and 2 "t/o" means one or two "T " glitches in the download, but it did complete. For 3 those were basically continuous and it couldn't complete. tftp was of a 16M initrd. Based on that I'm now running a full test with tx delay == 1. Ian. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
