Quantcast

Using UART 2 on an Overo

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Using UART 2 on an Overo

nz_michaelh
Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not listed on the board pin out, but according to the TI datasheet U2_TX should be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to stay low instead of idling high as expected.

Linux lists three serial ports and I can quite happily write to UART 1 and UART 3.  I see on the gumstix site that they planned to use ttyS1 for on-board Bluetooth so I wonder if the line hasn't been brought out.

Thanks for any help,

Michael Hope
Controls Engineer

HAMILTONJET
CWF Hamilton & Co Ltd, Lunns Rd, PO Box 709, Christchurch, New Zealand
www.hamiltonjet.co.nz


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

R. P. McMurphy
I am using all 3 Overo serial ports without a problem.

Perhaps the configuration in your OS is not setting the mux for the
pin? Remember to also clear the mux for the mirror pins GPIO142/143

On 3/16/09, Michael Hope <[hidden email]> wrote:

> Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not
> listed on the board pin out, but according to the TI datasheet U2_TX should
> be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to
> stay low instead of idling high as expected.
>
> Linux lists three serial ports and I can quite happily write to UART 1 and
> UART 3.  I see on the gumstix site that they planned to use ttyS1 for
> on-board Bluetooth so I wonder if the line hasn't been brought out.
>
> Thanks for any help,
>
> Michael Hope
> Controls Engineer
>
> HAMILTONJET
> CWF Hamilton & Co Ltd, Lunns Rd, PO Box 709, Christchurch, New Zealand
> www.hamiltonjet.co.nz
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> gumstix-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Steve Sakoman
On Mon, Mar 16, 2009 at 4:53 AM, R. P. McMurphy <[hidden email]> wrote:

> I am using all 3 Overo serial ports without a problem.
>
> Perhaps the configuration in your OS is not setting the mux for the
> pin? Remember to also clear the mux for the mirror pins GPIO142/143
>
> On 3/16/09, Michael Hope <[hidden email]> wrote:
>> Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not
>> listed on the board pin out, but according to the TI datasheet U2_TX should
>> be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to
>> stay low instead of idling high as expected.
>>
>> Linux lists three serial ports and I can quite happily write to UART 1 and
>> UART 3.  I see on the gumstix site that they planned to use ttyS1 for
>> on-board Bluetooth so I wonder if the line hasn't been brought out.

UART 1 (ttyS0) and UART 3 (ttyS2) are brought out to the expansion connector:

UART 1: on pins 24 and 48 of J4
(http://www.gumstix.net/Hardware/view/I/O-connectors-cabling/Gumstix-Overo-70-pin-connector-J4-features-Extended-Memory-Bus-and-
MMC-signals/112.html)

UART3: on pins 26 and 31 of J1
(http://www.gumstix.net/Hardware/view/Motherboard-I/O/Connector-J1-for-Overo/112.html)

UART2 (ttyS1) is used for the BT function in an upcoming version of
the motherboard.  The default u-boot routes these signals from
GPIO140-143 to the bluetooth module and hence these signals are *not*
available on the expansion connector.

However . . . if you know your code will *never* be run on the wifi/bt
version of the motherboard, you can alter the pinmux configuration to
disable routing UART2 to the above mentioned pins and instead route
them to GPIO144-147, which are available on the expansion connector J1
(see link above for J1 pinout)  You can alter the pinmux either in
u-boot or in a custom kernel.

Steve

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

nz_michaelh
In reply to this post by nz_michaelh
Thanks for the help.  The change was to change the mux in u-boot to map the UART through the default pins:

--- a/board/omap3/overo/overo.h
+++ b/board/omap3/overo/overo.h
@@ -214,14 +214,14 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(MMC2_DAT6),                (IEN  | PTU | EN  | M1)) /*MMC2_DIR_CMD*/\
  MUX_VAL(CP(MMC2_DAT7),                (IEN  | PTU | EN  | M1)) /*MMC2_CLKIN*/\
  /*Bluetooth*/\
