new esp32-s3 misbehaving

[atx823]

I have a new s3 breakout board which I made. I can program it successfully using an ftdi usb adapter, but after reboot I get a couple of boot messages and then just lot of invalid header errors: "invalid header: 0xa5ff005a".

Anyone have any ideas or debugging suggestions?

The output is as follows:

Code: Select all

...
[100%] Built target gen_project_binary
RmtStepTest.bin binary size 0x37ab0 bytes. Smallest app partition is 0x100000 bytes. 0xc8550 bytes (78%) free.
[100%] Built target app_check_size
[100%] Built target app
esptool esp32s3 -p /dev/ttyUSB0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 2MB 0x10000 RmtStepTest.bin
esptool.py v4.4
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: f6:42:fa:e1:5b:f8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00010000 to 0x00047fff...
Compressed 228016 bytes to 119434...
Writing at 0x00010000... (12 %)
Writing at 0x0001d154... (25 %)
Writing at 0x00022edb... (37 %)
Writing at 0x00029351... (50 %)
Writing at 0x0002f037... (62 %)
Writing at 0x00037eca... (75 %)
Writing at 0x0003fdd3... (87 %)
Writing at 0x00045a8e... (100 %)
Wrote 228016 bytes (119434 compressed) at 0x00010000 in 2.9 seconds (effective 628.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
[100%] Built target app-flash
Done
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
...

Then the invalid header line repeats indefinitely. I tried reading the chip id with esptool.py, and got this:

Code: Select all

$ esptool.py --trace chip_id
esptool.py v4.4
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting...TRACE +0.000 command op=0x08 data len=36 wait_response=1 timeout=0.100 data=
    0707122055555555 5555555555555555 | ... UUUUUUUUUUUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    55555555                          | UUUU
TRACE +0.000 Write 46 bytes: 
    c000082400000000 0007071220555555 | ...$........ UUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    5555555555555555 5555555555c0     | UUUUUUUUUUUUU.
TRACE +0.000 Read 2 bytes: 3561
TRACE +0.000 Read invalid data: 3561
TRACE +0.000 Remaining data in serial buffer: 
.TRACE +0.051 command op=0x08 data len=36 wait_response=1 timeout=0.100 data=
    0707122055555555 5555555555555555 | ... UUUUUUUUUUUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    55555555                          | UUUU
TRACE +0.000 Write 46 bytes: 
    c000082400000000 0007071220555555 | ...$........ UUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    5555555555555555 5555555555c0     | UUUUUUUUUUUUU.
TRACE +0.000 Read 2 bytes: 6630
TRACE +0.000 Read invalid data: 6630
TRACE +0.000 Remaining data in serial buffer: 
.TRACE +0.050 command op=0x08 data len=36 wait_response=1 timeout=0.100 data=
    0707122055555555 5555555555555555 | ... UUUUUUUUUUUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    55555555                          | UUUU
TRACE +0.000 Write 46 bytes: 
    c000082400000000 0007071220555555 | ...$........ UUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    5555555555555555 5555555555c0     | UUUUUUUUUUUUU.
TRACE +0.000 Read 2 bytes: 6572
TRACE +0.000 Read invalid data: 6572
...

[ESP_Sprite]

I think you're only flashing the app, and not the bootloader. If your S3 is new, it won't have a proper 2nd stage bootloader in flash. If this is an ESP-IDF project, you can fix this by running 'idf.py flash'.

[atx823]

Yes, that was it.

Many thanks!