Hi,

I have my Teensy OTA firmware update script running great now, with one small problem.  It appears that the post-build event is triggered both on the 'compile-only' (F7) operation AND the 'compile-and-upload' (F5) operation.

I normally do a LOT of 'compile-only' cycles between each 'compile-and-upload' cycle, so is there a way of NOT triggering the post-build execution of board.txt commands after a F7 compile-only operation? 

TIA,

Frank

Simon@Visual Micro wrote on Oct 27^th, 2021 at 3:01pm:


Thanks for the link to the build events and hooks.  Right now I have a single 'postbuild' command line:

recipe.hooks.postbuild.1.pattern=cmd.exe /c "c:\Program Files (x86)\teraterm\ttpmacro.exe" /v "c:\users\Frank\Documents\Arduino\Teensy Projects\TeensyOTADemo\TeensyOTA1.ttl" "{vm.runtime.build.final_output_path}" {serial.port} {build.project_name} 

I would like to skip this line if when I press F7, but run it when I press F5.  I don't see anything in the list of actions that would allow me to know whether I was doing a 'build-with-upload' (F5) or 'build-but-don't-upload' (F7). Am I missing something?

TIA,

Frank

Tim,

Menu items are 'Build->Build Solution' (F7) and 'Debug->Start Debugging' (F5).  See screenshots below

Tim,

I have looked through the referenced document, but I still don't see how they help me tell if the compile was started as a 'build' (F7) or 'debug' (F5) compile.   

There is obviously something I'm missing here. what can the recipe.hooks.deploy.preupload, or recipe.hooks.deploy.postupload actions do that are relevant?  Please talk slowly and use small words, because I'm denser than the average programmer


TIA,

Frank

Tim,

Ah, I see now.  I didn't make the connection between 'preupload' and 'only runs when you attempt to upload, i.e. F5'.  

OK, I tried it, but it didn't work out quite like I'd hoped.  I replaced:

recipe.hooks.postbuild.1.pattern=cmd.exe /c "c:\Program Files (x86)\teraterm\ttpmacro.exe" /v "{build.project_path}\TeensyOTA1.ttl" "{vm.runtime.build.final_output_path}" {serial.port} {build.project_name}
 

with

recipe.hooks.deploy.preupload.1.pattern=cmd.exe /c "c:\Program Files (x86)\teraterm\ttpmacro.exe" /v "{build.project_path}\TeensyOTA1.ttl" "{vm.runtime.build.final_output_path}" {serial.port} {build.project_name}
 

Now the command doesn't run on F7 - yay! - but errors out on F5. The error is:

 
Uploading 'T35_WallE3_V1' to 'Teensy 3.5' using 'COM7'
'c:\Program' is not recognized as an internal or external command,
Error running hook: cmd.exe /c "c:\Program Files (x86)\teraterm\ttpmacro.exe" /v "C:\Users\Frank\Documents\Arduino\T35_WallE3_V1\TeensyOTA1.ttl" "C:\Users\Frank\Documents\Arduino\T35_WallE3_V1\Release\" COM7 T35_WallE3_V1.ino
operable program or batch file.
No Teensy boards were found on any USB ports of your computer.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
     The upload process has finished.

So, it appears the 'preupload' hook may parse things differently than the 'postbuild' hook?

Thoughts?

Frank



Frank

Simon,

Yep - that did the trick 

Frank