- MUX_VAL(CP(MCBSP3_DX),                (IEN  | PTD | DIS | M1)) /*UART2_CTS*/\
- MUX_VAL(CP(MCBSP3_DR),                (IDIS | PTD | DIS | M1)) /*UART2_RTS*/\
- MUX_VAL(CP(MCBSP3_CLKX),      (IDIS | PTD | DIS | M1)) /*UART2_TX*/\
- MUX_VAL(CP(MCBSP3_FSX),       (IEN  | PTD | DIS | M1)) /*UART2_RX*/\
- MUX_VAL(CP(UART2_CTS),                (IEN  | PTD | DIS | M4)) /*GPIO_144 - LCD_EN*/\
- MUX_VAL(CP(UART2_RTS),                (IEN  | PTD | DIS | M4)) /*GPIO_145*/\
- MUX_VAL(CP(UART2_TX),         (IEN  | PTD | DIS | M4)) /*GPIO_146*/\
- MUX_VAL(CP(UART2_RX),         (IEN  | PTD | DIS | M4)) /*GPIO_147*/\
+ MUX_VAL(CP(MCBSP3_DX),                (IDIS | PTD | DIS | M0)) /*McBSP3_DX*/\
+ MUX_VAL(CP(MCBSP3_DR),                (IEN  | PTD | DIS | M0)) /*McBSP3_DR*/\
+ MUX_VAL(CP(MCBSP3_CLKX),      (IEN  | PTD | DIS | M0)) /*McBSP3_CLKX  */\
+ MUX_VAL(CP(MCBSP3_FSX),       (IEN  | PTD | DIS | M0)) /*McBSP3_FSX*/\
+ MUX_VAL(CP(UART2_CTS),                (IEN  | PTU | EN  | M0)) /*UART2_CTS*/\
+ MUX_VAL(CP(UART2_RTS),                (IDIS | PTD | DIS | M0)) /*UART2_RTS*/\
+ MUX_VAL(CP(UART2_TX),         (IDIS | PTD | DIS | M0)) /*UART2_TX*/\
+ MUX_VAL(CP(UART2_RX),         (IEN  | PTD | DIS | M0)) /*UART2_RX*/\
  MUX_VAL(CP(UART1_TX),         (IDIS | PTD | DIS | M0)) /*UART1_TX*/\
  MUX_VAL(CP(UART1_RTS),                (IEN  | PTU | DIS | M4)) /*GPIO_149*/ \
  MUX_VAL(CP(UART1_CTS),                (IEN  | PTU | DIS | M4)) /*GPIO_150-MMC3_WP*/\

I'm now able to talk to a CSR based C46AHR Bluetooth module at 1 Mbaud.  Using dial up networking to a Linux box I can transfer files at 35 kbytes/s.

Interestingly the Bluetooth module would respond at 115200 and 1 Mbaud but not at the usual suspects of 230400, 460800, or 921600.

-- Michael


-----Original Message-----
From: Michael Hope
Sent: Monday, 16 March 2009 4:38 p.m.
To: '[hidden email]'
Subject: Using UART 2 on an Overo

Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not listed on the board pin out, but according to the TI datasheet U2_TX should be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to stay low instead of idling high as expected.

Linux lists three serial ports and I can quite happily write to UART 1 and UART 3.  I see on the gumstix site that they planned to use ttyS1 for on-board Bluetooth so I wonder if the line hasn't been brought out.

Thanks for any help,

Michael Hope
Controls Engineer

HAMILTONJET
CWF Hamilton & Co Ltd, Lunns Rd, PO Box 709, Christchurch, New Zealand www.hamiltonjet.co.nz


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

msinger
In reply to this post by Steve Sakoman
Steve,

   What if I'm running on a Air/Fire, but don't need to use the BT, only the WIFI?  Can I use UART 2 on
140-143?

    Thanks

