Netboot full image loading AST2400

[Aaron]

After some hacking on  obmc-init it turns out theres an even easier way to
do this via kernel boot commands.

Just need

1) set  "openbmc-init-download-files" as kernel boot arg

2) create new env var to tftp over the ro image

env set openbmcinitdownloadurl tftp://192.168.2.136/image-rofs

3) copy from the deploy/images directory the  image-rofs file to tftp root.

ast# env print
1c800b5b=0
baudrate=115200
bootargs=console=ttyS4,115200n8 root=/dev/ram rw openbmc-init-download-files
bootcmd=tftpboot 40a00000 image-current;bootm 40a80000;
bootdelay=2
ethact=FTGMAC100#0
ethaddr=00:24:EC:F0:55:6B
ipaddr=192.168.2.143
openbmcinitdownloadurl=tftp://192.168.2.136/image-rofs
serverip=192.168.2.136
spi_dma=yes
stderr=serial
stdin=serial
stdout=serial
verify=yes

Environment size: 411/65531 bytes
ast#

What I cant work out is how to get the eth0 IP set before init runs, so
hacked it into obmc-init for now.

Aaron


On 20 June 2018 at 03:44, Aaron <aaron_ppus at fmad.com> wrote:

> Nice thanks. Kind of curious why alot of the AST2400 BMC images limit RAM
> to 210MB or so. Perhaps its so you can load the full image in the reserved
> ram?
>
> On 19 June 2018 at 11:17, Lei YU <mine260309 at gmail.com> wrote:
>
>> > It seems like there would an easy way to do this for
>> development/bringup, asking instead of hacking on the code for a change.
>> >
>> > Im bringing up a system by loading an image via u-boot across the
>> network into the upper section of ram, then booting from there. It
>> relocates itself to the reset vector and generally works well.
>>
>> You could refer to
>> https://lists.ozlabs.org/pipermail/openbmc/2017-December/010264.html
>> for TFTP kernel + NFS rootfs boot.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20180705/76cfa177/attachment.html>