New Hantek DSO2X1X models?

[imk]

I found a little annoying bug. The usb drive doesn't get mounted automatically in 20210517 SW.
However when you go to Utility menu and click Update, it gets mounted.

This can be seen on the console. The usb drive was plugged for a while (+1minute) and nothing happened.
After pushing update:

Code: [Select]

[  427.926037] phy phy-1c13400.phy.0: Changing dr_mode to 1
[  427.931558] read not supported msg id 2
[  428.582770] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[  428.809222] usb-storage 1-1:1.0: USB Mass Storage device detected
[  428.872963] scsi host0: usb-storage 1-1:1.0
[  429.926631] scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
[  429.939195] sd 0:0:0:0: [sda] 30240768 512-byte logical blocks: (15.5 GB/14.4 GiB)
[  430.019892] sd 0:0:0:0: [sda] Write Protect is off
[  430.030880] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  430.102795] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  430.333670]  sda: sda1
[  430.353794] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  431.295795] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
0:Got Signal with value mount


Hello David, good find re this bug are you going to report it to Hantek? at 'support@hantek.com'
I think the more we bring this stuff to there attention the sooner we will have a great little not big bucks scope!
imk

[DavidAlfa]

Is anyone here already being in contact with Hantek?
I think it's better to have just one person updating them with the news in this thread, instead a dozen people spamming their support mail.
I sent an email to them asking if it was posssible to help by testing their new firmwares and giving feedback about the results.
If they agree ( I don't think so) it would be great!

[imk]

Is anyone here already being in contact with Hantek?
I think it's better to have just one person updating them with the news in this thread, instead a dozen people spamming their support mail.
I sent an email to them asking if it was posssible to help by testing their new firmwares and giving feedback about the results.
If they agree ( I don't think so) it would be great!

David I contacted Hantek on 25/May and have received as you know dso3kb_20210510 which is better than the installed dso3kb_20210416
I have today sent them the latest bug report as outlined in previous post.
I am not sure if one person reporting bugs or multiple people the same bug will return the best result?
I am open to either, but do we all have the same scope e.g same model, board version and unhacked etc
imk

[DavidAlfa]

Did you try 20210517?It's been there for a long time

[Sergey_Malyshev]

Hello.DSO2D15
I installed the firmware dso3kb_20210510 Firmware: 3200.
there was a firmware dso3kb_20201118
Firmware: 3000.
how to get back Firmware: 3000?

[imk]

Did you try 20210517?It's been there for a long time

David
20210517 I can only see dso3kb_20210416 on Hantek site and dso3kb_20210510 is one they sent me a link to (think it maybe beta)
where did you find 20210517?
imk

[DavidAlfa]

Hello.DSO2D15
I installed the firmware dso3kb_20210510 Firmware: 3200.
there was a firmware dso3kb_20201118
Firmware: 3000.
how to get back Firmware: 3000?

You have to use platform tools. Check my google drive folder.
Some will change your FW to 3101 or 3102, but they all work ok if you had FW3000.
The only fw making trouble is 20210510, that changes it to FW3200 and breaks calibration.
Mine was 3000, I installed 20210517(FW3102) and it works a lot better than the old versions.

If you have any issues, you can flash 20201221(FW3000) that will completely restore it.
Serial, model and HW will be undefined after flashing platform tools, but it doesn't seem to matter.
If you want restore them, copy the script do_other_update(Edit Model-Serial-Hardware) to the root of the usb drive.
Rename it to do_other_update. Edit and change the model and serial number.
Then you can update throught the system menu to the latest compatible version (actually 20210416).
If "do_other_update" is present, the system will run it automatically.

where did you find 20210517?

Someone sent be a PM with that fw. It's not an update, but a full fw, it's in platform tools.

[imk]

David thanks for the platform-tools-20210517(FW3102) info.
I had a look and think i'll await reply from Hantek rather than brick my scope.
imk

[Sergey_Malyshev]

Thank you, your firmware helped.

[DavidAlfa]

I had a look and think i'll await reply from Hantek rather than brick my scope.

They're unbrickable, don't worry about that, FEL mode is a low level boot mode linked to the SOC itself.
No matter what, you can always enter FEL mode by pushing the button below the DSO and powering it on, then flash anything.
I erased the whole flash. I even removed it physically. It always works.

Thank you, your firmware helped.

Nice! But that fw is old and very unstable. It has a lot of issues. Try without fear the 3102 version!

[imk]

Hello followers of this thread,

Re my previous post re UART Trigger/Decode locking up the scope when adjust the timebase Sec/Dev.

I have just completed testing with i2c Trigger/Decode and problem is the same sorry to report, hence i think there is some generic refresh serial trigger issue.

Also when i was testing the i2c serial trigger I adjusted the Acquire->Mem Depth from 4k to 4m and scope locked up :-(
However a simple power off/on cycle does not fix the problem as when the scope starts up it is still in 4m mode and immediately crashes again.
So i had to unplug the leads to remove input signals, reset mem depth to 4k, then plug the leads in again.

I have reported this and previous UART serial trigger/decode to Hantek.

Lastly the i2c Sync Decode is terrible, monitor mode is not too bad, but analyzing a complex i2c data sequence will be difficult as only a few bytes of data is displayed.

Even i am beginning to lose faith in this scope, or maybe my expectations were simply to high.
I still think as a simple waveform (sine/square bit of audio ) scope with integrated signal generator it seems to work well and is probably good value for monies.
But for protocol decoding I will be using my DreamSource Lab logic analyzer.
As I don't think this range of scopes has enough horse power or software sophistication to handle serial protocol triggering/decoding.
I hope Hantek fix the problems and prove me wrong :-)

imk

[Sergey_Malyshev]

Tell me where to download version 3102?
Thanks a lot in advance.

[Sergey_Malyshev]

after the firmware(dso3kb_20210416) usb stopped working.
Sorry for my English.
https://youtu.be/8ov14v8Vshg

[DavidAlfa]

Yes, that's something I noticed too!
A fix is going to utility/update, without updating.
It will enable de USB and start working.

[Sergey_Malyshev]

//Hi David.
//Can you find out in more detail what I need to do?
//After all, the usb port does not respond to usb memory.
//maybe others already had such a problem and it was already mentioned on the forum?
-------------------------------------------------------------------------------------------------------------------
Thanks, I figured it out by reading the forum and working with your files.
Version 3102 did not work, and now version 3101 has been installed and is being calibrated.

[DavidAlfa]

Dude, let's keep that stuff in the hacking thread!
I also made the same mistake...  deleted that

[DavidAlfa]

 

[Microcheap]

Well, nobody can say this scope is a useless toy anymore... 

[Sergey_Malyshev]

 

[DavidAlfa]

It gives an idea of the poor performance of the CPU...
At  default CPU speed the game runs pretty choppy, it needs almost 700MHz to run properly.
The stm32F429 does a lot better at 168MHz, that's the difference of having a FPU!

[AndrewBCN]

OMG this is just A-M-A-Z-I-N-G!         

[AndrewBCN]

It gives an idea of the poor performance of the CPU...
At  default CPU speed the game runs pretty choppy, it needs almost 700MHz to run properly.
The stm32F429 does a lot better at 168MHz, that's the difference of having a FPU!

Yes, the ARM926 CPU in the L2C100s is a 20-year old design from 2001(!), while the Cortex-M4 in the STM32F429 is a much more recent architecture. I think AllWinner went with the ARM926 for this chip because they got the IP for next to nothing. This CPU is supposed to cost $1 in quantity, while the STM32F429 costs around $5.

[DavidAlfa]

I wanted to make an update package that simply runs Doom, but there's a problem.
Whenever you start the update process, the keyboard is disabled on purpose to force rebooting.
So it would work but no way to play.
What I did was to install a daemon that monitors the Doom files, once the USB is plugged, it will stop Phoenix, start Doom, and wait for it to exit, then restart Phoenix.
The modification can be easily reversed.
I'll upload the files in a moment

[AndrewBCN]

I wanted to make an update package that simply runs Doom, but there's a problem.
Whenever you start the update process, the keyboard is disabled on purpose to force rebooting.
...

Hmmm, I think there is a good chance that what happens when you start the update process is that the USB keyboard driver (or some other keyboard driver) kernel module is unloaded, not that the keyboard is disabled per se.
As usual, you can check that quite easily with a simple lsmod command, before and after the update process is started.

[DavidAlfa]

Not exactly, because they key presses are still shown in dmesg.
It's something related to the shell.
The only thing I know is that libanolis starts the update package with "sh -c", which probably affects it.
I'm not a pro at linux