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

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

[Nikhil V]

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

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

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

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

[Andrei Kartashev]

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

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

[Nikhil V]

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

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 <a.kartashev@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

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

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

[Andrei Kartashev]

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
> <a.kartashev@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

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

[Nikhil V]

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

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 <a.kartashev@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@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

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

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

[Nikhil V]

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

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@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@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@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

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

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

[Patrick Williams]

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

On Wed, Jan 05, 2022 at 04:40:52PM +0530, Nikhil V wrote:
 
>     Trying to implement openbmc on SAMA5D27 development board and to use secure boot feature provided by microchip. To make openbmc more secure.

I don't have much help on your specific problem, but I think there is some
surprise in your use of this chip for a few reasons.

   - This isn't really a BMC-oriented chip and is likely missing hardware that
     a BMC would typically have for interacting with the host processors.

   - The A5 core in this chip is probably slower than the AST2500 (or maybe in
     the same ballpark) which is already a generation behind.

   - Aspeed has secure boot support also / already.

This isn't to say that you might not be able to get the SAMA5D27 working as a
BMC-like device for your system, but the fact that nobody else has decided to
build a server around it would give me a bit of concern if it showed up in a
system design I was working on.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Nikhil V]

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

Hi Patrick,

   

   Thanks for your response, I totally agree with above points. As I have SAMA5D27 lying arround and i wanted to explore/understand openbmc.

   Also i have seen some people have implemented openbmc on beaglebone, raspberry pi, Freescale Processors.

   As no one has tried porting openbmc with Atmel SAM series processor, I thought that i can give it a try to port openbmc on SAMA5D27,

   Any pointer or document will be helpful. 



Thanks & Regards,

Nikhil Muley










---- On Wed, 05 Jan 2022 22:31:42 +0530 Patrick Williams <patrick@stwcx.xyz> wrote ----



On Wed, Jan 05, 2022 at 04:40:52PM +0530, Nikhil V wrote: 
 
>     Trying to implement openbmc on SAMA5D27 development board and to use secure boot feature provided by microchip. To make openbmc more secure. 
 
I don't have much help on your specific problem, but I think there is some 
surprise in your use of this chip for a few reasons. 
 
 - This isn't really a BMC-oriented chip and is likely missing hardware that 
 a BMC would typically have for interacting with the host processors. 
 
 - The A5 core in this chip is probably slower than the AST2500 (or maybe in 
 the same ballpark) which is already a generation behind. 
 
 - Aspeed has secure boot support also / already. 
 
This isn't to say that you might not be able to get the SAMA5D27 working as a 
BMC-like device for your system, but the fact that nobody else has decided to 
build a server around it would give me a bit of concern if it showed up in a 
system design I was working on. 
 
-- 
Patrick Williams

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