Beaglebone Bootloader

Tue Jun 23 04:59:34 UTC 2015

If it is any help. this is the configuration on my SDCard that loads debian
linux from SDCard.

##Video: Uncomment to override:
##see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt
#kms_force_mode=video=HDMI-A-1:1024x768 at 60e

##Enable systemd
systemd=quiet init=/lib/systemd/systemd

##BeagleBone Cape Overrides

##BeagleBone Black:
##Disable HDMI/eMMC
#optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G

##Disable HDMI
#optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

##WIP: v3.13+ capes..
#cape=lcd4-01
#cape=

##note: the eMMC flasher script relies on the next line
mmcroot=UUID=8f529ad7-82d1-4d8e-91dc-31e9e2080813 ro
mmcrootfstype=ext4 rootwait fixrtc

##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
console=ttyO0,115200n8

kernel_file=zImage
initrd_file=initrd.img

loadaddr=0x82000000
initrd_addr=0x88080000
fdtaddr=0x88000000

initrd_high=0xffffffff
fdt_high=0xffffffff

loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file};
setenv initrd_size ${filesize}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}

loadfiles=run loadkernel; run loadinitrd; run loadfdt
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
${kms_force_mode} root=${mmcroot} rootfstype=${mmcrootfstype} ${systemd}

uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr}
${initrd_addr}:${initrd_size} ${fdtaddr}
#

On Tue, Jun 23, 2015 at 12:59 PM, Angelo Fraietta <
newsgroups at smartcontroller.com.au> wrote:

