Re: [yocto] Updating uboot to v2013.01

2013-02-28 Thread Rudolf Streif
Hey Satya,

Sorry for the delayed response.

Well, it should create the kernel image and wrap it for u-boot. At least
that is my experience and what I just did during a YP class on the weekend
for the BeagleBone.

What is linux-dummy? Is that a kernel recipe that you created?

I second what Khem said that you may be missing the BSP or have incorrect
entries in your machine configuration file. That file ties machine-specific
stuff such as kernel, bootloader etc. together.

I am not sure about the device tree compiler. YP builds dtc as a native
package. The only reason I can imagine is that it was not built when you
are trying to build u-boot.

The SRCREV tags for u-boot I got from git.denx.de:

2013.01.01:
http://git.denx.de/?p=u-boot.git;a=tag;h=8512592e47cc968d2d6eb788acde761ebc3acbf6

2013.01:
http://git.denx.de/?p=u-boot.git;a=tag;h=35c192cf449860aec8766e20a51bf2052a1dc968

They are the git commit tags.

Cheers,
Rudi


On Tue, Feb 26, 2013 at 11:44 PM, Satya Swaroop Damarla 
swaroop.dama...@gmail.com wrote:

 Hey Rudy,

 I think, it doesnot automatically take a kernel but we have to choose the
 kernel and I chose it v3.2 but seems it doesnot support my board and so I
 should take a kernel from the original and configure it to my need Here
 is the only error message I see about linux kernel

 WARNING: linux-dummy: No generic license file exists for: GPL in any
 provider

 my board is Avionic Tamonten Carrier, based on NVIDIA harmony board.
 Suggestions are very much appreciated but I am also currently trying to
 solve it.. I just downloaded a git kernel from the avionic site and can you
 please tell me how to configure it to so that the build system takes this
 as kernel and build it

 Greets,
 Satya


 On Tue, Feb 26, 2013 at 6:21 PM, Rudolf Streif 
 rstr...@linuxfoundation.org wrote:

 Satya,

 So what exactly do you get when building the kernel? No image at all in
 tmp/deploy/images? What do the logs for the kernel recipes say?

 Rudi


 On Mon, Feb 25, 2013 at 11:36 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey hans,

 I think you are right about the kernel device tree.. I think it should
 come with the kernel but I have no idea why it works.. Only an expert
 should say why it works.. I think my work is not complete. I can generate
 the rootfs and the uboot.bin file but not the uImage... I have no idea...
 Diid you complete generating the image for the board?

 Greets,
 Satya


 On Mon, Feb 25, 2013 at 5:05 PM, Hans Beckérus 
 hans.becke...@gmail.comwrote:



 25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA swar...@weisser.at:

 Guys. I found the solution to this problem

 I think if you already install uboot-tools or uboot-mkimage packes from
 Ubuntu repository then it is used instead of the one that is downloaded and
 we should uninstall the packages and then rerun the build,,... Then IT
 WORKS... So, thank you for the time and enegry... I assume this thread is
 closed and this is the solution and if this doesnot work for some then
 please post it and we may discuss the situation depending on the problem,

 Greetings  Regards,
 Satya

 Same comment here as for the device tree compiler. You should use the
 uboot tools/version as they come with the package. Not the one used by the
 host distro. To me this is not a proper solution.



 On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif 
 rstr...@linuxfoundation.org wrote:

 Satya,

 I will look into it later today. I am currently at the Linux
 Foundation's Embedded Linux Conference.

 Rudi


 On Thu, Feb 21, 2013 at 2:10 AM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 Hello Guys,

 I have not received any reply from you. If you can help me to figure
 out what the errors mean when adding a new .bb or recipe file then I can
 learn the mistake and take care in the new recipes I request your 
 time


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus 
 hans.becke...@gmail.com wrote:

 On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:
  Hey hans, this is what he meant,
 
  In the machine config file add the following
 
  PREFERRED_VERSION_u-boot ?= v2013.01%  or
 PREFERRED_VERSION_u-boot ?=
  v2013.01.01%
 
  By the way did you already complete the first part... There is
 also other
  file called u-boot-fw-utils_2012.04.01.bb ... I think we
 should do the
  same...
 
  Hans bytheway,  are you also working on the same board or
 diffferent board
  with same problem?
 

 Different board, same core, similar problem ;)
 Now I get it. Thanks. But still question 

