Hmm ok, so I removed the cape_enable=bone_capemgr.enable_partno=BB_UART2
and added dtb=am335x-boneblack-ttyS2.dtb from/to uEnv and now I have no ttyO2 there. I have verified that am335x-boneblack-ttyS2.dtb is in /boot/dtbs/4.1.13-ti-r33 Understood on the lockup, hopefully it won't be needed if this works around it!!! On Tue, Nov 24, 2015 at 4:49 PM, Robert Nelson <[email protected]> wrote: > On Tue, Nov 24, 2015 at 10:37 AM, Lee Armstrong <[email protected]> wrote: > > Thanks Robert, really appreciate that and did’t see dtb-rebuilder before. > > > > I will give that a go. Just applied and rebooting. > > > > Can I remove the loading of the cape BB-UART2 as a result of this and > will > > the port change from ttyO2 to ttyS2? > > Yeap, you won't need the cape loading.. Don't worry about the > ttyO2/ttyS2, it'll have the same exact name /dev/ttyX that the overlay > did.. > > PS, kernel/systemd/udev in wheezy/jessie is setup to do a /dev/ttyS > <-> /dev/ttyO linking... > > > Also is there a way to verify it’s in PIO mode now as well. > > > > Finally, if I do get the lockup, is there any info I can get you at all!! > > If we still get a lockup, we should cc/ping these guys: > > > https://github.com/RobertCNelson/ti-linux-kernel/commit/622efc9bbb23861488f06cfa580b31bcaa27fa0d > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
