Author Topic: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?  (Read 775797 times)

0 Members and 2 Guests are viewing this topic.

Online Bud

  • Super Contributor
  • ***
  • Posts: 4829
  • Country: ca
Not sure i understand the turning the thing off and on and resetting  but glad it worked in the end!
Facebook-free life and Rigol-free shack.
 

Offline oaba

  • Contributor
  • Posts: 27
  • Country: ie
I was just reading about it. If you turn it OFF and ON a couple times the scope can boot suddenly.
That did not work for me.
But with the serial connection. I was using the r command to keep reseting it. And it was booting up. That was enough for me to do a firmware upgrade from the usb stick.
 

Online Bud

  • Super Contributor
  • ***
  • Posts: 4829
  • Country: ca
I see. Did you monitor the first "good" startup log? I've seen something that may be interpreted as sort of "self healing" of the flash, when during boot if the scope cant read flash it pulls the second image and if successful, marks failed flash sectors on the first image.
Facebook-free life and Rigol-free shack.
 

Offline Pinkus

  • Frequent Contributor
  • **
  • Posts: 689
I was just reading about it.
He probably read my comments somewhere about when my DSOX4000 had flash problems. My scope often started 1 times out of 10 when switched on, the other 9 times it hung after a while. Though it got worse and finally, sometimes it needed 100 tries. Sending a Reset through UBOOT will do the same but is quicker and healthier for the electronics than 100x switch-off / switch-on.

@oaba: do not feel too lucky and be prepared: rewriting/updating the firmware did help for a few weeks at the beginning but my scope quickly failed again. Later, even this flash-rewrite did not help anymore (neither USB or UART or ethernet).
 

Offline oaba

  • Contributor
  • Posts: 27
  • Country: ie
Pinkus.
What was at the end? Because I contacted Keysight they not interested.
Only if I pay for the diagnostic, post, and at the end the new board.  (thousands)

I am thinking to replace the flash. Is there anyone did that before?
 

Offline oaba

  • Contributor
  • Posts: 27
  • Country: ie
I celebrate with a flash cake. To keep the boys cool :popcorn:.
 

Offline oaba

  • Contributor
  • Posts: 27
  • Country: ie
« Last Edit: June 21, 2021, 07:20:12 pm by oaba »
 


Offline TK

  • Super Contributor
  • ***
  • Posts: 1658
  • Country: us
  • I am a Systems Analyst who plays with Electronics
I am not sure you can replace the flash without loosing calibration and serial number information...
 

Offline Pinkus

  • Frequent Contributor
  • **
  • Posts: 689
Pinkus.
What was at the end? Because I contacted Keysight they not interested.
Only if I pay for the diagnostic, post, and at the end the new board.  (thousands)
I asked Keysight about the repair and of course I also was afraid, that the examination alone would cost a fortune. But no, it was not. This is what they answered:
Within approx. 4 working days after receiving your device , we will perform a technical examination and send you an offer for repair and calibration.  There are no costs for the examination.

Fortunately, they identified the flash as the cause and applied the service note regarding corrupted flash. Result: free repair  :phew:
To be honest: I knew the problem was caused by the flash chip. If they would have tried to sneak out, I would be a Keysight hater by now. Now I am the opposite as I honor companies that take responsibility for such problems. Win-Win  :D
 

Offline oaba

  • Contributor
  • Posts: 27
  • Country: ie
TK
You have to dump the content first.
1: with a programmer. (Elnec can program and read this flash.)
2:If you good enough. You can write your own code to make your micro to read the flash  and send it to the JTAG. Trough the JTAG you can have a full controll of you controller. First you have to put it on halt. And after you can run your own software on it. Example read the flash memory and send it to the JTAG.
We should  find someone who has tis programmer with the bga63  adapter.
So you always have a safety net. Even when your scope going to be 20 years old.  You can recover it.
 

Online Howardlong

  • Super Contributor
  • ***
  • Posts: 5104
  • Country: gb
I just realised that in 7.40 Keysight have added USB trigger/decoding, including HS for >=1GHz scopes.

On my MSOX3104T, which already has a kosher factory installed bundle, upgrading to 7.40 didn't enable USB trigger/decode.

I enabled it using the patched 7.40 .ksx with the following infiniivision.lnk:

Code: [Select]
69#"\Program Files\infiniiVision\infiniivisionLauncher.exe" -l D3000USBB

Note that this only applies if you already have the original bundle installed on a >=1GHz scope. The original 1GHz bandwidth and bundle options remain installed.

If you have a different starting point such as bandwidths and/or pre-installed options, different settings may apply.

Note that HS requires a high speed differential probe, whereas FS and LS work on all analogue & digital channels.

Hmm... that feature was pretty much the only reason I have a Tek MDO4000 on the bench, and an expensive Tek differential probe.
« Last Edit: July 04, 2021, 08:06:52 pm by Howardlong »
 
The following users thanked this post: 2N3055

