From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] A20-olinuxino-micro hangs in U-boot if powered from MINI-USB only.
Date: Fri, 28 Dec 2018 01:20:14 +0300 [thread overview]
Message-ID: <5C25501E.5020906@yandex.ru> (raw)
In-Reply-To: <2015861864.15538610.1545943686958@mail.yahoo.com>
Hi,
27.12.2018 23:48, 'John S' via linux-sunxi:
>> Well, IMHO is has to do with Olimex because they designed this specific
>> circuitry, and the circuitry is such that 5V voltage constantly applied
>> to the micro-usb connector might essentially become disconnected (at the
>> board side) by programming -- if I understood it correctly.
>
> The software needs to be responsible for its own actions.
Sure, ideally. That's why I reported.
> Does the problem you reported occur with the Olimex image(s)? If so it may be wise to report it to Olimex.
I can't say about Olimex images at the moment because I switched to more
current (alternative) images and subsequently to mainline openwrt and
the board is already mounted for intended operation. Maybe I do some
experiments later. I'd like to clarify, I don't blame Olimex, they are
nice. Keeping close to mainline is not always easy.
> If not, which commit or change caused it?
Again, I can't say at the moment. Not even sure if it could be fixed on
the software side.
> BTW I read in the Olimex documentation that best practice is to power it differently than the way you mention.
Yes, that is true.
But powering through mini-usb is so wonderfully handy!
Thank you,
Regards,
Nikolai
> John
>
prev parent reply other threads:[~2018-12-27 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 22:04 [U-Boot] A20-olinuxino-micro hangs in U-boot if powered from MINI-USB only Nikolai Zhubr
2018-12-24 17:32 ` [U-Boot] [linux-sunxi] " Diego Roversi
2018-12-24 19:27 ` Nikolai Zhubr
2018-12-24 19:54 ` John S
2018-12-24 21:54 ` Nikolai Zhubr
2018-12-27 20:48 ` John S
2018-12-27 22:20 ` Nikolai Zhubr [this message]
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=5C25501E.5020906@yandex.ru \
--to=n-a-zhubr@yandex.ru \
--cc=u-boot@lists.denx.de \
/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