Rigol MSO1074Z Destroyed During Attempted Hack - HELP PLEASE

[m2kara]

Hi Everybody,
I am a newbie in electronics, and bought this Rigol MSO1074Z from a friend not too long ago.
The problem is, I seem to have managed to destroy it when I tried to hack it following the Youtube post, SDGEE #04 Unlocking Rigol MSO1074Z Options, (which was by the way done very well).
I followed the instructions in the video as follows:
 1. Connecting the Olimex ARM-USB-OCD-H to the MSO1074Z JTAG header
 2. Started the DOS command window
 3. Powered the oscilloscope
 4. Entered the command prompt to connect to the oscilloscope.

The following were the outcomes:
1. The scope immediately went blank (as shown in the attachment) and won't boot again.
2. I got a an error from the command prompt that the device was not found. This was my mistake since I forgot to install the 
Olimex ARM-USB-OCD-H driver.

I will very much appreciate some help figuring how I can bring my oscilloscope back to life if at all possible.
I want to apologize in advance if this topic has been covered already, and thank you all in advance for you help.

Thanks,
m2kara...

[ataradov]

None of the things in that video are destructive on their own. So you must have done something else wrong.

So what happens after you do install the drivers and repeat the process?

[m2kara]

Alex,
You are right, I don't see anything in the video that is destructive on their own either.
After installing the driver, I'm now able to connect to the any other devices using JTAG, except the scope.
And I can see why I can't connect to scope since it won't boot to begin with.

[ataradov]

JTAG is hardware-level thing, you don't need the CPU to be booted, or even have any memory attached to it.

Can you actually show exact messages OpenOCD shows? Can it read IDCODE of the device at least?

If it does not see anything on the JTAG at all, then chances are the CPU is dead due to static/shorts/wrong voltages applied to the wrong pins, etc.

[m2kara]

Alex,
Thanks for your responses.
I checked all the connections I did, and everything looks fine.
The message that I'm getting in the command prompt is as attached below.

Thanks,
m2kara.

[ataradov]

Well, do what it says, specify the clock frequency. It did not even try to talk to the target device, since it does not know how to do that yet.

[m2kara]

Yes, I just added a command "adapter_khz 1000" in the target config file.
I was able to connect with Telnet, although with a bunch of errors, and the target wouldn't respond.
I guess it's time to try doing a little learning...

[ataradov]

Telnet is useless at this point. You need to get CPU to respond. None of this output really indicates that CPU is alive at all.

And for experiments, set this clock way lower, something like 100 kHz, just in case.

[m2kara]

Alex,
Same thing with the lower clock speed of 100KHz.

[ataradov]

Same thing with the lower clock speed of 100KHz.

I did not expect this alone to change things. It is just a good idea to keep things slow when debugging.

A this point I would skip the script stuff, since it obviously will fail. And try to simply connect to the target processor and read IDCODE register. Having another scope or at least a logic analyzer would be helpful as well.

Also try to get some documentation on a processor and check for basic signs of life - Xtals running, pins toggling, etc.

[m2kara]

Yes, will do that and you know what I find out.
Thanks much.

[MarkF]

The following were the outcomes:
1. The scope immediately went blank (as shown in the attachment) and won't boot again.

Alex,
You are right, I don't see anything in the video that is destructive on their own either.
After installing the driver, I'm now able to connect to the any other devices using JTAG, except the scope.
And I can see why I can't connect to scope since it won't boot to begin with.

Yes, I just added a command "adapter_khz 1000" in the target config file.
I was able to connect with Telnet, although with a bunch of errors, and the target wouldn't respond.
I guess it's time to try doing a little learning...

Sounds to me like you shorted the scope when you connected to the JTAG header.  Before doing anything else, I would disconnect the scope and verify that it still boots and operates properly.  Then, re-connect to the JTAG and verify it's connected correctly.

[ataradov]

I would disconnect the scope and verify that it still boots and operates properly.

This is the problem. The scope does not boot even without JTAG connected. At least that's the problem I was diagnosing here.

[stj]

closeups of any soldering work and cables may be good