From: Andrei Gherzan <andrei@gherzan.ro>
To: Andreas Enbacka <andreas.enbacka@gasera.fi>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] Issue with 8250/16550 UART1 access in raspberrypi (meta-raspberrypi)
Date: Fri, 5 Jun 2015 17:11:29 +0200 [thread overview]
Message-ID: <20150605151129.GF1829@gmail.com> (raw)
In-Reply-To: <001701d09ebe$2f3a5030$8daef090$@gasera.fi>
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
next prev parent reply other threads:[~2015-06-05 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-06-09 7:22 ` Andreas Enbacka
2015-08-10 0:10 ` Andrei Gherzan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150605151129.GF1829@gmail.com \
--to=andrei@gherzan.ro \
--cc=andreas.enbacka@gasera.fi \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.