I also dont think that there is a device tree with this name. I will
however try you tips at mo day in the morning and let know here. Thank you
for help.
On September 11, 2015 3:41:52 PM Charles Steinkuehler
<char...@steinkuehler.net> wrote:
On 9/11/2015 3:41 AM, Bremenpl wrote:
Am I still doing something wrong?
Two things to check:
1) The kernel will load any compiled in overlays in preference to
files in /lib/firmware. I don't think there's a BB_AVRDUDE overlay
compiled into the kernel, but you can test by changing the name of
your *.dtbo file to something guaranteed to be unique (or give it a
custom version number) and try to load that instead. That will force
the kernel to look for the file in /lib/firmware.
2) You can crawl through the live device tree (/proc/device-tree/*)
and make sure it's what you're expecting. It's easy to have one typo
or similar that will mess up everything you're trying to do. :)
--
Charles Steinkuehler
char...@steinkuehler.net
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the
Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/kL9YPe8NuPg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
