Re: [beagleboard] Running X on a headless Beaglebone black...problems
Hi Sid, THANKS A LOT for this! Great! No hassle with MIT Cookies and xauth and... Best! Again a live was saved! ;) Best regards, mcc Sid Boyce sbo...@blueyonder.co.uk [14-10-11 07:40]: Xvfb is the answer. https://wiki.archlinux.org/index.php/Headless_With_X With the Xvfb package installed on Ubuntu ARM and over an ssh login Xvfb , works without any of the other stuff mentioned in the URL above or on Wikipedia. Regards Sid. On 11/10/14 03:40, meino.cra...@gmx.de wrote: Hi, The Beaglebone Black runs Gentoo Linux with kernel 3.8.13-bone67. After trying to switch to newer system I found some missing features and new features ;) I dont prefer over 3.8.13-bone67. So I will stay with this one until its worth to switch. My Beaglebone Black should run in headless mode: No kind of display is attached. But I want to run X and use X forwarding to my PC. Unfortunately X does not start... Log: beagleboneblack:/home/mccramercat /var/log/Xorg.0.log [ 3544.547] X.Org X Server 1.15.0 Release Date: 2013-12-27 [ 3544.554] X Protocol Version 11, Revision 0 [ 3544.557] Build Operating System: Linux 3.8.13-20150516.01-bone53 armv7l Gentoo [ 3544.559] Current Operating System: Linux beagleboneblack 3.8.13-bone67 #2 SMP Thu Sep 25 05:52:37 CEST 2014 armv7l [ 3544.561] Kernel command line: console=tty1 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G [ 3544.566] Build Date: 09 June 2014 04:21:01PM [ 3544.568] [ 3544.570] Current version of pixman: 0.32.4 [ 3544.574]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3544.575] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3544.588] (==) Log file: /var/log/Xorg.0.log, Time: Sat Oct 11 04:12:05 2014 [ 3544.619] (==) Using config directory: /etc/X11/xorg.conf.d [ 3544.621] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 3544.629] (==) No Layout section. Using the first Screen section. [ 3544.629] (==) No screen section available. Using defaults. [ 3544.630] (**) |--Screen Default Screen Section (0) [ 3544.630] (**) | |--Monitor default monitor [ 3544.636] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 3544.637] (==) Automatically adding devices [ 3544.637] (==) Automatically enabling devices [ 3544.637] (==) Automatically adding GPU devices [ 3544.701] (**) FontPath set to: /usr/share/fonts/terminus, /usr/share/fonts/dina, /usr/share/fonts/proggy-fonts, /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 3544.701] (==) ModulePath set to /usr/lib/xorg/modules [ 3544.701] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 3544.703] (II) Loader magic: 0x1c8e68 [ 3544.703] (II) Module ABI versions: [ 3544.703]X.Org ANSI C Emulation: 0.4 [ 3544.703]X.Org Video Driver: 15.0 [ 3544.704]X.Org XInput driver : 20.0 [ 3544.704]X.Org Server Extension : 8.0 [ 3544.711] Initializing built-in extension Generic Event Extension [ 3544.713] Initializing built-in extension SHAPE [ 3544.716] Initializing built-in extension MIT-SHM [ 3544.718] Initializing built-in extension XInputExtension [ 3544.721] Initializing built-in extension XTEST [ 3544.723] Initializing built-in extension BIG-REQUESTS [ 3544.724] Initializing built-in extension SYNC [ 3544.726] Initializing built-in extension XKEYBOARD [ 3544.727] Initializing built-in extension XC-MISC [ 3544.728] Initializing built-in extension XINERAMA [ 3544.730] Initializing built-in extension XFIXES [ 3544.732] Initializing built-in extension RENDER [ 3544.733] Initializing built-in extension RANDR [ 3544.734] Initializing built-in extension COMPOSITE [ 3544.735] Initializing built-in extension DAMAGE [ 3544.736] Initializing built-in extension MIT-SCREEN-SAVER [ 3544.737] Initializing built-in extension DOUBLE-BUFFER [ 3544.739] Initializing built-in extension RECORD [ 3544.740] Initializing built-in extension DPMS [ 3544.741] Initializing built-in extension Present [ 3544.742] Initializing built-in extension DRI3 [ 3544.743] Initializing built-in extension X-Resource [ 3544.745] Initializing built-in extension XVideo [ 3544.745] Initializing built-in extension XVideo-MotionCompensation [ 3544.747] Initializing built-in extension XFree86-VidModeExtension [ 3544.747] Initializing built-in
[beagleboard] Re: Running X on a headless Beaglebone black...problems
meino.cra...@gmx.de wrote: Hi, The Beaglebone Black runs Gentoo Linux with kernel 3.8.13-bone67. After trying to switch to newer system I found some missing features and new features ;) I dont prefer over 3.8.13-bone67. So I will stay with this one until its worth to switch. My Beaglebone Black should run in headless mode: No kind of display is attached. But I want to run X and use X forwarding to my PC. Unfortunately X does not start... You don't need X running on the client machine (which the BBB is in this case if I understand what you're trying to do). The sequence to run an X application on the BBB with the desktop on your display would be:- chris$ ssh -X BBB Debian GNU/Linux 7 BeagleBoard.org BeagleBone Debian Image 2014-09-04 Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian chris@bbb's password: Last login: Thu Sep 18 01:54:51 2014 from chris.zbmc.eu chris@beaglebone:~$ abiword ... and abiword runs on the BBB but is displayed on my desktop. The machine on which the X display runs is the X server, the machine running the application is the X client. -- Chris Green ยท -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How can I enable SPI in 3.17?
After upgrading kernel to 3.17, my working program and test program does not work. And I think that this is related to SPI device. How can I properly enable SPI0 in 3.17? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Running X on a headless Beaglebone black...problems
No problem, I have used it on Beaglebone White and now on a Parallella-16 where the latest kernel has a yet unfixed problem starting X so I run GUI programs that way. X worked on the previous kernel but I need other functions available only on the latest one. Regards Sid. On 11/10/14 08:01, meino.cra...@gmx.de wrote: Hi Sid, THANKS A LOT for this! Great! No hassle with MIT Cookies and xauth and... Best! Again a live was saved! ;) Best regards, mcc Sid Boyce sbo...@blueyonder.co.uk [14-10-11 07:40]: Xvfb is the answer. https://wiki.archlinux.org/index.php/Headless_With_X With the Xvfb package installed on Ubuntu ARM and over an ssh login Xvfb , works without any of the other stuff mentioned in the URL above or on Wikipedia. Regards Sid. On 11/10/14 03:40, meino.cra...@gmx.de wrote: Hi, The Beaglebone Black runs Gentoo Linux with kernel 3.8.13-bone67. After trying to switch to newer system I found some missing features and new features ;) I dont prefer over 3.8.13-bone67. So I will stay with this one until its worth to switch. My Beaglebone Black should run in headless mode: No kind of display is attached. But I want to run X and use X forwarding to my PC. Unfortunately X does not start... Log: beagleboneblack:/home/mccramercat /var/log/Xorg.0.log [ 3544.547] X.Org X Server 1.15.0 Release Date: 2013-12-27 [ 3544.554] X Protocol Version 11, Revision 0 [ 3544.557] Build Operating System: Linux 3.8.13-20150516.01-bone53 armv7l Gentoo [ 3544.559] Current Operating System: Linux beagleboneblack 3.8.13-bone67 #2 SMP Thu Sep 25 05:52:37 CEST 2014 armv7l [ 3544.561] Kernel command line: console=tty1 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G [ 3544.566] Build Date: 09 June 2014 04:21:01PM [ 3544.568] [ 3544.570] Current version of pixman: 0.32.4 [ 3544.574]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3544.575] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3544.588] (==) Log file: /var/log/Xorg.0.log, Time: Sat Oct 11 04:12:05 2014 [ 3544.619] (==) Using config directory: /etc/X11/xorg.conf.d [ 3544.621] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 3544.629] (==) No Layout section. Using the first Screen section. [ 3544.629] (==) No screen section available. Using defaults. [ 3544.630] (**) |--Screen Default Screen Section (0) [ 3544.630] (**) | |--Monitor default monitor [ 3544.636] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 3544.637] (==) Automatically adding devices [ 3544.637] (==) Automatically enabling devices [ 3544.637] (==) Automatically adding GPU devices [ 3544.701] (**) FontPath set to: /usr/share/fonts/terminus, /usr/share/fonts/dina, /usr/share/fonts/proggy-fonts, /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 3544.701] (==) ModulePath set to /usr/lib/xorg/modules [ 3544.701] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 3544.703] (II) Loader magic: 0x1c8e68 [ 3544.703] (II) Module ABI versions: [ 3544.703]X.Org ANSI C Emulation: 0.4 [ 3544.703]X.Org Video Driver: 15.0 [ 3544.704]X.Org XInput driver : 20.0 [ 3544.704]X.Org Server Extension : 8.0 [ 3544.711] Initializing built-in extension Generic Event Extension [ 3544.713] Initializing built-in extension SHAPE [ 3544.716] Initializing built-in extension MIT-SHM [ 3544.718] Initializing built-in extension XInputExtension [ 3544.721] Initializing built-in extension XTEST [ 3544.723] Initializing built-in extension BIG-REQUESTS [ 3544.724] Initializing built-in extension SYNC [ 3544.726] Initializing built-in extension XKEYBOARD [ 3544.727] Initializing built-in extension XC-MISC [ 3544.728] Initializing built-in extension XINERAMA [ 3544.730] Initializing built-in extension XFIXES [ 3544.732] Initializing built-in extension RENDER [ 3544.733] Initializing built-in extension RANDR [ 3544.734] Initializing built-in extension COMPOSITE [ 3544.735] Initializing built-in extension DAMAGE [ 3544.736] Initializing built-in extension MIT-SCREEN-SAVER [ 3544.737] Initializing built-in extension DOUBLE-BUFFER [ 3544.739] Initializing built-in extension RECORD [ 3544.740] Initializing built-in extension DPMS [ 3544.741] Initializing built-in extension Present [ 3544.742] Initializing built-in extension DRI3 [ 3544.743] Initializing built-in extension X-Resource [ 3544.745]
[beagleboard] Bonescript and cloud9 problems. Just seems very flakey...
I'm running Angstrom and Cloud9 v0.6 I have been trying some of the simple examples and they seem to be very unstable. The analog input examples that display values to the console either do nothing, display a value once or display the value continually (as they are supposed to) but with odd delays now and again. Is there something I'm doing wrong or something I need to update to get even simple Bonescripts to work more than once??? Any help appreciated. I am a newbie on BBB and bonescript, coming from arduino stuff. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Bonescript and cloud9 problems. Just seems very flakey...
I have Angstrom v2012.12 by the way. On Saturday, October 11, 2014 6:31:26 PM UTC+1, Richard Markham wrote: I'm running Angstrom and Cloud9 v0.6 I have been trying some of the simple examples and they seem to be very unstable. The analog input examples that display values to the console either do nothing, display a value once or display the value continually (as they are supposed to) but with odd delays now and again. Is there something I'm doing wrong or something I need to update to get even simple Bonescripts to work more than once??? Any help appreciated. I am a newbie on BBB and bonescript, coming from arduino stuff. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] troubleshooting hung up SD card - processes trying to access SD card just hang
Hi, After working around the random reboot issue with kernel 3.14.19-ti-r28 by compiling the kernel without watchdog support (details here https://groups.google.com/forum/embed/?place=forum%2Fbeagleboardshowsearch=trueshowpopout=trueshowtabs=truehideforumtitle=trueparenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForumsafterlogin=#!category-topic/beagleboard/beaglebone-black/vgeh336p0P4), I ran into a different issue on my BBB (rev. A5C) today. From what I can tell, during my overnight backup last night, the SD card somehow locked up (with user led1 permanently lit) and any process that had tried to access the SD card was locked up as well. Trying to kill any of the hung processes with sudo kill pid wouldn't work in most cases and only resulted in an unkillable process, because after I did that, sudo kill -9 pid would be useless as well. So I killed most of the processes with kill -9, but I still ended up with a bunch completely hosed. The SD access was completely busted so not even a simple ls command worked anymore. That would just hang as well and I'd have to kill -9 it. The rest of the BBB was working just fine, as long as I didn't access the SD. The CPU was pretty much idle, except for postgresql process that tried to access the database that is also on the SD, but obviously couldn't anymore. I also discovered that my eMMC (from which I boot my Debian 7 while the SD card is used for storage), was almost out of space. That was mostly due to me installing a number of kernel versions over the last couple of days, which contributed to a shortage in space. Note that my tmp and log folder are on a USB drive and thus the system eMMC wasn't completely filled up and was still working. While I initially thought the low available memory to be the cause of the problem, and I certainly wish for that to be the answer, I fear it might be happening again. I do have netconsole logging running and of course, nothing was in the log. The SD card I use is a SanDisk Ultra 32GB Micro SDHC. So I'm wondering if you have any suggestions on what I can do to gather more information on the issue, should it arise again? Would I be able to do some sort of process dump, e.g. of the process handling the SD card? If so, could anyone point me to information on how that is done and what process I would have to run it on? I kind of guess that it might be the mmcqd/0 process? That's one I've seen causing an issue on the 3.8.13 kernel where it randomly froze up and I do recall that on these occasions, the usr LED1 also was always lit. My report of that issue (and the kernel panic details) can be found here https://github.com/beagleboard/linux/issues/12. I appreciate any pointers and assistance you can offer. Sebastian -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Running Python on PC to simulate Beaglebone Python
Use one of the many remote python libraries. Rpyc could do it. Have the code accessible from a shared drive, use module reload, and run the functions and play with the objects as if they were local. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: WEC 7 Can't BOOT on BBB using SD Card
Hi, Previously i tried BBB image with HDMI driver and not tried with Chipsee touch screen. I'll check and let you know if i found. Thanks Regards On 8 October 2014 21:19, plam.s...@gmail.com wrote: Hi I'm tring to find WinCE 6 image for Beaglebone Black that will support the Chipsee 7'' capacitive touch screen and the IO. Can you help with information. Thanks. On Sunday, June 15, 2014 4:21:32 AM UTC-5, rchrd...@gmail.com wrote: Hi, I have been using WinCe 6 / .Net Compact Framework on the Beaglebone Black and the LCD7 touchscreen with success. A couple of things you might like to look at: 1. Make sure the partition boot flag is set. 2. Always copy MLO to the partition first. 3. Check if there is any output on debug uart. 4. Contact the person who offered the port for help. There are separate BSPs for HDMI, LCD7, etc ... You need to select the correct BSP from the codeplex web site. .Net Compact Framework is supported. Touchscreen works well. Providing BSP is setup correctly UARTS work. I have found that GUI apps written in c# work very well on the Beaglebone Black with touch screen. You use VisualStudio on PC to cross-compile apps. I haven't bothered to test Activesync yet. Instead I just copy files to the SDHC card. If you are planning to do some serious application development and use the Beaglebone hadrware features you will have to look at creating you own BSP's. Otherwise you will have to get someone else to do it. Regards ... On Tuesday, June 10, 2014 5:24:55 PM UTC+10, ASWIN PP wrote: Hi friends, I have loaded a 4GB SD card with the MLO, EBOOTSD.nb0 and NK.bin that comes with the Demo package WEC7 BBB 01.05.00, Also I have formatted the card with Fat32 and 4096 byte sectors (using hp format tool), and I have used the TI SD card utility for flashing the SD card, Also I have pushed the user button before power up, But noting happens!!! In some procedure they said to format using hp format tool, copy mlo,ebootsd,nk.bin in correct order and press usr boot button and power up.. but not booting... when I power the board up the leds won't flash, , So I think it's a boot problem, How can I be sure that the MLO is in the first sector of the SD card? I have loaded angstrom img succsfuly on BeagleBone Black. I am using 4gb sd card, windows 7 and virtual machine xp. so please consider the issue and help me... Thanks Regards aswin pp -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/f_FXey_q4YM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] PRU Assembly Questiony.
All pru GPIO are accessible via a single register, so it's one tick,just like any other register (two for loading a 32 bit immediate value). Arm GPIO are never accessible in a single tick since there way outside the Pru and have to go over the OCP bus. See http://nomel.tumblr.com/post/30006622413/beaglebone-tutorial-accessing-main-memory-from-the-pru -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] BBB USB Gadget Serial
I am trying to set up a serial port emulation over USB on BBB. On my system I have ubuntu installed with an RCN kernel (tired 3.13.11 as well as 3.15.10). The g_serial module loads just fine, creates /dev/ttyG0. The problem is on the other side, when I plug in the USB cable into my linux box, lsusb does not show BBB as a serial device, in fact it doesnt show it at all. There is no device discovery notification. I've tried to boot into Windows as well, same problem - the machine does not detect the USB connection. I can power my BBB over this same cable with no issues (I do however have a separate 5v power supply connected most of the time, as I have a 7 LCD connected). Any ideas would be appreciated. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel
Andrew, It seems that the pre-built image size (8,018,460,672 bytes) is slightly larger than a 8G uSD card size (7,939,784,704 bytes Sandisk HC). I had difficulty to write the image to the SD. Win32DiskImager (under Win7) complains; Image Writer (Ubuntu 12.04) also complains. dd command does not report error. However the BBB did not boot. Unfortunately I don't have 16G uSD on hand. I am in a process creating another virtual machine so I can build from source and remove some packages. I wonder if I am on the right path and there is some easier way out. Thanks, Lei On Friday, October 10, 2014 8:47:46 AM UTC-4, Andrew Henderson wrote: Right now, I don't have any plans to flash the eMMC. BBBAndroid is currently intended to be a prototyping platform, so I'd prefer to make the entire OS easily removable in case you need to mount it on a different machine and fix any changes that you made to .rc, .dtbo, or .ko files in the rootfs file system. SGX support is planned, as soon as the 3.14/3.17 kernels move a little further along. I plan on moving all of my projects to the newer kernels once all of the features that I need are there. On Friday, October 10, 2014 12:10:18 AM UTC-4, Adam Singer wrote: Wow great job Andrew! Just ran with this image with ease. Is there anything built in that can be used to flash to eMMC? Any plans to integrate with the SGX drivers for better graphics drivers? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
