All of lore.kernel.org
 help / color / mirror / Atom feed
* [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
@ 2015-06-04 12:01 Andreas Enbacka
  2015-06-04 12:31 ` Valentin Le bescond
  2015-06-05 15:11 ` Andrei Gherzan
  0 siblings, 2 replies; 6+ messages in thread
From: Andreas Enbacka @ 2015-06-04 12:01 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]

Hello,

 

After a long break, I have returned to the Yocto project, and generally very
pleased. A lot of progress has been done since I last used the project (two
years ago), and now in my opinion everything works very smoothly.

 

I have used yocto to build a custom image for the RaspberryPi Compute
Module. Generally everything works ok, however I am experiencing problem
with accessing the UART1 port on the raspberryPi. I am using a library
called wiringPi to put the appropriate GPIO pins in the correct mode (alt5)
for RXD1/TXD1 (pins 32/33). Also I have used menuconfig to enable the
8250/16550 serial port support in the kernel (3.18.5+). After booting the
image I examined the dmesg output, and it shows following information
related to 8250/16550:

..

[   1.010958] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled

[   1.013920] serial8250.0: ttyS0 at MMIO 0x20215040 (irq = 29, base_baud =
7812500) is a 8250

.

 

Then I put the pins 32/33 into alternative mode alt5, and try to connect to
the port /dev/ttyS0 using minicom (baud 115200). Trying to enter something
into the Mincom terminal does not give any indications on our connected
oscilloscope (connected to the relevant pins), however change of the alt
mode earlier was observed correctly. The serial port should not be using any
flow control, but when trying to disable the flow control using Minicom (it
was on by default) freezes the complete RaspberryPi system (requiring to
disconnect and reconnect power).

 

Does anyone have any thoughts what could be the cause of these issues (e.g.,
problems with driver etc)? Any information would be greatly appreciated. In
the project we are working on we would need to use both uart ports (0/1)
provided by the compute module (the uart0 is a pl011 and by disabling
console use of /dev/ttyAMA0 we were able to successfully connect to that
port).

 

Thanks for the great work with the Yocto platform.

 

Sincerely,

Andreas Enbacka

SW designer

Gasera Ltd

 


