Hello,

I've also faced the same issue.

Even though I tried editing the /boot/uEnv.txt file, I cannot enable uart

cape_enable=bone_capemgr.enable_partno=BB-UART2


I had to use 
config-pin P9_21 uart
config-pin P9_22 uart

to enable my uart2 channel.

@Zach : Please try the same and let me know. I don't know if it will work 
in Ubuntu.

@Robert or anyone else, why enabling uart in uEnv.txt is not successful 
always?


On Friday, 18 August 2017 02:51:05 UTC+5:30, Zach wrote:
>
> Hello there, I am attempting to activate UART pins on the BeagleBone Black 
> with Ubuntu 16.04 kernel 4.4.68
>
> ubuntu@arm:~$ uname -a
> Linux arm 4.4.68-ti-r111 #1 SMP Wed Jun 28 13:40:31 UTC 2017 armv7l armv7l 
> armv7l GNU/Linux
>
> I have tried editing the /boot/uEnv.txt file.
>
> cape_enable=bone_capemgr.enable_partno=BB-UART1
>
>
> I have tried 
> echo BB-UART1 > /sys/devices/platform/bone_capemgr/slots
>
> Which causes the BBB to stall, I even let it sit for almost 2 hours once 
> to no results.
>
> ubuntu@arm:~$ ls -l /dev/ttyO*
> lrwxrwxrwx 1 root root 5 Jul 14 14:48 /dev/ttyO0 -> ttyS0
> lrwxrwxrwx 1 root root 5 Jul 14 14:48 /dev/ttyO1 -> ttyS1
> lrwxrwxrwx 1 root root 5 Jul 14 14:48 /dev/ttyO2 -> ttyS2
> lrwxrwxrwx 1 root root 5 Jul 14 14:48 /dev/ttyO4 -> ttyS4
> ubuntu@arm:~$ ls -l /dev/ttyS*
> crw--w---- 1 root tty     4, 64 Jul 14 14:48 /dev/ttyS0
> crw-rw---- 1 root dialout 4, 65 Jul 14 14:48 /dev/ttyS1
> crw-rw---- 1 root dialout 4, 66 Jul 14 14:48 /dev/ttyS2
> crw-rw---- 1 root dialout 4, 67 Jul 14 14:48 /dev/ttyS3
> crw-rw---- 1 root dialout 4, 68 Jul 14 14:48 /dev/ttyS4
> crw-rw---- 1 root dialout 4, 69 Jul 14 14:48 /dev/ttyS5
>
>
>
> I have tried 
> config-pin 911 uart
> config pin 913 uart
> ubuntu@arm:~$ config-pin -q 911
> P9_11 Mode: uart
> ubuntu@arm:~$ config-pin -q 913
> P9_13 Mode: uart
>
> But still no data being transferred.  My end goal is to use ROS with a 
> PixHawk for drone flights.  Any help would be greatly appreciated.
>
>   
>

-- 
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/04c14572-ce48-426b-b3ef-b3f6772c1eae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to