> I can see I missed a step from Ben's tutorial where it creates the image
> file.
> I copied the image to tftp and it did not work
>
> I also tried doing out of Bens tutorial the
>
> dd if=bone_hello.exe-sdcard.img of=/dev/mmcblk0 bs=4096
>
> However, nothing was displayed on my monitor and the three LEDS lit,
> followed by the light on ethernet port. It did this about three times and
> then booted into normal BBB linux. It looked to me like it was resetting,
> however, can't be sure.
>
> Is someone able to email me a working image for BBB so I can see it that
> will boot.
>
> Thanks
>
> On Tue, Jun 23, 2015 at 8:46 AM, Angelo Fraietta <
> newsgroups at smartcontroller.com.au> wrote:
>
>> Does not boot.
>> I have u-boot on the SD card. I know it is being called because if I
>> disconnect the ethernet, it freezes and does not boot. If I remove SDcard
>> and remove ethernet, it boots normally
>> I have tftp on 192.168.0.25
>>
>> My configuration is exactly this
>>
>> ### BBB : Configuration
>> ipaddr=192.168.0.53
>> serverip=192.168.0.25
>> netmask=255.255.255.0
>>
>> ### XKY-OS : Configuration
>> baseaddr=0x81000000
>> application=/TICKER
>>
>> ### Boot BBB from network
>> nfsargs=setenv bootargs console=${console} root=/dev/nfs
>> nfsroot=${serverip}:${rootpath} rw
>> ip=${ipaddr}:${serverip}:${serverip}:${netmask}::eth0:off
>> xkyboot=run nfsargs; tftp ${baseaddr} ${application}; bootm ${baseaddr}
>> uenvcmd=run xkyboot
>>
>>
>> I have copied ticker.exe to root folder
>> I tried
>> application=/TICKER
>> application=/ticker.exe
>> application=/TICKER.EXE
>>
>> Just boots into normal regardless of what I do (except removing ethernet
>> with SDCard in). Looking at U-boot in display looks the same as though
>> three was no SDcard. How can I freeze screen to read what it all says?
>>
>> I tested my tftp server like this
>>
>> http://www.gunnalag.com/2013/08/05/how-to-test-tftp-server-from-a-client-system-in-windows/
>>
>> I did
>> tftp -i 1923.168.0.25 get ticker.exe
>>
>> And it worked fine
>>
>> So if I am using ticker.exe, what should application=/TICKER be? Is it
>> case sensitive? Does it need .exe at the end? Am I supposed to be using
>> ticker.exe?
>> Can someone send me an exe that does load in BBB so I can see if it is
>> that loads.
>>
>>
>> Also, I followed tutorial for installing U-boot on an SDCard which boots
>> linux from SDCard and that works
>>
>> http://www.armhf.com/boards/beaglebone-black/bbb-sd-install/
>>
>>
>> Any suggestions would be great
>>
>>
>> Thanks
>>
>>
>> On Mon, Jun 22, 2015 at 6:39 PM, Cláudio Silva <claudiodcsilva at gmail.com>
>> wrote:
>>
>>> Hi Angelo,
>>>
>>> xkyboot is just a command name that is executed by uenvcmd; you can name
>>> whatever you want. "XKYAPP2" is the executable name. It should placed on
>>> the tftp server's root, or otherwise you need to provide the full path to
>>> it.
>>> Is your tftp server working correctly? Try to test from a tftp client on
>>> Linux.
>>>
>>> Best Regards,
>>> Cláudio
>>>
>>> On Mon, Jun 22, 2015 at 6:51 AM Angelo Fraietta <
>>> newsgroups at smartcontroller.com.au> wrote:
>>>
>>>> I am using BBB also
>>>>
>>>> I have had a look at what you have provided
>>>> are XKYAPP2 and xkyboot  your app names?
>>>>
>>>> Lets say I wanted to boot ticker from tftp server (assume my tftp
>>>> server has same ip address as yours)
>>>>
>>>> I have copied
>>>> development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack/testsuites/samples/ticker/ticker.exe
>>>> to the root of my tftp server
>>>>
>>>> I am assuming this is entire uEnv.txt What should it look like (I have
>>>> provided whole of your file here). Thanks
>>>>
>>>>
>>>> ### BBB : Configuration
>>>> ipaddr=192.168.0.202
>>>> serverip=192.168.0.2
>>>> netmask=255.255.255.0
>>>>
>>>> ### XKY-OS : Configuration
>>>> baseaddr=0x81000000
>>>> application=/XKYAPP2
>>>>
>>>> ### Boot BBB from network
>>>> nfsargs=setenv bootargs console=${console} root=/dev/nfs nfsroot=${serverip}:${rootpath} rw ip=${ipaddr}:${serverip}:${serverip}:${netmask}::eth0:off
>>>> xkyboot=run nfsargs; tftp ${baseaddr} ${application}; bootm ${baseaddr}
>>>>
>>>> uenvcmd=run xkyboot
>>>>
>>>> On Fri, Jun 19, 2015 at 6:14 PM, Cláudio Silva <
>>>> claudiodcsilva at gmail.com> wrote:
>>>>
>>>>> You should be able to boot RTEMS through TFTP. At least I do it in the
>>>>> BBB, I assume the white version should work as well. You just have to
>>>>> change uboot configuration and setup a tftp server.
>>>>>
>>>>> My current uboot configuration is the following:
>>>>> https://gist.github.com/cdcs/76c4dd49c2d574bd68cc
>>>>>
>>>>> Cláudio
>>>>>
>>>>> On Fri, Jun 19, 2015 at 5:57 AM Chris Johns <chrisj at rtems.org> wrote:
>>>>>
>>>>>> On 19/06/2015 1:56 pm, Angelo Fraietta wrote:
>>>>>> > Those links I posted -- do any of them work with RTEMS?
>>>>>> >
>>>>>>
>>>>>> I do not know. I have no interested uboot. Maybe someone else knows.
>>>>>>
>>>>>> Chris
>>>>>> _______________________________________________
>>>>>> users mailing list
>>>>>> users at rtems.org
>>>>>> http://lists.rtems.org/mailman/listinfo/users
>>>>>>
>>>>>
>>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20150623/ee47cb76/attachment-0002.html>