2.0.4 build successfull but with error...

[abortega]

hi... just want to know if this is okay or normal? the build was successfull and stored in build folder as XIAOZHI.BIN... but during the build process there was an error or warning... and i notice the filesize is only 2478kb... compare to the one i donwload here at github the merege-binary.bin is 8743kb... is it okay to flash the xiaozhi.bin??? thanks so much...

C:/Espressif/frameworks/esp-idf-v5.5.1/components/lwip/lwip/src/include/lwip/sockets.h:419:9: note:this is the location of the previous definition
419 | #define _IO(x,y) ((long)(IOC_VOID|((x)<<8)|(y)))
| ^~~
C:/Espressif/frameworks/esp-idf-v5.5.1/xiaozhi-esp32/managed_components/espressif__esp_video/include/linux/ioctl.h:55:9: warning: "_IOR" redefined
55 | #define _IOR(type,nr,size) _IOC(_IOC_READ,(type),(nr),(_IOC_TYPECHECK(size)))
| ^~~~
C:/Espressif/frameworks/esp-idf-v5.5.1/components/lwip/lwip/src/include/lwip/sockets.h:421:9: note:this is the location of the previous definition
421 | #define _IOR(x,y,t) ((long)(IOC_OUT|((sizeof(t)&IOCPARM_MASK)<<16)|((x)<<8)|(y)))
| ^~~~
C:/Espressif/frameworks/esp-idf-v5.5.1/xiaozhi-esp32/managed_components/espressif__esp_video/include/linux/ioctl.h:56:9: warning: "_IOW" redefined
56 | #define _IOW(type,nr,size) _IOC(_IOC_WRITE,(type),(nr),(_IOC_TYPECHECK(size)))
| ^~~~
C:/Espressif/frameworks/esp-idf-v5.5.1/components/lwip/lwip/src/include/lwip/sockets.h:423:9: note:this is the location of the previous definition
423 | #define _IOW(x,y,t) ((long)(IOC_IN|((sizeof(t)&IOCPARM_MASK)<<16)|((x)<<8)|(y)))

[78]

These warnings exist in the IDF 5.5. It seems your firmware is successfully built. You can use the follow command to flash the firmware:

# idf.py flash monitor

Or get the merged binary:

# idf.py merge-bin

[abortega]

Thank you so much...

[abortega]

btw... may i know what is the difference with xiaozhi.bin vs merge-binary.bin besides the filesize..??? and which one you prefer to use to flash??? thanks in advance...

[78]

xiaozhi.bin is like a Linux kernel. merge-binary.bin is like a disk image with parition table, boot loader, kernel inside.

[abortega]

thanks for the info... one last thing... i notice that you can also build directly using the config.json and "python scripts\release.py [board-name]... and it seems it is much straight forward... i just need to edit the config.json and it can build exactly what type of LCD you want... is this okay to used this approach? thanks in advance... and do i still need to do "idf.py menuconfig"???

this is my procedure to compile a board... is this the correct procedure?? can share the proper procecure... thanks again...
idf.py set-target esp32s3
idf.py menuconfig
idf.py build

then i will add this command as well as you advice
idf.py merge-bin

[78]

You can check the content of config.json of a board.

It often contains the specific configuration for the board such as flash size, parition tables, or camera options. So it is recommended to use python scripots/release.py [board-name] to build the firmware.

You can also follow the README.md in the board folder to do the configuration manually.

[abortega]

I just notice... The "python scripts\release.py (boardname)" merge-binary.bin were 8mb... While the "idf.py build/idf.py merge-bin" merge-binary.bin result was only 2.6mb... is there any significant to those? I can safely flash both without any issue?

Thank so much again...

[78]

Just remember to run release.py to configure the sdkconfig. You can stop the compilation (or press Ctrl+C) after this step. Then, you can run idf.py merge-bin. The result will always be the same unless you modify the sdkconfig.

[abortega]

wow... it works... thank you SO much...