Re: [yocto] Updating uboot to v2013.01

2013-02-27 Thread Khem Raj
On Tue, Feb 26, 2013 at 11:44 PM, Satya Swaroop Damarla
swaroop.dama...@gmail.com wrote:
 Hey Rudy,

 I think, it doesnot automatically take a kernel but we have to choose the
 kernel and I chose it v3.2 but seems it doesnot support my board and so I
 should take a kernel from the original and configure it to my need Here
 is the only error message I see about linux kernel

 WARNING: linux-dummy: No generic license file exists for: GPL in any
 provider


well it seems you are missing a whole BSP for this board. So I would suggest
to go through the BSP guide and setup one for your board

 my board is Avionic Tamonten Carrier, based on NVIDIA harmony board.
 Suggestions are very much appreciated but I am also currently trying to
 solve it.. I just downloaded a git kernel from the avionic site and can you
 please tell me how to configure it to so that the build system takes this as
 kernel and build it

 Greets,
 Satya


 On Tue, Feb 26, 2013 at 6:21 PM, Rudolf Streif rstr...@linuxfoundation.org
 wrote:

 Satya,

 So what exactly do you get when building the kernel? No image at all in
 tmp/deploy/images? What do the logs for the kernel recipes say?

 Rudi


 On Mon, Feb 25, 2013 at 11:36 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:

 hey hans,

 I think you are right about the kernel device tree.. I think it should
 come with the kernel but I have no idea why it works.. Only an expert should
 say why it works.. I think my work is not complete. I can generate the
 rootfs and the uboot.bin file but not the uImage... I have no idea... Diid
 you complete generating the image for the board?

 Greets,
 Satya


 On Mon, Feb 25, 2013 at 5:05 PM, Hans Beckérus hans.becke...@gmail.com
 wrote:



 25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA swar...@weisser.at:

 Guys. I found the solution to this problem

 I think if you already install uboot-tools or uboot-mkimage packes from
 Ubuntu repository then it is used instead of the one that is downloaded and
 we should uninstall the packages and then rerun the build,,... Then IT
 WORKS... So, thank you for the time and enegry... I assume this thread is
 closed and this is the solution and if this doesnot work for some then
 please post it and we may discuss the situation depending on the problem,

 Greetings  Regards,
 Satya

 Same comment here as for the device tree compiler. You should use the
 uboot tools/version as they come with the package. Not the one used by the
 host distro. To me this is not a proper solution.



 On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif
 rstr...@linuxfoundation.org wrote:

 Satya,

 I will look into it later today. I am currently at the Linux
 Foundation's Embedded Linux Conference.

 Rudi


 On Thu, Feb 21, 2013 at 2:10 AM, Satya Swaroop DAMARLA
 swar...@weisser.at wrote:

 Hello Guys,

 I have not received any reply from you. If you can help me to figure
 out what the errors mean when adding a new .bb or recipe file then I can
 learn the mistake and take care in the new recipes I request your 
 time


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA
 swar...@weisser.at wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus
 hans.becke...@gmail.com wrote:

 On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:
  Hey hans, this is what he meant,
 
  In the machine config file add the following
 
  PREFERRED_VERSION_u-boot ?= v2013.01%  or
  PREFERRED_VERSION_u-boot ?=
  v2013.01.01%
 
  By the way did you already complete the first part... There is
  also other
  file called u-boot-fw-utils_2012.04.01.bb ... I think we should
  do the
  same...
 
  Hans bytheway,  are you also working on the same board or
  diffferent board
  with same problem?
 

 Different board, same core, similar problem ;)
 Now I get it. Thanks. But still question remains how in earth I
 managed to build the kernel if not also having copied/renamed the
 mkimage .bb?
 Is the PREFERRED_VERSION_u-boot used to determine what mkimage and
 fw
 utils it picks up?
 Then it might be that since I/we build u-boot as a separate
 package,
 but kernel lifts in the mkimage stuff, it works but the wrong
 package
 was used.
 In my case obviously compatible, but not recommended I guess. Also,
 I
 agree that the fw utils should probably be in sync similar to
 mkimage.

 Hans

 
 
 
 
 
  On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus
  hans.becke...@gmail.com
  wrote:
 
  On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
  rstr...@linuxfoundation.org wrote:
   Satya,
  
   Simply look at the u-boot recipes in meta/recipes-bsp/u-boot
   such as
   u-boot_2012.04.01.bb. You can 

