From: Mikko Perttunen <mikko.perttunen-/1wQRMveznE@public.gmane.org>
To: Marcel Ziswiler <marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: [Resend] SHIELD (tegra114-roth) Serial Console UART
Date: Sat, 14 Feb 2015 00:20:49 +0200 [thread overview]
Message-ID: <54DE78C1.9080103@kapsi.fi> (raw)
In-Reply-To: <54DE775B.4020409-/1wQRMveznE@public.gmane.org>
On 02/14/2015 12:14 AM, Mikko Perttunen wrote:
> On 02/14/2015 12:04 AM, Marcel Ziswiler wrote:
>>
>>
>> Hi there
>>
>> Does by any chance anybody know how one can get a serial console UART
>> on SHIELD (tegra114-roth)? I know there is some kind of a debug
>> connector inside [1] similar to e.g. the one found on Cardhu albeit
>> not assembled of course but is that pinout standardized?
>>
>> [1] https://d3nevzfk7ii3be.cloudfront.net/igi/TTSTtfTvwlwWfbhR.huge
>>
>> Cheers
>>
>> Marcel
>
> I remember the actual debug pads being on the bottom side of the board
> on the right side of the SoC (i.e., right of the green rectangle on your
> picture).
Actually, I am tired and confused about the orientation of things; but
anyway on the bottom side, which makes access difficult.
If you go that way, someone @nvidia.com can probably look up
> the UART pads for you. However, another way (that I used briefly) is to
> grab one of these:
> http://store.r0ck.me/products/usd-breakout-board
> and with some pinmux editing get a 3V3 serial port out of the microSD slot.
>
> Cheers,
> Mikko
>
>
next prev parent reply other threads:[~2015-02-13 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ABAE5648-C477-451F-ACF6-6314C8B198DB@ziswiler.com>
[not found] ` <ABAE5648-C477-451F-ACF6-6314C8B198DB-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
2015-02-13 22:04 ` [Resend] SHIELD (tegra114-roth) Serial Console UART Marcel Ziswiler
[not found] ` <61E1CB06-407A-4F7E-B5D9-BCFA8B2CCE99-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
2015-02-13 22:14 ` Mikko Perttunen
[not found] ` <54DE775B.4020409-/1wQRMveznE@public.gmane.org>
2015-02-13 22:20 ` Mikko Perttunen [this message]
2015-02-14 3:40 ` Alexandre Courbot
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=54DE78C1.9080103@kapsi.fi \
--to=mikko.perttunen-/1wqrmvezne@public.gmane.org \
--cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox