**** BEGIN LOGGING AT Tue Jul 05 02:59:57 2011 Jul 05 07:44:28 hi Jul 05 07:44:30 anybody around? Jul 05 07:44:42 rlrosa: hi Jul 05 07:44:48 bluelightning: hi! Jul 05 07:45:29 bluelightning: i have a question, perhaps you can help me. how do i get a filesystem using bitbake? i want to compile the omap3-pwm, and i need to ref a rootfs Jul 05 07:45:57 bluelightning: i managed to get uImage, u-boot.bin, etc, but i cannot find the root filesystem Jul 05 07:46:26 what target did you build? i.e. bitbake Jul 05 07:47:36 bluelightning: bitbake virtual/kernel -c clean, then -c compile -f, then -c deploy Jul 05 07:47:51 bluelightning: (i configured the beagle stuff before that) Jul 05 07:48:21 my suggestion would be instead of all that, just build an image Jul 05 07:48:29 that will build the kernel and everything else as well Jul 05 07:48:38 bitbake console-image ? Jul 05 07:48:53 yep, console-image is one option Jul 05 07:49:03 will it use the stuff i configured for the beagle? Jul 05 07:49:18 if you have MACHINE = "beagleboard" absolutely Jul 05 07:49:26 great Jul 05 07:49:39 and do you know where i will be able to find the rootfs files? Jul 05 07:49:39 what else did you do to "configure" it for the beagle? Jul 05 07:49:52 tmp/deploy/images Jul 05 07:50:38 i modified setup-scripts/sources/openembedded/recipes/linux/linux-omap-psp-2.6.32/beagleboard/defconfig Jul 05 07:51:59 ok, that should be fine Jul 05 07:52:06 i'm running now, it take about 15' i think Jul 05 07:52:12 one more thing just to check Jul 05 07:52:21 what did you change in the kernel config just out of curiosity? Jul 05 07:53:26 some timer. the stuff mentioned here https://github.com/scottellis/omap3-pwm Jul 05 07:53:52 this is the script i want to use https://github.com/scottellis/omap3-pwm/blob/master/beagle-source-me.txt Jul 05 07:54:04 i'm having trouble with the KERNELDIR var Jul 05 07:54:36 wow now it's all there Jul 05 07:54:41 nice going! Jul 05 07:54:42 thanks! Jul 05 07:54:51 :) Jul 05 07:55:06 no problem Jul 05 07:56:04 now i can document in a reasonable way :) i had it working, but i didn't remember what i had done. i want our quadrotor project to be nicely documented and followable, so other don't annoy bluelightning about KERNELDIR Jul 05 08:00:59 well really this external module should be built within OE and not separately, that will save others a lot of pain Jul 05 08:04:10 do you think this will happen eventually or are you suggesting me doing something? Jul 05 08:04:12 (brb) Jul 05 08:05:28 well, I'm suggesting that somebody should Jul 05 08:06:09 it's probably not that much work, we have other examples of building external kernel modules I think Jul 05 08:06:26 i'm really new at all this, but i'll probably be learning a lot. it would be nice to help out Jul 05 08:06:40 ultimately all of this kernel stuff should be pushed towards mainline of course Jul 05 08:07:00 and that's really the responsibility of whoever wrote the code for the module Jul 05 08:07:31 i'll message him, see what he plans Jul 05 08:07:39 thanks for the help Jul 05 08:07:40 :) Jul 05 08:08:36 np Jul 05 08:32:34 bluelightning: are you still around? Jul 05 08:33:45 rlrosa: yep Jul 05 08:33:57 great Jul 05 08:34:12 do you know what command generates the MLO and the u-boot.bin files? Jul 05 08:34:42 i had them, but i ran a bunch of stuff to get them. it would save me some time if you already know what does what Jul 05 08:34:54 if you're busy i'll just play around until i find it... Jul 05 08:35:10 if you bitbake u-boot it should produce them... I would have thought building an image would cause u-boot to be built Jul 05 08:36:51 it Jul 05 08:36:54 it Jul 05 08:36:56 sorry Jul 05 08:37:20 it's not in tmp/deploy/glibc/images/beagleboard Jul 05 08:37:29 (that's where it used to be) Jul 05 08:37:48 what happens if you bitbake u-boot? Jul 05 08:39:24 i got the u-boot now Jul 05 08:39:29 i still don't have the MLO Jul 05 08:39:35 (did i say i wanted it?) Jul 05 08:40:05 ah, I think that's provided by x-load Jul 05 08:40:14 so bitbake x-load Jul 05 08:41:43 i get an error with that Jul 05 08:41:59 | install: cannot stat `/home/rrosa/work/setup-scripts/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/x-load-1_1.5.0+r24+gitr04b1732220078d47c18a84cbafc52e45db71f13d-r24/git/x-load.bin.ift': No such file or directory Jul 05 08:41:59 NOTE: package x-load-1_1.5.0+r24+gitr04b1732220078d47c18a84cbafc52e45db71f13d-r24: task do_deploy: Failed Jul 05 08:41:59 ERROR: Function 'do_deploy' failed (see /home/rrosa/work/setup-scripts/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/x-load-1_1.5.0+r24+gitr04b1732220078d47c18a84cbafc52e45db71f13d-r24/temp/log.do_deploy.21147 for further information) Jul 05 08:41:59 ERROR: Task 14 (/home/rrosa/work/setup-scripts/sources/openembedded/recipes/x-load/x-load_git.bb, do_deploy) failed with exit code '1' Jul 05 08:41:59 ERROR: '/home/rrosa/work/setup-scripts/sources/openembedded/recipes/x-load/x-load_git.bb' failed Jul 05 08:53:39 i had it at some point, so i guess i have to figure out the correct order of things Jul 05 08:55:58 building console-image ought to take care of building these things Jul 05 08:56:08 if they are needed for the image Jul 05 08:56:17 if not, there's a bug IMHO Jul 05 08:56:31 maybe some tmp thing/ Jul 05 08:56:39 made it, used it, killed it_ Jul 05 08:56:41 ? Jul 05 08:57:01 what do you mean? Jul 05 08:57:22 that maybe bitbake console-image generated what it needed and then deleted it Jul 05 08:57:58 i have a file named config-beagleboard.config Jul 05 08:58:04 i do not know what it is Jul 05 08:58:29 (i sort of know that MLO is some small pgm loaded at boot up) Jul 05 08:59:00 no, it wouldn't have done that I don't think Jul 05 08:59:43 should i report this to the angstrom devel list or some other place? Jul 05 09:00:40 i found a post that claims this is the correct order bitbake base-image  Jul 05 09:00:40 bitbake console-image x11-image  Jul 05 09:00:40 bitbake MLO  Jul 05 09:00:40 bitbake x-load  Jul 05 09:00:43 i'll try that Jul 05 09:01:04 right, ok, so there's a target called MLO, wasn't aware of that Jul 05 09:01:17 don't bother with x11-image unless you really want that, it'll take ages Jul 05 09:01:27 (there doesn't seem to be such a target....) Jul 05 09:01:51 not in source/openembedded/recipes Jul 05 09:02:52 I'm sure it's the x-load recipe that's supposed to produce that Jul 05 09:03:03 it contains instructions to create it Jul 05 09:03:13 do you know some command such as "make clean" Jul 05 09:03:19 to start over? Jul 05 09:03:53 easiest way to start over is just delete tmpdir (or move it out of the way) Jul 05 09:04:01 ok Jul 05 09:04:06 or rather, TMPDIR Jul 05 09:04:14 whatever you have that set to Jul 05 09:05:01 then I would suggest bitbake console-image followed by bitbake x-load Jul 05 09:05:17 then bitbake console-image, x-load, u-boot, should get it all there? Jul 05 09:05:21 no base-image? Jul 05 09:06:24 no, you should only need to build one image Jul 05 09:06:32 ok Jul 05 09:06:33 one more Jul 05 09:06:40 what's with the virtual/kernel stuff? Jul 05 09:06:48 you may need to build u-boot, but I would hope that console-image for beagleboard would do that for you Jul 05 09:06:53 frankly it should do the rest as well Jul 05 09:06:53 ok Jul 05 09:07:11 virtual/kernel is just a virtual target to build the kernel for your device Jul 05 09:07:25 any image will need to build that anyway Jul 05 09:07:34 ok.. Jul 05 09:07:58 could you suggest any place wherei could read about this stuff or just google? Jul 05 09:10:26 hmm... well there's lots of stuff about OE out there Jul 05 09:10:50 there's the manual of course, not sure if it's actually entertaining reading though Jul 05 09:11:13 ok, just wanted to know if you had some specifici ultra great reference Jul 05 09:11:47 not really, I've just been around the OE community for quite a while :) Jul 05 09:16:31 ok thanks for your help Jul 05 09:16:53 i'll leave the commands running and check what happened for breakfast Jul 05 09:17:03 thanks again! bye! Jul 05 09:25:50 cya Jul 05 10:58:13 angstrom: 03testlab  07yocto * r1ded27f5da 10testlab/c6a816x_evm/eglibc/systemd-GNOME-image/ (4 files): c6a816x-evm: systemd-GNOME-image configured for angstrom v2011.07-core using branch master and revision ee72f1a91dbda6c86064c251d09f6b7edf616868 Jul 05 15:40:27 angstrom: 03testlab  07yocto * r2df1cb1616 10testlab/c6a816x_evm/eglibc/systemd-image/ (4 files): c6a816x-evm: systemd-image configured for angstrom v2011.07-core using branch (nobranch) and revision e5f11a5df1ee0afb4d780233b2e854b29171325a **** ENDING LOGGING AT Wed Jul 06 02:59:57 2011