svf2xsvf: at least libxsvf seems to move the machine before XSDRE

The XSDRE opcode entry state seems confusing, but at least the libxsvf
state machine seems to move to the DRCAPTURE state just as it would
before an XSDR opcode. Go with that for now, rather than using XSTATE
to do so - it could invoke other undefined behavior.

tools/svf2xsvf.py

@@ -497,11 +497,6 @@ try:
                         struct.pack_into( ">i", obuf, 0, xsdrsize )  # big endian 4 byte int to obuf
                         output.write( obuf )
 
-                    obuf = bytearray(2)
-                    obuf[0] = XSTATE
-                    obuf[1] = DRCAPTURE
-                    output.write( obuf )
-                        
                     cmdbuf[0] = XSDRE
                     output.write( cmdbuf )
                     obuf = makeXSVFbytes( tdi )