[beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Yes it seems lots of people are in the same situation. OK, so despite all the halabaloo about Device Tree Overlays you still need to build a custom kernel to add a new cape at boot, is that so? I kind of thought the whole point was getting rid of that ;-) -- For more options, visit http://beagl

[beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Yes - same problem here; I just added the echo > $SLOTS script to /etc/profile to walk around all this. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group a

[beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Hy, I´m having a very similar problem. I am using the current version of ubuntu for BBB (Ubuntu 14.04 LTS (GNU/Linux 3.8.13-bone47 armv7l)) and tried to a device tree overlay with this guide for the exact same cape: http://the8thlayerof.net/2013/10/28/canbus-beagle-bone-black-as-a-canbus-data-l

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On 11/15/2013 07:08 AM, Jesper We wrote: > Yes it seems lots of people are in the same situation. OK, so despite > all the halabaloo about Device Tree Overlays you still need to build a > custom kernel to add a new cape at boot, is that so? > I kind of thought the whole point was getting rid of tha

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

OK, I bit the bullet and went through the custom kernel build process. Put my .dts in kernel/firmware/capes/ and added it to the kernel/firmware/MakefileDTO ...and so it works. Conclusion: The reason the Circuitco Capes work is that they are already compiled into the standard distribution. The

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On Fri, Nov 15, 2013 at 2:52 PM, Jesper We wrote: > OK, I bit the bullet and went through the custom kernel build process. > Put my .dts in kernel/firmware/capes/ and added it to the > kernel/firmware/MakefileDTO > > ...and so it works. > > Conclusion: The reason the Circuitco Capes work is that t

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Really :-) ? This is all it takes to make it work as advertised? Makes me wonder why that is not in the default distribution... On Friday, November 15, 2013 8:56:01 PM UTC, RobertCNelson wrote: > > > You can also just disable the kernel config switch for building > firmware inside the kernel. T

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Robert, after much headscratching at the various Angstrom download and instruction pages, which seem to be in various stages of bit-rot, I switched my attention to your stuff, which seems a lot more well maintained. I'm now using omap-image-builder to create an image. I have chosen to work with

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On 11/15/2013 9:08 AM, Jesper We wrote: > Yes it seems lots of people are in the same situation. OK, so despite all > the halabaloo about Device Tree Overlays you still need to build a custom > kernel to add a new cape at boot, is that so? > I kind of thought the whole point was getting rid of th

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On Sun, Nov 17, 2013 at 9:43 AM, Jesper We wrote: > Robert, after much headscratching at the various Angstrom download and > instruction pages, which seem to be in various stages of bit-rot, I switched > my attention to your stuff, which seems a lot more well maintained. > > I'm now using omap-ima

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Staring a bit more at the build logs I think I see an error from the build_image.sh run that could be causing this. Towards the end, qemu crashes while doing something with the boot scrips, see log excerpt below. I'm running Ubuntu 13.10 with version "QEMU emulator version 1.5.0 (Debian 1.5.0+df

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Actually, staring a bit more at the build logs I see an error from the build_image.sh run that causes both my problems. Towards the end, in chroot.sh/startup_script(), qemu segfaults while git clone-ing the boot scrips, see log excerpt below. I'm running Ubuntu 13.10 with version "QEMU emulator v

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

I just read this thread and thought "wow, this is the same set of experiences I've had over the last couple months." "OK, I have read this threadtwice now, and I still fail to see any real solution in between the di

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

I tried to replace qemu 1.5 with a locally built qemu 1.6.1, and run build_image.sh. This gives me: Cloning into '/opt/boot-scripts'... qemu: Unsupported syscall: 374 remote: Counting objects: 65, done. remote: Compressing objects: 100% (60/60), done. remote: Total 65 (delta 26), reused 44 (delt

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On Mon, Nov 18, 2013 at 1:21 AM, Jesper We wrote: > I tried to replace qemu 1.5 with a locally built qemu 1.6.1, and run > build_image.sh. > > This gives me: > > > Cloning into '/opt/boot-scripts'... > qemu: Unsupported syscall: 374 > remote: Counting objects: 65, done. > remote: Compressing objec

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On 4/25/2014 5:37 AM, Andreas Tauböck wrote: > > and I get a permission denied when i want to add it manually with: > > ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots > -bash: slots: Permission denied The redirect happens before the sudo, try: sudo su -c "echo TT3201:001 >

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

I think sudo -S might work too, but have not tested this myself yet. On Fri, Apr 25, 2014 at 4:51 AM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 4/25/2014 5:37 AM, Andreas Tauböck wrote: > > > > and I get a permission denied when i want to add it manually with: > > > > ubuntu@

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

Well, neither of them works: ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo su -c "echo TT3201:001 > slots" [sudo] password for ubuntu: bash: line 0: echo: write error: No such file or directory ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo -S "echo TT3201:001 > slots" sudo: echo TT3201:001 > slots:

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On Mon, Apr 28, 2014 at 8:26 AM, Andreas Tauböck wrote: > Well, neither of them works: > > ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo su -c "echo TT3201:001 > slots" > [sudo] password for ubuntu: > bash: line 0: echo: write error: No such file or directory > ubuntu@arm:/sys/devices/bone_capemgr.

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On 4/28/2014 8:40 AM, Robert Nelson wrote: > firmware 'TT3201-001.dtbo' for board-name 'Override Board Name', > version '001' > [ 356.670369] bone-capemgr bone_capemgr.9: failed to load firmware > 'TT3201-001.dtbo' Note that this is the exact filename it's looking for in /lib/firmware, and based

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

On Mon, Apr 28, 2014 at 8:43 AM, Charles Steinkuehler wrote: > On 4/28/2014 8:40 AM, Robert Nelson wrote: > >> firmware 'TT3201-001.dtbo' for board-name 'Override Board Name', >> version '001' >> [ 356.670369] bone-capemgr bone_capemgr.9: failed to load firmware >> 'TT3201-001.dtbo' > > Note that