I doubt anything like this exists, especially for assembly. The lower level the language, the harder it is to analyze. Drawing the flow chart yourself is probably the best solution, especially since this really helps your understanding of the problem. You could run the code in a simulator/debugger to get a feel for execution flow. I used to draw lots of diagrams with pencil and paper back when I was still coding assembly.