Thanks. I have intermittent access to a windows machine, so I can test some things out - again as a control so I can try to adapt to my normal workflow.
So for now I am able to flash the locally compiled boot loader to the 1060 EVK. Great news. I am also able to download your demo 1060 app and run that using the bootloader... and switch between the application and the bootloader at will. Again progress!
The MCUBootUtility you reference in your docs and videos is just a wrapper around sdphost and blhost just like the NXP provided secure provisioning tools, so I should be able to adapt that to os x since those command line tools are cross platform. I'll work on documenting that and provide any details if anyone is interested for posterity here.
The next little bit of complication is that I am trying to upload a *.bin which has been compiled independently of the utasker app framework. You have a video here which references a generate.bat file which I don't seem to see anywhere, but it's readable in the video, so I can see that the part I'm interested in seems to be just one command which is in the other specific generate.bat files in your application folders...
https://www.youtube.com/watch?v=5iT7KP691ls&ab_channel=mjbcswitzerlandRoughly translated:
uTaskerConvert.exe blinky.bin blinky-upload.bin -0x1234 -a748b6531124
however, when I copy this new bin file over to UPLOAD_FOLDER, it does not "consume" it... it just sits there unlike when I upload the sample app from website and/or the built sample utasker application, it reboots itself as soon as it copies and begins running immediately.
I assume I'm missing something, but I'm not sure. Still trying to work through that. I verified that the auth value and magic number are the same as in the build of the bootloader... Must be something else the loader is verifying.