Hi Everyone. I'm trying to get the SPI devices working in the 4.1 kernel,
but I don't really want to use the cape manager / overlays. I don't see
any dtsi files for the SPI devices in the 4.1 source. The
am335x-bone-spi0-spidev.dtsi and am335x-bone-spi1-spidev.dtsi are missing.
I had
It seems that the file include/linux/of.h gets modified during the kernel
configuration process. If after configuring the kernel I change the
problem functions to be static inline, the 4.1 kernel builds fine for the
am335x.
$(SED) 's/int of_changeset_add_property_copy(/static inline
Hi,
I attempted to upgrade from the kernel from 3.14 to 4.1 today. I'm getting
some compilation issues which seem to be caused by certain dynamically
generated function definitions not being declared static inline in
include/linux/of.h. If I hand edit this file and add a static inline in
/mmcblkX not /dev/mmcX, anyway ls -l /sys/bus/mmc/devices
works fine n this end, I'd say you have a problem. Exactly what ? No idea .
. .
On Sat, Jan 10, 2015 at 9:44 PM, Dallas Clement dallas.a...@gmail.com
javascript: wrote:
Could someone at least confirm that I should be able to see device
. . .except now I can not remember what
. . .heh
On Sun, Jan 11, 2015 at 9:13 AM, Dallas Clement dallas.a...@gmail.com
javascript: wrote:
Thanks for confirming William. Yeah it was working on 3.14 for me also.
I had too many other problems with 3.14 (mainly SPI devices) and had to
revert
Could someone at least confirm that I should be able to see device files
/dev/mmc0* and /dev/mmc1* for both the eMMC and an SD card assuming both
are present? It seems like the 3.8 kernel is playing hanky panky with
these mmc devices.
On Wednesday, January 7, 2015 at 3:01:58 PM UTC-6, Dallas
I've got a beagle bone black which is booting a self built 3.8 kernel over
TFTP / NFS. The kernel source is from
(https://github.com/beagleboard/linux.git). For some reason, I am not able
to see a mmc block device assigned. The cape manager sees it and assigns
it to a slot. But ls -l
Hi,
I recently upgraded from the 3.8 kernel to 3.14 and have been experiencing
difficulty with reading from the SPI. I seem to always read back zero's
with a test program that was previously working on 3.8. I have tried
switching the pin mux sclk from an input to an output. Doesn't seem to
Hey Robert, I know this thread is getting long in the tooth. Originally I
had asked for help on enabling the SPI devices on the 3.14 kernel. You got
me past that with some patches. However, I just did a merge from the
latest upstream and now my SPI devices are not enabled any more when I boot
I got it figured out. The SPI dev include dtsi were commented out after my
merge. I guess the default state is SPI devices disabled.
On Sun, Oct 5, 2014 at 1:27 PM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Hey Robert, I know this thread is getting long in the tooth. Originally I
had
Wow! Thanks for the quick response. Will give it a shot.
On Wed, Aug 27, 2014 at 9:50 AM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement
dallas.a.clem
you can
think of that I should check?
Thanks,
Dallas
On Wed, Aug 27, 2014 at 10:07 AM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Wow! Thanks for the quick response. Will give it a shot.
On Wed, Aug 27, 2014 at 9:50 AM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26
I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb
On Wed, Aug 27, 2014 at 9:33 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Wed, Aug 27, 2014 at 9:23 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement
dallas.a.clem
You're my hero! :) Working like a champ now! Thanks a million.
On Wed, Aug 27, 2014 at 9:42 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
I just pasted my am335x-boneblack.dts to http://pastebin.com
Hi All,
I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone
black. I understand that the capemgr support is no longer there. I need
some tips on how to enable these devices in the kernel. I don't care if it
is done statically at kernel build time. My application has
Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
Hi All,
I am trying to enable both SPI devices in the 3.14 kernel for a
beaglebone
black. I understand that the capemgr support is no longer there. I
need
some
Hi All,
I would like to be able to reliably build my own images for u-boot, the
kernel, and the Angstrom rootfs. I have followed this guide in using Yocto
/ OE to do so, but no joy.
http://wp.angstrom-distribution.org/?page_id=53
It looks like this stuff is not fully baked for the bbb.
I found another related topic in this discussion group which helped me get
past this.
http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FKhBhvyBVOXQ%2Fdiscussion
I was able to build Angstrom just fine following these instructions.
On Fri, Aug 1, 2014 at 9:19 AM, Dallas Clement
Thanks John. Do you by chance know how to build a flashing image for the
bbb?
On Fri, Aug 1, 2014 at 2:02 PM, John Syn john3...@gmail.com wrote:
From: Dallas Clement dallas.a.clem...@gmail.com
Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com
Date: Friday, August 1, 2014
I noticed that there is no device tree image (dtb) file in my deploy
directory after the build completes. What do I need to do to get one?
On Fri, Aug 1, 2014 at 3:05 PM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Thanks John. Do you by chance know how to build a flashing image
:02)
C
Is the next step to send a MLO?
On Tue, Jul 22, 2014 at 5:33 PM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Thanks Steve. That was my understanding as well. I'll give that a shot.
On Tue, Jul 22, 2014 at 4:20 PM, Steve txkip...@gmail.com wrote:
For UART or USB you do
at 7:26 AM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Hi Steve, It looks like the u-boot-spl.bin is working. This is what I'm
seeing on my minicom console:
Welcome to minicom 2.6.1
OPTIONS: I18n
Compiled on Feb 11 2012, 18:12:55.
Port /dev/ttyUSB0
Press CTRL-A Z for help
I was able to send the MLO file via minicom / x-modem just fine to the
board. However after the transfer completed, nothing happened. Should I
expect to see any output on the serial console afterward?
On Mon, Jul 21, 2014 at 10:14 AM, Dallas Clement dallas.a.clem...@gmail.com
wrote:
Okay
file is only used for Memory Booting (SD/Card, eMMC) while the
u-boot-spl.bin file is used for Peripheral Booting (UART, USB).
Steve K.
On Tuesday, July 22, 2014 7:55:51 AM UTC-5, Dallas Clement wrote:
I was able to send the MLO file via minicom / x-modem just fine to the
board. However
has 8 bytes head
, the first 4 bytes is dest and the second 4 bytes is length .
This is for boot from NAND /eMMC , and when download from serial . the
boot rom will download to fixed address and limit length .
2014-07-21 12:04 GMT+08:00 John Syn john3...@gmail.com:
From: Dallas Clement
Hi,
I am trying to boot my BBB over a serial connection, and need a little
help. I have followed the instructions for UART recovery listed
here http://elinux.org/BeagleBoardRecovery
I built the pserial tool and an x-loan.bin, but when I try to load it, I
just getting hanging.
$ sudo
ckermit - serial and network communications package
Second link package mentioned is available, so looks to be possible.
On Sun, Jul 20, 2014 at 7:44 AM, Dallas Clement dallas.a...@gmail.com
javascript: wrote:
Hi,
I am trying to boot my BBB over a serial connection, and need a little
help
that my pserial command does
work with a BBB and the BBB ROM code does respond with its ASIC ID and does
in fact download the x-load.bin. It looks like I just need to figure out
what the correct boot switch power on sequence is now.
On Sunday, July 20, 2014 10:36:45 AM UTC-5, Dallas Clement
28 matches
Mail list logo
