Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

hmmm . . . https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-armv7l.tar.xz On Fri, Dec 4, 2015 at 3:24 PM, Robert Nelson wrote: > > > On Fri, Dec 4, 2015 at 4:21 PM, William Hermans wrote: > >> *Wheezy users, sorry gcc is just too old, you'll be

Re: [beagleboard] UART FIFO Size & CTS Threshold

Thanks Robert. 64 for the FIFO is what I suspected but couldn't see the CTS threshold. Was that 48? Also these look pretty hard coded into the kernel. Anyone know a way of setting these after a compilation or how to compile in with other values? Lee -- For more options, visit

Re: [beagleboard] Call a C program from PHP

A left-field option would be to communicate with a script running with full privileges via a couple of user-space files. This way you'd have: 1) A script run at startup, which looks for certain values in a couple of user-space files - possibly files within your server folder. The script then

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

4.x is the new LTS version whilst 5.x is "stable". I would stick with 4.x and it is a HUGE improvement over the older versions as they have now merged with iojs which kept up to date with V8 improvements. Lee On Thursday, December 10, 2015 at 6:26:15 PM UTC, William Hermans wrote: > > Scratch

[beagleboard] UART FIFO Size & CTS Threshold

Hi all, Been looking through the kernel source for 4.1 with Debian 8.1 and trying to work out some of the things on the UARTs, but I can't seem to find the code! - What is the FIFO UART buffer size and is it configurable? - What is the FIFO trigger size for the CTS line to assert and is

Re: [beagleboard] UART FIFO Size & CTS Threshold

On Thu, Dec 10, 2015 at 12:56 PM, Lee Armstrong wrote: > Hi all, > > Been looking through the kernel source for 4.1 with Debian 8.1 and trying to > work out some of the things on the UARTs, but I can't seem to find the code! > > What is the FIFO UART buffer size and is it

[beagleboard] Re: external RTC chip recommandation?

On Wednesday, December 9, 2015 at 10:39:49 PM UTC-8, c2h2 wrote: > > Hi all, > > onboard RTC draws too much current, > > onboard RTC? What board are you using? I'm familiar with the BBB not having any onboard RTC. > need to have low current RTC chip, no need to be super accurate, low cost

[beagleboard] Re: Compilation fails with dtsi file not found.

Hi Guys, unfortunately i am also not able to find this file am335x-boneblack-1ghz.dtsi could you provide me with the exact location. Thank you Attila On Monday, July 27, 2015 at 4:31:34 AM UTC+2, DeKay wrote: > > Hi > > I am trying to compile the 4.1 kernel as per this eewiki link >

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

On Thu, Dec 10, 2015 at 1:29 PM, Moon Walker wrote: > Hi Guys, > > unfortunately i am also not able to find this file > am335x-boneblack-1ghz.dtsi > > could you provide me with the exact location. If you need that file to override your clock frequency, then your git

[beagleboard] Re: Compilation fails with dtsi file not found.

Hi Robert, thank you for your prompt reply. I am in your dtb-rebuilder repo and trying to use the 1wire driver since monday unsuccessfully. I am so disappointed now since with arduino it succed in an hour... Thx Attila On Monday, July 27, 2015 at 4:31:34 AM UTC+2, DeKay wrote: > > Hi > > I am

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Can't install 4.2 on an x86 / x86-64 system through APT. It pulls in 5.2.x, as does the crappy Nodejs wiki script. This takes me back to the 90's again, when many things( Linux ) failed on installation, and it's really starting to aggravate me. The packages I'm having issues with is phantom.js,

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

I asked a question and pointed my frustration wit linux! You are the one not constructive!! But do not worry man! I went to the previous debian image and made it in half an hour. Thank you for your nothing. On 10 Dec 2015 22:03, "William Hermans" wrote: > *I am so disappointed

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

On Thu, Dec 10, 2015 at 2:36 PM, William Hermans wrote: > I'm probably going to stick with 0.10.41 No luck with 4.2.x? Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Giving this https://github.com/mark-webster/node-debian a shot. Sure beats having to find a good method for building manually. Seems to be working great so far for v4.2.3 On Thu, Dec 10, 2015 at 2:10 PM, William Hermans wrote: > Actually, APT attempts to pull in 0.10.33 I

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

Wah ? On Thu, Dec 10, 2015 at 2:14 PM, moonwalker wrote: > I asked a question and pointed my frustration wit linux! You are the one > not constructive!! > But do not worry man! I went to the previous debian image and made it in > half an hour. > Thank you for your

