Palmetto netboot instructions

[Brad Bishop]

Joel

Phosphor is just an alias for openbmc.  The target for a build in OE is set in build/conf/local.conf by the machine variable.  The qemu target is ‘qemuarm’  -  the Palmetto target is palmetto.  obmc-phosphor-image is an image recipe - those are orthogonal to the build target.

If you are starting from scratch without a build/conf directory you can just:

TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf . oe-init-build-env

and that will populate local.conf for palmetto.

OE does has support for putting the initramfs into the kernel.  I tried briefly to get that going but I didn’t get very far.

Thx - Brad

> On Oct 6, 2015, at 2:17 AM, Joel Stanley <joel at jms.id.au> wrote:
> 
> Hey Brad,
> 
> On Tue, Oct 6, 2015 at 4:35 PM, Brad Bishop <brad at bwbmail.net> wrote:
>> Please let me know if you run into any problems with this procedure or have
>> any feedback.  Thanks.
> 
> Thanks for the instructions!
> 
>> On build system:
>> 
>> 1 - pull updates from here: https://github.com/bradbishop/openbmc-1
>> 2 - bitbake obmc-phosphor-image
> 
> I thought 'phosphor' was the qemu target we were using for OpenBMC
> development, and that we would have a 'palmetto' target for running on
> the hardware. Can you clarify for me?
> 
>> 3 - tmp/sysroots/x86_64-linux/usr/bin/mkimage -A arm -O linux -C none -T
>> ramdisk -a 0x50200000 -d
>> tmp/deploy/images/palmetto/obmc-phosphor-image-palmetto.cpio.gz initrd
>> 4 - scp tmp/deploy/images/palmetto/cuImage <tftp>:/tftpboot
>> 5 - scp tmp/deploy/images/palmetto/initrd <tftp>:/tftpboot
> 
> Can we get bitbake to build the rootfs into the kernel?
> 
> Cheers,
> 
> Joel