OpenBMC on Raspberry PI 3.

OpenBMC on Raspberry PI 3.

[Javier Romero]

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

Hi People,

I'm building an OpenBMC image for target Palmetto on Ubuntu 16.04 to try to
make it work on the Raspberry PI 3. I've followed these steps:


*1.  *sudo apt-get install -y git build-essential libsdl1.2-dev texinfo
gawk chrpath diffstat

*2.* git clone git@github.com:openbmc/openbmc.git

*3.* cd openbmc

*4-* export TEMPLATECONF=meta-openbmc-machines/meta-
openpower/meta-ibm/meta-palmetto/conf

*tester@obmc:/openbmc$* . oe-init-build-env ~/my-build

*tester@obmc:~/my-build$* bitbake obmc-phosphor-image

*tester@obmc:/$* cd /home/tester/my-build/tmp/deploy/images/palmetto/

*tester@obmc:/$* tar -xvf
obmc-phosphor-image-palmetto-20171005142206.static.mtd.all.tar

*tester@obmc:/$* ls -lha
total 65M
drwxr-xr-x  2 root   root   4.0K Oct  5 15:37 .
drwxr-xr-x 24 root   root   4.0K Oct  5 10:29 ..
*-rw-rw-r--  1 tester tester  32M Oct  5 14:03 image-bmc*
-rw-rw-r--  2 tester tester  33M Oct  5 14:03
obmc-phosphor-image-palmetto-20171005142206.static.mtd.all.tar


Would like to know if it is the *image-bmc* file, what I will have to flash
on the SD card of the Raspberry to load OpenBMC.

Have also build an image of Linux Yocto for Raspberry PI 3.

Thanks for your attention.

Regards,




*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*

