Hi

Trying to get some context here so few questions:-

Which IDE?
Do you know about "vMicro>Publish Server Data Files (spiffs)"?

Thanks

We need to come up with something more flexible but you can call the spiffs system from a post build event. Passing an invalid port just creates the .bin withouth upload. It will show an error that releates to the invalid port but the .bin should have created OK.

Unfortunetly it will always create the bin in a sub folder below the specified folder but the sub folder name shouldn't change if your spiffs options don't change.

The default output uses the temp build folder which you can see in the verbose output or when "vMicro>Compiler>Show build folder" is enabled.

There are two esp8266 examples below. One using the build folder variables and one with hard coded output folder.

There is also an ESP32 variation in the example below (in case other readers need it).

Add the following into a board.txt in the project folder, save it then click build.

Code:

# ESP8266 post build spiffs creation
#

# Use build folder -build.path="{build.path}"
# recipe.hooks.postbuild.1.pattern="{vm.platform.root.path}/../../ESP8266FSUpload.exe" -serial.port=NO_PORT -build.path="{build.path}" -target_platform="{target_platform}" -runtime.tools.mkspiffs.path="{runtime.tools.mkspiffs.path}" -board.name="{name}" -upload.verbose={upload.verbose} -upload.resetmethod={upload.resetmethod} -upload.speed={upload.speed}  -platform.path="{runtime.platform.path}" -project.name="{build.project_name}" -project.path="{build.project_path}" -tools.esptool.cmd="{tools.esptool.cmd}" -runtime.tools.esptool.path="{runtime.tools.esptool.path}" -compiler.path="{compiler.path}" -build.spiffs_start="{build.spiffs_start}" -build.spiffs_end="{build.spiffs_end}" -build.spiffs_pagesize="{build.spiffs_pagesize}" -build.spiffs_blocksize="{build.spiffs_blocksize}"

#Use specific path
recipe.hooks.postbuild.1.pattern="{vm.platform.root.path}/../../ESP8266FSUpload.exe" -serial.port=NO_PORT -build.path="C:\myrepos\Sketch17\Sketch17\Release" -target_platform="{target_platform}" -runtime.tools.mkspiffs.path="{runtime.tools.mkspiffs.path}" -board.name="{name}" -upload.verbose={upload.verbose} -upload.resetmethod={upload.resetmethod} -upload.speed={upload.speed}  -platform.path="{runtime.platform.path}" -project.name="{build.project_name}" -project.path="{build.project_path}" -tools.esptool.cmd="{tools.esptool.cmd}" -runtime.tools.esptool.path="{runtime.tools.esptool.path}" -compiler.path="{compiler.path}" -build.spiffs_start="{build.spiffs_start}" -build.spiffs_end="{build.spiffs_end}" -build.spiffs_pagesize="{build.spiffs_pagesize}" -build.spiffs_blocksize="{build.spiffs_blocksize}"



# ESP32 post build spiffs creation
#
# recipe.hooks.postbuild.1.pattern="{vm.platform.root.path}/../../ESP32FSUpload.exe" -serial.port=NO_PORT -build.path="{build.path}" -target_platform="esp32" -runtime.tools.mkspiffs.path="{runtime.tools.mkspiffs.path}" -board.name="{name}" -upload.speed={upload.speed}  -platform.path="{runtime.platform.path}" -project.name="{build.project_name}" -project.path="{build.project_path}" -compiler.path="{compiler.path}" -build.partitions="{build.partitions}" -upload.tool={upload.tool} -tools.esptool_py.cmd="{tools.esptool_py.cmd}"  -runtime.tools.esptool_py.path="{runtime.tools.esptool_py.path}" -build.flash_mode={build.flash_mode} -build.flash_freq={build.flash_freq}
 

Hello,
Is there something similar that i could add to board.txt that after uploading the sketch allows me to also upload the spiffs file ?

Will this work when i click on the Upload button ?

1)
Can you explain why you needed the bin created prior to upload? The standard "vMicro>Upload Server Data Files" creates the bin and then does the upload at the same time. It would help to understand why you need the task split into two parts.

2) General Info

You can add any pre or post build and upload events that you want. If you switch on vMicro>Compiler>Verbose, vMicro>Compiler>Show build properties and vMicro>Uploader>Verbose you will see all the available build/upload properties when you perform the various tasks. All the properties that show for each task (build or upload) can be used to make up event hooks.

recipe.hooks.prebuild
recipe.hooks.postbuild
recipe.hooks.preupload
recipe.hooks.postupload

nb:

Events support multiple hooks. That is why my previous postbuild example is suffixed with ".1.pattern". This means you could add ".2.pattern" if needed but you might only need .1

A top tip is to look at the build properties and verbose output to see if your selected toolchain already uses any of the events. I think teensy is the only one that currently uses the postbuild. I don't recall another tool chain that uses any of the "post" events. If a tool chain does use an event yours will probably need to be ".2"

That sounds like an amazing OTA mode Interesting thanks

If you click the Upload server data files menu item it will show the params