sakoman wrote
On Mon, Mar 16, 2009 at 4:53 AM, R. P. McMurphy <loginreg@gmail.com> wrote:
> I am using all 3 Overo serial ports without a problem.
>
> Perhaps the configuration in your OS is not setting the mux for the
> pin? Remember to also clear the mux for the mirror pins GPIO142/143
>
> On 3/16/09, Michael Hope <Michael.Hope@hamjet.co.nz> wrote:
>> Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not
>> listed on the board pin out, but according to the TI datasheet U2_TX should
>> be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to
>> stay low instead of idling high as expected.
>>
>> Linux lists three serial ports and I can quite happily write to UART 1 and
>> UART 3.  I see on the gumstix site that they planned to use ttyS1 for
>> on-board Bluetooth so I wonder if the line hasn't been brought out.

UART 1 (ttyS0) and UART 3 (ttyS2) are brought out to the expansion connector:

UART 1: on pins 24 and 48 of J4
(http://www.gumstix.net/Hardware/view/I/O-connectors-cabling/Gumstix-Overo-70-pin-connector-J4-features-Extended-Memory-Bus-and-
MMC-signals/112.html)

UART3: on pins 26 and 31 of J1
(http://www.gumstix.net/Hardware/view/Motherboard-I/O/Connector-J1-for-Overo/112.html)

UART2 (ttyS1) is used for the BT function in an upcoming version of
the motherboard.  The default u-boot routes these signals from
GPIO140-143 to the bluetooth module and hence these signals are *not*
available on the expansion connector.

However . . . if you know your code will *never* be run on the wifi/bt
version of the motherboard, you can alter the pinmux configuration to
disable routing UART2 to the above mentioned pins and instead route
them to GPIO144-147, which are available on the expansion connector J1
(see link above for J1 pinout)  You can alter the pinmux either in
u-boot or in a custom kernel.

Steve

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Bernhard Wörndl-Aichriedler
Hey!

As far as I see, UART2 is not wired to any connector -> no.

Regards

Bernhard Wörndl-Aichriedler


Am 06.05.2010 16:17, schrieb msinger:
Steve,

   What if I'm running on a Air/Fire, but don't need to use the BT, only the
WIFI?  Can I use UART 2 on
140-143?

    Thanks


sakoman wrote:
  
On Mon, Mar 16, 2009 at 4:53 AM, R. P. McMurphy [hidden email]
wrote:
    
I am using all 3 Overo serial ports without a problem.

Perhaps the configuration in your OS is not setting the mux for the
pin? Remember to also clear the mux for the mirror pins GPIO142/143

On 3/16/09, Michael Hope [hidden email] wrote:
      
Hi there.  Has anyone had any luck using UART 2 on the Overo?  It's not
listed on the board pin out, but according to the TI datasheet U2_TX
should
be available on P146/PWM11 and U2_RX on P147/PWM8.  The TX line seems to
stay low instead of idling high as expected.

Linux lists three serial ports and I can quite happily write to UART 1
and
UART 3.  I see on the gumstix site that they planned to use ttyS1 for
on-board Bluetooth so I wonder if the line hasn't been brought out.
        
UART 1 (ttyS0) and UART 3 (ttyS2) are brought out to the expansion
connector:

UART 1: on pins 24 and 48 of J4
(http://www.gumstix.net/Hardware/view/I/O-connectors-cabling/Gumstix-Overo-70-pin-connector-J4-features-Extended-Memory-Bus-and-
MMC-signals/112.html)

UART3: on pins 26 and 31 of J1
(http://www.gumstix.net/Hardware/view/Motherboard-I/O/Connector-J1-for-Overo/112.html)

UART2 (ttyS1) is used for the BT function in an upcoming version of
the motherboard.  The default u-boot routes these signals from
GPIO140-143 to the bluetooth module and hence these signals are *not*
available on the expansion connector.

However . . . if you know your code will *never* be run on the wifi/bt
version of the motherboard, you can alter the pinmux configuration to
disable routing UART2 to the above mentioned pins and instead route
them to GPIO144-147, which are available on the expansion connector J1
(see link above for J1 pinout)  You can alter the pinmux either in
u-boot or in a custom kernel.

Steve

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users


    
  

------------------------------------------------------------------------------

_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

msinger
144-147 ;-)


<quote author="Bernhard Wörndl-Aichriedler">
Hey!

As far as I see, UART2 is not wired to any connector -> no.

Regards

*Bernhard Wörndl-Aichriedler*
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

msinger
In reply to this post by Bernhard Wörndl-Aichriedler
144-147 ;-)


