From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "Milan Buška" <milan.buska-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Jetson TX2 and serial console
Date: Tue, 13 Feb 2018 10:50:35 +0000 [thread overview]
Message-ID: <3718cdb9-d929-44a4-d726-ad3c6bc6b627@nvidia.com> (raw)
In-Reply-To: <CAFCWPPLsFit2xL8YCEAV2AQPLSg6C27Jzetw9JvThfwuePUp8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Milan,
On 12/02/18 17:39, Milan Buška wrote:
> Hi Jon,
>
> Use
> USB to TTL Serial Cable - Debug / Console Cable for Raspberry Pi
>
> Jetson TX2 J21 Pin 8 (UART 1 TXD) → Cable RXD (White Wire)
> Jetson TX2 J21 Pin 10 (UART 1 RXD) → Cable TXD (Green Wire)
> Jetson TX2 J21 Pin 9 (GND) → Cable GND (Black Wire)
I believe that you want J17. Can you try connecting the debug cable to
that header?
> Again, I am sorry to be burdening this mailing list with stupid questions
Not at all. This is the correct forum for mainline kernel related
questions. If you have generic Jetson-TX2 or L4T questions then the
right place is here [0].
Cheers
Jon
[0] https://devtalk.nvidia.com/default/board/139/jetson-embedded-systems/
--
nvpublic
next prev parent reply other threads:[~2018-02-13 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFCWPPKe6LW1+Uu40tGz4jzYwHY6MvU2D79HauWxRHOentVq3A@mail.gmail.com>
[not found] ` <CAFCWPPKe6LW1+Uu40tGz4jzYwHY6MvU2D79HauWxRHOentVq3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-12 8:20 ` Jetson TX2 and serial console Jon Hunter
[not found] ` <4e6b2e2a-af20-3bf3-149c-497584b17212-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-12 17:39 ` Milan Buška
[not found] ` <CAFCWPPLsFit2xL8YCEAV2AQPLSg6C27Jzetw9JvThfwuePUp8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-13 10:50 ` Jon Hunter [this message]
[not found] ` <3718cdb9-d929-44a4-d726-ad3c6bc6b627-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-13 14:46 ` Milan Buška
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=3718cdb9-d929-44a4-d726-ad3c6bc6b627@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=milan.buska-Re5JQEeQqe8AvxtiuMwx3w@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