On Wednesday, January 8, 2014 11:47:12 AM UTC-5, [email protected] wrote: > > I have a setup that loads u-boot onto the BBB over the serial port, and > then tells u-boot to load the .dtb and kernel from a local TFTP server. > Loading the small .dtb file works perfectly (although slowly), and > succeeds. Loading the kernel takes too long, causes lots of retries, and > finally errors out. If I manually get the kernel from that same TFTP server > onto my laptop, it loads in about 11 seconds--over wifi--so the server is > working fine. It's just u-boot's TFTP client that seems to be causing the > errors. I have seen other messages around the net advising changing the > server's block size to 1468, which I did, and telling u-boot to turn dcache > off, which isn't an option anymore, but it still fails. >
Please note that (by accident) dcache isn't enabled for am335x targets until the upcoming release and turning off dcache will give slower, not faster, downloads. Has anyone actually got this working? Which tftp server are you using, and > what parameters? Is there a patch to u-boot that might fix its client? > I'm slightly curious as to what / whose binary you were using that was failing to work so badly that it turned out to not be a cable issue (as I was thinking it might be, on starting to read this thread). -- Tom -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" 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/groups/opt_out.
