On Sun, Jan 15, 2017 at 2:31 AM, TJF wrote:
> Yes, QEP is ready. I also found a workarround for the PWM issue, so my
> development version fully works on 4.x kernels. But I still couldn't find a
> block of time to finish the documentation, yet.
Have you tried it on the
Hi All
I am trying to edit and save the /etc/network/interfaces file on beaglebone
black board, the message i am getting while saving as" readonly", even
though i am a root user.
How to change the readonly to readwrite.
Thanks & regards,
Madhu
--
For more options, visit
Hi John!
Am Sonntag, 29. Januar 2017 03:58:21 UTC+1 schrieb john3909:
>
> The IIO driver is faster and can achieve higher sampling rates.
>
The sampling rate limitation is the FiFo buffer in the TSC_ADC_SS. Both
drivers can operate at full speed. iio puts more load on the ARM CPU.
> Also the
Yeah stop using those ratty cables you get from hot cellphones. Man up and
pay the "big bucks" at Walmart.
Kidding. lol.
On Friday, July 1, 2016 at 10:59:44 AM UTC-7, Bryan Wilcutt wrote:
>
> I have a somewhat custom BB distro I've made and all is well except one
> thing I've noticed that is
And yes I agree I really cringe at device trees, they are just so damn hard
to debug, I don't know any tools that can help us debug it.
On Saturday, January 28, 2017 at 7:03:29 PM UTC-8, Ashwini Bhat wrote:
>
> Ok, I am going to try the IOT image, this is the link:
>
Ok, I am going to try the IOT image, this is the link:
http://beagleboard.org/latest-images and I am choosing the one under
alternate debian images.
debian@beaglebone:~$ uname -ar
Linux beaglebone 4.4.36-ti-r72 #1 SMP Wed Dec 7 22:29:53 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:~$
OK, best way (and this really is an IoT question if you look at it) is to
look at the most efficient (ie. fastest, least labor intensive) way of
doing it. BBB's are small, so please don't try to install an SMTP server
and stuff on it when you can do this.
The mutt and the HTTP API approach are
> On Jan 27, 2017, at 4:43 PM, Renzo Fabián wrote:
>
> john3909,
>
> there's no reason to use the PRUs. I only need read 6 analog inputs in
> real-time. I thought the only way would be using the PRUs. And the best way
> by means of lbpruio.
Well, it all depends on what
OK, I just got my BBB so I gotta talk a bit out of my butt (having not done
this yet myself).
What you need to do is get it "interrupt driven". However you do it.
I'm thinking there is a GPIO pin that has this capability (and
realistically accessible via the OS in whatever dev environment you
I thought I'd also put this in too. Once you know how, the process to get
your tethered BBB running is slick and fast even for the beginner.
Don't read this if you are running the BBB with an HDMI monitor and
keyboard. However if you are old waterfall guy like me and like your UN*X
host with
I had a problem with my core drivers for the host not installing (so you
can teather the BBB to a desktop via USB to miniUSB on the BBB). It just
came up with red X's every time.
There are a lot of "fixes" out there that are pretty flakey so I thought
I'd post the most linear path I found.
Is there an acceptable, easy way of setting up a BBBW as a wifi hot spot
using its built-in wifi? By easy I mean like an installation type process
rather than a laborious build and make process? All I want to do is serve
web pages to wifi tablets at short ranges.
Just how good is the wifi in
Ok, experimented with it some more and came up with a basic protocol for
getting it to boot. What you do is you kind of fiddle with the power button
and keep plugging and unplugging the USB cable (I'm powering my BBB through
the miniusb to my Windows 10 desktop).
What you do is you ground
I've worked on a lot of boards over the years, so I have a strong sense for
the kinesthetic issues that even custom electronics can have. I've had this
problem myself (and am still having it from time to time).
My spider sense tells me that the BBB is right at the accepted maximum
current draw
There is kind of an involved way in C that is how it is done (similar to
how Apache runs as a long-running daemon).
What you do is you fork() with the parameters set up such that it invokes a
daughter shell process that survives after the parent process is
terminated. The reason why the
Love Python, however I am a dyed-in-the-wool GCC C/C++ programmer for
decades.My question has to do with GCC.
OK, I realized that I needed to configure the BBB R3 so that its P8 and P9
pins were set for UART (got that far myself). I kind of took an overkill
approach.
What I did was I copied
Hello All,
I am using eclipse Luna to perform cross compilation of C++ project for
beaglebone black target.
for the same I am using g++-4.9-arm-linux-gnueabihf.
I am trying to use C++ 11 std::thread and have linker flag to be -pthread.
But the linker is giving me below issues:
Building
I successfully update to the new kernel, it was version 45, not 44 so even
a little bit newer.
After updating the DT with the pru include, I rebooted. No ethernet!
Also, I can tell from the LEDs that something is very wrong.
The heartbeat is there, but one of the other LEDs is blinking steadily
Am Samstag, 28. Januar 2017 01:38:31 UTC+1 schrieb Renzo Fabián:
>
> TJF,
>
> so I only need a C-code file like io_inputs.c (from libpruio examples)?
>
Yes, just C code for the ARM. But io_inputs.c operates in IO mode (no
accurate timing). Better use MM (measurement) or RB (ring buffer) mode.
19 matches
Mail list logo