Re: [yocto] Updating uboot to v2013.01

2013-02-26 Thread Rudolf Streif
As Hans said, you should not need to install any of these host packages
since Yocto is for most part all self-contained. If you think that you need
to install host packages then there may be something wrong with building a
particular tool for the development host. That is typically done with
BBCLASSEXTENDS = native or BBCLASSETENDS = native native-sdk.

Rudi


On Mon, Feb 25, 2013 at 7:56 AM, Satya Swaroop Damarla 
swaroop.dama...@gmail.com wrote:

 Another important package that has to be installed in  the apt-get
 install device-tree-compiler package. This was adviced by the Thierry
 Reding, wh wrote the uboot config for Tamonten board.. Rudolf, may I ask
 you how did you find the SRCREV values for the uboot packages ... It would
 be great to know as there is not sufficient literature avilable to explain
 this on the internet...


 On Mon, Feb 25, 2013 at 3:58 PM, Satya Swaroop DAMARLA swar...@weisser.at
  wrote:

 Guys. I found the solution to this problem

 I think if you already install uboot-tools or uboot-mkimage packes from
 Ubuntu repository then it is used instead of the one that is downloaded and
 we should uninstall the packages and then rerun the build,,... Then IT
 WORKS... So, thank you for the time and enegry... I assume this thread is
 closed and this is the solution and if this doesnot work for some then
 please post it and we may discuss the situation depending on the problem,

 Greetings  Regards,
 Satya


 On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif 
 rstr...@linuxfoundation.org wrote:

 Satya,

 I will look into it later today. I am currently at the Linux
 Foundation's Embedded Linux Conference.

 Rudi


 On Thu, Feb 21, 2013 at 2:10 AM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 Hello Guys,

 I have not received any reply from you. If you can help me to figure
 out what the errors mean when adding a new .bb or recipe file then I can
 learn the mistake and take care in the new recipes I request your time


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus 
 hans.becke...@gmail.com wrote:

 On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:
  Hey hans, this is what he meant,
 
  In the machine config file add the following
 
  PREFERRED_VERSION_u-boot ?= v2013.01%  or
 PREFERRED_VERSION_u-boot ?=
  v2013.01.01%
 
  By the way did you already complete the first part... There is
 also other
  file called u-boot-fw-utils_2012.04.01.bb ... I think we should
 do the
  same...
 
  Hans bytheway,  are you also working on the same board or
 diffferent board
  with same problem?
 

 Different board, same core, similar problem ;)
 Now I get it. Thanks. But still question remains how in earth I
 managed to build the kernel if not also having copied/renamed the
 mkimage .bb?
 Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw
 utils it picks up?
 Then it might be that since I/we build u-boot as a separate package,
 but kernel lifts in the mkimage stuff, it works but the wrong package
 was used.
 In my case obviously compatible, but not recommended I guess. Also, I
 agree that the fw utils should probably be in sync similar to
 mkimage.

 Hans

 
 
 
 
 
  On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus 
 hans.becke...@gmail.com
  wrote:
 
  On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
  rstr...@linuxfoundation.org wrote:
   Satya,
  
   Simply look at the u-boot recipes in meta/recipes-bsp/u-boot
 such as
   u-boot_2012.04.01.bb. You can simply copy it and name it
   u-boot_2013.01.bb
   and then modify SRCREV to the revision that corresponds to the
 tag
   2013.01
   or 2013.01.01 in git.denx.de:
  
   for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
   for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
  
   Do the same for u-boot-mkimage and include the u-boot version
 with your
   bsp.
  
   Rudi
  
  
  Hi Rudi, sorry to chime in , but I have a similar problem but do
 not
  really get the last thing you said.
  What do you mean by including the u-boot version in the bsp? Also
 is
  it a must to also copy the mkimage .bb or will the system find a
  suitable one automatically?
  The thing is that I only copied/edited the u-boot .bb but never
 the
  mkimage. Still my kernel successfully builds the kernel uImage!?
  Some magic that I have missed :)
 
  Hans
 
 
   On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
   swaroop.dama...@gmail.com wrote:
  
   Hi Guys,
  
   I need support for uboot on Tamonten board but the version on
 it is
   v2012.04 but I came to know that v2012.10 

Re: [yocto] Updating uboot to v2013.01

2013-02-26 Thread Satya Swaroop Damarla
Hey Rudy,

I think, it doesnot automatically take a kernel but we have to choose the
kernel and I chose it v3.2 but seems it doesnot support my board and so I
should take a kernel from the original and configure it to my need Here
is the only error message I see about linux kernel

WARNING: linux-dummy: No generic license file exists for: GPL in any
provider

my board is Avionic Tamonten Carrier, based on NVIDIA harmony board.
Suggestions are very much appreciated but I am also currently trying to
solve it.. I just downloaded a git kernel from the avionic site and can you
please tell me how to configure it to so that the build system takes this
as kernel and build it

Greets,
Satya


On Tue, Feb 26, 2013 at 6:21 PM, Rudolf Streif
rstr...@linuxfoundation.orgwrote:

 Satya,

 So what exactly do you get when building the kernel? No image at all in
 tmp/deploy/images? What do the logs for the kernel recipes say?

 Rudi


 On Mon, Feb 25, 2013 at 11:36 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey hans,

 I think you are right about the kernel device tree.. I think it should
 come with the kernel but I have no idea why it works.. Only an expert
 should say why it works.. I think my work is not complete. I can generate
 the rootfs and the uboot.bin file but not the uImage... I have no idea...
 Diid you complete generating the image for the board?

 Greets,
 Satya


 On Mon, Feb 25, 2013 at 5:05 PM, Hans Beckérus 
 hans.becke...@gmail.comwrote:



 25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA swar...@weisser.at:

 Guys. I found the solution to this problem

 I think if you already install uboot-tools or uboot-mkimage packes from
 Ubuntu repository then it is used instead of the one that is downloaded and
 we should uninstall the packages and then rerun the build,,... Then IT
 WORKS... So, thank you for the time and enegry... I assume this thread is
 closed and this is the solution and if this doesnot work for some then
 please post it and we may discuss the situation depending on the problem,

 Greetings  Regards,
 Satya

 Same comment here as for the device tree compiler. You should use the
 uboot tools/version as they come with the package. Not the one used by the
 host distro. To me this is not a proper solution.



 On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif 
 rstr...@linuxfoundation.org wrote:

 Satya,

 I will look into it later today. I am currently at the Linux
 Foundation's Embedded Linux Conference.

 Rudi


 On Thu, Feb 21, 2013 at 2:10 AM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 Hello Guys,

 I have not received any reply from you. If you can help me to figure
 out what the errors mean when adding a new .bb or recipe file then I can
 learn the mistake and take care in the new recipes I request your time


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus 
 hans.becke...@gmail.com wrote:

 On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:
  Hey hans, this is what he meant,
 
  In the machine config file add the following
 
  PREFERRED_VERSION_u-boot ?= v2013.01%  or
 PREFERRED_VERSION_u-boot ?=
  v2013.01.01%
 
  By the way did you already complete the first part... There is
 also other
  file called u-boot-fw-utils_2012.04.01.bb ... I think we
 should do the
  same...
 
  Hans bytheway,  are you also working on the same board or
 diffferent board
  with same problem?
 

 Different board, same core, similar problem ;)
 Now I get it. Thanks. But still question remains how in earth I
 managed to build the kernel if not also having copied/renamed the
 mkimage .bb?
 Is the PREFERRED_VERSION_u-boot used to determine what mkimage and
 fw
 utils it picks up?
 Then it might be that since I/we build u-boot as a separate package,
 but kernel lifts in the mkimage stuff, it works but the wrong
 package
 was used.
 In my case obviously compatible, but not recommended I guess. Also,
 I
 agree that the fw utils should probably be in sync similar to
 mkimage.

 Hans

 
 
 
 
 
  On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus 
 hans.becke...@gmail.com
  wrote:
 
  On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
  rstr...@linuxfoundation.org wrote:
   Satya,
  
   Simply look at the u-boot recipes in meta/recipes-bsp/u-boot
 such as
   u-boot_2012.04.01.bb. You can simply copy it and name it
   u-boot_2013.01.bb
   and then modify SRCREV to the revision that corresponds to the
 tag
   2013.01
   or 2013.01.01 in git.denx.de:
  
   for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
   for 2013.01.01: 

