From: Herbert Poetzl <herbert@13thfloor.at>
To: u-boot@lists.denx.de
Subject: Serial console via USB (USBTTY) ...
Date: Thu, 1 Apr 2021 18:17:31 +0200 [thread overview]
Message-ID: <20210401161730.GQ14419@MAIL.13thfloor.at> (raw)
In-Reply-To: <CAHp75VexxAY=1cqzHvcg963Kd-sxyujW3sTr5KkVx2rq5MK1Qg@mail.gmail.com>
Hello Andy!
Thanks for the quick feedback!
On Thu, Apr 01, 2021 at 04:10:57PM +0300, Andy Shevchenko wrote:
> On Thu, Apr 1, 2021 at 2:19 PM Herbert Poetzl <herbert@13thfloor.at> wrote:
>> I'm trying to get a serial console via USB working on
>> STM32MP1 but I'm encountering some problems there ...
>> The u-boot README suggests to add the following config
>> entries to the board specific .h file:
>> CONFIG_USB_DEVICE
>> CONFIG_USB_TTY
>> CONFIG_USBD_HS (for high speed support)
>> CONFIG_SYS_CONSOLE_IS_IN_ENV
>> ... but when doing so, I get a number of linker errors
>> which suggest that there is something missing:
>> https://pastebin.com/raw/bbpCu8jy
>> Marek (via IRC) suggested that this is because the
>> USB_TTY seems to be based on the old gadget framework
>> and needs to be updated to the new one.
> Precisely!
Are there any examples of such a conversion or is there
some guide how to convert drivers from the 'old' framework
to the 'new' one?
>> It was also suggested that a port of the Linux serial
>> function driver would be a good alternative to get
>> CDC/ACM functionality into u-boot and that Andy might
>> already be working on this ...
> I abandoned that, but I can send what I have (it still doesn't
> properly work to me).
Would definitely be interesting to see, as it seems that
other function drivers (those are the f_* ones, as far
as I understood) seem to work just fine.
>> So my questions are:
>> - What is currently the best/easiest approach to
>> get a serial console via USB working?
> Create a support for it.
> You may consider it as there is no support.
Okay, how do I best start with that?
>> - Is the port from Linux in a stage that it can
>> be tested and/or finalized within a easonable
>> amount of time?
> Not from me (I started but encountered so many issues here and
> there, besides the fact that it's really time consuming).
I understand ...
>> - Can I help getting this working?
> If you do it yourself. I can help with testing on my platform.
Great! Thanks in advance!
Best,
Herbert
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2021-04-01 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 11:19 Serial console via USB (USBTTY) Herbert Poetzl
2021-04-01 13:10 ` Andy Shevchenko
2021-04-01 16:17 ` Herbert Poetzl [this message]
2021-04-01 16:36 ` Andy Shevchenko
2021-04-01 18:45 ` Herbert Poetzl
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=20210401161730.GQ14419@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--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