<quote author="Bernhard Wörndl-Aichriedler">
Hey!

As far as I see, UART2 is not wired to any connector -> no.

Regards

*Bernhard Wörndl-Aichriedler*
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

ekoshimo
Hello all -

I'm using an Overo Water with a Summit expansion board.  I believe I got UART2 (/dev/ttyS1) working by building a custom u-boot image which sets the mux values on pins 27 and 29.  I'm haven't tried to verify that I can do this from the userspace using devmem2, but I think that approach should work as well.

I spent some time with the OMAP35xx TRM figuring out what I should be modifying.

Thanks,
ed

<quote author="msinger">
144-147 ;-)


Bernhard Wörndl-Aichriedler wrote
Hey!

As far as I see, UART2 is not wired to any connector -> no.

Regards

*Bernhard Wörndl-Aichriedler*
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Elvis Dowson
In reply to this post by Bernhard Wörndl-Aichriedler
Hi,

On May 6, 2010, at 6:21 PM, Bernhard Wörndl-Aichriedler wrote:

As far as I see, UART2 is not wired to any connector -> no.

The OMAP3 chip uses pin muxing, so internally it has many devices but you only have a lesser number of physical pin outs. So, you can set the pin muxing, to bring out a specific internal chip function, out to a particular connector. 

Here is a patch that you can apply to u-boot to disable bluetooth and enable UART 2. You can add this patch to your u-boot OpenEmbedded recipe and build u-boot. This approach sets the pin muxing at boottime. Another option is to reconfigure it in the kernel, although I haven't attempt that.

Best regards,

Elvis Dowson



diff --git a/board/omap3/overo/overo.h b/board/omap3/overo/overo.h
index 0b59120..59dc76d 100644
--- a/board/omap3/overo/overo.h
+++ b/board/omap3/overo/overo.h
@@ -213,14 +213,14 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(MMC2_DAT6), (IEN  | PTU | EN  | M1)) /*MMC2_DIR_CMD*/\
  MUX_VAL(CP(MMC2_DAT7), (IEN  | PTU | EN  | M1)) /*MMC2_CLKIN*/\
  /*Bluetooth*/\
- MUX_VAL(CP(MCBSP3_DX), (IEN  | PTD | DIS | M1)) /*UART2_CTS*/\
- MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M1)) /*UART2_RTS*/\
- MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M1)) /*UART2_TX*/\
- MUX_VAL(CP(MCBSP3_FSX), (IEN  | PTD | DIS | M1)) /*UART2_RX*/\
+ MUX_VAL(CP(MCBSP3_DX), (IDIS | PTD | DIS | M0)) /*McBSP3_DX*/\
+ MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M0)) /*McBSP3_DR*/\
+ MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M0)) /*McBSP3_CLKX*/\
+ MUX_VAL(CP(MCBSP3_FSX), (IDIS | PTD | DIS | M0)) /*McBSP3_FSX*/\
  MUX_VAL(CP(UART2_CTS), (IEN  | PTD | DIS | M4)) /*GPIO_144 - LCD_EN*/\
  MUX_VAL(CP(UART2_RTS), (IEN  | PTD | DIS | M4)) /*GPIO_145*/\
- MUX_VAL(CP(UART2_TX), (IEN  | PTD | DIS | M4)) /*GPIO_146*/\
- MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M4)) /*GPIO_147*/\
+ MUX_VAL(CP(UART2_TX), (IDIS | PTD | DIS | M0)) /*UART2_TX*/\
+ MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M0)) /*UART2_RX*/\
  MUX_VAL(CP(UART1_TX), (IDIS | PTD | DIS | M0)) /*UART1_TX*/\
  MUX_VAL(CP(UART1_RTS), (IEN  | PTU | DIS | M4)) /*GPIO_149*/ \
  MUX_VAL(CP(UART1_CTS), (IEN  | PTU | DIS | M4)) /*GPIO_150-MMC3_WP*/\
