Skip to content

selfmade kczip from foreign .bin file throws warnings #5

Description

@Flittermelint

Hi,

currently working on two projects building Powershell modules for communication with an ESP32 and ESP32S3 I stumbled upon this cool project.
I tried to find out how to build a kczip and could manage it, but loading throws a few warnings:

14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Extracting partition table from the archive...
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Partition table file found: partition-table.bin
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition table...
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=1, Subtype=2, Address=9000, Size=5000, Name=nvs
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=1, Subtype=0, Address=E000, Size=2000, Name=otadata
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=0, Subtype=16, Address=10000, Size=140000, Name=app0
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=0, Subtype=17, Address=150000, Size=140000, Name=app1
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=1, Subtype=130, Address=290000, Size=160000, Name=spiffs
14/04/2025 21:47:35 [Debug] ESP_Flasher.Services.PartitionTableExtractor: Parsing partition entry from raw data.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Parsed partition entry: Type=1, Subtype=3, Address=3F0000, Size=10000, Name=coredump
14/04/2025 21:47:35 [Warning] ESP_Flasher.Services.PartitionTableExtractor: Invalid partition entry detected, skipping...
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Reached end of partition table.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.PartitionTableExtractor: Partition table parsing completed successfully.
14/04/2025 21:47:35 [Warning] ESP_Flasher.Services.AppHeaderExtractor: Invalid magic word found in app header.
14/04/2025 21:47:35 [Warning] ESP_Flasher.Services.AppHeaderExtractor: Invalid magic byte found in app header.
14/04/2025 21:47:35 [Warning] ESP_Flasher.Services.AppHeaderExtractor: Invalid magic byte found in app header.
14/04/2025 21:47:35 [Information] ESP_Flasher.Services.AppHeaderExtractor: App header found in firmware.bin

Debugging led me to the following values

PartitionTableExtractor.cs line 80
buffer =
0xeb,0xeb,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,
0x97,0x2d,0xae,0x2f,0xf8,0x72,0xa0,0x14,0x2d,0x60,0xba,0xd1,0x24,0xc0,0x66,0x6b

AppHeaderExtractor.cs line 91 > header.MagicWord = 4294967295 (0xFFFFFFFF)
AppHeaderExtractor.cs line 64 > header.Magic = 170 (0xAA)
AppHeaderExtractor.cs line 64 > header.Magic = 1 (0x01)

I'm unsure if I should try to flash the .bin file anyway, but I want to avoid bricking the device ;-)

Any help is greatly appreciated. And if I can help with further debugging, please let me know...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions