Dallas,

Thanks for that link, I've never seen it before and will likely be of some
use in the future if I need to boot via serial. Looks very intensive too.


On Wed, Jul 23, 2014 at 5:03 PM, John Syn <[email protected]> wrote:

>
> From: Dallas Clement <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Wednesday, July 23, 2014 at 3:35 PM
> To: "[email protected]" <[email protected]>
>
> Subject: Re: [beagleboard] Want to serial boot my BBB
>
> It looks like next step is to load u-boot.img, which works nicely.  Thanks
> for the clues everyone!
>
> This web-page is a very helpful guide for anyone else trying to boot from
> the serial port:
> http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_UBoot_Board_Port
>
> Looking at the wiki, I think the 06.00.00.00.00-template is probably
> stripped of most u-boot functionality (ethernet, mmc, etc) and is able to
> fit into SRAM and that is why MLO is not needed.
>
> Regards,
> John
>
>
>
>
>
> On Wed, Jul 23, 2014 at 7:26 AM, Dallas Clement <
> [email protected]> wrote:
>
>> Hi Steve, It looks like the u-boot-spl.bin is working.  This is what I'm
>> seeing on my minicom console:
>>
>> Welcome to minicom 2.6.1
>>
>>
>>
>> OPTIONS: I18n
>>
>> Compiled on Feb 11 2012, 18:12:55.
>>
>> Port /dev/ttyUSB0
>>
>>
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>>
>> ot SPL 2013.07-00012-g31df114 (Jul 11 2014 - 20:33:02)
>>
>> CCCCCCCCC
>>
>> Is the next step to send a MLO?
>>
>>
>> On Tue, Jul 22, 2014 at 5:33 PM, Dallas Clement <
>> [email protected]> wrote:
>>
>>> Thanks Steve.  That was my understanding as well.  I'll give that a shot.
>>>
>>>
>>> On Tue, Jul 22, 2014 at 4:20 PM, Steve <[email protected]> wrote:
>>>
>>>> For UART or USB you do not use the MLO file. When you build u-boot you
>>>> should have a spl/u-boot-spl.bin file. This is what you send over x-modem.
>>>> The MLO file is only used for Memory Booting (SD/Card, eMMC) while the
>>>> u-boot-spl.bin file is used for Peripheral Booting (UART, USB).
>>>>
>>>> Steve K.
>>>>
>>>>
>>>> On Tuesday, July 22, 2014 7:55:51 AM UTC-5, Dallas Clement wrote:
>>>>
>>>>> I was able to send the MLO file via minicom / x-modem just fine to the
>>>>> board. However after the transfer completed, nothing happened.  Should I
>>>>> expect to see any output on the serial console afterward?
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 10:14 AM, Dallas Clement <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Okay, thanks very much!  I'll give that a try.
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 3:23 AM, liyaoshi <[email protected]> wrote:
>>>>>>
>>>>>>> Sorry , I have made a mistake .
>>>>>>>
>>>>>>> On omap3 board ,you should use pserial to download from serial
>>>>>>> And on am335x / dm8148 board. x-modem is enough.and MLO is for boot
>>>>>>> from serial
>>>>>>>
>>>>>>> So , please try to use teraterm , and upload from
>>>>>>> file->transfer->xmodem->send.
>>>>>>> Then power on the beaglebone board .
>>>>>>>
>>>>>>>
>>>>>>> 2014-07-21 16:17 GMT+08:00 liyaoshi <[email protected]>:
>>>>>>>
>>>>>>> If I remember correctly , You should load x-loader.bin  NOT MLO
>>>>>>>> While the different between MLO and x-loader.bin is MLO has 8 bytes
>>>>>>>> head , the first 4 bytes is dest and the second 4 bytes is length .
>>>>>>>> This is for boot from NAND /eMMC , and when download from serial .
>>>>>>>> the boot rom will download to fixed address and limit length .
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-07-21 12:04 GMT+08:00 John Syn <[email protected]>:
>>>>>>>>
>>>>>>>>
>>>>>>>>> From: Dallas Clement <[email protected]>
>>>>>>>>> Reply-To: "[email protected]" <[email protected]>
>>>>>>>>>
>>>>>>>>> Date: Sunday, July 20, 2014 at 9:19 AM
>>>>>>>>> To: "[email protected]" <[email protected]>
>>>>>>>>>
>>>>>>>>> Subject: Re: [beagleboard] Want to serial boot my BBB
>>>>>>>>>
>>>>>>>>> One other data point.  If I don't press and hold the boot switch
>>>>>>>>> when power is applied and instead wait a few seconds after applying 
>>>>>>>>> power
>>>>>>>>> and then press the boot switch, the pserial command is able to detect 
>>>>>>>>> the
>>>>>>>>> ASIC ID and download the x-loan.bin.
>>>>>>>>>
>>>>>>>>> You should be loading MLO, not x-load.bin. I also haven’t tried
>>>>>>>>> this myself, but loading via serial shouldn’t be any different from 
>>>>>>>>> loading
>>>>>>>>> from tftp. The load addresses should be identical.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> $ sudo ./pserial -p /dev/ttyUSB0 -f x-load.bin
>>>>>>>>> Waiting For Device ASIC ID: Press Ctrl+C to stop
>>>>>>>>> ASIC ID Detected: 0x85 0x74 0x61 0x90
>>>>>>>>> Sending 2ndFile:
>>>>>>>>> Downloading file: 100.000% completed (10516/10516 bytes)
>>>>>>>>> File download completed.
>>>>>>>>>
>>>>>>>>> However, the BBB boots from the eMMC instead of the x-loan.bin I
>>>>>>>>> downloaded.  So this is progress.  It means that my pserial command 
>>>>>>>>> does
>>>>>>>>> work with a BBB and the BBB ROM code does respond with its ASIC ID 
>>>>>>>>> and does
>>>>>>>>> in fact download the x-load.bin.  It looks like I just need to figure 
>>>>>>>>> out
>>>>>>>>> what the correct boot switch power on sequence is now.
>>>>>>>>>
>>>>>>>>> On Sunday, July 20, 2014 10:36:45 AM UTC-5, Dallas Clement wrote:
>>>>>>>>>>
>>>>>>>>>> Hi William.  Thanks for the help.  I'm stuck much earlier on than
>>>>>>>>>> u-boot.  I am expecting the ROM to return the ASIC ID when I run the
>>>>>>>>>> pserial command to try and load the first stage boot loader 
>>>>>>>>>> (x-load.bin).
>>>>>>>>>>  I'm not even able to get past that.  It looks like either I have 
>>>>>>>>>> the wrong
>>>>>>>>>> pserial command or maybe the BBB ROM does not provide an ASIC ID.  I 
>>>>>>>>>> don't
>>>>>>>>>> know enough about the Sitara processor to say.  If I can get the 
>>>>>>>>>> x-loader
>>>>>>>>>> to work, I think I am home free because it should be able to load a
>>>>>>>>>> u-boot.bin.
>>>>>>>>>>
>>>>>>>>>> On Sunday, July 20, 2014 10:18:50 AM UTC-5, William Hermans wrote:
>>>>>>>>>>>
>>>>>>>>>>> Ok after reading the second link fully, I noticed a few things.
>>>>>>>>>>>
>>>>>>>>>>> First, the boot file is different. We have zImage typically, so
>>>>>>>>>>> I would assume the bootz command would be necessary. *OR* you could 
>>>>>>>>>>> convert
>>>>>>>>>>> a zImage to uImage.
>>>>>>>>>>>
>>>>>>>>>>> Secondly, the base load address is different, so this would need
>>>>>>>>>>> to be taken into account. Although I think changing this would be 
>>>>>>>>>>> fairly
>>>>>>>>>>> simple.
>>>>>>>>>>>
>>>>>>>>>>> Lastly, we also need to load the device tree board file, and I
>>>>>>>>>>> am a bit confused about this for loading serially.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Jul 20, 2014 at 7:59 AM, William Hermans <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> uboot is supposed to handle serial booting. However, I have no
>>>>>>>>>>>> personal hands on. Just a quick google search showed many results 
>>>>>>>>>>>> however.
>>>>>>>>>>>> One thing to note is that uboot for the BBB is patched, so possibly
>>>>>>>>>>>> different. It does not however make sense for this feature to be 
>>>>>>>>>>>> patched
>>>>>>>>>>>> out, so I would assume that it should work.
>>>>>>>>>>>>
>>>>>>>>>>>> Sorry for the less than definitive answer, perhaps someone with
>>>>>>>>>>>> hands on will respond. You can however experiment on your own.
>>>>>>>>>>>>
>>>>>>>>>>>> http://blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:
>>>>>>>>>>>> serial_port_loading_files
>>>>>>>>>>>> http://blog.mezeske.com/?p=483
>>>>>>>>>>>>
>>>>>>>>>>>> $ apt-cache search ckermit
>>>>>>>>>>>> ckermit - serial and network communications package
>>>>>>>>>>>>
>>>>>>>>>>>> Second link package mentioned is available, so looks to be
>>>>>>>>>>>> possible.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Jul 20, 2014 at 7:44 AM, Dallas Clement <
>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am trying to boot my BBB over a serial connection, and need
>>>>>>>>>>>>> a little help.  I have followed the instructions for UART 
>>>>>>>>>>>>> recovery listed
>>>>>>>>>>>>> here http://elinux.org/BeagleBoardRecovery
>>>>>>>>>>>>>
>>>>>>>>>>>>> I built the pserial tool and an x-loan.bin, but when I try to
>>>>>>>>>>>>> load it, I just getting hanging.
>>>>>>>>>>>>>
>>>>>>>>>>>>> $ sudo ./pserial -p /dev/ttyUSB0 -f x-load.bin
>>>>>>>>>>>>> Waiting For Device ASIC ID: Press Ctrl+C to stop
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am using a 6 pin TTL to USB cable to my PC.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Perhaps the x-load.bin I am using is for the wrong processor
>>>>>>>>>>>>> (BeagleBoard)?  If so, maybe I can convert the MLO produced by 
>>>>>>>>>>>>> the BBB
>>>>>>>>>>>>> u-boot build to a x-load.bin.  Just need a few pointers on how to 
>>>>>>>>>>>>> do that.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Dallas
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> 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/d/optout.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> For more options, visit http://beagleboard.org/discuss
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>> the Google Groups "BeagleBoard" group.
>>>>>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>>>>>> topic/beagleboard/bsIWXc2pJJY/unsubscribe.
>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>> [email protected].
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> For more options, visit http://beagleboard.org/discuss
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "BeagleBoard" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/beagleboard/bsIWXc2pJJY/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>
> --
> 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/d/optout.
>
>  --
> 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/d/optout.
>

-- 
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/d/optout.

Reply via email to