to test what you want use a device overlay first.
then you can adapt the overlay to be loaded at boot time
On 8/30/2016 7:24 AM, 'El Smiedro' via BeagleBoard wrote:
>
> Hello everyone,
>
> currently I am using a BBB with debian 3.8.13 and I would like to
> change the dtb file to get some
Hello everyone,
currently I am using a BBB with debian 3.8.13 and I would like to change
the dtb file to get some GPIO-pins with pulldown by default. I searched
many sites, but I think many information are not up to date (read something
about the device tree is not used anymore?!). Is
Well, it looks like I'm off by 2 years. Please welcome the class for 2016.
--Mark
On Tuesday, August 30, 2016 at 9:57:14 AM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching
> an Embedded Linux class based on the BeagleBone Black [1]. I'm
The purpose of this posting is to announce that I'm once again teaching
an Embedded Linux class based on the BeagleBone Black [1]. I'm
teaching as open-source as I can and have have posted many of course
materials on eLinux.org [2] and github[3].
I'm always open to ideas on what topics to
Hi,
Is there any Sub Ghz cape for beaglebone/board?
references for Sub Ghz devices from TI and NXP
: http://www.ti.com/lsds/ti/wireless_connectivity/sub-1_ghz/overview.page
What is the status of drivers/iio/pulse/tiecap.c?
I found some references to it from 2014, e.g., this one
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-February/230125.html
but do not know what has happened with it/why it has not made it into
the kernel.
Cheers
Christoph
--
For
Hi Bill. I want to do this too. I checked your sourceforge rep and could
not find your OV7670 interface.
maybe we can collaborate. contact me thru www.baremetal.tech
later...dd
On Thursday, June 11, 2015 at 10:53:11 PM UTC+3, Bill M wrote:
>
> William, Charles, and Karl,
Hi Ventura. I am debugging a bare metal MMU and I am having much trouble
with
mapping the memory sections (DDR, OCMC, Dev) and cache.
Actually I don't know where the problem is. It just hangs when I enable
IRQ.
Can you tell me exactly how you solved your DDR3 timing problem?
Forgot to copy kernel messages for 4.1 kernel
[ 4531.561953] mmcqd/1: page allocation failure: order:3, mode:0x204020
[ 4531.561989] CPU: 0 PID: 607 Comm: mmcqd/1 Not tainted 4.1.18-005-ts-armv7l
#2
[ 4531.562001] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 4531.562063] []