unexpected eof error

Toit

#unexpected eof error

Thread channel in help

~~boss~~ 07/20/2025 10:53 AM

this showed up when i run jag monitor

~~boss~~ 07/20/2025 10:53 AM

PS C:\Users\bossc\toit> jag monitor -a
Starting serial monitor of port 'COM3' ...
Error: unexpected EOF

~~boss~~ 07/20/2025 10:54 AM

i tried resetting it but it didnt work

OP~~boss~~

PS C:\Users\bossc\toit> jag monitor -a
Starting serial monitor of port 'COM3' ...
Error: unexpected EOF

floitsch 07/25/2025 07:51 AM

A few things to look at:
- did the same setup already work before, or does it work with a different esp32?
- is the USB cable of good quality? Unfortunately a very common issue.
- is the port correct? If you unplug the esp32, does 'COM3' disappear?
- if connected through a USB hub, try to connect directly.
- if this is an ESP with built-in USB (C3, S3, ...) it might need an envelope with USB support.

~~boss~~ 07/26/2025 10:16 AM

it think it was probably cable ploblem,buying new cable.

~~boss~~ 07/29/2025 02:13 AM

i have just bought new cable but nothing changed

~~boss~~ 07/29/2025 02:22 AM

my observation is that i can run code on it but when i tried to monitor it code stops immediately

OP~~boss~~

my observation is that i can run code on it but when i tried to monitor it code stops immediately

floitsch 07/29/2025 04:22 AM

Running code is done via WiFi, so that's unaffected by the UART.

Can you flash the device?

~~boss~~ 08/01/2025 05:07 AM

i already did but still the same error

~~boss~~ 08/01/2025 05:07 AM

and it used to work as normal last month(edited)

floitsch 08/01/2025 10:28 AM

The question was mainly if the serial port works for flashing.

Not that a jag monitor automatically resets the device. You can use -a (attach) to avoid that.

~~boss~~ 08/01/2025 01:06 PM

PS C:\Users\bossc\toit> jag monitor -a
Starting serial monitor of port 'COM3' ...
Error: unexpected EOF

floitsch 08/01/2025 01:07 PM

So this is a normal esp32 that you can flash on this port, but you can't use monitor on it?

~~boss~~ 08/01/2025 01:08 PM

yes

floitsch 08/01/2025 01:09 PM

I have never seen this...
Could you try with the esp-idf to see if it works there?

~~boss~~ 09/01/2025 09:43 AM

ok,but how can i use toit on esp-idf?

~~boss~~ 09/01/2025 09:44 AM

and i just bought new esp but its still the same error

floitsch 09/01/2025 09:46 AM

You can't.
Fundamentally, we are trying to figure out what's going wrong.
There are two things we can try:
- use idf.py monitor instead of jag monitor.
- use esp-idf on its own, without Toit.
That would exclude things.

floitsch 09/01/2025 09:46 AM

I'm also thinking of reasons for why things don't work.
Could it be that you have another program (like Arduino IDE), ... that tries to grab the port?(edited)

floitsch 09/01/2025 09:47 AM

Maybe, on Windows, another program can steal the uart port.

floitsch

I'm also thinking of reasons for why things don't work. Could it be that you have another program (like Arduino IDE), ... that tries to grab the port?(edited)

~~boss~~ 09/01/2025 09:47 AM

no i doesnt.i ran only vscode

floitsch 09/01/2025 09:48 AM

also try jag monitor -a.

floitsch 09/01/2025 09:49 AM

That doesn't reset the board.

floitsch 09/01/2025 09:49 AM

Just to see if that makes a difference.

~~boss~~ 09/01/2025 09:50 AM

PS C:\Users\bossc> jag monitor -a
Starting serial monitor of port 'COM5' ...
Error: unexpected EOF

floitsch 09/01/2025 09:51 AM

it looks like jag monitor just can't read data from the device, or the port is reset frequently.

floitsch 09/01/2025 09:51 AM

can you flash the device normally with Jaguar?

~~boss~~ 09/01/2025 09:52 AM

yes

floitsch 09/01/2025 09:54 AM

https://www.serialterminal.com/

floitsch 09/01/2025 09:54 AM

Try this page.

floitsch 09/01/2025 09:54 AM

Change the baudrate to 115200

floitsch 09/01/2025 09:54 AM

Then connect.

floitsch 09/01/2025 09:54 AM

Press the reset button on the device, to make sure some output should be visible.

floitsch 09/01/2025 09:55 AM

~~boss~~ 09/01/2025 09:55 AM

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2810,len:0xdc
load:0x403c8700,len:0x4
load:0x403c8704,len:0xa08
load:0x403cb700,len:0x257c
entry 0x403c8854
E (325) quad_psram: PSRAM ID read error: 0x00ffffff, PSRAM chip not found or not supported, or wrong PSRAM line mode
E (325) esp_psram: PSRAM enabled but initialization failed. Bailing out.
[toit] INFO: starting 
[toit] DEBUG: clearing RTC memory: invalid checksum
[toit] INFO: running on ESP32S3 - revision 0.2
[wifi] DEBUG: connecting
[wifi] INFO: retrying {reason: expired authentication}
[wifi] DEBUG: connected

floitsch 09/01/2025 09:55 AM

Interesting.

floitsch 09/01/2025 09:56 AM

So this really is a program with Jaguar (and thus the Go UART library).

floitsch 09/01/2025 09:56 AM

which version do you use?

floitsch

which version do you use?

~~boss~~ 09/01/2025 09:57 AM

the toit?

floitsch 09/01/2025 09:57 AM

yes. Jaguar.

~~boss~~ 09/01/2025 09:57 AM

Version:         v1.53.0
SDK version:     v2.0.0-alpha.184
Build date:      2025-06-03T07:57:41Z

floitsch 09/01/2025 09:58 AM

I think we have released a newer one in the meantime.

floitsch 09/01/2025 09:58 AM

Could you try to update and see if that changes things?

~~boss~~ 09/01/2025 10:01 AM

PS C:\Users\bossc> jag firmware update
Failed to ping 'vast-bridge'.
Scanning for device with ID: '8cdf1898-9989-4d3c-8fc9-1cc51f740dc1'
v silly-proposal (address: http://192.168.1.180:9000, 32-bit)
Updating firmware on 'silly-proposal' to Toit SDK v2.0.0-alpha.184

   100%  1474k  |  [################### Jaguar #######################]

~~boss~~ 09/01/2025 10:02 AM

why does the version doesnt change?

floitsch 09/01/2025 10:03 AM

winget upgrade --id=Toit.Jaguar -e

floitsch 09/01/2025 10:03 AM

jag firmware update

only updates the device with the firmware of the current Jaguar.

floitsch 09/01/2025 10:03 AM

So once you have done a Jaguar update you will need to run the firmware update.

~~boss~~ 09/01/2025 10:11 AM

updated still the same.

floitsch 09/01/2025 10:12 AM

ok.

floitsch 09/01/2025 10:12 AM

I don't have any windows machine to test right now, but I will try to find one.
In the meantime just use the web-page as a work-around.

floitsch 09/01/2025 10:12 AM

It's not perfect, as it won't automatically decode stack-traces, but that shouldn't be a huge blocker.

floitsch 09/01/2025 10:13 AM

What's the version of your Windows?

~~boss~~ 09/01/2025 10:13 AM

windows 11

~~boss~~ 09/04/2025 11:47 AM

I have just discovered new info , the error only occurs to my pc other pc just works as normal

floitsch 09/04/2025 12:14 PM

On the general chat someone else reported that it worked for them.

floitsch 09/04/2025 12:14 PM

Very curious.

57 messages in total