I have tried both 1,6,5 and 1.6.4 and download the "stable " !!! board platform for the esp8266
The platform.txt is hopelessly confused . firstly there is no entries for esptool.py ( which I have working for my ESP native development setup)
Secondly where people have suggested additions for esptool.py, the info relates to .bin files that esptool ( as in esptool-ck) generates
Am I right in assuming that the #create hex script in platform.txt
recipe.objcopy.hex.pattern="{runtime.tools.esptool.path}/{compiler.esptool.cmd}" -eo "{runtime.platform.path}/bootloaders/eboot/eboot.elf" -bo "{build.path}/{build.project_name}.bin" -bm {build.flash_mode} -bf {build.flash_freq} -bz {build.flash_size} -bs .text -bp 4096 -ec -eo "{build.path}/{build.project_name}.elf" -bs .irom0.text -bs .text -bs .data -bs .rodata -bc -ec
seems to produce a bin ( as in Blinky.cpp.bin) that is a single flash able file for the esp8266 ?.. but this seems to be aimed at the FOTA script that follows ( i.e. using espota)
surely the script need to produce a 0x00 and a 0x40 bin file that can be handled by esptool.py,
this seems to be completely missing
i.e. its not the missing esptool.py thats the issue , its the esptool ( -ck) that is in the create hex that seems junk to me
any ideas on how to straighten this out