[ERROR: Nothing RPROVIDES 'u-boot-default-env']

[Nikhil V]

hi,

    What are your expectations and final goal?

    Trying to implement openbmc on SAMA5D27 development board and to use secure boot feature provided by microchip. To make openbmc more secure.



    Looking at boot sequence of SAMA5D27 

    (https://microchipdeveloper.com/32mpu:boot-sama5d2-series and http://ww1.microchip.com/downloads/en/AppNotes/DS00002748A.pdf)

    • ROM code (first stage loader)

    • AT91bootstrap bootloader (second stage loader)

    • U-Boot bootloader (third stage loader)



    In Normal Situation for eg. if we implement openbmc in beaglebone black bootprocess seen by openbmc

    • ROM code (first stage loader)

    • U-Boot bootloader (second stage loader)





Is additional layer of AT91bootstrap causing problem to openbmc to give "ERROR" during bitbake?



Thanks & Regards,

Nikhil Muley








---- On Mon, 03 Jan 2022 18:45:24 +0530 Nikhil V <nikhil.vu at zohocorp.com> wrote ----



Hello Andrei Kartashev,

                                 Thanks for your patience and support.

                                 As suggested by you to try with normal yocto build and then go for OpenBMC.

                                 I have a success with yocto image for SAMA5D27 development board and tested and verified using steps described in following link

                                ( https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d27Som1EKMainPage )

                                 But i got error when i do same for openbmc, 

                                 

                              As i am new to openbmc and may be i am wrong with my interpretation

                                 I have the following Interpretation towards problem.

                                 If you look into meta/recipe-bsp/u-boot/libubootenv_0.3.1.bb

                                 It describe that it "It provides hardware-independent replacement for fw_printenv/setenv utilities provided by U-Boot"

             

                                 If you look into meta-atmel/recipe-bsp 

                                 There is nothing indicating fw_printenv/setenv at u-boot-at91_2020.01.bb recipe.

                           

                           Correct me if I am wrong.



Thanks & Regards,

Nikhil Muley








---- On Mon, 03 Jan 2022 18:00:56 +0530 Andrei Kartashev <mailto:a.kartashev at yadro.com> wrote ----



Well, as I say, they don't use u-boot.inc an they don't implement u- 
boot-default-env. I can't give you an universal hint on how to solve 
this, but I advice you to build upstream Yocto for your platform first 
(I mean, generic yocto, instead of OpenBMC). Once you succeeded with 
upstream Yocto, integrating into OpenBMC would be less painful. 
 
What you trying to do is not a typical usecase for OpenBMC, generally 
we don't do like this. What are your expectations and final goal? 
 
On Mon, 2022-01-03 at 17:06 +0530, Nikhil V wrote: 
> Hello kartashev, 
>                        Thanks for your quick response, I will provide 
> some background on what i am trying to achieve. 
>                        I am using openbmc, downloaded from following 
> location, steps are as follow, 
>                        
>                         1)  git clone 
> https://github.com/openbmc/openbmc.git -b dunfell 
>                         2)  git clone 
> git://github.com/linux4sam/meta-atmel.git -b dunfell 
>                         3)  . openbmc-env build-sama5d27 
>                         4)  then add following layers 
>                               bitbake-layers add-layer ../meta-atmel 
> ../meta-security ../meta-openembedded/meta-perl ../meta- 
> openembedded/meta-initramfs 
>                         5)   Edit in local.conf 
>                               MACHINE="sama5d27-som1-ek-sd" 
>                         6)   bitbake obmc-phosphor-image 
> 
> "Since there is no such platform as "at91" in OpenBMC, we don't know 
> what recipe do you use for u-boot." 
> Here I am using meta-atmel layer provided by microchip. It has its 
> own u-boot under meta-atmel/recipe-bsp. 
> you will find it once you downloaded it from step 2. 
> 
> when i do bitbake obmc-phosphor-image i am getting error. ERROR: 
> Nothing RPROVIDES 'u-boot-default-env' 
> 
> hope i have described my problem correctly. 
> 
> For any query feel free to contact. 
> 
> Thanks & Regards, 
> Nikhil Muley 
> 
> 
> ---- On Mon, 03 Jan 2022 16:40:09 +0530 Andrei Kartashev 
> <mailto:a.kartashev at yadro.com> wrote ---- 
> 
> > Hello, 
> >   
> > It's hard to say what's wrong without knowing of what are you 
> > exactly 
> > doing. Since there is no such platform as "at91" in OpenBMC, we 
> > don't 
> > know what recipe do you use for u-boot. 
> > Generally, u-boot recipe should include u-boot.inc: 
> >   
> > > require recipes-bsp/u-boot/u-boot.inc 
> >   
> > This include file provide u-boot-default-env recipe 
> > https://github.com/openbmc/openbmc/blob/master/poky/meta/recipes-bsp/u-boot/u-boot.inc#L215 
> >   
> > On Mon, 2022-01-03 at 15:34 +0530, Nikhil V wrote: 
> > > Hi, 
> > >      I am trying to build image for openbmc on SAMA5D27-som1-ek1 
> > > development board made by microchip(atmel). SAMA5D27 board has 
> > > yocto 
> > > support. 
> > >      I have added meta-atmel layer to openbmc, while 
> > > building/compiling 
> > > using " bitbake obmc-phosphor-image ", I am facing following 
> > > error, 
> > >      
> > >       [ERROR: Nothing RPROVIDES 'u-boot-default-env'] 
> > > 
> > >       I have tried by updating with following content but didnt 
> > > get any 
> > > result. 
> > >                 PREFERRED_PROVIDER_u-boot = "u-boot-at91" 
> > >                 PREFERRED_PROVIDER_virtual/bootloader = "u-boot- 
> > > at91" 
> > > 
> > >       Can you help me to find a solution. 
> > > 
> > >   
> > > Thanks & Regards, 
> > > Nikhil Muley 
> > > 
> > > 
> > > 
> >   
 
-- 
Best regards, 
Andrei Kartashev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220105/ab373d36/attachment-0001.htm>