U2 programmer problem - Saleae Logic Probe measurements, SOLVED

[Demon]

...I don't see you have any trigger set up...

What would you suggest?

I figure using MCLR is the key, but under what conditions?

I checked the manual but didn't see too much detail on trigger. I've never used a "trigger" before, it does exactly that right? It starts the procedure and then that condition is ignored?

So I'd look for MCLR going up?

I assume getting rid of that Blank Check Before and Verify After steps could help too, it's not really necessary.

[mister_e]

Disconnect any extra hardware attached to your computer (camera, printer & plah plah plah)

Clean the USB driver with UsbDeview, reconnect your U2 programmer, wash & rinse again.

[mister_e]

BTW, is the Saelig probe able to handle the 13V (or so) on the MCLR pin?!?

Get rid of it while programming.

[Demon]

Disconnect any extra hardware attached to your computer (camera, printer & plah plah plah)

Clean the USB driver with UsbDeview, reconnect your U2 programmer, wash & rinse again.

I only have mouse and keyboard attached.

Cleaned with Usbdeview, uninstalled programmer, rebooted, reinstalled v4.32 from CD and everything works ok!

Merci le Bleuet!

[mister_e]

[Insert Big Grin here]

[Demon]

I upped the rate to 100M@200KHz.

(the bottom PC is the one that programs properly)

This is the start of the programming step:



At first glance things look practically identical. The only thing I haven't figured yet in Logic is how to get the same zoom ratio to make it easier to visually compare 2 windows.


This is a zoom on that very first PGC signal from the red box:




The PGC signals are somewhat delayed relative to PGD.


And this is the second PGC signal:



An even bigger difference in signals.


I guess I'm stuck to using the old Pentium 4 until I figure this out.

(I have to say I love my Saleae logic probe)