Offline Electrojunky

  • Newbie
  • Posts: 1
  • Country: us
A big thank you to all of the people that have made this possible! You guys are truly amazing.

Does anyone know if this method will work on Keysight's S series oscilloscope? I've searched the forums but wasn't able to find any mention of it.
 

Online Howardlong

  • Super Contributor
  • ***
  • Posts: 5104
  • Country: gb
Has anyone had any luck doing USB HS triggers or decode on the 3104T?

I can get full- and low-speed to work no problem.

I'm using an 1130A calibrated 1.5GHz probe with E2675A differential browser with 01131-62102 91 ohm tips. Scope's calibrated and passes self test. The same happens with an 1131A 3.5GHz probe with differential browser.

An MDO4104C with P6330 3.5GHz differential probe & TPA-BNC adapter decodes just fine.

Screenshots attached...
« Last Edit: July 18, 2021, 04:52:11 pm by Howardlong »
 

Online Howardlong

  • Super Contributor
  • ***
  • Posts: 5104
  • Country: gb
Has anyone had any luck doing USB HS triggers or decode on the 3104T?

I can get full- and low-speed to work no problem.

I'm using an 1130A calibrated 1.5GHz probe with E2675A differential browser with 01131-62102 91 ohm tips. Scope's calibrated and passes self test. The same happens with an 1131A 3.5GHz probe with differential browser.

An MDO4104C with P6330 3.5GHz differential probe & TPA-BNC adapter decodes just fine.

Screenshots attached...


I installed the USB trial licence, and it turns out it's a bug, USB HS trigger/decode doesn't work yet on MSOX3104T, this from KeysightCare Technical and Application Support:

Quote
We could reproduce the issue and found out that the 4000A x-series scope is working fine, but the 3000T x-series scope, which you use, is not and we also got the red lines. Therefore we logged a defect report to our R&D and they will fix it in the next releases. To set the priority to our R&D correctly, could you please let me know if you have any deadline in your projects that prevents you from doing your work or are you able to work with the TEK scopes while we are fixing the issue?

Thank you very much for bringing this to our attention. We are always looking forward to customers feedback to improve our software and hardware.
 
The following users thanked this post: 2N3055, eplpwr

Online Howardlong

  • Super Contributor
  • ***
  • Posts: 5104
  • Country: gb
Turns out it's a bit more than a bug...

Quote
Unfortunately I don't have good news to share.

R&D looked into the issue with the 3000T x-series scope and USB 2.0 HS and found out that 3000T x-series scopes can’t support USB High Speed due to HW limitations. SW support for USB HS was accidentally added in the 7.35 GUI along with the intended and working USB LS and FS support.

In summary, USB LS and FS all work in the following.  As far as USB HS…
•   The 3000T Series FPGA cannot handle USB HS.
•   The 4000X Series has a secondary FPGA that handles USB HS in 1GHz+ models
•   The 6000X Series can handle USB HS it in its main FPGA.
R&D is investigating the changes to remove USB HS support from the 3000T Series GUI (targeted for the 7.50 release) while Marketing is reviewing the changes needed to customer facing documents.

My apologies for the mistake which we did in our documentation and software. This will be corrected soon.

Do you also have a 4000X or 6000X series scope from us?

Let me know if I can assist you any further in getting a 4000X or 6000X scope from one of our partners in the UK or with any other question. I hope we didn't loose your trust and you are still interested in ditching the TEKs ;)

 

Offline 2N3055

  • Super Contributor
  • ***
  • Posts: 3663
  • Country: hr
Turns out it's a bit more than a bug...

Quote
Unfortunately I don't have good news to share.

R&D looked into the issue with the 3000T x-series scope and USB 2.0 HS and found out that 3000T x-series scopes can’t support USB High Speed due to HW limitations. SW support for USB HS was accidentally added in the 7.35 GUI along with the intended and working USB LS and FS support.

In summary, USB LS and FS all work in the following.  As far as USB HS…
•   The 3000T Series FPGA cannot handle USB HS.
•   The 4000X Series has a secondary FPGA that handles USB HS in 1GHz+ models
•   The 6000X Series can handle USB HS it in its main FPGA.
R&D is investigating the changes to remove USB HS support from the 3000T Series GUI (targeted for the 7.50 release) while Marketing is reviewing the changes needed to customer facing documents.

My apologies for the mistake which we did in our documentation and software. This will be corrected soon.

Do you also have a 4000X or 6000X series scope from us?

Let me know if I can assist you any further in getting a 4000X or 6000X scope from one of our partners in the UK or with any other question. I hope we didn't loose your trust and you are still interested in ditching the TEKs ;)


Well, I don't buy it..

They created D3000USBB USB 2.0 Trigger and Decode for 3000T X-Series license type, datasheets, and whole infrastructures...

You tell me they did all that and didn't test it just a bit.. You managed to find a problem, in what, 2 hours....

