Any information you're willing to share as to how you load files via serial
would be awesome. Personally, I love reading about this sort of thing . ..


On Wed, Jan 8, 2014 at 11:22 AM, <[email protected]> wrote:

> Thanks, and I'd seen that article, but you're right--I'm doing something
> different. I have a BBB-based development board, and I'm writing a script
> that loads a full distribution onto it starting from a blank slate--i.e.,
> nothing in the eMMC, no SD card. Most of it is working.
>
> I think Jack is right--it's a network driver issue. When I revert to the
> stock u-boot v2013.10, the tftp works better.
>
> On Wednesday, January 8, 2014 9:59:29 AM UTC-8, William Hermans wrote:
>>
>> http://www.embeddedhobbyist.com/debian-tips/beaglebone-
>> black/beaglebone-black-network-boot/
>>
>> The above link is an article I wrote in the subject of network booting.
>> uboot, MLO, and uEnv.txt are on an SD card, but the kernel, and device tree
>> overlay  is pulled in via TFTP, finally rootfs over NFS.
>>
>> This works fine, and might be a little slow, but nothing like what you're
>> explaining in your post. I am just using the standard package that comes
>> with Debian wheezy stable, and I have never experienced these problems
>> you're mentioning here.
>>
>>
>>
>>
>> On Wed, Jan 8, 2014 at 9:51 AM, Jack Mitchell 
>> <[email protected]>wrote:
>>
>>> On 08/01/14 16:47, [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.
>>> >
>>> > 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?
>>> >
>>> > --
>>> > 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.
>>>
>>> Which version of u-boot are you using? Could it not also be the ethernet
>>> drivers? I would try updating to the latest u-boot version and see if
>>> you're still having issues.
>>>
>>> Cheers,
>>>
>>> --
>>>   Jack Mitchell ([email protected])
>>>   Embedded Systems Engineer
>>>   Cambridgeshire, UK
>>>   http://www.embed.me.uk
>>> --
>>>
>>> --
>>> 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.
>>>
>>
>>  --
> 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.
>

-- 
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.

Reply via email to