[-- Attachment #2: Type: text/html, Size: 2332 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Rick Altherr]

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

When you run  export TEMPLATECONF=meta-openbmc-machines/meta-
openpower/meta-ibm/meta-palmetto/conf, you are telling the build system
that you want to build images for the BMC processor used on the Palmetto
machine (Aspeed AST2400).  That image won't boot on a RaspberryPi.  What
you'll need to do is create a new layer in meta-openbmc-machines for a
RaspberryPi that includes the raspberrypi layer, specifies the correct
kernel device tree, etc.  Take a look at the meta-ast2500-evb and
https://github.com/Nuvoton-Israel/meta-bsp-nuvoton/tree/master/meta-openbmc-machines/meta-evb/meta-evb-nuvoton/meta-evb-npcm750/conf
for examples of what a machine to support an evaluation board (evb) looks
like.

On Fri, Oct 6, 2017 at 8:38 AM, Javier Romero <xavinux@gmail.com> wrote:

> Hi People,
>
> I'm building an OpenBMC image for target Palmetto on Ubuntu 16.04 to try
> to make it work on the Raspberry PI 3. I've followed these steps:
>
>
> *1.  *sudo apt-get install -y git build-essential libsdl1.2-dev texinfo
> gawk chrpath diffstat
>
> *2.* git clone git@github.com:openbmc/openbmc.git
>
> *3.* cd openbmc
>
> *4-* export TEMPLATECONF=meta-openbmc-machines/meta-
> openpower/meta-ibm/meta-palmetto/conf
>
> *tester@obmc:/openbmc$* . oe-init-build-env ~/my-build
>
> *tester@obmc:~/my-build$* bitbake obmc-phosphor-image
>
> *tester@obmc:/$* cd /home/tester/my-build/tmp/deploy/images/palmetto/
>
> *tester@obmc:/$* tar -xvf obmc-phosphor-image-palmetto-
> 20171005142206.static.mtd.all.tar
>
> *tester@obmc:/$* ls -lha
> total 65M
> drwxr-xr-x  2 root   root   4.0K Oct  5 15:37 .
> drwxr-xr-x 24 root   root   4.0K Oct  5 10:29 ..
> *-rw-rw-r--  1 tester tester  32M Oct  5 14:03 image-bmc*
> -rw-rw-r--  2 tester tester  33M Oct  5 14:03 obmc-phosphor-image-palmetto-
> 20171005142206.static.mtd.all.tar
>
>
> Would like to know if it is the *image-bmc* file, what I will have to
> flash on the SD card of the Raspberry to load OpenBMC.
>
> Have also build an image of Linux Yocto for Raspberry PI 3.
>
> Thanks for your attention.
>
> Regards,
>
>
>
>
> *Javier Romero*
>
> *E-mail: xavinux@gmail.com <xavinux@gmail.com>*
>
> *Skype: xavinux*
>
>

[-- Attachment #2: Type: text/html, Size: 3834 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

On Sat, 7 Oct 2017, at 03:29, Rick Altherr wrote:
> When you run  export TEMPLATECONF=meta-openbmc-machines/meta-
> openpower/meta-ibm/meta-palmetto/conf, you are telling the build system
> that you want to build images for the BMC processor used on the Palmetto
> machine (Aspeed AST2400).  That image won't boot on a RaspberryPi.  What
> you'll need to do is create a new layer in meta-openbmc-machines for a
> RaspberryPi that includes the raspberrypi layer, specifies the correct
> kernel device tree, etc. 

 As a heads-up, some of this work has already been done:

https://github.com/openbmc/openbmc/tree/master/meta-openbmc-machines/meta-evb/meta-evb-raspberrypi/conf

It was added in this change:

https://gerrit.openbmc-project.xyz/#/c/508/

I don't think it was thoroughly tested and it has probably bit-rotted,
but maybe it's existence will flatten out the learning curve a bit.

Cheers,

Andrew

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

Rick / Andrew,

Thank you very much for your answer and suggestions.

I'm looking at that repository on Github now.

Regards,




*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-06 18:28 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:

>
>
> On Sat, 7 Oct 2017, at 03:29, Rick Altherr wrote:
> > When you run  export TEMPLATECONF=meta-openbmc-machines/meta-
> > openpower/meta-ibm/meta-palmetto/conf, you are telling the build system
> > that you want to build images for the BMC processor used on the Palmetto
> > machine (Aspeed AST2400).  That image won't boot on a RaspberryPi.  What
> > you'll need to do is create a new layer in meta-openbmc-machines for a
> > RaspberryPi that includes the raspberrypi layer, specifies the correct
> > kernel device tree, etc.
>
>  As a heads-up, some of this work has already been done:
>
> https://github.com/openbmc/openbmc/tree/master/meta-
> openbmc-machines/meta-evb/meta-evb-raspberrypi/conf
>
> It was added in this change:
>
> https://gerrit.openbmc-project.xyz/#/c/508/
>
> I don't think it was thoroughly tested and it has probably bit-rotted,
> but maybe it's existence will flatten out the learning curve a bit.
>
> Cheers,
>
> Andrew
>

[-- Attachment #2: Type: text/html, Size: 2704 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

[-- Attachment #1: Type: text/plain, Size: 4609 bytes --]

I've tried these steps:

*1. tester@obmc:~$ *cd openbmc

*2. tester@obmc:/openbmc$ *export
TEMPLATECONF=meta-openbmc-machines/meta-evb/meta-evb-raspberrypi/conf

*3. tester@obmc:/openbmc$ *. oe-init-build-env ~/my-build-raspberrypi

*4. tester@obmc:~/my-build-raspberrypi$ *bitbake obmc-phosphor-image

*Build Configuration:*
*BB_VERSION        = "1.32.0"*
*BUILD_SYS         = "x86_64-linux"*
*NATIVELSBSTRING   = "Ubuntu-16.04"*
*TARGET_SYS        = "arm-openbmc-linux-gnueabi"*
*MACHINE           = "raspberrypi"*
*DISTRO            = "openbmc-phosphor"*
*DISTRO_VERSION    = "0.1.0"*
*TUNE_FEATURES     = "arm armv6  vfp arm1176jzfs callconvention-hard"*
*TARGET_FPU        = "hard"*
*meta              *
*meta-poky         *
*meta-oe           *
*meta-networking   *
*meta-python       *
*meta-virtualization *
*meta-phosphor     *
*meta-raspberrypi  = "master:65edf7d796c34012982632d0a724d80ff44c9e4a"*


But the following error appears:

*ERROR: linux-raspberrypi-1_4.4.48+gitAUTOINC+7ddf96fbb7-r0
do_kernel_metadata: Function failed: do_kernel_metadata (log file is
located at
/home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)*
*ERROR: Logfile of failure stored in:
/home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276*
*Log data follows:*
*| DEBUG: Executing shell function do_kernel_metadata*
*| ERROR. input file "phosphor-gpio-keys" does not exist*
*| ERROR: could not process input files:
/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
phosphor-gpio-keys*
*|        See /tmp/tmp.GA2zgVbszZ for details*
*| ERROR. input file "phosphor-gpio-keys" does not exist*
*| ERROR: could not process input files:
/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
phosphor-gpio-keys*
*|        See /tmp/tmp.BEzIPRvVMy for details*
*| WARNING: exit code 1 from a shell command.*
*| ERROR: Function failed: do_kernel_metadata (log file is located at
/home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)*
*ERROR: Task
(/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata)
failed with exit code '1'*
*NOTE: Tasks Summary: Attempted 632 tasks of which 0 didn't need to be
rerun and 1 failed.*
*Summary: 1 task failed:*
*
/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata*
*Summary: There were 6 WARNING messages shown.*
*Summary: There was 1 ERROR message shown, returning a non-zero exit code.*

Is there something wrong with the steps I've tried ?

Regards,




*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-06 20:02 GMT-03:00 Javier Romero <xavinux@gmail.com>:

> Rick / Andrew,
>
> Thank you very much for your answer and suggestions.
>
> I'm looking at that repository on Github now.
>
> Regards,
>
>
>
>
> *Javier Romero*
>
> *E-mail: xavinux@gmail.com <xavinux@gmail.com>*
>
> *Skype: xavinux*
>
>
> 2017-10-06 18:28 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
>
>>
>>
>> On Sat, 7 Oct 2017, at 03:29, Rick Altherr wrote:
>> > When you run  export TEMPLATECONF=meta-openbmc-machines/meta-
>> > openpower/meta-ibm/meta-palmetto/conf, you are telling the build system
>> > that you want to build images for the BMC processor used on the Palmetto
>> > machine (Aspeed AST2400).  That image won't boot on a RaspberryPi.  What
>> > you'll need to do is create a new layer in meta-openbmc-machines for a
>> > RaspberryPi that includes the raspberrypi layer, specifies the correct
>> > kernel device tree, etc.
>>
>>  As a heads-up, some of this work has already been done:
>>
>> https://github.com/openbmc/openbmc/tree/master/meta-openbmc-
>> machines/meta-evb/meta-evb-raspberrypi/conf
>>
>> It was added in this change:
>>
>> https://gerrit.openbmc-project.xyz/#/c/508/
>>
>> I don't think it was thoroughly tested and it has probably bit-rotted,
>> but maybe it's existence will flatten out the learning curve a bit.
>>
>> Cheers,
>>
>> Andrew
>>
>
>

[-- Attachment #2: Type: text/html, Size: 9030 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

[-- Attachment #1: Type: text/plain, Size: 3989 bytes --]

On Sun, 2017-10-08 at 01:45 -0300, Javier Romero wrote:
> I've tried these steps:
> 
> 1. tester@obmc:~$ cd openbmc
> 
> 2. tester@obmc:/openbmc$ export TEMPLATECONF=meta-openbmc-machines/meta-evb/meta-evb-raspberrypi/conf
> 
> 3. tester@obmc:/openbmc$ . oe-init-build-env ~/my-build-raspberrypi
> 
> 4. tester@obmc:~/my-build-raspberrypi$ bitbake obmc-phosphor-image
> 
> Build Configuration:
> BB_VERSION        = "1.32.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-16.04"
> TARGET_SYS        = "arm-openbmc-linux-gnueabi"
> MACHINE           = "raspberrypi"
> DISTRO            = "openbmc-phosphor"
> DISTRO_VERSION    = "0.1.0"
> TUNE_FEATURES     = "arm armv6  vfp arm1176jzfs callconvention-hard"
> TARGET_FPU        = "hard"
> meta              
> meta-poky         
> meta-oe           
> meta-networking   
> meta-python       
> meta-virtualization 
> meta-phosphor     
> meta-raspberrypi  = "master:65edf7d796c34012982632d0a724d80ff44c9e4a"
> 
> 
> But the following error appears:
> 
> ERROR: linux-raspberrypi-1_4.4.48+gitAUTOINC+7ddf96fbb7-r0 do_kernel_metadata: Function failed: do_kernel_metadata (log file is located at /home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)
> ERROR: Logfile of failure stored in: /home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276
> Log data follows:
> | DEBUG: Executing shell function do_kernel_metadata
> | ERROR. input file "phosphor-gpio-keys" does not exist
> | ERROR: could not process input files: /home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig /home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch phosphor-gpio-keys
> |        See /tmp/tmp.GA2zgVbszZ for details
> | ERROR. input file "phosphor-gpio-keys" does not exist
> | ERROR: could not process input files: /home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig /home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch phosphor-gpio-keys
> |        See /tmp/tmp.BEzIPRvVMy for details
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_kernel_metadata (log file is located at /home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)
> ERROR: Task (/home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 632 tasks of which 0 didn't need to be rerun and 1 failed.
> Summary: 1 task failed:
>   /home/tester/openbmc/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata
> Summary: There were 6 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> Is there something wrong with the steps I've tried ?

Nope, that's just an outright bug in the raspi support. I'd recommend several
things here:

1. Open an issue in the github issue tracker[0]
2. Cook up a patch! It looks like this might have to do with assumptions made
   in meta-phosphor/conf/distro/openbmc-phosphor.conf, as the raspi uses a
   different kernel tree to the ASPEED SoCs
3. For better or worse patches are submitted via Gerrit[1], so push your patch
   there

Make sure to speak up here or on IRC if you get stuck :)

Andrew

[0] https://github.com/openbmc/openbmc/issues
[1] https://gerrit.openbmc-project.xyz/#/q/status:open

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

[-- Attachment #1: Type: text/plain, Size: 4339 bytes --]

Andrew,

Thans for your answer.

Bug reported: https://github.com/openbmc/openbmc/issues/2434

I`d like to try to cook up a patch, but do I need to know a specific
language programming to do this ?

Regards,











*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-08 9:44 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:

> On Sun, 2017-10-08 at 01:45 -0300, Javier Romero wrote:
> > I've tried these steps:
> >
> > 1. tester@obmc:~$ cd openbmc
> >
> > 2. tester@obmc:/openbmc$ export TEMPLATECONF=meta-openbmc-
> machines/meta-evb/meta-evb-raspberrypi/conf
> >
> > 3. tester@obmc:/openbmc$ . oe-init-build-env ~/my-build-raspberrypi
> >
> > 4. tester@obmc:~/my-build-raspberrypi$ bitbake obmc-phosphor-image
> >
> > Build Configuration:
> > BB_VERSION        = "1.32.0"
> > BUILD_SYS         = "x86_64-linux"
> > NATIVELSBSTRING   = "Ubuntu-16.04"
> > TARGET_SYS        = "arm-openbmc-linux-gnueabi"
> > MACHINE           = "raspberrypi"
> > DISTRO            = "openbmc-phosphor"
> > DISTRO_VERSION    = "0.1.0"
> > TUNE_FEATURES     = "arm armv6  vfp arm1176jzfs callconvention-hard"
> > TARGET_FPU        = "hard"
> > meta
> > meta-poky
> > meta-oe
> > meta-networking
> > meta-python
> > meta-virtualization
> > meta-phosphor
> > meta-raspberrypi  = "master:65edf7d796c34012982632d0a724d80ff44c9e4a"
> >
> >
> > But the following error appears:
> >
> > ERROR: linux-raspberrypi-1_4.4.48+gitAUTOINC+7ddf96fbb7-r0
> do_kernel_metadata: Function failed: do_kernel_metadata (log file is
> located at /home/tester/my-build-raspberrypi/tmp/work/
> raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.
> 4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)
> > ERROR: Logfile of failure stored in: /home/tester/my-build-
> raspberrypi/tmp/work/raspberrypi-openbmc-linux-
> gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/
> temp/log.do_kernel_metadata.7276
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_metadata
> > | ERROR. input file "phosphor-gpio-keys" does not exist
> > | ERROR: could not process input files: /home/tester/openbmc/import-
> layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
> /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> phosphor-gpio-keys
> > |        See /tmp/tmp.GA2zgVbszZ for details
> > | ERROR. input file "phosphor-gpio-keys" does not exist
> > | ERROR: could not process input files: /home/tester/openbmc/import-
> layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
> /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> phosphor-gpio-keys
> > |        See /tmp/tmp.BEzIPRvVMy for details
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_metadata (log file is located at
> /home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-
> gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/
> temp/log.do_kernel_metadata.7276)
> > ERROR: Task (/home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata) failed
> with exit code '1'
> > NOTE: Tasks Summary: Attempted 632 tasks of which 0 didn't need to be
> rerun and 1 failed.
> > Summary: 1 task failed:
> >   /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata
> > Summary: There were 6 WARNING messages shown.
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
> > Is there something wrong with the steps I've tried ?
>
> Nope, that's just an outright bug in the raspi support. I'd recommend
> several
> things here:
>
> 1. Open an issue in the github issue tracker[0]
> 2. Cook up a patch! It looks like this might have to do with assumptions
> made
>    in meta-phosphor/conf/distro/openbmc-phosphor.conf, as the raspi uses a
>    different kernel tree to the ASPEED SoCs
> 3. For better or worse patches are submitted via Gerrit[1], so push your
> patch
>    there
>
> Make sure to speak up here or on IRC if you get stuck :)
>
> Andrew
>
> [0] https://github.com/openbmc/openbmc/issues
> [1] https://gerrit.openbmc-project.xyz/#/q/status:open

[-- Attachment #2: Type: text/html, Size: 6653 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]

On Sun, 2017-10-08 at 23:57 -0300, Javier Romero wrote:
> Andrew,
> 
> Thans for your answer.
> 
> Bug reported: https://github.com/openbmc/openbmc/issues/2434
> 
> I`d like to try to cook up a patch, but do I need to know a specific
> language programming to do this ?

Hmm, good question. This is probably a bug in how a bitbake
configuration/recipe configures the kernel. As such I'd suggest getting a
handle on Yocto, which is the build and configuration system we use. Here's the
quick start guide:

http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html

There's also a rather daunting Mega Manual, which is useful as a reference
(rather than reading the whole thing):

http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html

Back to the bug itself, from the output that you gave I expect it's some issue
with the following directive:

https://github.com/openbmc/openbmc/blob/master/meta-phosphor/conf/distro/openbmc-phosphor.conf#L57

i.e. the issue is that that linux-raspberrypi (the kernel recipe used for the
raspberry pi[1][2]) doesn't have a 'phosphor-gpio-keys' feature. The implicit
assumption is that the configuration will be using the linux-obmc tree[3][4][5], which
is our fork of the kernel (primarily for Aspeed SoC support).

More generally, knowledge of Python (Yocto/bitbake, some OpenBMC userspace), C
(u-boot, kernel, qemu, also requires a some comfort with assembler) and C++ (most
of the phosphor reference userspace applications) is useful.

Hope that helps.

Andrew

[1] https://github.com/openbmc/openbmc/blob/4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
[2] https://github.com/openbmc/openbmc/blob/4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc
[3] https://github.com/openbmc/openbmc/blob/4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.10.bb
[4] https://github.com/openbmc/openbmc/blob/4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/recipes-kernel/linux/linux-obmc.inc

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Yi TZ Li]

[-- Attachment #1: Type: text/plain, Size: 3241 bytes --]


Javier,

Andrew has mentioned the cause of the bug.

When I added the RaspberryPi configure to OpenBMC, I referred to
configuration of other boards, like:
"meta-openbmc-machines/meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf", you
might also refer to other working machines.

The original target was to build an OpenBMC image for RaspberryPi, but I
never tested on a real hardware.
More work is required to run OpenBMC on a Raspberry Pi.

The "meta-phosphor" layer has been changed since that time, we need to
update RaspberryPi configurations accordingly.

Thanks,
-Yi

> From: Andrew Jeffery <andrew@aj.id.au>
> To: Javier Romero <xavinux@gmail.com>
> Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> Date: 09/10/2017 02:41 PM
> Subject: Re: OpenBMC on Raspberry PI 3.
> Sent by: "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org>
>
> On Sun, 2017-10-08 at 23:57 -0300, Javier Romero wrote:
> > Andrew,
> >
> > Thans for your answer.
> >
> > Bug reported: https://github.com/openbmc/openbmc/issues/2434
> >
> > I`d like to try to cook up a patch, but do I need to know a specific
> > language programming to do this ?
>
> Hmm, good question. This is probably a bug in how a bitbake
> configuration/recipe configures the kernel. As such I'd suggest getting a
> handle on Yocto, which is the build and configuration system we
use.Here's the
> quick start guide:
>
>
http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html
>
> There's also a rather daunting Mega Manual, which is useful as a
reference
> (rather than reading the whole thing):
>
> http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html
>
> Back to the bug itself, from the output that you gave I expect it's some
issue
> with the following directive:
>
> https://github.com/openbmc/openbmc/blob/master/meta-phosphor/conf/
> distro/openbmc-phosphor.conf#L57
>
> i.e. the issue is that that linux-raspberrypi (the kernel recipe used for
the
> raspberry pi[1][2]) doesn't have a 'phosphor-gpio-keys' feature. The
implicit
> assumption is that the configuration will be using the linux-obmc
> tree[3][4][5], which
> is our fork of the kernel (primarily for Aspeed SoC support).
>
> More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
userspace), C
> (u-boot, kernel, qemu, also requires a some comfort with assembler)
> and C++ (most
> of the phosphor reference userspace applications) is useful.
>
> Hope that helps.
>
> Andrew
>
> [1] https://github.com/openbmc/openbmc/blob/
> 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> [2] https://github.com/openbmc/openbmc/blob/
> 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc
> [3] https://github.com/openbmc/openbmc/blob/
> 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> recipes-kernel/linux/linux-obmc_4.10.bb
> [4] https://github.com/openbmc/openbmc/blob/
> 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> recipes-kernel/linux/linux-obmc.inc[attachment "signature.asc"
> deleted by Yi TZ Li/China/IBM]

[-- Attachment #2: Type: text/html, Size: 4803 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

[-- Attachment #1: Type: text/plain, Size: 4384 bytes --]

Andrew,

"*More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
userspace), C (u-boot, kernel, qemu, also requires a some comfort with
assembler) and C++ (most of the phosphor reference userspace applications)
is useful.*"

I see, but I'm not a programmer, have start by building an image of Yocto
for the Raspberry PI to learn more about Yocto, Poky and bitbake. Links you
provided are very welcome and useful!


Yi,



*"The original target was to build an OpenBMC image for RaspberryPi, but I
never tested on a real hardware.*
I've the Raspberry PI 3 at disposal for testing on a real hardware.

*More work is required to run OpenBMC on a Raspberry Pi. The
"meta-phosphor" layer has been changed since that time, we need to update
RaspberryPi configurations accordingly."*

Something I can help and with this although Im not a programmer?

Thanks for your answers and kind attention.

Regards,




*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-09 6:39 GMT-03:00 Yi TZ Li <shliyi@cn.ibm.com>:

> Javier,
>
> Andrew has mentioned the cause of the bug.
>
> When I added the RaspberryPi configure to OpenBMC, I referred to
> configuration of other boards, like:
> "meta-openbmc-machines/meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf",
> you might also refer to other working machines.
>
> The original target was to build an OpenBMC image for RaspberryPi, but I
> never tested on a real hardware.
> More work is required to run OpenBMC on a Raspberry Pi.
>
> The "meta-phosphor" layer has been changed since that time, we need to
> update RaspberryPi configurations accordingly.
>
> Thanks,
> -Yi
>
> > From: Andrew Jeffery <andrew@aj.id.au>
> > To: Javier Romero <xavinux@gmail.com>
> > Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> > Date: 09/10/2017 02:41 PM
> > Subject: Re: OpenBMC on Raspberry PI 3.
> > Sent by: "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org>
> >
> > On Sun, 2017-10-08 at 23:57 -0300, Javier Romero wrote:
> > > Andrew,
> > >
> > > Thans for your answer.
> > >
> > > Bug reported: https://github.com/openbmc/openbmc/issues/2434
> > >
> > > I`d like to try to cook up a patch, but do I need to know a specific
> > > language programming to do this ?
> >
> > Hmm, good question. This is probably a bug in how a bitbake
> > configuration/recipe configures the kernel. As such I'd suggest getting a
> > handle on Yocto, which is the build and configuration system we
> use.Here's the
>
> > quick start guide:
> >
> > http://www.yoctoproject.org/docs/2.1/yocto-project-qs/
> yocto-project-qs.html
> >
> > There's also a rather daunting Mega Manual, which is useful as a
> reference
> > (rather than reading the whole thing):
> >
> > http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html
> >
> > Back to the bug itself, from the output that you gave I expect it's some
> issue
> > with the following directive:
> >
> > https://github.com/openbmc/openbmc/blob/master/meta-phosphor/conf/
> > distro/openbmc-phosphor.conf#L57
> >
> > i.e. the issue is that that linux-raspberrypi (the kernel recipe used
> for the
> > raspberry pi[1][2]) doesn't have a 'phosphor-gpio-keys' feature. The
> implicit
> > assumption is that the configuration will be using the linux-obmc
> > tree[3][4][5], which
> > is our fork of the kernel (primarily for Aspeed SoC support).
> >
> > More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
> userspace), C
> > (u-boot, kernel, qemu, also requires a some comfort with assembler)
> > and C++ (most
> > of the phosphor reference userspace applications) is useful.
> >
> > Hope that helps.
> >
> > Andrew
> >
> > [1] https://github.com/openbmc/openbmc/blob/
> > 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> > raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> > [2] https://github.com/openbmc/openbmc/blob/
> > 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> > raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc
> > [3] https://github.com/openbmc/openbmc/blob/
> > 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> > recipes-kernel/linux/linux-obmc_4.10.bb
> > [4] https://github.com/openbmc/openbmc/blob/
> > 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> > recipes-kernel/linux/linux-obmc.inc[attachment "signature.asc"
> > deleted by Yi TZ Li/China/IBM]
>
>

[-- Attachment #2: Type: text/html, Size: 8013 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

[-- Attachment #1: Type: text/plain, Size: 3489 bytes --]

Hi Javier,

A few notes on how to make best use of the mailing list:

First, mail to the list is best sent plain-text. I see you use gmail -
if you're using the web interface there's a drop-down menu at the
bottom right of the composer where you can select the plain-text
option.

Secondly, I notice you quote both Yi and I below in your reply, and
appear to have constructed the reply yourself: the best way to deal
with multiple people in a conversation is to reply to their emails
individually and directly, rather than consolidating your thoughts in
one reply. This keeps the threads of conversation easy to follow
(though gmail's conversation interface is linear rather than tree view,
so this might not be obvious but it does affect others reading the
list).

Third: You have the knack of replying to quotes from the sender, but
this is best served by making use of the reply-indentation that your
composer should already provide (e.g. '> some quoted text'). For
example what I'm doing below:

On Mon, 2017-10-09 at 13:09 -0300, Javier Romero wrote:
> Andrew,
> 
> "More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
> userspace), C (u-boot, kernel, qemu, also requires a some comfort
> with assembler) and C++ (most of the phosphor reference userspace
> applications) is useful."
> 
> I see, but I'm not a programmer, have start by building an image of
> Yocto for the Raspberry PI to learn more about Yocto, Poky and
> bitbake. Links you provided are very welcome and useful!

Ah - so I don't think you've outlined why you picked OpenBMC for the
job. Can you give us a quick run-down?

Without further information and assuming you just want to get an image
you've built with Yocto onto a Raspberry Pi, there appears to be a good
unofficial how-to here:

http://www.jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html

This should get you something that works without having to deal with
any of the broken assumptions currently baked into the OpenBMC code-
base with respect to the Raspberry Pi.

> 
> 
> Yi,
> 
> "The original target was to build an OpenBMC image for RaspberryPi,
> but I never tested on a real hardware.
> 
> I've the Raspberry PI 3 at disposal for testing on a real hardware.
> 
> More work is required to run OpenBMC on a Raspberry Pi. The "meta-
> phosphor" layer has been changed since that time, we need to update
> RaspberryPi configurations accordingly."
> 
> Something I can help and with this although Im not a programmer? 

Not already having programming experience is going to make it harder,
and I wouldn't necessarily take queues from how we use Yocto (I'm no
expert but I feel that we don't do some things quite by the book).

Yocto borrows lots of ideas from shell scripting and is implemented in
python. Further, it allows you to pretty freely mix the two in recipes
thus it would be helpful to get a grasp of these environments (and
Yocto itself). Without some experience it leaves us with high latency
interactions between you and Yi if Yi is to continue developing the
Raspberry Pi support. I expect this will end up frustrating both of
you, but it's up to you both to decide.

There are going to be easier projects out there than OpenBMC to cut
your teeth with, but if you are keen to learn to program, feel you have
the drive to do so and Yi is happy to help out with your interest in
the Raspberry Pi then by all means stick around :)

Andrew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

Hi Andrew,
Thank you very much for your suggestions, I'll follow them.


>
> Ah - so I don't think you've outlined why you picked OpenBMC for the
> job. Can you give us a quick run-down?

I'm an individual contributor on the Open Compute Project and follow
the Hardware Management Group, OpenBMC is on their project scope and
sounds very interesting for me, so decide to participate and see if I
can be useful.


>
> Without further information and assuming you just want to get an image
> you've built with Yocto onto a Raspberry Pi, there appears to be a good
> unofficial how-to here

I've built an image of Yocto to learn more about it, as see that is
what OepBMC use.


>
> There are going to be easier projects out there than OpenBMC to cut
> your teeth with, but if you are keen to learn to program, feel you have
> the drive to do so and Yi is happy to help out with your interest in
> the Raspberry Pi then by all means stick around :)

Have bought the Raspberry PI a few days ago, to start contibuting to
the OpenBMC project and try to make it work on the RPI. I can learn
what is needed on the way, and that is why I'm here and decide to
participate, to contribute while learning new things. But if more
programming advanced knowledge is requiered to participate on the
OpsnBMC project, maybe I'll have to cut my teeth with other project as
you said.

Thanks again for your kind attention.

Regards,

Javier Romero
E-mail: xavinux@gmail.com
Skype: xavinux



2017-10-09 21:14 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
> Hi Javier,
>
> A few notes on how to make best use of the mailing list:
>
> First, mail to the list is best sent plain-text. I see you use gmail -
> if you're using the web interface there's a drop-down menu at the
> bottom right of the composer where you can select the plain-text
> option.
>
> Secondly, I notice you quote both Yi and I below in your reply, and
> appear to have constructed the reply yourself: the best way to deal
> with multiple people in a conversation is to reply to their emails
> individually and directly, rather than consolidating your thoughts in
> one reply. This keeps the threads of conversation easy to follow
> (though gmail's conversation interface is linear rather than tree view,
> so this might not be obvious but it does affect others reading the
> list).
>
> Third: You have the knack of replying to quotes from the sender, but
> this is best served by making use of the reply-indentation that your
> composer should already provide (e.g. '> some quoted text'). For
> example what I'm doing below:
>
> On Mon, 2017-10-09 at 13:09 -0300, Javier Romero wrote:
>> Andrew,
>>
>> "More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
>> userspace), C (u-boot, kernel, qemu, also requires a some comfort
>> with assembler) and C++ (most of the phosphor reference userspace
>> applications) is useful."
>>
>> I see, but I'm not a programmer, have start by building an image of
>> Yocto for the Raspberry PI to learn more about Yocto, Poky and
>> bitbake. Links you provided are very welcome and useful!
>
> Ah - so I don't think you've outlined why you picked OpenBMC for the
> job. Can you give us a quick run-down?
>
> Without further information and assuming you just want to get an image
> you've built with Yocto onto a Raspberry Pi, there appears to be a good
> unofficial how-to here:
>
> http://www.jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html
>
> This should get you something that works without having to deal with
> any of the broken assumptions currently baked into the OpenBMC code-
> base with respect to the Raspberry Pi.
>
>>
>>
>> Yi,
>>
>> "The original target was to build an OpenBMC image for RaspberryPi,
>> but I never tested on a real hardware.
>>
>> I've the Raspberry PI 3 at disposal for testing on a real hardware.
>>
>> More work is required to run OpenBMC on a Raspberry Pi. The "meta-
>> phosphor" layer has been changed since that time, we need to update
>> RaspberryPi configurations accordingly."
>>
>> Something I can help and with this although Im not a programmer?
>
> Not already having programming experience is going to make it harder,
> and I wouldn't necessarily take queues from how we use Yocto (I'm no
> expert but I feel that we don't do some things quite by the book).
>
> Yocto borrows lots of ideas from shell scripting and is implemented in
> python. Further, it allows you to pretty freely mix the two in recipes
> thus it would be helpful to get a grasp of these environments (and
> Yocto itself). Without some experience it leaves us with high latency
> interactions between you and Yi if Yi is to continue developing the
> Raspberry Pi support. I expect this will end up frustrating both of
> you, but it's up to you both to decide.
>
> There are going to be easier projects out there than OpenBMC to cut
> your teeth with, but if you are keen to learn to program, feel you have
> the drive to do so and Yi is happy to help out with your interest in
> the Raspberry Pi then by all means stick around :)
>
> Andrew

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

On Tue, 2017-10-10 at 11:01 -0300, Javier Romero wrote:
> > Ah - so I don't think you've outlined why you picked OpenBMC for the
> > job. Can you give us a quick run-down?
> 
> I'm an individual contributor on the Open Compute Project and follow
> the Hardware Management Group, OpenBMC is on their project scope and
> sounds very interesting for me, so decide to participate and see if I
> can be useful.

Ah, nice. Good to have some background :)

> > 
> > There are going to be easier projects out there than OpenBMC to cut
> > your teeth with, but if you are keen to learn to program, feel you have
> > the drive to do so and Yi is happy to help out with your interest in
> > the Raspberry Pi then by all means stick around :)
> 
> Have bought the Raspberry PI a few days ago, to start contibuting to
> the OpenBMC project and try to make it work on the RPI. I can learn
> what is needed on the way, and that is why I'm here and decide to
> participate, to contribute while learning new things.

Great! I look forward to you helping us improve our documentation and
on-boarding of contributors. It might be rocky but it should help those
coming along in the future.

>  But if more
> programming advanced knowledge is requiered to participate on the
> OpsnBMC project, maybe I'll have to cut my teeth with other project as
> you said.

Play it by ear - I just wasn't sure what your motivations were. But
since you're coming from the OCP background with an interest in
hardware management, it makes sense to stick around here. As long as
you get in touch when you get stuck we'll find someone to help answer
your questions.

Cheers,

Andrew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

> Great! I look forward to you helping us improve our documentation and
> on-boarding of contributors. It might be rocky but it should help those
> coming along in the future.

A starting point to start my contribution, so, how can I help on this?



Javier Romero
E-mail: xavinux@gmail.com
Skype: xavinux



2017-10-11 0:05 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
> On Tue, 2017-10-10 at 11:01 -0300, Javier Romero wrote:
>> > Ah - so I don't think you've outlined why you picked OpenBMC for the
>> > job. Can you give us a quick run-down?
>>
>> I'm an individual contributor on the Open Compute Project and follow
>> the Hardware Management Group, OpenBMC is on their project scope and
>> sounds very interesting for me, so decide to participate and see if I
>> can be useful.
>
> Ah, nice. Good to have some background :)
>
>> >
>> > There are going to be easier projects out there than OpenBMC to cut
>> > your teeth with, but if you are keen to learn to program, feel you have
>> > the drive to do so and Yi is happy to help out with your interest in
>> > the Raspberry Pi then by all means stick around :)
>>
>> Have bought the Raspberry PI a few days ago, to start contibuting to
>> the OpenBMC project and try to make it work on the RPI. I can learn
>> what is needed on the way, and that is why I'm here and decide to
>> participate, to contribute while learning new things.
>
> Great! I look forward to you helping us improve our documentation and
> on-boarding of contributors. It might be rocky but it should help those
> coming along in the future.
>
>>  But if more
>> programming advanced knowledge is requiered to participate on the
>> OpsnBMC project, maybe I'll have to cut my teeth with other project as
>> you said.
>
> Play it by ear - I just wasn't sure what your motivations were. But
> since you're coming from the OCP background with an interest in
> hardware management, it makes sense to stick around here. As long as
> you get in touch when you get stuck we'll find someone to help answer
> your questions.
>
> Cheers,
>
> Andrew