-- 
1.6.0.3




------------------------------------------------------------------------------


_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

msinger
Thanks Elvis,
 
Added the changes to board_mux in board-overo.c and rebuilt the kernel.  Works fine.
 


From: Elvis Dowson [mailto:[hidden email]]
Sent: Thursday, May 06, 2010 4:57 PM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Using UART 2 on an Overo

Hi,

On May 6, 2010, at 6:21 PM, Bernhard Wörndl-Aichriedler wrote:

As far as I see, UART2 is not wired to any connector -> no.

The OMAP3 chip uses pin muxing, so internally it has many devices but you only have a lesser number of physical pin outs. So, you can set the pin muxing, to bring out a specific internal chip function, out to a particular connector. 

Here is a patch that you can apply to u-boot to disable bluetooth and enable UART 2. You can add this patch to your u-boot OpenEmbedded recipe and build u-boot. This approach sets the pin muxing at boottime. Another option is to reconfigure it in the kernel, although I haven't attempt that.

Best regards,

Elvis Dowson



diff --git a/board/omap3/overo/overo.h b/board/omap3/overo/overo.h
index 0b59120..59dc76d 100644
--- a/board/omap3/overo/overo.h
+++ b/board/omap3/overo/overo.h
@@ -213,14 +213,14 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(MMC2_DAT6), (IEN  | PTU | EN  | M1)) /*MMC2_DIR_CMD*/\
  MUX_VAL(CP(MMC2_DAT7), (IEN  | PTU | EN  | M1)) /*MMC2_CLKIN*/\
  /*Bluetooth*/\
- MUX_VAL(CP(MCBSP3_DX), (IEN  | PTD | DIS | M1)) /*UART2_CTS*/\
- MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M1)) /*UART2_RTS*/\
- MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M1)) /*UART2_TX*/\
- MUX_VAL(CP(MCBSP3_FSX), (IEN  | PTD | DIS | M1)) /*UART2_RX*/\
+ MUX_VAL(CP(MCBSP3_DX), (IDIS | PTD | DIS | M0)) /*McBSP3_DX*/\
+ MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M0)) /*McBSP3_DR*/\
+ MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M0)) /*McBSP3_CLKX*/\
+ MUX_VAL(CP(MCBSP3_FSX), (IDIS | PTD | DIS | M0)) /*McBSP3_FSX*/\
  MUX_VAL(CP(UART2_CTS), (IEN  | PTD | DIS | M4)) /*GPIO_144 - LCD_EN*/\
  MUX_VAL(CP(UART2_RTS), (IEN  | PTD | DIS | M4)) /*GPIO_145*/\
- MUX_VAL(CP(UART2_TX), (IEN  | PTD | DIS | M4)) /*GPIO_146*/\
- MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M4)) /*GPIO_147*/\
+ MUX_VAL(CP(UART2_TX), (IDIS | PTD | DIS | M0)) /*UART2_TX*/\
+ MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M0)) /*UART2_RX*/\
  MUX_VAL(CP(UART1_TX), (IDIS | PTD | DIS | M0)) /*UART1_TX*/\
  MUX_VAL(CP(UART1_RTS), (IEN  | PTU | DIS | M4)) /*GPIO_149*/ \
  MUX_VAL(CP(UART1_CTS), (IEN  | PTU | DIS | M4)) /*GPIO_150-MMC3_WP*/\
-- 
1.6.0.3



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2855 - Release Date: 05/06/10 02:26:00


------------------------------------------------------------------------------


_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Eric97
In reply to this post by Elvis Dowson
Hi,

What kind of extension board are you using? I am using the summit version, but the UART3 can only TX instead of RX. According to the signal reference, the UART3 RX pin is also shared with the console port. May i know this cause the RX problem? Btw, i am using the QNX source package for development.

