For a more meaningful display, set your scope to 2V/div and 500ns or 1us/div, this is a 5 volt and 1MHz system.

Start with the clock or E signal at 2V/1us /div and you should see a more or less perfect square wave. Adjust trigger level if necessary until the waveform "freezes" in display.

Then, you can move the scope probe to other signals but don't touch the scope settings. If you see a solid line near 0 or 5 volts that means the signal stays at logic 0 or 1, or doesn't change very often. Most, if not all, logic signals in game CPU do change states continuously so a solid 0 or 1 is usually a sign of problem. For signals changing only occasionally, such as IRQ, you need to tinker with scopes triggering settings, but anyway if you observe the clock and E signals and activity on data/address bus the CPU is definitely running. Next to check would be the /CE inputs of ROM and RAM, those should be periodically pulsing low.

Yes, your clock and E are fine but there is definitely something wrong with VMA, it should be mostly high. Try another 6802.

Edit: also might be possible that the CPU has problems reading ROM and gets a WAI instruction and then halts waiting for interrupt with VMA low. Anyway, testing with another CPU chip will help.

VMA stands for valid memory address. CPU sets VMA high when it has set a memory address on the bus, for reading or writing memory. So whenever the CPU is running a program the VMA should show activity.

The CPU can be set to a state in which it does nothing, but waits for an interrupt (a low in IRQ or NMI pins) and in that state it does not assert VMA.

I would try with another CPU first.