It's either political, or we have a bigger problem, that they don't test as they used to....

Anyways, I saved some money...
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 2250
  • Country: pt
Sinisa,

It's just HS limitation, or I'm seeing it wrong?
 

Offline 2N3055

  • Super Contributor
  • ***
  • Posts: 3663
  • Country: hr
Sinisa,

It's just HS limitation, or I'm seeing it wrong?
No  I think you're right.. Only HS is problem. If it is technical, this is one place where hardware decode is a problem, not a solution..
 

Online Howardlong

  • Super Contributor
  • ***
  • Posts: 5104
  • Country: gb
You tell me they did all that and didn't test it just a bit.. You managed to find a problem, in what, 2 hours....

Probably in total. I went back to it about three or four times... sometimes it's, you know, operator error. Sleeping on these things or trying it a day or two later you sometimes get a light bulb switch on in your head.

I have to say when I put in the ticket originally, I was still pretty sure they were going to tell me it was operator error.

As previously mentioned in my note on 18th, yes, it does work in both LS & FS. It's just HS that's the problem. It'd be a bit of a pain if you'd shelled out for both the option and a diff probe...

 
The following users thanked this post: 2N3055

Offline tv84

  • Super Contributor
  • ***
  • Posts: 2250
  • Country: pt
this is one place where hardware decode is a problem, not a solution..

Yes, comes with the territory... we (specially you guys) all praise their HW benefits, must understand those limitations.

Also, comes from the reuse of the same SW base which is also something that we like to see.

 

Online TheSteve

  • Supporter
  • ****
  • Posts: 3295
  • Country: ca
  • Living the Dream
Turns out it's a bit more than a bug...

Quote
Unfortunately I don't have good news to share.

R&D looked into the issue with the 3000T x-series scope and USB 2.0 HS and found out that 3000T x-series scopes can’t support USB High Speed due to HW limitations. SW support for USB HS was accidentally added in the 7.35 GUI along with the intended and working USB LS and FS support.

In summary, USB LS and FS all work in the following.  As far as USB HS…
•   The 3000T Series FPGA cannot handle USB HS.
•   The 4000X Series has a secondary FPGA that handles USB HS in 1GHz+ models
•   The 6000X Series can handle USB HS it in its main FPGA.
R&D is investigating the changes to remove USB HS support from the 3000T Series GUI (targeted for the 7.50 release) while Marketing is reviewing the changes needed to customer facing documents.

My apologies for the mistake which we did in our documentation and software. This will be corrected soon.

Do you also have a 4000X or 6000X series scope from us?

Let me know if I can assist you any further in getting a 4000X or 6000X scope from one of our partners in the UK or with any other question. I hope we didn't loose your trust and you are still interested in ditching the TEKs ;)


Maybe they want to trade your MSOX3104T for a MSOX4104A
VE7FM
 

Offline TK

  • Super Contributor
  • ***
  • Posts: 1658
  • Country: us
  • I am a Systems Analyst who plays with Electronics
USB HS is a complex protocol, very verbose and probably cumbersome to debug on a DSO screen, except for some specific bug chasing using triggers.  I use an old Lecroy CATC USB 2.0 protocol analyzer I got on eBay for around $150 and software is still available for download from Lecroy and it runs on Windows 10.  It can capture full USB HS and some units even comes with exerciser that allows you to generate USB signals.
 

Offline 2N3055

  • Super Contributor
  • ***
  • Posts: 3663
  • Country: hr
Turns out it's a bit more than a bug...

Quote
Unfortunately I don't have good news to share.

R&D looked into the issue with the 3000T x-series scope and USB 2.0 HS and found out that 3000T x-series scopes can’t support USB High Speed due to HW limitations. SW support for USB HS was accidentally added in the 7.35 GUI along with the intended and working USB LS and FS support.

In summary, USB LS and FS all work in the following.  As far as USB HS…
•   The 3000T Series FPGA cannot handle USB HS.
•   The 4000X Series has a secondary FPGA that handles USB HS in 1GHz+ models
•   The 6000X Series can handle USB HS it in its main FPGA.
R&D is investigating the changes to remove USB HS support from the 3000T Series GUI (targeted for the 7.50 release) while Marketing is reviewing the changes needed to customer facing documents.

My apologies for the mistake which we did in our documentation and software. This will be corrected soon.

Do you also have a 4000X or 6000X series scope from us?

Let me know if I can assist you any further in getting a 4000X or 6000X scope from one of our partners in the UK or with any other question. I hope we didn't loose your trust and you are still interested in ditching the TEKs ;)


Maybe they want to trade your MSOX3104T for a MSOX4104A

Yeah, if they'll do it for the price of USB option.. >:D I'll be interested too...  :-+
 

Offline 2N3055

  • Super Contributor
  • ***
  • Posts: 3663
  • Country: hr
And a question to gurus here:

what is MSOX3104G ?

What kind of model is that?
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf