Hi,
I'm having an issue with a SPI device that works with Kernel 3.8. but not
with the 4.4.x series. I have also tried the latest one 4.4.41-ti-r82.
The device exists in both cases and I cannot think of a reason.
Can you give me a hint what I might try to debug it?
I tried the SPI loopback test
If you load overlays that are already included in your image, then you do
not have to update the initramfs. But if you create your own custom
overlay, it will not be included in the initramfs.
On Thu, Dec 15, 2016 at 4:10 PM, Phil wrote:
> Thanks for the info. I am not so
Thanks for the info. I am not so sure about the need to update initramfs
though. Just for yuks, I specified my custom overlay in uEnv.txt, and it
seems to have loaded properly, which I confirmed by inspecting the output
of dmesg. I am still verifying that my SPI ports work as expected (phase
On Thu, Dec 15, 2016 at 12:36 PM, Phil wrote:
> On Thursday, December 15, 2016 at 11:20:13 AM UTC-6, Phil wrote:
>
I have written a device tree overlay that incorporates SPI0, SPI1 and the
> PRUSS, and where SPI1 uses a GPIO for a 2nd chip select. Can I load this in
> the
On Thursday, December 15, 2016 at 11:20:13 AM UTC-6, Phil wrote:
>
> I am having almost the identical issue with SPI as pbft, except that I am
> running BBB's with *4.4.19-bone-rt-r13* and *4.4.38-bone-rt-r14*. I
> assume these can be fixed as per your suggestion, but it appears that the
>
I am having almost the identical issue with SPI as pbft, except that I am
running BBB's with *4.4.19-bone-rt-r13* and *4.4.38-bone-rt-r14*. I assume
these can be fixed as per your suggestion, but it appears that the
dtb-rebuilder is for the TI kernels only. Is this the case? If so, how
should
Fixed and working - thanks for your help and your quick response. I *could*
have banged my head against the wall a good deal longer on this one. It
feels so good when you stop doing that.
On Monday, October 3, 2016 at 4:58:55 PM UTC-4, RobertCNelson wrote:
>
> On Mon, Oct 3, 2016 at 3:54 PM,
Thanks. Love your work, by the way. Pretty near perfect for my needs. We
have an open-source building control built on top of the BBB - we created
the world's largest cape and stuffed it with industrial-grade I/O:
On Mon, Oct 3, 2016 at 3:54 PM, pbft wrote:
> Killing me here - I'm running 4.4.21-ti-r45. Is it worth just getting the
> newer kernel?
Yeah, just upgrade:
sudo apt-get update
sudo apt-get install linux-image-4.4.21-ti-r47
sudo reboot
Killing me here - I'm running 4.4.21-ti-r45. Is it worth just getting the
newer kernel?
On Monday, October 3, 2016 at 4:52:45 PM UTC-4, RobertCNelson wrote:
>
> On Mon, Oct 3, 2016 at 3:46 PM, pbft
> wrote:
> > Thanks. I'm using your precompiled kernel, so I assume I
On Mon, Oct 3, 2016 at 3:46 PM, pbft wrote:
> Thanks. I'm using your precompiled kernel, so I assume I checkout / download
> your 'dtb-rebuilder' and recompile the am335x dtb files that live in
> /boot/dtbs// - correct?
yeah..
Or if your running: 4.4.21-ti-r47 or newer, r47 was
Thanks. I'm using your precompiled kernel, so I assume I checkout /
download your 'dtb-rebuilder' and recompile the am335x dtb files that live
in /boot/dtbs// - correct?
> Disable the "edma-fix" it's causing spi issues in v4.4.x
>
> Just comment out it out like:
>
>
>
On Mon, Oct 3, 2016 at 3:20 PM, pbft wrote:
> I have several overlays that I've been using with an earlier (4.1.10)
> kernel. In trying to port everything to a more recent kernel, my two SPI
> overlays don't create pingroups and don't set pinmux attributes. I've
> recompiled them
I have several overlays that I've been using with an earlier (4.1.10)
kernel. In trying to port everything to a more recent kernel, my two SPI
overlays don't create pingroups and don't set pinmux attributes. I've
recompiled them using the dtc that came with the new kernel with no effect.
They
14 matches
Mail list logo