[-- Attachment #2: Type: text/html, Size: 4918 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
  2015-06-04 12:01 [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi) Andreas Enbacka
@ 2015-06-04 12:31 ` Valentin Le bescond
  2015-06-04 12:41   ` Andreas Enbacka
  2015-06-05 15:11 ` Andrei Gherzan
  1 sibling, 1 reply; 6+ messages in thread
From: Valentin Le bescond @ 2015-06-04 12:31 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]

Hi !

I'm really no expert but am very interested in the subject.

Did you modify the device tree ? From what I understand in the DT that
you'll find pinmux definition right ?

Regards.


2015-06-04 14:01 GMT+02:00 Andreas Enbacka <andreas.enbacka@gasera.fi>:

> Hello,
>
>
>
> After a long break, I have returned to the Yocto project, and generally
> very pleased. A lot of progress has been done since I last used the project
> (two years ago), and now in my opinion everything works very smoothly.
>
>
>
> I have used yocto to build a custom image for the RaspberryPi Compute
> Module. Generally everything works ok, however I am experiencing problem
> with accessing the UART1 port on the raspberryPi. I am using a library
> called wiringPi to put the appropriate GPIO pins in the correct mode (alt5)
> for RXD1/TXD1 (pins 32/33). Also I have used menuconfig to enable the
> 8250/16550 serial port support in the kernel (3.18.5+). After booting the
> image I examined the dmesg output, and it shows following information
> related to 8250/16550:
>
> ..
>
> [   1.010958] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>
> [   1.013920] serial8250.0: ttyS0 at MMIO 0x20215040 (irq = 29, base_baud
> = 7812500) is a 8250
>
> …
>
>
>
> Then I put the pins 32/33 into alternative mode alt5, and try to connect
> to the port /dev/ttyS0 using minicom (baud 115200). Trying to enter
> something into the Mincom terminal does not give any indications on our
> connected oscilloscope (connected to the relevant pins), however change of
> the alt mode earlier was observed correctly. The serial port should not be
> using any flow control, but when trying to disable the flow control using
> Minicom (it was on by default) freezes the complete RaspberryPi system
> (requiring to disconnect and reconnect power).
>
>
>
> Does anyone have any thoughts what could be the cause of these issues
> (e.g., problems with driver etc)? Any information would be greatly
> appreciated. In the project we are working on we would need to use both
> uart ports (0/1) provided by the compute module (the uart0 is a pl011 and
> by disabling console use of /dev/ttyAMA0 we were able to successfully
> connect to that port).
>
>
>
> Thanks for the great work with the Yocto platform.
>
>
>
> Sincerely,
>
> Andreas Enbacka
>
> SW designer
>
> Gasera Ltd
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

[-- Attachment #2: Type: text/html, Size: 4303 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
  2015-06-04 12:31 ` Valentin Le bescond
@ 2015-06-04 12:41   ` Andreas Enbacka
  0 siblings, 0 replies; 6+ messages in thread
From: Andreas Enbacka @ 2015-06-04 12:41 UTC (permalink / raw)
  To: Valentin Le bescond; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]

Hello Valentin,

I used the wiringPi library to put the pins into the alternative mode. 

Regards,
Andreas

> 4 jun 2015 kl. 15:31 skrev Valentin Le bescond <valentin.lebescond@gmail.com>:
> 
> Hi !
> 
> I'm really no expert but am very interested in the subject.
> 
> Did you modify the device tree ? From what I understand in the DT that you'll find pinmux definition right ?
> 
> Regards.
> 
> 
> 2015-06-04 14:01 GMT+02:00 Andreas Enbacka <andreas.enbacka@gasera.fi>:
>> Hello,
>> 
>>  
>> 
>> After a long break, I have returned to the Yocto project, and generally very pleased. A lot of progress has been done since I last used the project (two years ago), and now in my opinion everything works very smoothly.
>> 
>>  
>> 
>> I have used yocto to build a custom image for the RaspberryPi Compute Module. Generally everything works ok, however I am experiencing problem with accessing the UART1 port on the raspberryPi. I am using a library called wiringPi to put the appropriate GPIO pins in the correct mode (alt5) for RXD1/TXD1 (pins 32/33). Also I have used menuconfig to enable the 8250/16550 serial port support in the kernel (3.18.5+). After booting the image I examined the dmesg output, and it shows following information related to 8250/16550:
>> 
>> ..
>> 
>> [   1.010958] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>> 
>> [   1.013920] serial8250.0: ttyS0 at MMIO 0x20215040 (irq = 29, base_baud = 7812500) is a 8250
>> 
>> …
>> 
>>  
>> 
>> Then I put the pins 32/33 into alternative mode alt5, and try to connect to the port /dev/ttyS0 using minicom (baud 115200). Trying to enter something into the Mincom terminal does not give any indications on our connected oscilloscope (connected to the relevant pins), however change of the alt mode earlier was observed correctly. The serial port should not be using any flow control, but when trying to disable the flow control using Minicom (it was on by default) freezes the complete RaspberryPi system (requiring to disconnect and reconnect power).
>> 
>>  
>> 
>> Does anyone have any thoughts what could be the cause of these issues (e.g., problems with driver etc)? Any information would be greatly appreciated. In the project we are working on we would need to use both uart ports (0/1) provided by the compute module (the uart0 is a pl011 and by disabling console use of /dev/ttyAMA0 we were able to successfully connect to that port).
>> 
>>  
>> 
>> Thanks for the great work with the Yocto platform.
>> 
>>  
>> 
>> Sincerely,
>> 
>> Andreas Enbacka
>> 
>> SW designer
>> 
>> Gasera Ltd
>> 
>>  
>> 
>> 
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 

[-- Attachment #2: Type: text/html, Size: 4852 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
  2015-06-04 12:01 [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi) Andreas Enbacka
  2015-06-04 12:31 ` Valentin Le bescond
@ 2015-06-05 15:11 ` Andrei Gherzan
  2015-06-09  7:22   ` Andreas Enbacka
  1 sibling, 1 reply; 6+ messages in thread
From: Andrei Gherzan @ 2015-06-05 15:11 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

Hello Andreas,

I don't have a Compute module to test anything so I'll just say some hints that
might help.

On Thu, Jun 04, 2015 at 03:01:26PM +0300, Andreas Enbacka wrote:
>    Hello,
>
>
>    After a long break, I have returned to the Yocto project, and generally
>    very pleased. A lot of progress has been done since I last used the
>    project (two years ago), and now in my opinion everything works very
>    smoothly.
>
>
>    I have used yocto to build a custom image for the RaspberryPi Compute
>    Module. Generally everything works ok, however I am experiencing
>    problem with accessing the UART1 port on the raspberryPi. I am using a
>    library called wiringPi to put the appropriate GPIO pins in the correct
>    mode (alt5) for RXD1/TXD1 (pins 32/33). Also I have used menuconfig to
>    enable the 8250/16550 serial port support in the kernel (3.18.5+).
>    After booting the image I examined the dmesg output, and it shows
>    following information related to 8250/16550:
>
>    ..
>
>    [   1.010958] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>
>    [   1.013920] serial8250.0: ttyS0 at MMIO 0x20215040 (irq = 29,
>    base_baud = 7812500) is a 8250

You will need to configure the pins before starting the driver. And this can be
done either by messing with the DTS or my compiling the driver as module and
insmod it after you configure the pins.

>    Then I put the pins 32/33 into alternative mode alt5, and try to
>    connect to the port /dev/ttyS0 using minicom (baud 115200). Trying to
>    enter something into the Mincom terminal does not give any indications
>    on our connected oscilloscope (connected to the relevant pins), however
>    change of the alt mode earlier was observed correctly. The serial port
>    should not be using any flow control, but when trying to disable the
>    flow control using Minicom (it was on by default) freezes the complete
>    RaspberryPi system (requiring to disconnect and reconnect power).

I'm not sure about the pin configuration of UART1 function but the
documentation seems to be covering this topic:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2835/BCM2835-ARM-Peripherals.pdf

Hope this helps,

--
Andrei Gherzan


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
  2015-06-05 15:11 ` Andrei Gherzan
@ 2015-06-09  7:22   ` Andreas Enbacka
  2015-08-10  0:10     ` Andrei Gherzan
  0 siblings, 1 reply; 6+ messages in thread
From: Andreas Enbacka @ 2015-06-09  7:22 UTC (permalink / raw)
  To: 'Andrei Gherzan'; +Cc: yocto

Hello Andrei,

I attempted to compile the driver as a module, and ismod it after using
wiringPi to configure the pins for uart1 (bcm pins 32/33), however the
system still freeze (freeze occurs when attempting to close Minicom, and
when attempting to switch off hardware flow control which of some reason is
enabled by default when connecting to /dev/ttyS0). I am using kernel
3.18.5+, could this have some impact? Or could some addresses for uart1
require modifications in the driver?

Best regards,
Andreas Enbacka

-----Original Message-----
From: Andrei Gherzan [mailto:andrei@gherzan.ro] 
Sent: 5. kesäkuuta 2015 18:11
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi] Issue with 8250/16550 UART1 access
in raspberrypi (meta-raspberrypi)

Hello Andreas,

I don't have a Compute module to test anything so I'll just say some hints
that might help.

On Thu, Jun 04, 2015 at 03:01:26PM +0300, Andreas Enbacka wrote:
>    Hello,
>
>
>    After a long break, I have returned to the Yocto project, and generally
>    very pleased. A lot of progress has been done since I last used the
>    project (two years ago), and now in my opinion everything works very
>    smoothly.
>
>
>    I have used yocto to build a custom image for the RaspberryPi Compute
>    Module. Generally everything works ok, however I am experiencing
>    problem with accessing the UART1 port on the raspberryPi. I am using a
>    library called wiringPi to put the appropriate GPIO pins in the correct
>    mode (alt5) for RXD1/TXD1 (pins 32/33). Also I have used menuconfig to
>    enable the 8250/16550 serial port support in the kernel (3.18.5+).
>    After booting the image I examined the dmesg output, and it shows
>    following information related to 8250/16550:
>
>    ..
>
>    [   1.010958] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
>
>    [   1.013920] serial8250.0: ttyS0 at MMIO 0x20215040 (irq = 29,
>    base_baud = 7812500) is a 8250

You will need to configure the pins before starting the driver. And this can
be done either by messing with the DTS or my compiling the driver as module
and insmod it after you configure the pins.

>    Then I put the pins 32/33 into alternative mode alt5, and try to
>    connect to the port /dev/ttyS0 using minicom (baud 115200). Trying to
>    enter something into the Mincom terminal does not give any indications
>    on our connected oscilloscope (connected to the relevant pins), however
>    change of the alt mode earlier was observed correctly. The serial port
>    should not be using any flow control, but when trying to disable the
>    flow control using Minicom (it was on by default) freezes the complete
>    RaspberryPi system (requiring to disconnect and reconnect power).

I'm not sure about the pin configuration of UART1 function but the
documentation seems to be covering this topic:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2835/BCM28
35-ARM-Peripherals.pdf

Hope this helps,

--
Andrei Gherzan



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
  2015-06-09  7:22   ` Andreas Enbacka
@ 2015-08-10  0:10     ` Andrei Gherzan
  0 siblings, 0 replies; 6+ messages in thread
From: Andrei Gherzan @ 2015-08-10  0:10 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

Hello,

On Tue, Jun 09, 2015 at 10:22:52AM +0300, Andreas Enbacka wrote:
> Hello Andrei,
>
> I attempted to compile the driver as a module, and ismod it after using
> wiringPi to configure the pins for uart1 (bcm pins 32/33), however the
> system still freeze (freeze occurs when attempting to close Minicom, and
> when attempting to switch off hardware flow control which of some reason is
> enabled by default when connecting to /dev/ttyS0). I am using kernel
> 3.18.5+, could this have some impact? Or could some addresses for uart1
> require modifications in the driver?
>

That's a bummer. Were you able to fix it in the meanwhile?

--
Andrei Gherzan


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-08-10  0:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-04 12:01 [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi) Andreas Enbacka
2015-06-04 12:31 ` Valentin Le bescond
2015-06-04 12:41   ` Andreas Enbacka
2015-06-05 15:11 ` Andrei Gherzan
2015-06-09  7:22   ` Andreas Enbacka
2015-08-10  0:10     ` Andrei Gherzan

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.