Great - thanks! So there is no way to do that programmatically via PMIC?
2016-12-29 8:59 GMT+01:00 Alex Hayman :
> If you cut that trace on a BBB, then the BBB won't power itself up via USB.
>
> On Friday, December 23, 2016 at 4:25:08 AM UTC-5, Heinz Hummel wrote:
>>
>>
dtb_overlay=/lib/firmware/BB-SPIDEV0-00A0.dtbo
*Seems* to work fine as well. I've no reason to think it doesn't work, but
I have not tested the SPI transmission with spidev_test, or a logic
analyzer *YET*. The overlay does seem to load the drivers fine
loading
Ok so here is the quick skinny( untested ) to setup spidev on kernel 4.x.
By untested, I mean I have not actually tested the signal generated, or
received by the device. I was reading however, there is a "spidev_test" bit
of code you can use to test send / receive by shorting MISO to MOSI( I'm
So, if you think "ah this is confusing . . ." it does get worse.
The new future way( I suspect) to load overlays at boot will likely be
through uboot. Robert has recently added this functionality into uboot,
I've tested it, and it does seem to work great. But I think this is for
4.1.x kernels and
I'd probably try to run your executable through strace, and output into a
file.
On Sun, Jan 1, 2017 at 1:25 PM, John Franey wrote:
> I have hdmi audio working up until 10 minutes from boot time. Exactly 10
> minutes.every boot.
>
> I test with 'speaker-test'. Running
I meant to say I've not used SPI on any embedded Linux platform. I do have
plenty of experience with SPI on bare metal MCU's.
On Sun, Jan 1, 2017 at 3:35 PM, Greg wrote:
> Nice! I will add this as a reference to my project documentation.
>
> Regarding the fact that you
On Sun, Jan 1, 2017 at 2:08 PM, Greg wrote:
> Hi William, if you could point to an easily discoverable source which says
> that Universal IO is available in the latest images and encouraged to be
> used, then you could be correct.
> Being able to successfully manipulate
Nice! I will add this as a reference to my project documentation.
Regarding the fact that you have to run config-pin after each boot, you can
add a section that the config-pin commands can be added
to whatever start-up configuration is most appropriate.
The way I am doing this currently is to
Ok, here's the first
draft:
https://github.com/claytongulick/beagle_bone_black_spi/blob/master/README.md
Corrections and additions are welcome!
On Sunday, January 1, 2017 at 8:43:41 AM UTC-6, Greg wrote:
>
> Hi Clayton, what you have written is correct and the Device Tree is a
> significant
That's a great idea Greg, I'll do that, thanks!
On Sun, Jan 1, 2017 at 8:43 AM, Greg wrote:
> Hi Clayton, what you have written is correct and the Device Tree is a
> significant barrier to entry.
> The Universal IO is a good solution to this, and I've had good luck with
Hi William, if you could point to an easily discoverable source which says
that Universal IO is available in the latest images and encouraged to be
used, then you could be correct.
Being able to successfully manipulate the SOC multiplexer is fundamental to
getting a Beagleboard project off the
Do you have a serial debug cable ?
I have seen posts here saying that some messages only get spit out on
that port.
On 1/1/2017 1:25 PM, John Franey wrote:
> I have hdmi audio working up until 10 minutes from boot time. Exactly
> 10 minutes.every boot.
>
> I test with 'speaker-test'.
I have hdmi audio working up until 10 minutes from boot time. Exactly 10
minutes.every boot.
I test with 'speaker-test'. Running continuously. Output stops exactly at
TimeBoot + 10mins.
There is no outward appearance of a problem:
1) The output of speaker-test is not affected.
By the way, for me the key to understanding device tree was not to read any
of the garbage on the internet about it. But to actually go into several
device tree files, then learning about each subsystem used. Experimenting,
and all that. Plus I still don't know everything, but do know enough to at
Just to be clear . . . The Hadron collider in Genva is the biggest
engineering "feat" in the world . . .Involving over 10,000 scientists from
over 100 countries, and I'm not sure how many engineers.
Passed that, it's not surprising the Beaglebone works at all. For instance,
you do realize that
Hi Clayton, what you have written is correct and the Device Tree is a
significant barrier to entry.
The Universal IO is a good solution to this, and I've had good luck with it
while keeping in mind my requirements to manipulate the Device Tree have
been minimal.
The Beagleboard is driven by
16 matches
Mail list logo