tmedicci commented on issue #17809:
URL: https://github.com/apache/nuttx/issues/17809#issuecomment-3725545925
Thanks for the tests @cederom !
Indeed, I tried it myself without any problems with `wifinsh` defconfig and
the recommended toolchain. These defconfigs are also tested daily on our
internal pipeline.
About the errors, @henrykotze :
```
/home/henry/.espressif/tools/xtensa-esp-elf/esp-13.2.0_20240530/xtensa-esp-elf/bin/../lib/gcc/xtensa-esp-elf/13.2.0/../../../../xtensa-esp-elf/bin/ld:
warning: cannot find entry symbol __start; not setting start address
Memory region Used Size Region Size %age Used
ROM: 65504 B 4194272 B 1.56%
iram0_0_seg: 1040 B 168 KB 0.60%
irom0_0_seg: 65520 B 3342304 B 1.96%
dram0_0_seg: 0 GB 180736 B 0.00%
drom0_0_seg: 0 GB 4194272 B 0.00%
rtc_iram_seg: 0 GB 8 KB 0.00%
rtc_slow_seg: 0 GB 4 KB 0.00%
rtc_reserved_seg: 0 GB 24 B 0.00%
extmem_seg: 0 GB 4 MB 0.00%
[536/538] Generating ../../espressif_esp32_default.bin
```
Probably the entry symbol, referent to
[this](https://github.com/apache/nuttx/blob/3bf8b55d642e698a25d8f54eaebac6a660e05a42/arch/xtensa/src/esp32/esp32_start.c#L341)
function isn't being compiled. This is the firmware entrypoint and it's
mandatory.
About the libc functions: there are a bunch of functions defined in the
ESP32's ROM memory. Those are defined by a specific linker script by the
`esp-hal-3rdparty` repository. They are linked
[here](https://github.com/apache/nuttx/blob/3a74b82e093cd85f23916c710a46955af25f5e3f/arch/xtensa/src/esp32/hal.mk#L86).
When building NuttX, it would be available at
`arch/xtensa/src/chip/esp-hal-3rdparty/components/esp_rom/esp32/ld/esp32.rom.libc-funcs.ld`.
You either need to clone it and use it by yourself or use NuttX's building
system and include this linker file. Please note that each version of NuttX is
bound to a specific version of the HAL repository
[here](https://github.com/apache/nuttx/blob/3a74b82e093cd85f23916c710a46955af25f5e3f/arch/xtensa/src/esp32/Make.defs#L215).
Make sure you checkout to this version.
--
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]
