Max Filippov

Can you share the images that were flashed? Specifically `build/build-buildroot-esp32s3/images/*`

> These were the files generated by the build script > I built the linux for it and flashed it (accordingly for the USB serial to work with some modification...

[etc.jffs2.txt](https://github.com/user-attachments/files/15816549/etc.jffs2.txt) Also while testing it I've noticed that the jffs2 parser has been ignoring the first file on the file system, which happened to be the cmdline. I've pushed a...

> stuck at some other stage It's about the time when the kernel should start accessing flash. Let me take a look at that.

Could you try flashing the following kernel image and post its output: [xipImage.txt](https://github.com/user-attachments/files/15841690/xipImage.txt) That kernel has debug logging in the flash partition table parser and ipc code.

> The output after flashing the kernel image is the following: > ``` > [ 3.316678] esp32-ipc 600c0004.ipc: init_hw: queue 0: offset = -1024, mask = 3f > [ 3.320481]...

I used the following command: `parttool.py -b 2000000 write_partition --partition-name factory --input network_adapter.bin`

> Here is the output of the bootlogs after flashing that .bin file onto the board. Hmmm, puzzling. Could you please repeat it with the following [network_adapter.bin.txt](https://github.com/user-attachments/files/15899618/network_adapter.bin.txt)? It has some...

Hmmm… Even more puzzling. Just to make sure: nothing else appears if you wait a few more seconds after the line `[ 3.373631] esp32_ipc_tx: q->read = 0, q->write = 0`...

Is this output in chronological order, or is this a screen copy? `E (34138)` suggests that it happened 34 seconds after the boot, but there's no matching `E (34138) linux_ipc:...