Re: [yocto] Updating uboot to v2013.01

2013-02-25 Thread Satya Swaroop Damarla
hey hans,

I think you are right about the kernel device tree.. I think it should come
with the kernel but I have no idea why it works.. Only an expert should say
why it works.. I think my work is not complete. I can generate the rootfs
and the uboot.bin file but not the uImage... I have no idea... Diid you
complete generating the image for the board?

Greets,
Satya


On Mon, Feb 25, 2013 at 5:05 PM, Hans Beckérus hans.becke...@gmail.comwrote:



 25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA swar...@weisser.at:

 Guys. I found the solution to this problem

 I think if you already install uboot-tools or uboot-mkimage packes from
 Ubuntu repository then it is used instead of the one that is downloaded and
 we should uninstall the packages and then rerun the build,,... Then IT
 WORKS... So, thank you for the time and enegry... I assume this thread is
 closed and this is the solution and if this doesnot work for some then
 please post it and we may discuss the situation depending on the problem,

 Greetings  Regards,
 Satya

 Same comment here as for the device tree compiler. You should use the
 uboot tools/version as they come with the package. Not the one used by the
 host distro. To me this is not a proper solution.



 On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif 
 rstr...@linuxfoundation.org wrote:

 Satya,

 I will look into it later today. I am currently at the Linux Foundation's
 Embedded Linux Conference.

 Rudi


 On Thu, Feb 21, 2013 at 2:10 AM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 Hello Guys,

 I have not received any reply from you. If you can help me to figure out
 what the errors mean when adding a new .bb or recipe file then I can learn
 the mistake and take care in the new recipes I request your time


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop Damarla 
 swaroop.dama...@gmail.com wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA 
 swar...@weisser.at wrote:

 hey Guys... I get the following error... which I attached.. Its
 completely greek and latin to me.. Can you please help me..


 On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus 
 hans.becke...@gmail.com wrote:

 On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:
  Hey hans, this is what he meant,
 
  In the machine config file add the following
 
  PREFERRED_VERSION_u-boot ?= v2013.01%  or
 PREFERRED_VERSION_u-boot ?=
  v2013.01.01%
 
  By the way did you already complete the first part... There is also
 other
  file called u-boot-fw-utils_2012.04.01.bb ... I think we should
 do the
  same...
 
  Hans bytheway,  are you also working on the same board or
 diffferent board
  with same problem?
 

 Different board, same core, similar problem ;)
 Now I get it. Thanks. But still question remains how in earth I
 managed to build the kernel if not also having copied/renamed the
 mkimage .bb?
 Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw
 utils it picks up?
 Then it might be that since I/we build u-boot as a separate package,
 but kernel lifts in the mkimage stuff, it works but the wrong package
 was used.
 In my case obviously compatible, but not recommended I guess. Also, I
 agree that the fw utils should probably be in sync similar to mkimage.

 Hans

 
 
 
 
 
  On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus 
 hans.becke...@gmail.com
  wrote:
 
  On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
  rstr...@linuxfoundation.org wrote:
   Satya,
  
   Simply look at the u-boot recipes in meta/recipes-bsp/u-boot
 such as
   u-boot_2012.04.01.bb. You can simply copy it and name it
   u-boot_2013.01.bb
   and then modify SRCREV to the revision that corresponds to the
 tag
   2013.01
   or 2013.01.01 in git.denx.de:
  
   for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
   for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
  
   Do the same for u-boot-mkimage and include the u-boot version
 with your
   bsp.
  
   Rudi
  
  
  Hi Rudi, sorry to chime in , but I have a similar problem but do
 not
  really get the last thing you said.
  What do you mean by including the u-boot version in the bsp? Also
 is
  it a must to also copy the mkimage .bb or will the system find a
  suitable one automatically?
  The thing is that I only copied/edited the u-boot .bb but never the
  mkimage. Still my kernel successfully builds the kernel uImage!?
  Some magic that I have missed :)
 
  Hans
 
 
   On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
   swaroop.dama...@gmail.com wrote:
  
   Hi Guys,
  
   I need support for uboot on Tamonten board but the version on
 it is
   v2012.04 but I came to know that v2012.10 or v2013.01 supports
 the
   Tamontenboard through some guys here..
  
   It would be great if you can tell me how can I accomplish
 v2013.01 or
   v2012.10 into the build system and make it available so that 

