anchao commented on PR #8997:
URL: https://github.com/apache/nuttx/pull/8997#issuecomment-1505715638
> EDIT2: Nope, same thing happens. I'll try to build the docker image
locally.
@lucasssvaz
I can reproduce this problem if force esptool version to 3.3.1:
```bash
$ pip install esptool==3.3.1
$ make -j12
CPP:
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-devkit/../common/scripts/esp32c6_rom.ld->
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-devkiCPP:
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-devkit/../common/scripts/flat_memory.ld->
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-devkiCPP:
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-devkit/../common/scripts/legacy_sections.ld->
/home/archer/code/nuttx/n1/nuttx/boards/risc-v/esp32c6/esp32c6-dLD: nuttx
CP: nuttx.hex
MKIMAGE: ESP32-C6 binary
esptool.py --chip esp32c6 elf2image --flash_mode dio --flash_size "4MB" -o
nuttx.bin nuttx
usage: esptool [-h] [--chip
{auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32s3,esp32c3,esp32c6beta,esp32h2beta1,esp32h2beta2,esp32c2}]
[--port PORT] [--baud BAUD]
[--before
{default_reset,usb_reset,no_reset,no_reset_no_sync}] [--after
{hard_reset,soft_reset,no_reset,no_reset_stub}] [--no-stub] [--trace]
[--override-vddsdio [{1.8V,1.9V,OFF}]] [--connect-attempts
CONNECT_ATTEMPTS]
{load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,merge_bin,get_security_info,version}
...
esptool: error: argument --chip/-c: invalid choice: 'esp32c6' (choose from
'auto', 'esp8266', 'esp32', 'esp32s2', 'esp32s3beta2', 'esp32s3', 'esp32c3',
'esp32c6beta', 'esp32h2beta1', 'esp32h2beta2', 'esp32c2')
make: *** [tools/Unix.mk:527: nuttx] Error 2
```
I think upgrade the esptool version to 4.5.1 should be able to fix this
issue:
https://github.com/apache/nuttx/pull/9016
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