Re: [beagleboard] Re: external RTC chip recommandation?

> > *onboard RTC? What board are you using? I'm familiar with the BBB not > having any onboard RTC.* > It's actually on die, and it's pretty much useless, as there is no way to battery back it. On Thu, Dec 10, 2015 at 11:20 AM, R Miloh wrote: > > > On Wednesday, December

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Actually, APT attempts to pull in 0.10.33 I think the install output was saying. Either way, it was not working correctly. On Thu, Dec 10, 2015 at 1:57 PM, William Hermans wrote: > Can't install 4.2 on an x86 / x86-64 system through APT. It pulls in > 5.2.x, as does the

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

> > > > *I asked a question and pointed my frustration wit linux! You are the one > not constructive!! But do not worry man! I went to the previous debian > image and made it in half an hour. Thank you for your nothing. * > So, you asked a question, you got an answer, after which you felt

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

I'm probably going to stick with 0.10.41 On Thu, Dec 10, 2015 at 11:57 AM, Lee Armstrong wrote: > 4.x is the new LTS version whilst 5.x is "stable". I would stick with 4.x > and it is a HUGE improvement over the older versions as they have now > merged with iojs which kept

Re: [beagleboard] Re: Compilation fails with dtsi file not found.

> > *I am so disappointed now since with arduino it succed in an hour...* > So use your Arduino . . . unless you have something actually constructive to say. On Thu, Dec 10, 2015 at 1:06 PM, Moon Walker wrote: > Hi Robert, > > thank you for your prompt reply. > I am in

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Well, phantom.js installed fine with node v4.2.3. That build script is awesome, reminds me of your scripts Robert ;) Only 57 lines of code too . . . On Thu, Dec 10, 2015 at 3:13 PM, William Hermans wrote: > Giving this https://github.com/mark-webster/node-debian a shot. Sure

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Robert, I'm considering setting this up and testing. Currently working on an x86-64 Nodejs server, when I ran into that. Taking notes for setup so should be pretty much a copy paste experience for the BBB. On Thu, Dec 10, 2015 at 10:42 AM, William Hermans wrote: > hmmm . . .

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

> > *For workshops and my cape tester setup, I've been trying to get a* > * BeagleBone Black setup as a BBBlfs host and use udev rules to trigger* > * flashing when a BeagleBone is attached. Just as I was starting to test* > * it, I walked up with a big static charge and zapped my cape tester* > *

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

Scratch that. This version does not seem to work well with the packages I intend on using. On Thu, Dec 10, 2015 at 10:44 AM, William Hermans wrote: > Robert, > > I'm considering setting this up and testing. Currently working on an > x86-64 Nodejs server, when I ran into that.

Re: [beagleboard] X15 starting price

http://elinux.org/Beagleboard:BeagleBoard-X15 Gerald On Thu, Dec 10, 2015 at 8:40 PM, wrote: > Is there an estimated starting price on the new X15 boards? > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you

Re: [beagleboard] Re: X11VNC fighting me tooth and nail. Would really appreciate some help.

On 12/07/2015 10:36 AM, Bill Dussault wrote: > How do I get into the logfile? I did not know about that > Thanks Run x11vnc on thet beaglebone without the '-bg' argument. You probably also need to run it as sudo, if you are using the '-auth' argument. I'm confused about your more recent email.

[beagleboard] X15 starting price

Is there an estimated starting price on the new X15 boards? -- 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

[beagleboard] Re: external RTC chip recommandation?

The DS1302 are DS1307 most common, reasonably low cost. Adafruit has breakout boards and drivers for the DS1307, so you could use that as a reference design. Both are I2C bus devices, independently powered from the bus. Run for years from a little watch battery. Old Dallas Semiconductor parts,

[beagleboard] when give -qt-xcb parameter to Qt 5.5.1 ./configure doesn't work

I am trying to build Qt 5.5.1 on my host machine Ubuntu 14.04 to cross-compile for my BeagleBone Black running Debian Wheezy, I am not sure what steps are needed before I give -qt-xcb to ./configure. I read this http://doc.qt.io/qt-5/linux-requirements.html and it tells that some packages are

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

As Robert mentioned, I've also been using the BBBlfs project, which provides a USB-based bootloader, to load a kernel plus userspace where the eMMC looks like a USB flash drive. Usability across operating systems have kept us from pushing BBBlfs out as the default for end users where usability and