[beagleboard] Re: BeagleBoard, G540, Linux CNC
Replicape maybe? I have one that I'm about to install for 3D Printing. Using PRUS controls. All opensource as well. On Monday, October 23, 2017 at 8:44:49 PM UTC-5, mrar...@gmail.com wrote: > > > Wanting to replace my dead CNC computer with a beagleboard. I have a G540 > controller. Everyone says to connect it to the beaglebone but I see no > tutorial anywhere on pinning up a db25 connector to the board. This seems > so simple... lol. Can anyone point me in the correct direction? > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/dbb801d0-9b4e-4712-b15f-75c1bbf5e162%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] PRU
This github is great for getting started with the PRUs. Cuts right to the chase and provides examples for all the required files. Thanks Jason. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9970245b-fadc-42cf-ac8c-e31321469d61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] which program language is better for BBB
Never mind DOTE! lol... On Sun, Dec 21, 2014 at 1:18 PM, Rick Reynolds wrote: > "Two different tools for two different jobs - really. C++ is not a >> "better C" C++ is C++, and C is C." > > > I think Mr. Stroustrup would agree with that William. > > On Sun, Dec 21, 2014 at 10:26 AM, William Hermans > wrote: > >> I know the OP seems to have made his/her choice, but I had to comment on >> this one statement as it is incorrect, and "noob" eyes are watching I'm >> sure. >> >> *"Java has a large number of forward-looking concepts (e.g. decorators.) >>> C++ is "a better C" and can hit the bare metal hardware where Java cannot."* >> >> >> This statement is wrong. Two different tools for two different jobs - >> really. C++ is not a "better C" C++ is C++, and C is C. C++ has so much >> that is unique from C, and you can not have C++ with out C. Also, C in the >> strict sense is procedural, where C++ is object oriented. But as seen all >> over the web, anything can be warped to do just about - whatever. >> >> On Sun, Dec 21, 2014 at 7:40 AM, nima talebpour >> wrote: >> >>> thank you john, your answer was very helpful. I think,for the first step >>> I should try python :) . >>> >>> On Sunday, December 21, 2014 2:05:22 AM UTC+3:30, john3909 wrote: >>>> >>>> >>>> From: nima talebpour >>>> Reply-To: "beagl...@googlegroups.com" >>>> Date: Saturday, December 20, 2014 at 1:59 PM >>>> To: "beagl...@googlegroups.com" >>>> >>>> Subject: Re: [beagleboard] which program language is better for BBB >>>> >>>> 1- yes >>>> 2- no >>>> 3- yes, for example communicate with usart and so on. >>>> 4- I dont get your answer exactly >>>> 5- yes, C,C# and java. but i am amateur in java :D >>>> 6-as i told you in section 3 :D yes, Usart , control IO pins ,I2C,SPI >>>> >>>> I would say you have a few choices. Because you have C experience, I >>>> would recommend Python which is an interpreted language, but is still >>>> pretty fast and interfaces with C code when you need better performance. >>>> Python has a large library which will help speed up your development. >>>> Another choice is C++ and QT development environment which is very powerful >>>> at producing amazing GUI displays and also has everything you need to >>>> interface with your I/O. You could always stay with C and use one of the >>>> GUI libraries, but I’ll defer to others who have more experience in this >>>> area. >>>> >>>> Regards, >>>> John >>>> >>>> >>>> >>>> >>>> >>>> On Wednesday, December 17, 2014 11:14:15 PM UTC+3:30, john3909 wrote: >>>>> >>>>> >>>>> From: nima talebpour >>>>> Reply-To: "beagl...@googlegroups.com" >>>>> Date: Wednesday, December 17, 2014 at 6:02 AM >>>>> To: "beagl...@googlegroups.com" >>>>> Subject: [beagleboard] which program language is better for BBB1- >>>>> >>>>> I want to start write application for BBB. but i am confused. >>>>> which program language is better for BBB? >>>>> >>>>> Java or C++ and why? >>>>> >>>>> The obvious answer, it depends on what your application does. Answer >>>>> these and it will be easier to give you an answer: >>>>> >>>>>1. Do you have a GUI? >>>>>2. Will your app display output to a web browser? >>>>>3. Does your app interface with I/O and if so, what type? >>>>>4. What are the performance constraints? >>>>>5. Do you have any programming language experience? >>>>>6. Do you have any communication requirements? >>>>> >>>>> There are several other distinguishers, but let’s start with these and >>>>> go from there. BTW, Robert and William’s responses were hilarious. Really >>>>> made me laugh. >>>>> >>>>> Regards, >>>>> John >>>>> >>>>> >>>>> >>>>> which of these languages has a better examples and source codes ? >>>>> >>>>> thank you for guiding me. >>>>> >>>>&
Re: [beagleboard] which program language is better for BBB
> > "Two different tools for two different jobs - really. C++ is not a > "better C" C++ is C++, and C is C." I think Mr. Stroustrup would agree with that William. On Sun, Dec 21, 2014 at 10:26 AM, William Hermans wrote: > I know the OP seems to have made his/her choice, but I had to comment on > this one statement as it is incorrect, and "noob" eyes are watching I'm > sure. > > *"Java has a large number of forward-looking concepts (e.g. decorators.) >> C++ is "a better C" and can hit the bare metal hardware where Java cannot."* > > > This statement is wrong. Two different tools for two different jobs - > really. C++ is not a "better C" C++ is C++, and C is C. C++ has so much > that is unique from C, and you can not have C++ with out C. Also, C in the > strict sense is procedural, where C++ is object oriented. But as seen all > over the web, anything can be warped to do just about - whatever. > > On Sun, Dec 21, 2014 at 7:40 AM, nima talebpour wrote: > >> thank you john, your answer was very helpful. I think,for the first step >> I should try python :) . >> >> On Sunday, December 21, 2014 2:05:22 AM UTC+3:30, john3909 wrote: >>> >>> >>> From: nima talebpour >>> Reply-To: "beagl...@googlegroups.com" >>> Date: Saturday, December 20, 2014 at 1:59 PM >>> To: "beagl...@googlegroups.com" >>> >>> Subject: Re: [beagleboard] which program language is better for BBB >>> >>> 1- yes >>> 2- no >>> 3- yes, for example communicate with usart and so on. >>> 4- I dont get your answer exactly >>> 5- yes, C,C# and java. but i am amateur in java :D >>> 6-as i told you in section 3 :D yes, Usart , control IO pins ,I2C,SPI >>> >>> I would say you have a few choices. Because you have C experience, I >>> would recommend Python which is an interpreted language, but is still >>> pretty fast and interfaces with C code when you need better performance. >>> Python has a large library which will help speed up your development. >>> Another choice is C++ and QT development environment which is very powerful >>> at producing amazing GUI displays and also has everything you need to >>> interface with your I/O. You could always stay with C and use one of the >>> GUI libraries, but I’ll defer to others who have more experience in this >>> area. >>> >>> Regards, >>> John >>> >>> >>> >>> >>> >>> On Wednesday, December 17, 2014 11:14:15 PM UTC+3:30, john3909 wrote: From: nima talebpour Reply-To: "beagl...@googlegroups.com" Date: Wednesday, December 17, 2014 at 6:02 AM To: "beagl...@googlegroups.com" Subject: [beagleboard] which program language is better for BBB1- I want to start write application for BBB. but i am confused. which program language is better for BBB? Java or C++ and why? The obvious answer, it depends on what your application does. Answer these and it will be easier to give you an answer: 1. Do you have a GUI? 2. Will your app display output to a web browser? 3. Does your app interface with I/O and if so, what type? 4. What are the performance constraints? 5. Do you have any programming language experience? 6. Do you have any communication requirements? There are several other distinguishers, but let’s start with these and go from there. BTW, Robert and William’s responses were hilarious. Really made me laugh. Regards, John which of these languages has a better examples and source codes ? thank you for guiding me. -- 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...@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...@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. >> > > -- > 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/naQIshlHQEY/unsubscribe. > To unsubscribe from
Re: [beagleboard] which program language is better for BBB
What is your current level of programming experience? What laguages have you programmed in and on what platforms? -- 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] which program language is better for BBB
Nah... Just go for the COBOL. http://sourceforge.net/projects/open-cobol/ -- 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: 3.17.1-rc4 sudden reset
Just an FYI... We are currently working on a project using Rev C BBB and RCN 3.13.11-bone12 kernel. We had been experiencing random reboots. Sometimes multiple times per day and sometimes once per day, mostly at night. We determined that the reboots were only occuring when the BBB was being powered only from the 5VDC connector. We never saw a reboot when the BBB was either powered from, or just connected to, the USB OTG port. One of our engineers suggested that it might be a noise issue on the USB OTG port and the way that the TPS65217C PMIC works in the system. The way he explained it to me is that the PMIC is set up to default to the USB OTG port for power. If you leave the USB OTG port open, or floating, while powered from the 5VDC connector and then get noise on the USB OTG port then the PMIC will attempt to switch to USB OTG port and finding that there is no voltage there the system reboots. What we have done to solve the problem so far: I made a pigtail cable for the USB OTG port that simply ties the shield, ground and 5VDC together. There is no 5VDC on the USB OTG port when not connected to a host machine. Not a great final solution but it did prove the theory. With the pigtail installed we never get reboots, it's been tested on several BBBs now and is very consistent. So, reboots regularly without the pigtail and never with the pigtail installed. One other thing to note... On the schematic there are 4.7uF caps from both the USB OTG and 5VDC lines to ground. We were thinking that this could allow some relatively high frequency noise to pass to the PMIC. I don't know what the response time, that would cause a switch over, is on the PMIC. It's possible that something on the order of a .01uF - .1uF cap from the USB OTG 5VDC line to ground might also solve the problem. This has not been tested yet however. Hope this helps... On Thursday, October 30, 2014 4:50:43 AM UTC-5, Ives van der Flaas wrote: > > I'm running Robert C Nelson's latest 3.17 kernel (3.17.1-bone4) because I > need the new TI musb babble recovery code. It seems however that I'm having > some strange instability on my BBB. After somewhere between 10 and 24 > hours, the device seems to reset suddenly and without warning. There's no > kernel panic as far as I can see (no kernel.panic time-out in my sysctl > either) and nothing in the dmesg or kern log files. It suddenly resets. > > On the serial console, using my own FTDI cable, I was running "watch", and > when I returned the next day the program wasn't refreshing as it should > have been. I pressed enter and immediately a login prompt appeared. Uptime > was also way shorter than it should have been. > > Any clues on what might cause this? This seems a bit like a power supply > issue, but I've been running the same BBB for weeks using the same power > supply on a 3.8.13 kernel and that's always worked fine, while on this > kernel it can't even last a day. > > Thanks, > Ives > -- 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: Help Needed : For setting up plymouth on Beaglebone Black
Hello,
I know it's been a while since you posted this, thanks by the way. I was
able to use your instructions to get Plymouth installed and configured. :)
However, I'm getting a splash screen on shut-down but not on boot-up. I was
wondering if you'd experienced this and had a possible solution. I'm on a
BeagleBone Black running the Debian distro. I configured the splash in
uEnv.txt as you suggested.
Any help would be greatly appreciated.
Thanks,
Rick
On Sunday, April 13, 2014 9:38:02 AM UTC-5, Gunjan Gupta wrote:
>
> Hi,
>
> No reply in days, but I found the solution. Posting it for any one needing
> this information in the future.
>
> Here are the steps needed to be followed for setting up plymouth on
> beaglebone black running debian or ubuntu:
>
> Step 1) Install Plymouth-DRM.
>
> # apt-get install plymouth-drm
>
> Step 2) Select a theme for boot splash.
>
> # plymouth-set-default-theme --list # this lists
> the available themes for plymouth
>
> # plymouth-set-default-theme joy
>
> Step 3) Update initramfs
>
> # update-initramfs -u
>
> Step 4) Copy the newly created initrd.img file to /boot/uboot folder
>
> # cp /boot/initrd.img-$(uname -r) /boot/uboot/
>
> Step 5) Update the initrd file name in the /boot/uboot/uEnv.txt
>
> #initrd_file=initrd.img
> initrd_file=initrd.img-3.8.13-bone47
>
> Step 6) enable splash support by adding the following to
> /boot/uboot/uEnv.txt.
>
> # Place this at the bottom of the last line starting with optargs
>
> optargs=splash plymouth.ignore-serial-consoles ${optargs}
>
> just restart your beaglebone, and it will work.
>
> Hope this will be helpful for someone.
>
> Regards
> viraniac
>
--
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: Here is the BeagleBone Debian (beta) image you want to test
Ok, I took a little different tack. I just copied /usr/bin/xinput_calibrator from a non-customized BBB to my custom image and it works great. Thanks again for all your hard work Robert. You have taught me volumes. On Friday, May 23, 2014 6:34:54 PM UTC-5, RobertCNelson wrote: > > On Fri, May 23, 2014 at 6:03 PM, Rick Reynolds > > > wrote: > > Thanks for your help, and all your hard work, Robert. I have used your > > documentation extensively. > > > > When I execute "./autogen.sh --with-gui=x11" either directly on the > bone, > > from a an LXTerminal session, or over ssh I get the same end result. > it's > > basically the same thing I saw when trying to cross build. > > > > checking string usability... no > > checking string presence... no > > checking for string... no > > checking list usability... no > > checking list presence... no > > checking for list... no > > > > checking for stdbool.h that conforms to C99... yes > > checking for _Bool... yes > > checking for working strtod... yes > > ./configure: line 4987: syntax error near unexpected token `XINPUT,' > > ./configure: line 4987: `PKG_CHECK_MODULES(XINPUT, x11 xext xi > inputproto)' > > Install xinput > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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: Here is the BeagleBone Debian (beta) image you want to test
Hi Robert, xinput is already installed. "xinput version" is reporting "xinput version 1.6.0" and "xI version on server 2.2". Here's the output from "xinput list". debian@arm:~/Downloads/xinput_calibrator$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=8[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Logitech USB Keyboard id=6[slave keyboard (3)] ↳ Logitech USB Keyboard id=7[slave keyboard (3)] This is the output from apt-cache search xinput debian@arm:~/Downloads/xinput_calibrator$ sudo apt-cache search xinput chktex - Finds typographic errors in LaTeX curtain - handy curtain for the desktop gromit - GTK based tool to make annotations on screen libxi-dev - X11 Input extension library (development headers) libxi6 - X11 Input extension library libxi6-dbg - X11 Input extension library (debug package) lxde - LXDE metapackage lxinput - LXDE keyboard and mouse configuration lxinput-dbg - LXDE keyboard and mouse configuration (debug) spotlighter - gtk interface to make annotations on the screen whitedune - graphical VRML97/X3D viewer, editor, 3D modeller and animation tool x11proto-kb-dev - X11 XKB extension wire protocol xinput - Runtime configuration and test of XInput devices This is the output from apt-cache search inputproto x11proto-input-dev - X11 Input extension wire protocol On Friday, May 23, 2014 6:34:54 PM UTC-5, RobertCNelson wrote: > > On Fri, May 23, 2014 at 6:03 PM, Rick Reynolds > > > wrote: > > Thanks for your help, and all your hard work, Robert. I have used your > > documentation extensively. > > > > When I execute "./autogen.sh --with-gui=x11" either directly on the > bone, > > from a an LXTerminal session, or over ssh I get the same end result. > it's > > basically the same thing I saw when trying to cross build. > > > > checking string usability... no > > checking string presence... no > > checking for string... no > > checking list usability... no > > checking list presence... no > > checking for list... no > > > > checking for stdbool.h that conforms to C99... yes > > checking for _Bool... yes > > checking for working strtod... yes > > ./configure: line 4987: syntax error near unexpected token `XINPUT,' > > ./configure: line 4987: `PKG_CHECK_MODULES(XINPUT, x11 xext xi > inputproto)' > > Install xinput > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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: Here is the BeagleBone Debian (beta) image you want to test
Thanks for your help, and all your hard work, Robert. I have used your documentation extensively. When I execute "./autogen.sh --with-gui=x11" either directly on the bone, from a an LXTerminal session, or over ssh I get the same end result. it's basically the same thing I saw when trying to cross build. checking string usability... no checking string presence... no checking for string... no checking list usability... no checking list presence... no checking for list... no checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for working strtod... yes ./configure: line 4987: syntax error near unexpected token `XINPUT,' ./configure: line 4987: `PKG_CHECK_MODULES(XINPUT, x11 xext xi inputproto)' On Friday, May 23, 2014 11:37:05 AM UTC-5, RobertCNelson wrote: > > > > > On Fri, May 23, 2014 at 11:32 AM, Rick Reynolds > > > wrote: > >> Hi All, This is my first post on the group. Hope I'm in the correct >> place. Hate to sound like such a noob but, that's what I am. >> >> I am working with a Beaglebone Black revision B, 7" HDMI display and USB >> eGalax based touch screen. We are currently have 5 revision C boards on >> order. >> >> I am booting from a 2gb sd using the 3.14.4-bone4.1 kernel and >> debian-7.5-minimal-armhf-2014-05-07 rootfs. I did a cross build on a Wheezy >> VM using the info from >> http://eewiki.net/pages/viewpage.action?pageId=13599118. >> I have installed LXDE and everything is working really well. >> >> I have one small touchscreen issue however. It works correctly except >> that I cannot get the pointer to the edge of the screen. Not close enough >> to activate the panel menus and such. >> From what I've read I believe the xinput-calibrator utility would help >> solve this issue. But, I can't find the package with sudo apt-get install >> xinput-calibrator. >> >> I have downloaded the source for version 0.7.5 from freedesktop.org and >> I'm trying to cross build it. No luck so far... I know that this utility is >> installed by default on the latest Debian/LXDE images from Beagleboard.org >> but i really want to be able to configure and build all of this myself. >> > > It's easier to just build in on the bone.. (make sure libxi-dev is > installed) > > git clone https://github.com/tias/xinput_calibrator > cd xinput_calibrator > ./autogen.sh --with-gui=x11 > make > make install > make distclean > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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: Here is the BeagleBone Debian (beta) image you want to test
Hi All, This is my first post on the group. Hope I'm in the correct place. Hate to sound like such a noob but, that's what I am. I am working with a Beaglebone Black revision B, 7" HDMI display and USB eGalax based touch screen. We are currently have 5 revision C boards on order. I am booting from a 2gb sd using the 3.14.4-bone4.1 kernel and debian-7.5-minimal-armhf-2014-05-07 rootfs. I did a cross build on a Wheezy VM using the info from http://eewiki.net/pages/viewpage.action?pageId=13599118. I have installed LXDE and everything is working really well. I have one small touchscreen issue however. It works correctly except that I cannot get the pointer to the edge of the screen. Not close enough to activate the panel menus and such. >From what I've read I believe the xinput-calibrator utility would help solve this issue. But, I can't find the package with sudo apt-get install xinput-calibrator. I have downloaded the source for version 0.7.5 from freedesktop.org and I'm trying to cross build it. No luck so far... I know that this utility is installed by default on the latest Debian/LXDE images from Beagleboard.org but i really want to be able to configure and build all of this myself. What is the best method for providing the ./configure output and config.log content here? The tail of the ./configure output is below but I know it would probably be helpful to have the entire output and the config.log content. ./configure output - checking whether the /home/prism/bbb-dev/cc/linaro-03/bin/arm-linux-gnueabihf-g++ linker (/home/prism/bbb-dev/cc/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/arm-linux-gnueabihf/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for X... no checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for working strtod... no checking for pow... no checking for pow in -lm... yes ./configure: line 15509: syntax error near unexpected token `XINPUT,' ./configure: line 15509: `PKG_CHECK_MODULES(XINPUT, x11 xext xi inputproto)' prism@BBB-Dev-1:~/bbb-dev/cc/xinput-calibrator/xinput_calibrator-0.7.5$ ^C prism@BBB-Dev-1:~/bbb-dev/cc/xinput-calibrator/xinput_calibrator-0.7.5$ Any help is greatly appreciated. On Wednesday, March 5, 2014 4:51:19 PM UTC-6, Jason Kridner wrote: > > The latest BeagleBone Debian images are now posted at: > http://beagleboard.org/latest-images/ > > If you've upgraded the firmware on your BeagleBone or BeagleBone Black in > the past, the experience will be quite similar, but you might find the eMMC > flashing times a bit faster (~15 minutes rather than ~45 minutes) due to > less post-installation processing. Using the 2GB uSD card image also > flashes a bit faster and can be resized to whatever your uSD card size is > using some scripts under /opt/scripts/tools. > > Many, many thanks to Robert Nelson, Rob Rittman, Dave Anders, Cody Lacey, > the Cloud9 IDE team and so many others in getting us this far. > > Please take the time to give a detailed look over this image and report > any issues to the bug tracker on elinux.org: > http://bugs.elinux.org/projects/debian-image-releases > > While plugged in over USB, you'll see the familiar BEAGLE_BONE drive with > START.htm to tell you how to get the drivers configured if you haven't > already done so: > > [image: Inline image 2] > > > Clicking the link or visiting http://192.168.7.2, you'll see the familiar > on-board served documentation: > > [image: Inline image 1] > > I've introduced a few bugs to the documentation ( > http://github.com/beaglebone/bone101 and > http://beagleboard.github.io/bone101), so expect to find a lot of issues > there. Patches are welcome as are notes in the bug tracker to make sure I > don't miss dotting any i's or crossing any t's. This is your chance to try > to get some documentation into the system you'd like to see. I felt it was > pretty safe to save the documentation as an in-beta item because it > shouldn't impact functionality. > > One of the biggest new features you'll see is when you click on the Cloud9 > IDE link: > > [image: Inline image 3] > > This is a pre-open-source-beta-only release of version 3 of their IDE. > Down at the bottom of the Cloud9 IDE you'll see a new terminal window that > runs a full 'tmux' session. You can open up a bunch of these and it makes > logging into the board and executing command-line operations *super* simple. > > Cloud9 IDE version 3 now includes support for Python and the Adafruit_BBIO > library is included in these Debian images. That means you can simply paste > in your Python code and hit the "run" button, without any additional > download. I checked this out myself by doing a quick LED blink using the > Adafruit
