Hi John
I received the files and took a look.
The binary files are in motorola binary format and the problem is that the utility uTaskerCombine expects raw binary input files, which it combines into a single binary output file. When the Motorola format is used, the output is also in this format (although maybe corrupted)!
The utility uTaskerConvert is the one that does recognise Motorola binary input.
This means that there is a problem when two Motorola binary files need to be combined to one raw binary file, which is the case if you want to take the boot loader and an application and combine them for loading as a single file (you can however load each individually to get the same effect). The uTaskerConvert then works correctly when it generates further files that can be uploaded to the board.
As workaround the following seems to work:
1) Use uTaskerConvert to generate two binary files - one for the boot loader file and one of the application file. This results in two raw binary files with headers, which are not required. With a binary editor the headers (the first 8 bytes in each output file) can be deleted.
2) Now use uTaskerCombine to combine the two raw binary files from step 1 to result in a single raw binary file for loading to the target.
I will have a look at whether the uTaskerCombine utility could be adapted to also recognise Motorola binary format and automatically convert it when combining. Alternatively, whether the utility uTaskerConvert can be simply adapted to generate the raw binary output without the header (this is probably easier) so that it can be used generally to convert from Motorola binary to raw binary as pre-processing step when necessary.
Regards
Mark