seisatsu / EpilogueOS

An ESP32 linux-remeniscient shell and operating system based on MicroPython, with LoRa mesh-networking as its ultimate goal.
MIT License
3 stars 0 forks source link

Resolve initial serial port garbage on the Arduino serial monitor #14

Open pmer opened 2 years ago

pmer commented 2 years ago

One possibility could be that it's caused by the ESP32 bootloader emitting a message at 115200 baud.

Connecting to the serial port with 115200 and changing Serial.begin(9600) to Serial.begin(115200) in void setup () fixes the issue for me.

Resources:

Serial output I am seeing after making this change:

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1420
ho 0 tail 12 room 4
load:0x40078000,len:13540
load:0x40080400,len:3604
entry 0x400805f0
uLisp 4.0 
7900>

@seisatsu, how about you for?

seisatsu commented 2 years ago

I am also seeing mention of the bootloader always outputting at 115200 baud, but with the serial monitor at 115200 baud, I just get way more garbage, regardless of the value in Serial.begin(). Also is GNU Screen hanging for you whenever you try to connect from it?

pmer commented 2 years ago

What do you experience when you say that GNU Screen hangs?

I am always able to quit Screen safely via its Ctrl-A, k command, but sometimes for me the ESP32 hangs—it stops responding to any serial terminals, Screen or not.

seisatsu commented 2 years ago

Actually I think I just didn't know the correct command. I do experience the total hanging sometimes, which is going to be a serious issue we will probably require GDB to solve.

seisatsu commented 2 years ago

I'm actually not getting the garbage when connecting from Windows, but I'm not getting a prompt either until I send a line. For that problem I opened #19.