TIDL disables and reenables all C7x interrupts around critical sections of code, and depends on these interrupts being disabled or the preemption logic fails.  When logs are used, I see that the lower priority task can be preempted by the OS.  Suspicion is that logging uses critical sections also, and that it may not support nested interrupt locking.

Workaround for now is to disable all logging in TIDL by commenting out the body of the log callback function given to TIDL.