[yocto] Updating uboot to v2013.01

2013-02-20 Thread Satya Swaroop Damarla
Hi Guys,

I need support for uboot on Tamonten board but the version on it is
v2012.04 but I came to know that v2012.10 or v2013.01 supports the
Tamontenboard through some guys here..

It would be great if you can tell me how can I accomplish v2013.01 or
v2012.10 into the build system and make it available so that I can compile
the and get uImage

(Tamonten board is a derivative of harmony board with some changes and has
arm cortexa9 processor without neon extentions )

I am kind of new to add new .bb files and help is really appreciated as I
am not able to figure out how to add

Greetings  Regards,
Swaroop
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Updating uboot to v2013.01

2013-02-20 Thread Rudolf Streif
Satya,

Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
u-boot_2012.04.01.bb. You can simply copy it and name it
u-boot_2013.01.bband then modify SRCREV to the revision that
corresponds to the tag 2013.01
or 2013.01.01 in git.denx.de:

for 2013.01: 
3a9d879f6f64585b819af728b53be0a05037fe0dhttp://git.denx.de/?p=u-boot.git;a=commit;h=3a9d879f6f64585b819af728b53be0a05037fe0d
for 2013.01.01:
e8ae0fa5edd152b2b29c470b88429be4cdcd2c46http://git.denx.de/?p=u-boot.git;a=commit;h=e8ae0fa5edd152b2b29c470b88429be4cdcd2c46

Do the same for u-boot-mkimage and include the u-boot version with your bsp.

Rudi


On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla 
swaroop.dama...@gmail.com wrote:

 Hi Guys,

 I need support for uboot on Tamonten board but the version on it is
 v2012.04 but I came to know that v2012.10 or v2013.01 supports the
 Tamontenboard through some guys here..

 It would be great if you can tell me how can I accomplish v2013.01 or
 v2012.10 into the build system and make it available so that I can compile
 the and get uImage

 (Tamonten board is a derivative of harmony board with some changes and has
 arm cortexa9 processor without neon extentions )

 I am kind of new to add new .bb files and help is really appreciated as I
 am not able to figure out how to add

 Greetings  Regards,
 Swaroop

 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto




-- 
-- 
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation

rudolf.str...@linux.com
Phone: +1.619.631.5383
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B

Linux Foundation Events Schedule:  events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Updating uboot to v2013.01