Thank you,
Eric

Elvis Dowson wrote
Hi,

On May 6, 2010, at 6:21 PM, Bernhard Wörndl-Aichriedler wrote:

> As far as I see, UART2 is not wired to any connector -> no.

The OMAP3 chip uses pin muxing, so internally it has many devices but you only have a lesser number of physical pin outs. So, you can set the pin muxing, to bring out a specific internal chip function, out to a particular connector.

Here is a patch that you can apply to u-boot to disable bluetooth and enable UART 2. You can add this patch to your u-boot OpenEmbedded recipe and build u-boot. This approach sets the pin muxing at boottime. Another option is to reconfigure it in the kernel, although I haven't attempt that.

Best regards,

Elvis Dowson



diff --git a/board/omap3/overo/overo.h b/board/omap3/overo/overo.h
index 0b59120..59dc76d 100644
--- a/board/omap3/overo/overo.h
+++ b/board/omap3/overo/overo.h
@@ -213,14 +213,14 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(MMC2_DAT6), (IEN  | PTU | EN  | M1)) /*MMC2_DIR_CMD*/\
  MUX_VAL(CP(MMC2_DAT7), (IEN  | PTU | EN  | M1)) /*MMC2_CLKIN*/\
  /*Bluetooth*/\
- MUX_VAL(CP(MCBSP3_DX), (IEN  | PTD | DIS | M1)) /*UART2_CTS*/\
- MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M1)) /*UART2_RTS*/\
- MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M1)) /*UART2_TX*/\
- MUX_VAL(CP(MCBSP3_FSX), (IEN  | PTD | DIS | M1)) /*UART2_RX*/\
+ MUX_VAL(CP(MCBSP3_DX), (IDIS | PTD | DIS | M0)) /*McBSP3_DX*/\
+ MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M0)) /*McBSP3_DR*/\
+ MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M0)) /*McBSP3_CLKX*/\
+ MUX_VAL(CP(MCBSP3_FSX), (IDIS | PTD | DIS | M0)) /*McBSP3_FSX*/\
  MUX_VAL(CP(UART2_CTS), (IEN  | PTD | DIS | M4)) /*GPIO_144 - LCD_EN*/\
  MUX_VAL(CP(UART2_RTS), (IEN  | PTD | DIS | M4)) /*GPIO_145*/\
- MUX_VAL(CP(UART2_TX), (IEN  | PTD | DIS | M4)) /*GPIO_146*/\
- MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M4)) /*GPIO_147*/\
+ MUX_VAL(CP(UART2_TX), (IDIS | PTD | DIS | M0)) /*UART2_TX*/\
+ MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M0)) /*UART2_RX*/\
  MUX_VAL(CP(UART1_TX), (IDIS | PTD | DIS | M0)) /*UART1_TX*/\
  MUX_VAL(CP(UART1_RTS), (IEN  | PTU | DIS | M4)) /*GPIO_149*/ \
  MUX_VAL(CP(UART1_CTS), (IEN  | PTU | DIS | M4)) /*GPIO_150-MMC3_WP*/\
--
1.6.0.3




------------------------------------------------------------------------------


_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Geo_Homsy
In reply to this post by Steve Sakoman
Hi Steve--

I need to use UART2 on an Overo Fire.   I do NOT need bluetooth functionality.  I can try using the method you describe, but you say to be sure my code will NEVER run on a motherboard with BT/Wifi functionality.

Can I simply do your patch to uBoot and forget the BT module exists??

Yours,

//Geo
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Geo_Homsy
In reply to this post by msinger
msinger,

did you ever get any reply to this?  I have the same problem:  I need the wifi functionality, and THREE UARTs.  I don't need the bluetooth.

yours,

//Geo
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

mg0536
In reply to this post by Elvis Dowson
Elvis -

Thanks for this!  Very helpful. I'm a bit nervous building a new u-boot, but I will try it.

Is there a way to access this mux functionality via the /sys/class/gpio interface?

Thanks in advance,

