-
#450 Reply
Posted by
imk
on 17 Jun, 2021 15:51
-
tttonyyy,
Re paying for the hantek, yes i did pay with paypal and thanks for the reminder about my rights.
However Banggood have a Get Out Of Jail Free clause.
Have you contacted Hantek about this problem, Yes
Did you follow their advice, Yes i uploaded the new firmware.
Sorry will don't accept returns of modified products. :-(
Have you contacted Hantek about this problem, Yes
Did you follow their advice, No.
Follow their advice and get back to us. :-(
This is the Kobayashi Maru scenario, anyone know James T Kirk's number :-)
I think the way the return request is going I shall be out of time on Midnight Friday.
Not too worried, either ebay it, or await next firmware from Hantek which is few weeks overdue.
Maybe they are feeling the flak from these threads and having a do or die last push.
Has anyone checked the job adds for programmers at Hantek :-)
BTW when reporting new DSO2xxx features would it be worth noting the firmware release number/date?
all the best imk
-
#451 Reply
Posted by
DavidAlfa
on 17 Jun, 2021 18:37
-
It's not the AWG, anything you throw there with too high level and 20mV/div setting(1x) or less, makes it!
Will flash it again and ensure it's not a software issue, but...
-
#452 Reply
Posted by
Victor1964
on 17 Jun, 2021 18:40
-
-
#453 Reply
Posted by
imk
on 17 Jun, 2021 19:25
-
My Hintek DSO2D15 is OK
What firmware version are you on please?
-
-
I have a question?
Unintentionally installing the update dso3kb_20210510. On the FW (3000) software. The oscilloscope stopped working as it should !!! How can I become a licensed owner of this device? (DSO2D15)
-
#455 Reply
Posted by
Victor1964
on 17 Jun, 2021 20:45
-
DSO2000 Firmware
2021-04-20
-
#456 Reply
Posted by
imk
on 17 Jun, 2021 21:13
-
-
#457 Reply
Posted by
DavidAlfa
on 18 Jun, 2021 07:06
-
From Hantek site download firmware http://www.hantek.com/products/detail/17182 20210420
Inmcorrect, that update doesn't change Fw version!
I have a question?
Unintentionally installing the update dso3kb_20210510. On the FW (3000) software. The oscilloscope stopped working as it should !!! How can I become a licensed owner of this device? (DSO2D15)
I will delete that version as it only changes the fpga firmware, nothing else!
Check my GDrive folder, go to Mods/FW changer, download and run FW3000 update. Done!
These important details shuld be in the first post, actually the info is spreaded all over 20 pages (and rising), making it hard to find.
However, thread starter seem to have gone long time ago (Last login: December 30, 2020), making most important post completely useless.
People willl keep flashing wrong versions because of this.
Moderators: Can we take control of the first post to use it as an index / summary?
-
#458 Reply
Posted by
xuraax
on 18 Jun, 2021 08:06
-
@DavidAlfa,
That is the best advice to date.
As an obvious newbie on these topics I am in awe at the depth of knowledge possessed by some of you.
As a newbie it is actually confusing to draw any sort of conclusion from the 20 odd pages of comments put forward so far.
A summary of what has been learned so far from you guys will be greatly appreciated. For example the implication of the various firmwares 3000, 3100....3202 on the scope and which one to choose for a particular model!!!
Thanks for ALL your input.
Regards
-
-
The problem with the generator remained unresolved.
FW(3000).dso3kb_20210416.(DSO2D15)
-
#460 Reply
Posted by
AndrewBCN
on 18 Jun, 2021 08:44
-
I would suggest locking this thread and creating a new one with a first post that clearly explains the firmware update process, but still references this "old thread" for those who want the complete details, and also references the "hacking" thread for those who want to explore their Hantek DSO2X1X.
And perhaps in the new thread we can move on to comments about using these DSOs instead of bitching and whining about them (including by people who don't actually own one)?
EDIT: done creating the new thread, and I have reserved and will curate the first five posts with essential information and facts.
The new thread is here: https://www.eevblog.com/forum/testgear/hantek-dso2x1x-firmware-updates-and-best-use-practices/
-
#461 Reply
Posted by
tv84
on 18 Jun, 2021 08:53
-
The sooner you create the thread, the sooner people move there.
Regarding the "bitching and whining", it will continue to happen on BOTH threads. It's a feature.
-
#462 Reply
Posted by
Gerasim
on 18 Jun, 2021 09:57
-
I have also written here more than once about the problem with the generator. Rollback to the previous firmware does not help. But apparently few people are interested in this))
-
-
Let them work! Let's not get distracted by trifles. I hope they heard us.
-
#464 Reply
Posted by
Piton
on 18 Jun, 2021 11:02
-
Sergey_Malyshev, try long pressing the "Default Settings" button, there are options for a generator and maybe a calibration. I fixed this problem by soldering the memory and only then did I find this feature. But, as it turned out, it does not work for everyone.
-
#465 Reply
Posted by
DavidAlfa
on 18 Jun, 2021 11:07
-
It seems to work after you entered Utility menu first. The older sw versions have more options.
-
#466 Reply
Posted by
Piton
on 18 Jun, 2021 11:22
-
I also thought that in later versions they either removed it, or hid it somewhere. I have a very early version.
-
#467 Reply
Posted by
Gerasim
on 18 Jun, 2021 11:43
-
This menu also opens for me. But unfortunately, the generator calibration does not work and gives errors
-
#468 Reply
Posted by
Piton
on 18 Jun, 2021 11:56
-
So you need to restore your version. I didn’t have any errors on the error generator, I only had one of those points, but this was after recovery.
-
#469 Reply
Posted by
Gerasim
on 18 Jun, 2021 12:15
-
I originally had version 3000. The generator worked without errors. And there was only one calibration item in the menu. After installing versions 3101 and 3102, two calibration items appeared in the menu and a generator error appeared. When I installed my native 3000 version back, the problem did not disappear, but these two calibration items remained in the menu. Apparently the new firmware 3102 registered something in the flash and rollback to the old firmware does not completely erase the 3102 firmware data from the memory. So which version do you say I should still rollback to?
-
#470 Reply
Posted by
Gerasim
on 18 Jun, 2021 13:25
-
If there is no way to format the flash via USB without unsoldering it from the board in order to write the firmware to a clean flash, then you will have to order a new flash on Ali and try to upload the image to it.
-
#471 Reply
Posted by
DavidAlfa
on 18 Jun, 2021 13:55
-
I found few things:
- The fpga file from platform tools fw3000 is not the same as my factory fw3000 backup.
- Generator amplitude is fixed after restoring my files "/cache/cali.dat" and "/cache/dds_calbration.dat"
- Made a custom update package that replaces all /dso and /cache files with my factory ones. Worked.
Gerasim, try the attached update and tell if it makes any difference.
-
#472 Reply
Posted by
AndrewBCN
on 18 Jun, 2021 14:03
-
If there is no way to format the flash via USB without unsoldering it from the board in order to write the firmware to a clean flash, then you will have to order a new flash on Ali and try to upload the image to it.
See the hacking thread. DavidAlfa and I are working on two different solutions to read/write/backup/restore/modify the SPI NAND flash. DavidAlfa is writing a low-level program that reads and writes the SPI NAND flash through FEL. I am working on a small Linux distribution that can be loaded through FEL and uses the Linux kernel SPI NAND driver.
-
#473 Reply
Posted by
DavidAlfa
on 18 Jun, 2021 14:15
-
David is actually waiting for the ram linux method!
-
#474 Reply
Posted by
tttonyyy
on 18 Jun, 2021 14:21
-
Apparently the new firmware 3102 registered something in the flash and rollback to the old firmware does not completely erase the 3102 firmware data from the memory. So which version do you say I should still rollback to?
The calibration data is stored in file /dso/etc/data/cali.dat (did you back up your filesystem first?)
It is cached in /cache/cali.dat and on my system both files were binary different after recalibration. You could try (with the older firmware) calibration, power cycle, calibration, power cycle and see if the problem remains. I doubt that the FPGA image retains anything, it is loaded over SPI every time pheonix app starts at boot (or crashes and is restarted by David's restart script).
Calibration itself is another app
/dso/app/dso3000c_calibration that is invoked by phoenix, as far as we know it generates the cali.dat files based on values determined by the current FPGA image.