2013-02-20 Thread Hans Beckérus
On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
rstr...@linuxfoundation.org wrote:
 Satya,

 Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
 u-boot_2012.04.01.bb. You can simply copy it and name it u-boot_2013.01.bb
 and then modify SRCREV to the revision that corresponds to the tag 2013.01
 or 2013.01.01 in git.denx.de:

 for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
 for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46

 Do the same for u-boot-mkimage and include the u-boot version with your bsp.

 Rudi


Hi Rudi, sorry to chime in , but I have a similar problem but do not
really get the last thing you said.
What do you mean by including the u-boot version in the bsp? Also is
it a must to also copy the mkimage .bb or will the system find a
suitable one automatically?
The thing is that I only copied/edited the u-boot .bb but never the
mkimage. Still my kernel successfully builds the kernel uImage!?
Some magic that I have missed :)

Hans


 On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
 swaroop.dama...@gmail.com wrote:

 Hi Guys,

 I need support for uboot on Tamonten board but the version on it is
 v2012.04 but I came to know that v2012.10 or v2013.01 supports the
 Tamontenboard through some guys here..

 It would be great if you can tell me how can I accomplish v2013.01 or
 v2012.10 into the build system and make it available so that I can compile
 the and get uImage

 (Tamonten board is a derivative of harmony board with some changes and has
 arm cortexa9 processor without neon extentions )

 I am kind of new to add new .bb files and help is really appreciated as I
 am not able to figure out how to add

 Greetings  Regards,
 Swaroop

 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto




 --
 --
 Rudolf J. Streif
 Director of Embedded Solutions
 The Linux Foundation

 rudolf.str...@linux.com
 Phone: +1.619.631.5383
 Skype: rudolfstreif
 PGP: RSA 2048/2048 D6E7D28B

 Linux Foundation Events Schedule:  events.linuxfoundation.org
 Linux Foundation Training Schedule: training.linuxfoundation.org


 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Updating uboot to v2013.01

2013-02-20 Thread Satya Swaroop Damarla
Hey hans, this is what he meant,

In the machine config file add the following

PREFERRED_VERSION_u-boot ?= v2013.01%  or PREFERRED_VERSION_u-boot ?=
v2013.01.01%

By the way did you already complete the first part... There is also other
file called u-boot-fw-utils_2012.04.01.bb ... I think we should do the
same...

Hans bytheway,  are you also working on the same board or diffferent board
with same problem?






On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus hans.becke...@gmail.comwrote:

 On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
 rstr...@linuxfoundation.org wrote:
  Satya,
 
  Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
  u-boot_2012.04.01.bb. You can simply copy it and name it
 u-boot_2013.01.bb
  and then modify SRCREV to the revision that corresponds to the tag
 2013.01
  or 2013.01.01 in git.denx.de:
 
  for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
  for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
 
  Do the same for u-boot-mkimage and include the u-boot version with your
 bsp.
 
  Rudi
 
 
 Hi Rudi, sorry to chime in , but I have a similar problem but do not
 really get the last thing you said.
 What do you mean by including the u-boot version in the bsp? Also is
 it a must to also copy the mkimage .bb or will the system find a
 suitable one automatically?
 The thing is that I only copied/edited the u-boot .bb but never the
 mkimage. Still my kernel successfully builds the kernel uImage!?
 Some magic that I have missed :)

 Hans


  On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
  swaroop.dama...@gmail.com wrote:
 
  Hi Guys,
 
  I need support for uboot on Tamonten board but the version on it is
  v2012.04 but I came to know that v2012.10 or v2013.01 supports the
  Tamontenboard through some guys here..
 
  It would be great if you can tell me how can I accomplish v2013.01 or
  v2012.10 into the build system and make it available so that I can
 compile
  the and get uImage
 
  (Tamonten board is a derivative of harmony board with some changes and
 has
  arm cortexa9 processor without neon extentions )
 
  I am kind of new to add new .bb files and help is really appreciated as
 I
  am not able to figure out how to add
 
  Greetings  Regards,
  Swaroop
 
  ___
  yocto mailing list
  yocto@yoctoproject.org
  https://lists.yoctoproject.org/listinfo/yocto
 
 
 
 
  --
  --
  Rudolf J. Streif
  Director of Embedded Solutions
  The Linux Foundation
 
  rudolf.str...@linux.com
  Phone: +1.619.631.5383
  Skype: rudolfstreif
  PGP: RSA 2048/2048 D6E7D28B
 
  Linux Foundation Events Schedule:  events.linuxfoundation.org
  Linux Foundation Training Schedule: training.linuxfoundation.org
 
 
  ___
  yocto mailing list
  yocto@yoctoproject.org
  https://lists.yoctoproject.org/listinfo/yocto
 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Updating uboot to v2013.01

