I guess your overlay cannot 'disable' pins that're claimed by another overlay. And here you're facing the core problem when working with device trees: you won't get reliable error messages. Everything ends up with trail-and-error bug finding.
I've good reasons why I always drop config-pin and its overlays. Instead I developed and shared libpruio <https://github.com/DTJF/libpruio> and its pinmuxing. Your target is over the capabilities of the standard tools, but is well covered by the libpruio scope. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e5ec3da7-db00-423c-ac11-b3b84709a1d3%40googlegroups.com.
