On Friday, March 23, 2018 at 9:54:19 PM UTC-4, l...@temple.edu wrote:
>
> *I had a 4.9.78-ti-r94 kernel, and I used the update_kernel script to
> update the kernel to* *4.9.89-bone10. However, when I run "run_test_motor
> -f", I still get an error as:*
>
> ERROR: pru-rproc driver missing
>
>
>
On Wed, Apr 11, 2018 at 5:18 PM, Bobbi N Sean Donovan
wrote:
> Robert, thank you so much for the reply. I followed your link below on the
> doc on how to fix the image and I get the following error +Failed dependency
> check. I am trying to do this to the SDCard that the
On Sunday, April 8, 2018 at 1:03:57 PM UTC-4, RobertCNelson wrote:
> Ah, you found a fun bug in the old path.. I'll fix it up for the next
> person, but you can go down the new path with your setup...
>
> [snip...]
>
> in /boot/uEnv.txt
>
> remove your: dtb=am335x-boneblack-emmc-overlay.dtb
Hello all,
I trying patch file *am335x-boneblack.dts*
(http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-lsk-linux-4.4.y/arch/arm/boot/dts/am335x-boneblack.dts)
in yocto in order to using *pru* on my BBB. However I can't see any change
in
Robert, thank you so much for the reply. I followed your link below on the
doc on how to fix the image and I get the following error *+Failed
dependency check*. I am trying to do this to the SDCard that the BBB
booted from.
Any further suggestions?
Here is a copy of the Putty Dump
> On Apr 11, 2018, at 6:04 AM, pierrick.ra...@gadz.org wrote:
>
> Hi John,
> Thanks for the help, I looked into the iio_generic_buffer.c example and i
> patched it to disable the hardware triggers thanks to the patch presented on
> this page :
The sysfs gpio ABI will be removed from the Linux kernel in 2020. The new
ABI uses a character device to represent each gpiochip.
libgpiod started by Bartosz Golaszewski is a good way for userspace code to
use the the new ABI:
https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/about/
Hi, I've started looking at the sysfs gpio interface and saw some notes
that it's considered obsolete and deprecated. I'm looking for a good
pointer to the ABI (?) character driver interface for gpio. I'll probably
find one right after posting this. :)
In case I'm not using the right
> On Apr 11, 2018, at 6:04 AM, pierrick.ra...@gadz.org wrote:
>
> Hi John,
> Thanks for the help, I looked into the iio_generic_buffer.c example and i
> patched it to disable the hardware triggers thanks to the patch presented on
> this page :
On Wed, Apr 11, 2018 at 1:41 PM, wrote:
> I am trying to rollback the Debian image on my Beaglebone Black Rev C
> (Embest) from the image that shipped on it on the board Debian 8.3 Image
> 2016-01-24 kernel 4.1.15-ti-rt-43 to Debian 7.8 image 2015-03-01 kernel
>
I am trying to rollback the Debian image on my Beaglebone Black Rev C
(Embest) from the image that shipped on it on the board* Debian 8.3 Image
2016-01-24 kernel 4.1.15-ti-rt-43* to *Debian 7.8 image 2015-03-01 kernel
3.8.13-bone70* . I downloaded both files from
Hi
I Want to build android (6 or 7) for BBB wireless board.bo
can somebody suggest me from where to download source and build
instructions for BBB wireless board
regards
amit
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed
Hi
i want to build android (6 or 7) for Beagleboard black wireless board .
can somebody guide me from where to download AOSP source for this board
and the build steps .
i asked this because of below 2 reasons ::
a) On beagleboard website , it is mentioned 3rd party support for
I would like to test a concept with the Beaglebone Black configured with
the PREEMPT-RT patch.
An application would use the native Ethernet port and an USB-Ethernet
adapter to roundtrip transactions in an Ethernet based protocol. My goal is
to develop ou use a test application to imply the
Thanks for the info. That explains a lot. However, I see in the system
reference manual for the pocket there are eight pr1_pru1_pru_r31_xxx pins.
Any idea why only 4 were working in my test? Sounds like PRU1 should be
able to see 8.
All,
BeagleLogic, the software, will run on the PocketBeagle for sure, but the
pins will be limited as only a very limited number of PRU1 pins (the pins
marked pr1_pru_r31_xx) are broken out on the expansion headers. The way
BeagleLogic works is that PRU1 samples the pins while PRU0 writes
Ok, I finally did the following:
->ran a stock console image, 2018-02-01 on my BB-X15,
->copied the above referenced auto-mount scripts to that image on SD card.
->Converted that SD card image containing the mount point scripts to a
flasher image to flash the eMMC,
->inserted a blank SD card
Ok, I finally did the following:
->ran a stock console image, 2018-02-01 on my BB-X15,
->copied the above referenced auto-mount scripts to that image on SD card.
->Converted that SD card image containing the mount point scripts to a
flasher image to flash the eMMC,
->inserted a blank SD card
thanks Robert, I'll try this 1-bit mode
about the PRU now it's working. I change to kernel 4.9.88-ti-r108 and then
apt-get upgrade
I recommend this updated guide to understand PRU
https://gist.github.com/jonlidgard/1d9e0e92b4f219f3f40edfed260b851e
regards,
Sebastián
On Wednesday, April 4,
Hi John,
Thanks for the help, I looked into the iio_generic_buffer.c example and i
patched it to disable the hardware triggers thanks to the patch presented
on this page : https://www.teachmemicro.com/beaglebone-black-adc/ I am now
able to reader a buffer from the different channel.
However I
20 matches
Mail list logo