BlueFlashCmd.exe -trans 'SPIDEBUG_FILE=spi.log SPIDEBUG=ON' -chipver The key parameter here is SPIDEBUG_FILE - logging is activated when it's specified, and thus logging is always done to a file. One way to have logging go to a console is to use SPIDEBUG_FILE=con:, but then it won't be possible to redirect it. Hack For Mu 97d Servers. Besides SPIDEBUG=ON, there're other logging levels/features: • SPIDEBUG • SPIDEBUG_REPRODUCIBLE • SPIDEBUG_WRITES • SPIDEBUG_READS • SPIDEBUG_WIRE The keys may be also specified in the environment instead of -trans switch arguments. Looking at the output produced, it turns out it spends a lot in calibrating SPI speed, a way to that down is to use SPISLOW=ON setting right away. I've been fiddling with one of these modules for some time now, but mine has the limited linvorV1.5 firmware. Scrivener Linux Beta. I don't have a windows machine or access to the CSR tools.