Re: OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

On Wed, 2017-10-11 at 16:09 -0300, Javier Romero wrote:
> > Great! I look forward to you helping us improve our documentation and
> > on-boarding of contributors. It might be rocky but it should help those
> > coming along in the future.
> 
> A starting point to start my contribution, so, how can I help on this?

Ah I wasn't talking about anything in particular, just that we should
be able to improve our documentation from the questions you ask as you
try to get OpenBMC working on the Raspberry Pi. But regarding the
documentation, have you read through the docs repository at all?
Contributions are certainly welcome there:

https://github.com/openbmc/docs/

Cheers,

Andrew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: OpenBMC on Raspberry PI 3.

[Javier Romero]

> Ah I wasn't talking about anything in particular, just that we should
> be able to improve our documentation from the questions you ask as you
> try to get OpenBMC working on the Raspberry Pi

So, will have to wait till the bug I've reported is fixed to continue
working with OpenBMC on Raspberry, nothing else I can do with my RPI
and obmc?

> But regarding the documentation, have you read through the docs repository at all?

Yes, I have check the documentation.

Javier Romero
E-mail: xavinux@gmail.com
Skype: xavinux



2017-10-13 1:56 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
> On Wed, 2017-10-11 at 16:09 -0300, Javier Romero wrote:
>> > Great! I look forward to you helping us improve our documentation and
>> > on-boarding of contributors. It might be rocky but it should help those
>> > coming along in the future.
>>
>> A starting point to start my contribution, so, how can I help on this?
>
> Ah I wasn't talking about anything in particular, just that we should
> be able to improve our documentation from the questions you ask as you
> try to get OpenBMC working on the Raspberry Pi. But regarding the
> documentation, have you read through the docs repository at all?
> Contributions are certainly welcome there:
>
> https://github.com/openbmc/docs/
>
> Cheers,
>
> Andrew