**** BEGIN LOGGING AT Tue Mar 27 02:59:58 2012 Mar 27 09:55:54 hi :) how can i disable the autologin to x11 at login? Mar 27 11:23:00 does anybody know where I can find a simple C/C++ program to blink user LED on beaglebone? Mar 27 11:55:30 angs: I not have that board. Googling i found this http://hackaday.com/2012/03/15/twiddling-an-led-using-the-beaglebones-embedded-linux/ Mar 27 11:59:29 thank you spider-pork. I found some examples such examples in different languages, but not in C or C++ Mar 27 12:00:02 beaglebone runs angstroms dist. when I wrote a code for it and stores the code in sys file system, right? Mar 27 12:00:15 when it boots, I guess the stored program is erased Mar 27 12:00:21 try here http://osdir.com/ml/beagleboard/2011-12/msg00204.html Mar 27 12:00:36 how can I make the program permanently works on the angstroms OS? Mar 27 12:00:57 wow thank you very much Mar 27 12:00:59 :) Mar 27 12:01:00 you must build it and then run like ./yourprogram Mar 27 12:01:24 you could start it at boot editing rc.local Mar 27 12:01:38 you are welcome Mar 27 12:02:05 is there any example instruction for the boot editin? Mar 27 12:02:23 I am very new in linux, sorry for my noob question Mar 27 12:03:09 It's normal, we was noob almost one time in our life Mar 27 12:03:39 angstrom use init V procedure Mar 27 12:04:02 you could read here http://en.wikipedia.org/wiki/Init Mar 27 12:04:19 or you can do from bash "man init" Mar 27 12:04:49 be careful because some distro now use another kind of init process called upstart Mar 27 12:05:27 so if you run "man init" on ubuntu you'll read upstart procedure instruction instead of initv Mar 27 12:06:17 to make things even more complicated, angstrom now uses systemd instead of sysvinit Mar 27 12:06:39 :( Mar 27 12:07:26 I will google and read more about them Mar 27 12:07:32 thank you very much for your help Mar 27 12:07:33 http://en.wikipedia.org/wiki/Systemd Mar 27 12:07:35 and explanations Mar 27 12:07:44 bluelightning: thank you for that info Mar 27 12:08:33 bluelightning: 2011-03 maintenance still use sysvinit or the new systemd? Mar 27 12:08:40 *uses Mar 27 12:08:57 I'm not sure... possibly it is still using sysvinit Mar 27 12:08:59 configure: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E --sysroot=/media/USB_HDD2/mini6410/tmp/sysroots/armv6-angstrom-linux-gnueabi" fails sanity check Mar 27 12:09:07 building for mini6410 board got problems in eglibc_2.9.bb Mar 27 12:09:30 your hash not match with the package on repo Mar 27 12:09:44 (i think) Mar 27 12:10:01 TARGET_FPU = "hard" Mar 27 12:10:45 oh no wait forgot my answer Mar 27 12:11:22 Ananth__: have you got some info about log output file? Mar 27 12:13:01 2011-3 is sysvinit Mar 27 12:15:18 Spider-Pork: yes i got information from config.log and error reported is cc1: sorry, unimplemented: -mfloat-abi=hard and VFP Mar 27 12:15:47 #define PACKAGE_NAME "GNU C Library" Mar 27 12:15:51 #define PACKAGE_TARNAME "c-library" Mar 27 12:15:55 #define PACKAGE_VERSION "(see version.h)" Mar 27 12:15:59 #define PACKAGE_STRING "GNU C Library (see version.h)" Mar 27 12:16:04 #define PACKAGE_BUGREPORT "glibc" Mar 27 12:16:08 #define PKGVERSION "(EGLIBC) " Mar 27 12:16:11 #define REPORT_BUGS_TO "" Mar 27 12:16:15 #define HAVE_LIBIDN 1 Mar 27 12:16:24 #ifdef __STDC__ Mar 27 12:16:27 # include Mar 27 12:16:31 #else Mar 27 12:16:34 # include Mar 27 12:16:40 #endif Mar 27 12:16:43 main() Mar 27 12:16:47 { Mar 27 12:16:50 } Mar 27 12:17:00 if i try to compile this program Mar 27 12:17:13 i will end up with the error reported Mar 27 12:17:25 will that any way to over come this error Mar 27 12:17:47 I started a build with TARGET_FPU_armv6 = "soft" Mar 27 12:17:53 tp try my luck Mar 27 12:17:58 to try my luck Mar 27 12:29:03 Ananth__: are you crosscompiling that? Mar 27 12:30:04 yes Mar 27 12:31:03 are you using ARCH=ARM and the right toolchain? Mar 27 12:31:04 build@build-laptop:/media/USB_HDD2/mini6410/openembedded$ /media/USB_HDD2/mini6410/tmp/sysroots/i686-linux/usr/armv6/bin/arm-angstrom-linux-gnueabi-gcc hello.c -msoftcc1: error: unrecognized command line option "-msoft" hello.c:1: sorry, unimplemented: -mfloat-abi=hard and VFP Mar 27 12:31:38 build@build-laptop:/media/USB_HDD2/mini6410/openembedded$ /media/USB_HDD2/mini6410/tmp/sysroots/i686-linux/usr/armv6/bin/arm-angstrom-linux-gnueabi-gcc hello.c Mar 27 12:31:40 hello.c:1: sorry, unimplemented: -mfloat-abi=hard and VFP Mar 27 12:31:41 Is better to set the correct toolchain path inside your $PATH Mar 27 12:32:08 and in that case you must set ARCH=arm Mar 27 12:32:33 (I think) Mar 27 12:34:17 ok i try my luck. And my earliy try seams to be working TARGET_FPU_armv6 = "soft" Mar 27 12:34:18 ow, you are using arm gcc :/ Mar 27 12:34:32 so i think is not necessary ARCH Mar 27 12:35:12 i guess it is some thing to do with floating point (hadware/software) selection in toolchain Mar 27 12:36:02 but i have much idea how to make use if VFP-Unit Mar 27 12:36:11 but i dont have much idea how to make use if VFP-Unit Mar 27 12:40:02 you should export ARCH=arm and CROSS_COMPILE=/your_toolchain . For vfp-unit support check the doc of your arm-gcc Mar 27 12:41:31 where you took the toolchain? Mar 27 12:46:39 ah wait, I'm not sure about that: the VFP is standard inside armv7 core but it isn't on armv6 Mar 27 12:47:29 maybe your core didn't have it Mar 27 12:47:36 http://www.friendlyarm.net/products/mini6410 Mar 27 12:47:59 i am using that board. and it is stated that VFP-Unit and Jazelle is supported Mar 27 12:48:29 Yep I see Mar 27 12:48:40 1176 is the latest arm11 series Mar 27 12:49:02 try with options inside your gcc version Mar 27 12:49:05 check the manual Mar 27 12:49:21 I'm really noob abot that kind of problems :/ Mar 27 12:49:25 *about Mar 27 12:49:45 Actually iam looking for basic working image (not any optimized image for the board) Mar 27 12:50:28 so any working toolchain even software floating point is enough at this point of stage in my development stage Mar 27 12:51:20 Any arm-gcc toolchain version other than 4.3.3 is known to be working ? Mar 27 12:52:05 any way i am trying softfp with 4.3.3 still 10 more task are there to complete eglibc_2.9.bb Mar 27 12:52:09 I'm not an expert of gcc toolchain. Someone here suggested me to use Linaro toolchain for every core exluding for TI products Mar 27 12:52:25 for TI products you should use Codesourcery Lite Mar 27 12:53:36 ok. Now i can say to bitbake that to use linaro/ custom toolchain path location for compiling the bins ? Mar 27 12:53:46 I'm actually using this "Sourcery_G++_Lite-arm-2009q3-67" Mar 27 12:54:08 currently it is taking /media/USB_HDD2/mini6410/tmp/sysroots/i686-linux/usr/armv6/bin as toolchain path Mar 27 12:54:31 PATH=/yourtoolchain_path/bin:$PATH Mar 27 12:54:42 bitbake Mar 27 12:55:21 ah wait Mar 27 12:56:48 you can follow as "general guide" this link http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html Mar 27 12:57:10 and check the official doc of openembedded plus bitbake Mar 27 12:57:44 ok sure Mar 27 12:57:59 you should edit a conf file where explain to system what kind of target you are using, how many core you want to use for building and other stuff like these Mar 27 12:58:25 then source Mar 27 12:58:35 my local.conf is MACHINE = "mini6410" DISTRO = "angstrom-2008.1" LIBC = "eglibc" GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 de_DE.UTF-8 fr_FR.UTF-8 en_US.UTF-8" TARGET_FPU_armv6 = "soft" Mar 27 12:58:40 set the PATH (you can also do that inside the same config file) Mar 27 12:59:06 and then bitbake Mar 27 12:59:21 you colud find the list of images recipes inside recipes/images Mar 27 12:59:27 *could Mar 27 13:00:01 take a look to conf_example Mar 27 13:00:07 is pretty well documented Mar 27 13:00:22 I used that for my panda build Mar 27 13:00:31 ok. Mar 27 13:00:56 I need to go, I'll be back here tonight or tomorrow. Have fun :) Mar 27 13:01:06 cool my problem got solved my using TARGET_FPU_armv6 = "soft" Mar 27 13:01:20 glad to hear that Mar 27 13:01:23 bye! Mar 27 13:01:34 Thanks for guidance Spider-Pork bye Mar 27 13:01:43 np Mar 27 14:06:01 !logs Mar 27 14:50:43 Hello everyone. I'm building Angstrom for the SAM9G25 for the first time and I'm having issues with getting the console image to deploy. Before I go into more details, am I talking to the right group? Mar 27 15:38:06 he left too fast Mar 27 16:10:05 Hi all Mar 27 16:10:24 I have an SBC8100 and i'm trying to install angstrom on it Mar 27 16:10:52 every thing seems to works fine except the touchscreen Mar 27 16:11:01 (the LCD displays well) Mar 27 16:11:23 well, that is a good start :) Mar 27 16:11:23 but I can't manage to make that LCD working Mar 27 16:11:46 asdly i do not know anything that might help you Mar 27 16:11:54 I found that there is no xf86-input-tslib Mar 27 16:12:10 provided with the rootfs I generated online Mar 27 16:12:21 I want to cross compile this lib Mar 27 16:13:03 but I have no idae where I could retrieve the source for Xorg which is used inside angstrom Mar 27 16:14:34 did you check the feeds? Mar 27 16:14:38 I tried to get other tslid_dr from other distribution Mar 27 16:14:42 feeds ? Mar 27 16:15:09 http://www.angstrom-distribution.org/repo/ Mar 27 16:15:33 yeah Mar 27 16:16:36 I downloaded the source for tslib Mar 27 16:25:56 btw Mar 27 16:27:57 does anyone where I can buy a GOOD USB<->serial adaptater which works perfectly fine with linux ? Mar 27 20:11:55 what is the use of trigger in this line echo none > /sys/class/leds/beaglebone::usr1/trigger? Mar 27 20:12:02 is there any commands that I can type to read more about the trigger, brightness etc inside usr1? Mar 27 20:14:02 * russell-- getting a build failure for systemd-image (for beaglebone), something inscrutible in the do_rootfs related to pam modules??? Mar 27 20:18:04 Davidbrcz: which one do you have that doesn't work? Mar 27 20:18:27 and, what kind of serial? Mar 27 20:18:43 like traditional or 3.3V ttl? Mar 27 20:49:28 reug Mar 27 20:50:01 russell--, I don't understand what you are asking Mar 27 21:06:31 Davidbrcz: "does anyone where I can buy a GOOD USB<->serial adaptater which works perfectly fine with linux ?" Mar 27 21:06:50 yeap and ? Mar 27 21:06:57 they all work? Mar 27 21:07:10 hum Mar 27 21:07:17 most of them anyway Mar 27 21:07:20 :p Mar 27 21:07:22 all the ones i use do Mar 27 21:07:46 may be I found the one which doesn't work with linux Mar 27 21:08:10 what does lsusb give you for a vendor/device id? Mar 27 21:08:16 nothing Mar 27 21:08:20 that the issue Mar 27 21:08:47 It is not recognize by either windows 7 or Fedora Mar 27 21:09:04 maybe it's just a power cable Mar 27 21:09:38 what kind of connector is on the other end? Mar 27 21:09:45 with a RS 232 Mar 27 21:09:54 like a DB9? Mar 27 21:10:26 yeap Mar 27 21:10:40 male DB9 Mar 27 21:11:40 hmm. my experience buying random cables is that 90% of the time, usb stuff just work. if it doesn't work on windows either, maybe it's just broken? Mar 27 21:11:53 works* Mar 27 21:12:41 I don't know, my school give it to me Mar 27 21:12:47 the common chips like pl2303 or ftdi are well supported Mar 27 21:12:55 It was lying there inside a shelter Mar 27 21:13:19 where are you? Mar 27 21:13:46 ISAE/Supaero Mar 27 21:13:55 French engineering school Mar 27 21:14:01 nice Mar 27 21:14:08 you know it ? Mar 27 21:15:03 no, but i liked france when i visited ;-) Mar 27 21:15:07 :D Mar 27 21:15:15 this looks like one i have that works: http://www.amazon.fr/USB-1-1-serial-adapter-Serieller/dp/B0009M1L0W/ref=sr_1_9?ie=UTF8&qid=1332882861&sr=8-9 Mar 27 21:15:44 we might come visit again this summer Mar 27 21:15:50 and it looks like the one I have Mar 27 21:16:23 try it in another box, maybe your usb port is hosed Mar 27 21:17:20 hosed ? Mar 27 21:17:41 broken Mar 27 21:18:20 they works fine with other devices (mouse) Mar 27 21:19:32 even if it didn't have a working driver, it should show up in lsusb if there is a usb device there Mar 27 21:19:51 which makes me think the thing is just broken Mar 27 21:20:55 may be Mar 27 21:21:07 I'll ask tomorow for a new one Mar 27 21:21:34 that's what i'd do Mar 27 21:22:19 the linux/usb people are pretty aggressive about making that kind of device work, so it is surprising if it doesn't Mar 27 21:22:47 :D Mar 27 21:22:48 yeap Mar 27 21:23:12 It's vital when one needs to develop on a embded system Mar 27 21:24:56 normal old-fashioned serial is typically +5/-5V signalling, a lot of embedded devices use TTL level signalling 0V/3.3V, was the other thing i was mentioning Mar 27 21:25:35 hum Mar 27 21:25:52 I have no idea which one the SBC8100 is using Mar 27 21:26:11 and my touchscreen is still not working >< Mar 27 21:26:20 if it has a DB9 connector, it is probably the old-fashioned kind Mar 27 21:26:31 PC-style Mar 27 21:26:52 oki Mar 27 21:27:20 also, you might need a null-modem cable (i don't know anything about your SBC8100) Mar 27 21:27:35 to cross-over the TX and RX Mar 27 21:28:35 ?? Mar 27 21:30:48 the three wires you need for serial to work is ground transmit and receive Mar 27 21:31:13 it is essential that the transmit on one device connects to the receive on the other device and vice versa Mar 27 21:31:49 hum Mar 27 21:31:50 a null modem cable flips those for you, but if the connectors fit, then you are probably okay Mar 27 21:31:58 yeap Mar 27 21:32:03 it fits well Mar 27 21:32:13 in that case, never mind ;-) Mar 27 21:32:17 but i'll check datasheet **** ENDING LOGGING AT Wed Mar 28 02:59:58 2012