ADVANTEST R9211B

[m k]

First one other thing,
I/O map picture has *5E04xx FPUSEL and *5E08xx FP[V/Y]POL.
Maybe latter is polarity something.

Since clock is clearly working, no overly short pulses, keep it.

Trigger is different, I don't really understand how this machine operates behind the scenes.
Getting Started Manual section 5 is for Timing Analyzer.
There page 5-6 has a picture of 2 defined labels, page 5-8 has defined 1 edge.
After that it does Run and after that it shows a Timing Waveforms display and all waveforms are the same.
There label is named RAS but display is RAS 00 for all rows.
After that it changes the 2nd label to CAS and display is CAS 00, can't say what that 00 is.

So you should be able to do the same and change all rows to their individual pins that you have assigned earlier.
After that your picture should be so that all labels are different, triggered to 1st label and rest are what they are.
If you have not assigned any pins to other labels they all should be the same, up or down.
Your picture should also be so that triggered situation is center of the screen.
If you now want different waveforms you do new Run, or scroll around to see what other things have happened.

One difference between manual pictures and your earlier waveform pictures.
Manual picture has 'to trig' fields on the upper section, so maybe your trigger has never actually been there.

Above Then Find Edge field is Present For fields.
There must be something, > 30ns is fine.
It means that triggering level must stay longer than 30ns before it is accepted as a trigger.

External trigger input is for Armed by field of Timing Trace window and BNC Input selection there.
Don't know how it operates, maybe it's for general start of data collection since its other selection is Run.

I also remember from somewhere that some analyzers are tricky, maybe this is one of them.

[stfjohn]

I managed to get the dollar sign on all the labels, but the result doesn't seem to change...

[m k]

I don't really understand what I'm seeing.
POD 06 pin 9 CPU can be rational, it can be the first time R/_W goes down after reset.
Seems that you must add that other POD and make it a State Analyzer.

But anyway, only one trigger should be active at the time.
Turn Markers on to see what you have.

Overall timing is also something that it shouldn't.
There are some close to 50MHz pulses and the CPU is 10MHz thing.
Change Time/Div to 1000ns and do POD 06 pin 9 CPU picture again.
Then just press Run and take another picture of what you got.

First picture is from the very beginning and second from random position later.
Maybe we can learn something from their differences.

[stfjohn]

It's impossible: now the analyzer reads only 8 channels! The self test says that everything is fine, but evidently it is not so! I don't understand anything anymore! In any case the readings are always different every time I turn on the Advantest!

[m k]

Then we go back.

Earlier pictures have POD 1 and numbers after that.
That latter part must mean connected POD pins.
When you named those other labels you didn't add that "all" text, so it is internally created.
Means that if you have more than a single bit assigned to the label the machine add rows for all bits automatically.

So I think your 1st picture of reply #92 is right and so is reply #95.
Means that all bits to POD 1 and all other labels to trash.

After "POD 1" is "00" text, the latter must be a connected bit.
Next 'B' label has "all" text, no idea why the ending is not "01" that "POD 1 00" line indicates.

Go to System Configuration menu, maybe you can put the machine back to its initial state.
You have Analyzer 1 and 2, if both are on turn other one off.
Then change the Type of the active one to State.
Then select some other menu, stuff there are what they are, that's not important.
Then go back to System Configuration menu and change the active analyzer to Timing.

If you then go to Timing Format you should have a default settings.
Maybe that is already like you had in reply #92, but without those extra labels.

Next you can go to Timing Trace menu, POD pin 00 is right and 15 left.
So for triggering POD pin 06 you select 7th from right.

Next you should be in Timing waveforms display with original POD 1 lines.
Turn markers on, you should have only one trigger available.
Markers mean that you can check times between O and X, so no use for us.

Now you can tap Run and check what happens.
If waveforms are fine then fine, if not then go back to Timing Trace menu and take the trigger off.
Tap Run again and now the picture should be like it originally was.

Seems that the trigger must be delayed, so maybe that state analyzer side of the machine is needed.
One other possibility is to have a counter/timer, feed it with a clock pulse and flip external trigger when certain amount of pulses have happened.
Why's that.
Since all signals seem to pulse very early we must find means to delay the trigger so much that this first phase is gone.
For that we can use external trigger input, but I don't know where to connect it.
With state analyzer we can arm the timing analyzer part starting when high address lines (A23 to A20) have a state 5 (0101).
Assumption here is that when I/O is accessed first time the system has reached its normal operating phase.