Re: [yocto] Updating uboot to v2013.01
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 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 > 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 >>> > wrote: > On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla > 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 > >> 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 > >> > 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 >
Re: [yocto] Updating uboot to v2013.01
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 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 >> 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 >> >> 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, F
Re: [yocto] Updating uboot to v2013.01
25 feb 2013 kl. 16:56 skrev Satya Swaroop Damarla : > 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... > I do not get this. Why should you want to install this package? The dts compiler should be part of any complete kernel! I think it is the wrong solution to use the one from the host distro. You should use the one the specific kernel version provides. > > On Mon, Feb 25, 2013 at 3:58 PM, Satya Swaroop DAMARLA > 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 >> 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 >>> 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 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 > 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 >> wrote: >>> On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla >>> 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 >>> > >>> > wrote: >>> >> >>> >> On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif >>> >> 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 wil
Re: [yocto] Updating uboot to v2013.01
25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA : > 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 > 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 >> 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 >>> 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 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 > wrote: >> On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla >> 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 >> > >> > wrote: >> >> >> >> On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif >> >> 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 >> >> > 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.. >> >> >> >> >> >>
[yocto] Moving the yocto autobuilder irc bot to the main yocto channel.
All, In an effort to get more eyes looking at things when an autobuilder build fails, I've moved the yocto autobuilder irc bot from a test channel to the main yocto channel. It should be fairly low in spam, only announcing when a build either exceptions out, or changes failed/success state. There is documentation on how to play with it at http://buildbot.net/buildbot/docs/0.8.7/manual/cfg-statustargets.html#status-IRC. If things get too spammy, I can modify it a bit to turn the noise down. Please let me have any feedback on noise level (too much, too little, just right). Thanks, -b -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-ti] Wifi Module + udev configs
On Mon, Feb 18, 2013 at 08:56:06AM -0300, Raul Rosetto Munoz wrote:
> Any suggestions?
>
> I really do not know what to do, the file "/lib/udev/firmware" never appear.
FYI, starting with 176, udev handles loading firmware images internally, hence
dropping the /lib/udev/firmware binary. But there were some bugs related to
that functionality, which got fixed in version 178...
http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=ChangeLog;hb=HEAD
http://upstream-tracker.org/changelogs/libudev/181/changelog.html
As I said before, if you are using Danny branch, then you should stick to the
proven udev-164 that is in oe-core, unless you really want to have systemd, in
which case you look into meta-openembedded...
--
Denys
> 2013/2/14 Raul Rosetto Munoz
>
> > Now Im with 173 from meta-fsl bbapend, but I tryed with many others from
> > meta-oe and poky.
> >
> >
> >
> >
> >
> >
> > 2013/2/14 Denys Dmytriyenko
> >
> >> On Thu, Feb 14, 2013 at 02:23:14PM -0200, Raul Rosetto Munoz wrote:
> >> > Denys,
> >> > There are something strange,
> >> >
> >> > First there are no linux-firmware-{rtl8192cu,rtl8192ce,rtl8192su}
> >> > installed at rfs.
> >>
> >> I was talking about packages, looks like you have them already installed.
> >>
> >>
> >> > raul@phi04:.../tmp/deploy/images$ find
> >> > /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/ -name "*8192*"
> >> > /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/RTL8192E
> >> >
> >> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/rtlwifi/rtl8192sefw.bin
> >> >
> >> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/rtlwifi/rtl8192defw.bin
> >> >
> >> > Another problem is that "/lib/udev/firmware" are not installed to.
> >> >
> >> > raul@phi04:.../tmp/deploy/images$ find
> >> > /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/udev/ -name "*firmware*"
> >> > raul@phi04:.../tmp/deploy/images$
> >>
> >> What is your udev version?
> >>
> >>
> >> > But I can see theses files at my "tmp/sysroots/beaglebone"
> >> >
> >> > raul@phi04:.../tmp/sysroots/beaglebone$ find lib/firmware/ -name
> >> "*8192*"
> >> > lib/firmware/RTL8192E
> >> > lib/firmware/rtlwifi/rtl8192sefw.bin
> >> > lib/firmware/rtlwifi/rtl8192defw.bin
> >> > lib/firmware/rtlwifi/rtl8192cfw.bin
> >> > lib/firmware/rtlwifi/rtl8192cufw.bin
> >> >
> >> > raul@phi04:.../tmp/sysroots/beaglebone$ find lib/udev/ -name
> >> "*firmware*"
> >> > lib/udev/firmware
> >> > lib/udev/rules.d/50-firmware.rules
> >> >
> >> > I tryed copy this files for the sdcard but doesnt work.
> >> >
> >> > Do you have any suggest?
> >> >
> >> > Thanks for all help.
> >>
> >
> >
> >
> > --
> > *Raul Rosetto Muñoz*
> >
>
>
>
> --
> *Raul Rosetto Muñoz*
> ___
> meta-ti mailing list
> meta...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, February 26, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Agenda: * Opens collection - 5 min (Song) * Yocto Project 1.3.1 status - 10 min (Ross) * Yocto 1.4 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status * SWAT team rotation: Paul Eggleton->Jessica Zhang * Opens - 10 min * Team Sharing - 20 min -Original Appointment- We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference details Conference name: Yocto Technical Team Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time Participants: 30 Duration: 60 minutes Participant passcode: 76994298 Dial-in number: 1.972.995. US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.x76994298# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): >From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): >From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): >From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): >From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) >From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: >From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: >From IP phone dial 2643799 >From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: >From Baguio City use 4471177 >From Metro Manila area use 8702477 Singapore: >From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: >From IP phone dial 5606998 >From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: >From IP phone dial 1363 >From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01604 663003 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 26, 2012 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 1.4_M4.rc1 git tags and branches
I know I sent out rc info for milestone 4 last week, but due to lousy conference/hotel wireless I was unable to get the branches and tags made. They are now currently in place. Sorry if this caused any issues for anyone. poky: 7d22ef28e64de06b6238d0ef9b664c0bee6efa46 meta-intel: 150be7c8fb97ac88737f6017fdf9dd47b273bb3e meta-qt3: 06e2fe600de962cdba53c23de1207501439a9c9f eclipse-poky: d18c45e0f5367979f7402380ee123242da2b57d5 Location of 1.4_M4.rc1 artifacts are at: http://autobuilder.yoctoproject.org/pub/nightly/20130220-2 -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] uboot.bin and rootfs but not uImage
Hello Guys... I think uImage is important but it is not being generated by the yocto project. It only generated the rootfs and uboot.bin. Is there any variable that has to be introduced in the machine.conf (in my case it is skidata-tamonten.conf) Here is the configuration file #@TYPE: Machine #@NAME: skidata-tamonten machine #@DESCRIPTION: Machine configuration for the Tamonten board PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg" IMAGE_FEATURES += "package-management" EXTRA_IMAGEDEPENDS += " u-boot" # Uncomment the following line to enable the hard floating point abi. Note that # this breaks some binary libraries and 3D (neither of which ship with # meta-yocto). For maximum compatibility, leave this disabled. DEFAULTTUNE ?= "cortexa9t" include conf/machine/include/tune-cortexa9.inc IMAGE_FSTYPES += "tar.bz2 ext2" SERIAL_CONSOLE = "115200 ttyS0" PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" PREFERRED_VERSION_linux-yocto ?= "3.2%" KERNEL_IMAGETYPE = " uImage" PREFERRED_VERSION_u-boot ?= "v2013.01.01%" UBOOT_MACHINE = "tec_config" UBOOT_ENTRYPOINT = "0x1700" UBOOT_LOADADDRESS = "0x1700" MACHINE_FEATURES = "usbgadget usbhost vfat screen touchscreen keyboard" Greets, Satya ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Updating uboot to v2013.01
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 wrote: > > > 25 feb 2013 kl. 15:58 skrev Satya Swaroop DAMARLA : > > 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 >> 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 >> >> 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
