New Hantek DSO2X1X models?

[Prerunning]

AFG is back to normal and im going to make a new backup with the patches.  Thanks again!

[galanga]

Hi. Newbie here
I've seen this question asked several times, but never saw an answer.
If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?
Are there any revisions where that doesn't happen?

Thanks.

[BillyO]

If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?

Damn good question.

Keen to see any replies (especially with screen shots) 

[dirtmover]

If you update a C10 or D10 to a D15 using dso3kb_2D15_conversion.upk
has anyone confirmed that the bandwidth does actually change to 150mhz ?
Are there any revisions where that doesn't happen?

Thanks.

I can only see a few ways to manage the BW difference between these models:
1. Through the bill of materials - kind of stupid considering they currently only appear to produce a single PCB/BOM to cover both the C/D variants. In this case we're SOL with the SW hack.
2. Switchable hardware in the analog path - looking at the reverse engineered schematics, there's no indication this HW exists. If they've done it this way the SW hack should give you full BW.
3. Implement it using signal processing to give the impression the analog bandwidth is less than it actually is - possible but requires extra code and is probably more effort than they're prepared to put in. If they've done it this way the SW hack should give you full BW.
4. The 20x10 and 20x15 models have the exact same BW spec and they simply package a 100MHz probe with the 20x10 scopes and a 150MHz probe with the 20x15 scope - hmm, cheap, easy and quite frankly the sort of approach I'd expect Hantek to take!

My money is going on option 4. Just go buy yourself a couple of 150MHz probes to replace the 100MHz one that comes with the C10 or D10

[alias095]

good day. Who will be able to remove the KEY_SCAN_DATA, KEY_SCAN_RESET, KEY_SCAN_CLOCK lines on the lane with an oscilloscope with and without a front panel connected?

[DavidAlfa]

Why?

[alias095]

Keyboard no work

[DavidAlfa]

Check if all connector pins are ok between boards.
How did the oroblem appear? Suddenly? Sometimes it's a software lockup, It needs hard resetting or firmware flashing.

I only have this scope, so I can't capture these signals.

[alias095]

after replacement FPGA from donor..
The buttons work on the star FPGA, but there are no measurements.
I will order a new GW2AR-LV18LQ144
What's the difference between GW2A-LV18LQ144C8/I7 and
GW2AR-LV18LQ144, and which one should I order?
What is the difference between LQ144 and EQ144 cases? are they interchangeable or not?
Who changed FPGA to GOWIN?

[BillyO]

Are these seriously the things you need to go through to own this scope? 

[alias095]

why not?

[BillyO]

why not?

Ahh, use?

My two Siglents, my Tek 465 and a Hantek BE6074 (PC scope) all just work. I thought that's how it's supposed to be.   

I guess if your goal is to struggle to out do bad engineers, then you are in heaven.  However,  I buy T&M equipment to do tests and measurements.  I realize I might be in the minority in this thread.  Carry on..

[alias095]

I have other oscilloscopes both analog and digital and not one. With this just an interest of repair

[alias095]

You can also check the signal levels after switching on FPGA_READY, FPGA_DONE,FPGA_RECONFIG?

[alias095]

Attach boot log
Can update via rs232?
Or how you can check the operation of the FPGA or buttons?

[DavidAlfa]

You have a sample log here:
https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/msg3580941/#msg3580941

Update what? The firmware? The standard way of updating is using Platform-tools.

Flash the oldest platform-tools version, the keypad kernel module (/dso/etc/fpga_i2c_kb.ko) is a lot more verbose and shows the activity of any key/knob on the terminal.
If working, you'll see a lot of messages when handling the keypad:

Code: [Select]

[   19.680459] Get irq key
[   19.696630] dso keyboard: key (code 0x12) pressed.,17
[   19.830445] Get irq key
[   19.846219] dso keyboard: key (code 0x12) released.,17
[   21.380455] Get irq key
[   21.396163] dso keyboard: key (code 0xe) pressed.,13
[   21.505450] Get irq key
[   21.520995] dso keyboard: key (code 0xe) released.,13
[   22.180451] Get irq key
[   22.196021] dso keyboard: key (code 0x3) pressed.,2
[   22.280469] Get irq key
[   22.297215] dso keyboard: key (code 0x3) released.,2
[   22.380463] Get irq key
[   22.396282] dso keyboard: key (code 0x3) pressed.,2
[   22.480476] Get irq key
[   22.496142] dso keyboard: key (code 0x3) released.,2


[alias095]

Where can I download the oldest platform-tools version?

[DavidAlfa]

Read the FAQ in my signature.
I currently made any all-in-one package with all versions.

[alias095]

https://drive.google.com/drive/mobile/folders/1-J-Dz7aB6hV3MmuJj-t_35cBSadiGHVF

[alias095]

Flash Platform-tools version 2020.12.21   fpga_3000
there is no response to the buttons.
The lines confuse me:
[   12.653117] fpga_ctl_kbd_event:17, 3, 1, 4
[   12.657289] fpga_ctl_kbd_event:17, 5, 1, 14
[   12.661490] fpga_ctl_kbd_event:17, 7, 1, 54
How can I check the module /dso/etc/fpga_i2c_kb.ko)  and verbose and shows the activity of any key/knob on the terminal?
Ordered gw2ar...

[LarryR]

I just received my new DSO-2D15 today and it has a new version of software installed:
Version:  1.0.3.0.0
Date:      230327.00
Hardware: 003.002.001.000.000.000.000.001
Firmware: 3205

Just wondering if anyone knows what's been fixed/changed since 1.0.2.0.0

Thanks

[DavidAlfa]

Date:      230327.00

It's a newer software than available from Hantek.
Could you run Backup Builder and send me the dso3kb_CNxxx_FULL.upk / tar.bz2 file?
So I can make a new update package from it.

Any doubts read the FAQ 

[DavidAlfa]

Thanks for sending the file, LarryR 

New update:

»  2023.03.27 Unofficial update, extracted from a device that came with it from factory.

Changelog (Like always) is completely unknown!
(Or, most likely, what are the new bugs, following Hantek's updates trend...  )

Edit:
It seems the zoom is working again? (Able to move all the way back, instead limited to the trigger position)

[LarryR]

I just viewed the ascii strings in the application code for the scope and found may references to 'anolis'

Does anyone know if Hantek used https://openanolis.cn/ to build the application(s) for the scope?

[Algoma]

Its an Allwinner F1C200S running Sunxi Linux,

https://www.eevblog.com/forum/testgear/hacking-the-dso2x1x/ has much of the details so far.

Its likely that Hantek's software used Anolis Linux OS on another SoC .. Looking through the code, it has been ported to many differnt models of their scopes and there remains alot of scrap code.