2013-02-20 Thread Hans Beckérus
On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
swaroop.dama...@gmail.com wrote:
 Hey hans, this is what he meant,

 In the machine config file add the following

 PREFERRED_VERSION_u-boot ?= v2013.01%  or PREFERRED_VERSION_u-boot ?=
 v2013.01.01%

 By the way did you already complete the first part... There is also other
 file called u-boot-fw-utils_2012.04.01.bb ... I think we should do the
 same...

 Hans bytheway,  are you also working on the same board or diffferent board
 with same problem?


Different board, same core, similar problem ;)
Now I get it. Thanks. But still question remains how in earth I
managed to build the kernel if not also having copied/renamed the
mkimage .bb?
Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw
utils it picks up?
Then it might be that since I/we build u-boot as a separate package,
but kernel lifts in the mkimage stuff, it works but the wrong package
was used.
In my case obviously compatible, but not recommended I guess. Also, I
agree that the fw utils should probably be in sync similar to mkimage.

Hans






 On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus hans.becke...@gmail.com
 wrote:

 On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
 rstr...@linuxfoundation.org wrote:
  Satya,
 
  Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
  u-boot_2012.04.01.bb. You can simply copy it and name it
  u-boot_2013.01.bb
  and then modify SRCREV to the revision that corresponds to the tag
  2013.01
  or 2013.01.01 in git.denx.de:
 
  for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
  for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
 
  Do the same for u-boot-mkimage and include the u-boot version with your
  bsp.
 
  Rudi
 
 
 Hi Rudi, sorry to chime in , but I have a similar problem but do not
 really get the last thing you said.
 What do you mean by including the u-boot version in the bsp? Also is
 it a must to also copy the mkimage .bb or will the system find a
 suitable one automatically?
 The thing is that I only copied/edited the u-boot .bb but never the
 mkimage. Still my kernel successfully builds the kernel uImage!?
 Some magic that I have missed :)

 Hans


  On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
  swaroop.dama...@gmail.com wrote:
 
  Hi Guys,
 
  I need support for uboot on Tamonten board but the version on it is
  v2012.04 but I came to know that v2012.10 or v2013.01 supports the
  Tamontenboard through some guys here..
 
  It would be great if you can tell me how can I accomplish v2013.01 or
  v2012.10 into the build system and make it available so that I can
  compile
  the and get uImage
 
  (Tamonten board is a derivative of harmony board with some changes and
  has
  arm cortexa9 processor without neon extentions )
 
  I am kind of new to add new .bb files and help is really appreciated as
  I
  am not able to figure out how to add
 
  Greetings  Regards,
  Swaroop
 
  ___
  yocto mailing list
  yocto@yoctoproject.org
  https://lists.yoctoproject.org/listinfo/yocto
 
 
 
 
  --
  --
  Rudolf J. Streif
  Director of Embedded Solutions
  The Linux Foundation
 
  rudolf.str...@linux.com
  Phone: +1.619.631.5383
  Skype: rudolfstreif
  PGP: RSA 2048/2048 D6E7D28B
 
  Linux Foundation Events Schedule:  events.linuxfoundation.org
  Linux Foundation Training Schedule: training.linuxfoundation.org
 
 
  ___
  yocto mailing list
  yocto@yoctoproject.org
  https://lists.yoctoproject.org/listinfo/yocto
 


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto