Hello guys,

I have the same issue, indeed all the UARTs coming disabled with this 
image, even though all the /dev/ttyOx are available. My solution maybe is 
not the best one, but I just change the version of Debian 7 release 
2015-07-13, and everything works like we expect, I mean like books and 
tutorials about how to enable ports, and these stuff. Later I will try the 
RobertCNelson solution, it looks very well, maybe is a more reliable 
solution.

Regards


El lunes, 25 de abril de 2016, 10:26:00 (UTC-5), Jean-Sebastien Stoezel 
escribió:
>
> Hi:
>
> I have a BeagleBone Green running Linux version 4.1.15-ti-rt-r43 and 
> Debian 8.3 (Jessie). I am cannot seem to send or receive data on UART2.
>
> What I can see see is that UART2 is enabled:
>
> *[    4.368638] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160, 
> base_baud = 3000000) is a 8250).*
>
> I have used minicom, a C++ QT application, and an online script (
> http://jsfiddle.net/AjnJs/67/) to try and send data over UART2 but 
> nothing seems to get to the pins.
>
> I feel confident in the hardware I use to verify that no data is sent over 
> the UART2 pins (I have yet to get an oscilloscope out though).
>
> Looking at the BBG schematic, it seems the UART2 pins are shared with the 
> SPI. I am wondering if by default SPI might be configured, which might 
> prevent UART2 from operating.
>
> Has anybody ever gotten UART2 to work on the BBG? If so, what steps did 
> you take?
> What software check can I perform to verify UART2 is effectively ready to 
> operate?
>
> Regards,
> JS
>
>  
>

-- 
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/3ed757b7-65b8-4c69-858a-308d9a255ba8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to