LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: Sebastian Reichel <sre@kernel.org>,
	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 23:13:47 +0100	[thread overview]
Message-ID: <20180321221346.GA18313@amd> (raw)
In-Reply-To: <20180321215733.GE5799@atomide.com>

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

On Wed 2018-03-21 14:57:33, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.cz> [180321 20:32]:
> > 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 ;)
> > 
> > Hm. How big no-no is connecting USB-TTL adapter to D+/D- pins? Because
> > that's what I could do "easily" and seems to work ;-).
> 
> Well if the VBUS line is not connected the PMIC is muxed
> to USB carkit mode so the lines go to the UART on the SoC
> through some level shifter. If it works it should not cause
> any issues, the symptoms I saw earlier was corrupted UART
> console and noticed that what worked best for me was 3.3V
> ftdi based devices out of the collection of random pl2303
> and ftdi cables I had around.

So.. I do have some fun on the UART (^@ inserted).

> I guess somebody could try to measure the uart lines with
> a scope with nothing connected and sending out data from
> droid 4. Or look at the carkit spec for the UART voltage
> levels.

Voltmeter says Droid4 transmits at 3.3V.

Anyway, it now works for me well enough that I can attempt to debug
the .config file :-).
									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 --]

  reply	other threads:[~2018-03-21 22:13 UTC|newest]

Thread overview: 11+ 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-20 14:03 ` Tony Lindgren
2018-03-20 17:00   ` Sebastian Reichel
2018-03-21 19:32     ` Pavel Machek
2018-03-21 20:31     ` Pavel Machek
2018-03-21 21:57       ` Tony Lindgren
2018-03-21 22:13         ` Pavel Machek [this message]
2018-03-27 21:21     ` Pavel Machek
2018-03-30 12:19       ` Sebastian Reichel
2018-03-30 21:17         ` Pavel Machek
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=20180321221346.GA18313@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).