-Matt

Elvis Dowson wrote
Here is a patch that you can apply to u-boot to disable bluetooth and enable UART 2. You can add this patch to your u-boot OpenEmbedded recipe and build u-boot. This approach sets the pin muxing at boottime. Another option is to reconfigure it in the kernel, although I haven't attempt that.

diff --git a/board/omap3/overo/overo.h b/board/omap3/overo/overo.h
index 0b59120..59dc76d 100644
--- a/board/omap3/overo/overo.h
+++ b/board/omap3/overo/overo.h
@@ -213,14 +213,14 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(MMC2_DAT6), (IEN  | PTU | EN  | M1)) /*MMC2_DIR_CMD*/\
  MUX_VAL(CP(MMC2_DAT7), (IEN  | PTU | EN  | M1)) /*MMC2_CLKIN*/\
  /*Bluetooth*/\
- MUX_VAL(CP(MCBSP3_DX), (IEN  | PTD | DIS | M1)) /*UART2_CTS*/\
- MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M1)) /*UART2_RTS*/\
- MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M1)) /*UART2_TX*/\
- MUX_VAL(CP(MCBSP3_FSX), (IEN  | PTD | DIS | M1)) /*UART2_RX*/\
+ MUX_VAL(CP(MCBSP3_DX), (IDIS | PTD | DIS | M0)) /*McBSP3_DX*/\
+ MUX_VAL(CP(MCBSP3_DR), (IDIS | PTD | DIS | M0)) /*McBSP3_DR*/\
+ MUX_VAL(CP(MCBSP3_CLKX), (IDIS | PTD | DIS | M0)) /*McBSP3_CLKX*/\
+ MUX_VAL(CP(MCBSP3_FSX), (IDIS | PTD | DIS | M0)) /*McBSP3_FSX*/\
  MUX_VAL(CP(UART2_CTS), (IEN  | PTD | DIS | M4)) /*GPIO_144 - LCD_EN*/\
  MUX_VAL(CP(UART2_RTS), (IEN  | PTD | DIS | M4)) /*GPIO_145*/\
- MUX_VAL(CP(UART2_TX), (IEN  | PTD | DIS | M4)) /*GPIO_146*/\
- MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M4)) /*GPIO_147*/\
+ MUX_VAL(CP(UART2_TX), (IDIS | PTD | DIS | M0)) /*UART2_TX*/\
+ MUX_VAL(CP(UART2_RX), (IEN  | PTD | DIS | M0)) /*UART2_RX*/\
  MUX_VAL(CP(UART1_TX), (IDIS | PTD | DIS | M0)) /*UART1_TX*/\
  MUX_VAL(CP(UART1_RTS), (IEN  | PTU | DIS | M4)) /*GPIO_149*/ \
  MUX_VAL(CP(UART1_CTS), (IEN  | PTU | DIS | M4)) /*GPIO_150-MMC3_WP*/\
--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

Elvis Dowson-2

On Jun 19, 2012, at 10:31 PM, mg0536 wrote:

> Thanks for this!  Very helpful. I'm a bit nervous building a new u-boot, but
> I will try it.

Building u-boot is really trivial. :-) Don't worry about it!!

>
> Is there a way to access this mux functionality via the /sys/class/gpio
> interface?

I haven't tried that. Perhaps someone else on the list can comment on how
to do this.

Best regards,

Elvis Dowson
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

qmay123
Sorry if this is a repeat, I had to subscribe so I'm trying again:

Hey All,

I've been trying the above overo.h patch with no success, but I'm also pretty new at this. I'm pretty sure my mistakes are made in applying the patch and rebuilding the bootloader/kernel/image (i've tried every combination of the three). Any chance someone could give some explicit instructions on applying the patch? Preferably starting at editing the overo.h file through building a complete image? I'll make sure to verify and post in the appropriate wiki as a how-to. Thanks!

FYI my goal is to have 3 working serial ports, bluetooth is unnecessary. Thanks!

-QMay
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

rink113
QMay -

