I have moved away from doing this as a sigrok protocol decoder, because I was finding python far to slow when processing multi-GB capture files, and the sigrok GUI is not good with massive amounts of data.

So the lastest version of the tool is standalone, written in C, and is ~100x faster:
https://github.com/hoglet67/6502Decoder/wiki

The output is now a plain text file.

You can still use sigrok-cli to create the capture file. There are some usage examples here:
https://stardot.org.uk/forums/viewtopic ... 57#p182757

Another advantange is that no changes to sigrok are required.

I see you are using Windows. There are some Windows specific notes here:
https://stardot.org.uk/forums/viewtopic ... 69#p182769

What capture hardware do you have?

Dave

Dave,

Thanks for the prompt reply.

I'll take a look at the links and have a play with the standalone C version.

I have a 'Noname Saleae 24 MHz 8 bit probe' that I have been playing with but I also have a Hantek 6022BL on order, which has 16 channels. I have a vintage Tektronix 1225 which is a 48 channel analyser, but there does not appear to be a convenient way of getting the data off it, hence the interest in disassembling the RS232 6502 ROM.

I take it from your comments that you are not really into Sigrok PulseView but rather do things from the command line. I had hoped to add your decoder to PulseView, but have not been successful todate.

I also have the Tektronix 1230 RS232 and parallel printer roms in hex, so it should be possible to run your disassembler through them, though would suffer from not including the 6502 state information to determine which locations are data and which are code.

Peter

(Welcome Peter! There are smart disassemblers which try to trace out reachable code, which might help.)