Strange characters with picocom

General discussions and questions abound development of code with MicroPython that is not hardware specific.
Target audience: MicroPython Users.
Post Reply
User avatar
nebenzahl
Posts: 26
Joined: Mon Jul 01, 2019 5:38 pm
Location: Uruguaiana, Brazil
Contact:

Strange characters with picocom

Post by nebenzahl » Mon Mar 02, 2020 12:12 pm

Hi!
I need help with a problem.
I am using a D1 R32 board, it is the one that has the shape identical to an Arduino UNO.
I work on Arch Linux, and use Picocom to receive the results of the serial output.
Everything was fine, until the exit became unreadable with strange characters.

W (6�) cpu_start: +
�revisionq.B����Ɂthan����one config]�J��menucϙ��� Suggest �o upgrade it�5
A�(631) cpu_st�r�: Starting s�heduler on PRo�CPU.
�A�I��J����� pJUe�NULL��,��ձ�Ɂon PAU�
b'AT+CCALR?|�RH�Uɥ�����c�l�..

Use the command:

picocom / dev / ttyUSB0 -b 115200

But when I use the ESP32 MCU card, the output from the serial terminal is correct.

What could be happening?
Eng. Luiz Nebenzahl

User avatar
Roberthh
Posts: 3667
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: Strange characters with picocom

Post by Roberthh » Mon Mar 02, 2020 2:06 pm

I got output like yours with some boards (or to be more precise: with some USB/UART bridges) when using an USB hub. If that applies for you too, try a direct connection to your PC.

User avatar
nebenzahl
Posts: 26
Joined: Mon Jul 01, 2019 5:38 pm
Location: Uruguaiana, Brazil
Contact:

Re: Strange characters with picocom

Post by nebenzahl » Mon Mar 02, 2020 6:15 pm

Trying to solve the problem, I installed Ubuntu on a Virtual Machine inside my Arch Linux.
And to my surprise, in Ubuntu, in a Terminal, I ran Picocom, and it worked without problems.
So I think it's not a hardware problem, it could be something with Arch's USB driver.
What can it be then?
Eng. Luiz Nebenzahl

User avatar
nebenzahl
Posts: 26
Joined: Mon Jul 01, 2019 5:38 pm
Location: Uruguaiana, Brazil
Contact:

Re: Strange characters with picocom

Post by nebenzahl » Mon Mar 02, 2020 6:51 pm

I found the problem.
The CH340 chip, which the D1 card uses, had a problem with the 5.5 kernel module that now uses the CH341.
I upgraded my kernel to 5.6 and even using the CH341 module, communication has improved.
Eng. Luiz Nebenzahl

Post Reply