I also have been working through the scattered details of how to get UART 2 to be exposed to pins of the Gumstix Overo which are reffered to as GPIO 144-147 (146: TX, 147: RX, 144: CTS, 145: RTS) on various schematic diagrams and pinout tables. I just got it to work in the last hour (I actually subscribed to the list just so I could reply to your message). I got RX/TX working, I will try CTS and RTS soon (I need them). I found the following website very, very helpful with the detailed instructions you are looking for:

http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=55&Itemid=61

The page guides you through how to use bitbake to build a patched u-boot. It also explains how to build u-boot from the cross-compilation tools using 'make' and the compilers directly. I will say this, I tried to use the bitbake way and make a patch -- I for some reason couldn't make it happen -- perhaps I didn't have something set up right. Ultimately, I ended up using the section that explains how to do it WITHOUT bitbake, modified the overo.h file directly, did the make commands as described, copied the u-boot over to my microsd, and my uart2 now works on the described pins.

I don't know if this is critical (sometimes u-boot uImage, the rootfs have to be synced?) but in my case I built all of the files MLO, u-boot, uImage, and the root file system using bitbake first, and after trying to do the patch with bitbake and failing to get UART 2 exposed, I built just u-boot without bitbake and copied that to the microsd. Mine is thankfully working.

I hope that helps. That website seems to have several Overo related "how-tos" that may be of use to you as well.

- rink113
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

qmay123
Rink, thanks for the thorough repose, I haven't had a chance to test it out but plan to very soon. In the meantime, I used the solution from this thread


that was posted by Jesse. This has been working great and is done on boot and requires no building of the image, etc.

One word of caution is that I'm not sure if any processes are using ttyO2 on boot. Bluetooth has supposedly been turned off, however, I have a c++ program that uses the serial port and is set to run on boot, I often get errors when running at boot but not when running manually by logging in through ssh and running the program myself. I'm writing up a new thread for this problem and other serial issues as well. 

Thanks again! Will keep you posted. 

On Sun, Nov 11, 2012 at 4:25 PM, rink113 [via Gumstix] <[hidden email]> wrote:
QMay -

I also have been working through the scattered details of how to get UART 2 to be exposed to pins of the Gumstix Overo which are reffered to as GPIO 144-147 (146: TX, 147: RX, 144: CTS, 145: RTS) on various schematic diagrams and pinout tables. I just got it to work in the last hour (I actually subscribed to the list just so I could reply to your message). I got RX/TX working, I will try CTS and RTS soon (I need them). I found the following website very, very helpful with the detailed instructions you are looking for:

http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=55&Itemid=61

The page guides you through how to use bitbake to build a patched u-boot. It also explains how to build u-boot from the cross-compilation tools using 'make' and the compilers directly. I will say this, I tried to use the bitbake way and make a patch -- I for some reason couldn't make it happen -- perhaps I didn't have something set up right. Ultimately, I ended up using the section that explains how to do it WITHOUT bitbake, modified the overo.h file directly, did the make commands as described, copied the u-boot over to my microsd, and my uart2 now works on the described pins.

I don't know if this is critical (sometimes u-boot uImage, the rootfs have to be synced?) but in my case I built all of the files MLO, u-boot, uImage, and the root file system using bitbake first, and after trying to do the patch with bitbake and failing to get UART 2 exposed, I built just u-boot without bitbake and copied that to the microsd. Mine is thankfully working.

I hope that helps. That website seems to have several Overo related "how-tos" that may be of use to you as well.

- rink113



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.n6.nabble.com/Using-UART-2-on-an-Overo-tp660403p4966028.html
To unsubscribe from Using UART 2 on an Overo, click here.
NAML




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using UART 2 on an Overo

rink113
QMay -

I'm glad you got something working! I did look at the "during runtime" solution that you reference, but preferred doing it more "permanently" in u-boot so I never tried the other way (would have tried if several more u-boot attempts failed). If what you have works good enough, you may not want to change it!! But play/experiment as you see fit! Glad you got something going too.

- rink113
Loading...