From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Reichel <sre@kernel.org>
Cc: mpartap@gmx.net, Tony Lindgren <tony@atomide.com>,
kernel list <linux-kernel@vger.kernel.org>,
nekit1000@gmail.com, linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: 4.16-rc5 on Motorola Droid 4
Date: Wed, 21 Mar 2018 20:32:26 +0100 [thread overview]
Message-ID: <20180321193225.GA20561@amd> (raw)
In-Reply-To: <20180320170029.rv3u5wlvqxfl7z2v@earth.universe>
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
Hi!
> > Maybe get somebody to help you locally with the debug cable
> > soldering? :)
>
> I suppose people from your hackerspace can help you. It's really
> easy to do. Soldering can be avoided btw. You can just use a pair
> of scissors to cut a USB -> Micro USB cable and use a knife to remove
> isolation. Then screw each of the 4 wires into a terminal strip.
> There are USB-TTL adapters available, that have an attached cable.
> If you also cut the connector from such a cable and connect it to
> the other side of the terminal strip you are done. No soldering
> involved ;)
Hehe. After some more experiments, it looks like hardware hacking can
not be avoided :-(.
I should have enough connectors, but I don't know the pinouts. I also
seem to have D-SUN USB to TTL from you (thanks again!).
You say TTL, Tony says 3V3... so I guess the port can survive both?
Ok, I guess I really only need to connect GND, and then D- to RXD?
So... where is the D-.. aha, got it. I hope USB has to be robust
enough against me making experiments?
I connected it the best way I could, but I do not get data in minicom,
and RXD led stays lit. I guess that is not a good thing :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.16-rc5 on Motorola Droid 4
Date: Wed, 21 Mar 2018 20:32:26 +0100 [thread overview]
Message-ID: <20180321193225.GA20561@amd> (raw)
In-Reply-To: <20180320170029.rv3u5wlvqxfl7z2v@earth.universe>
Hi!
> > Maybe get somebody to help you locally with the debug cable
> > soldering? :)
>
> I suppose people from your hackerspace can help you. It's really
> easy to do. Soldering can be avoided btw. You can just use a pair
> of scissors to cut a USB -> Micro USB cable and use a knife to remove
> isolation. Then screw each of the 4 wires into a terminal strip.
> There are USB-TTL adapters available, that have an attached cable.
> If you also cut the connector from such a cable and connect it to
> the other side of the terminal strip you are done. No soldering
> involved ;)
Hehe. After some more experiments, it looks like hardware hacking can
not be avoided :-(.
I should have enough connectors, but I don't know the pinouts. I also
seem to have D-SUN USB to TTL from you (thanks again!).
You say TTL, Tony says 3V3... so I guess the port can survive both?
Ok, I guess I really only need to connect GND, and then D- to RXD?
So... where is the D-.. aha, got it. I hope USB has to be robust
enough against me making experiments?
I connected it the best way I could, but I do not get data in minicom,
and RXD led stays lit. I guess that is not a good thing :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180321/7dfb02ce/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Reichel <sre@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, nekit1000@gmail.com, mpartap@gmx.net
Subject: Re: 4.16-rc5 on Motorola Droid 4
Date: Wed, 21 Mar 2018 20:32:26 +0100 [thread overview]
Message-ID: <20180321193225.GA20561@amd> (raw)
In-Reply-To: <20180320170029.rv3u5wlvqxfl7z2v@earth.universe>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Hi!
> > Maybe get somebody to help you locally with the debug cable
> > soldering? :)
>
> I suppose people from your hackerspace can help you. It's really
> easy to do. Soldering can be avoided btw. You can just use a pair
> of scissors to cut a USB -> Micro USB cable and use a knife to remove
> isolation. Then screw each of the 4 wires into a terminal strip.
> There are USB-TTL adapters available, that have an attached cable.
> If you also cut the connector from such a cable and connect it to
> the other side of the terminal strip you are done. No soldering
> involved ;)
Hehe. After some more experiments, it looks like hardware hacking can
not be avoided :-(.
I should have enough connectors, but I don't know the pinouts. I also
seem to have D-SUN USB to TTL from you (thanks again!).
You say TTL, Tony says 3V3... so I guess the port can survive both?
Ok, I guess I really only need to connect GND, and then D- to RXD?
So... where is the D-.. aha, got it. I hope USB has to be robust
enough against me making experiments?
I connected it the best way I could, but I do not get data in minicom,
and RXD led stays lit. I guess that is not a good thing :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-03-21 19:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 22:04 4.16-rc5 on Motorola Droid 4 Pavel Machek
2018-03-18 22:04 ` Pavel Machek
2018-03-20 14:03 ` Tony Lindgren
2018-03-20 14:03 ` Tony Lindgren
2018-03-20 17:00 ` Sebastian Reichel
2018-03-20 17:00 ` Sebastian Reichel
2018-03-21 19:32 ` Pavel Machek [this message]
2018-03-21 19:32 ` Pavel Machek
2018-03-21 19:32 ` Pavel Machek
2018-03-21 20:31 ` Pavel Machek
2018-03-21 20:31 ` Pavel Machek
2018-03-21 21:57 ` Tony Lindgren
2018-03-21 21:57 ` Tony Lindgren
2018-03-21 22:13 ` Pavel Machek
2018-03-21 22:13 ` Pavel Machek
2018-03-27 21:21 ` Pavel Machek
2018-03-27 21:21 ` Pavel Machek
2018-03-30 12:19 ` Sebastian Reichel
2018-03-30 12:19 ` Sebastian Reichel
2018-03-30 21:17 ` Pavel Machek
2018-03-30 21:17 ` Pavel Machek
2018-03-31 0:40 ` Sebastian Reichel
2018-03-31 0:40 ` Sebastian Reichel
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=20180321193225.GA20561@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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.