From: Roberto Alejandro Espi Munoz <raespi@icid.cu>
To: barebox@lists.infradead.org
Subject: Re: serial port weird chars ...
Date: Fri, 07 Aug 2015 15:03:52 -0400 [thread overview]
Message-ID: <55C50118.3080202@icid.cu> (raw)
In-Reply-To: <20150807194104.b02642e26c441e906a1deeca@gmail.com>
Both scenarios work well on another host. On my host serial port when
interacting with one bootloader the communication is fine and with
barebox fails. When using a USB-serial adapter there's no problem.
Perhaps there's a problem on my board but why does the first connection
work and with barebox doesn't ?
On 08/07/2015 12:41 PM, Antony Pavlov wrote:
> On Fri, 07 Aug 2015 10:41:12 -0400
> Roberto Alejandro Espi Munoz <raespi@icid.cu> wrote:
>
>> Hi ... I'm currently having some trouble with displaying characters
>> correctly in my terminal. I'm using a board equivalent to the
>> mini2440. This one has a NOR and a NAND. I connect to it over a serial
>> port interface. When I boot up the board in debug mode I'm able to see
>> clearly the messages displayed by the S3C2440A USB Downloader which is
>> copied in the NOR interface, I then download my barebox binary over the
>> USB interface and when it boots I get a lot of weird characters on
>> screen. The console seems to respond correctly, I issue for example the
>> "reset" command and it resets but I can't make out what is displayed.
>> I was guessing at first a serial port configuration problem on my
>> operating system (I use Linux), tried it over on Windows and same
>> effect, the first bootloader works great and barebox when starting just
>> mangles the characters.
>>
>> The other weird problem is than when I use a USB-Serial converter to
>> connect to the board's serial port everything works !
>>
>> I'm currently using barebox 2012.09 and OpenSuse Linux 13.2
>>
>> Any ideas ? thanks
> You have the problem if you use your host computer motherboard serial port (no matter, Linux or Windows),
> isn't it?
> And no problem if you use USB-Serial dongle. So it looks like host serial port problem.
>
> Could you try to connect the board to another host computer?
>
> --
> Best regards,
> Antony Pavlov
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-08-07 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 14:41 serial port weird chars Roberto Alejandro Espi Munoz
2015-08-07 16:41 ` Antony Pavlov
2015-08-07 19:03 ` Roberto Alejandro Espi Munoz [this message]
2015-08-08 15:23 ` Antony Pavlov
2015-08-10 12:16 ` Roberto Alejandro Espi Munoz
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=55C50118.3080202@icid.cu \
--to=raespi@icid.cu \
--cc=barebox@lists.infradead.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 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.