For some batch/automated FW update I would like to capture fdt2.exe’s “console” output into the file. If I use Windows shell redirection for STDOUT and STDERR they both yield empty files.
It seems fdt2.exe opens some sort of ‘external’ console window where the actual output is written. Is there any elegant way to capture/save it?
Alternatively I could analyse log files created using -log option but they seem to be pretty massive (~400kB per successful run of fdt2).