Products > Test Equipment

New Hantek DSO2X1X models?

<< < (305/388) > >>

groomit:
Hi there, I'm new on this forum and overwhelmed by the amount of information shared.
I have the Hantek DSO standing around on my desk for quite a while now. It still has the factory firmware installed. After digging through all of the information on this thread as well as on the hacking thread, I'm still a bit confused regarding the backup steps necessary before tinkering around with firmware updates.
Can anyone please explain to me the difference between Flash-, EEPROM- and Backup-Builder? What contents are saved on each backup? I assume it is not sufficient to read the ROM with a CH341A and a clip - correct?

I don't mean to bother you with my request. It is just that I'd like to better understand what and what for I'm doing each backup.

Thanks in advance!

DavidAlfa:
Did you read the FAQ?
Backup builder does a copy of the important data like model, sn, generator calibration, current software, FPGA firmware and also the eeprom.

Backup builder files are enough recover but it's always good to make a 1:1 backup with  dsoflash just in case.

groomit:

--- Quote from: DavidAlfa on August 01, 2023, 01:44:57 pm ---Did you read the FAQ?
Backup builder does a copy of the important data like model, sn, generator calibration, current software, FPGA firmware and  larz eeprom.

Backup builder files are enough recover but it's always good to .ake a 1:1 backup with  dsoflash just in case.

--- End quote ---

Hi David,

Thanks for your fast reply. Yes, I went through your extensive FAQ section - Thank you for your work! But still it was confusing what backup does what.
So now I understood that Backup Builder already saves a lot of data:
- Generator Calibration Data
- Model and SN
- Software and FPGA-Firmware
- EEPROM

As you stated, that should be enough to recover. What more/else does dsoflash do? And do I understand it correct that no seperate EEPROM backup is necessary after running backup builder?
I think most of the confusion I'm running into is the lack of knowledge about what types of storage are present and what is stored on each storage.

vistorik:

--- Quote from: groomit on August 01, 2023, 01:59:03 pm ---What more/else does dsoflash do? And do I understand it correct that no seperate EEPROM backup is necessary after running backup builder?

--- End quote ---
David's dsoflash creates a complete memory dump, including the spare area of 64 bytes for every page of 2048 bytes in one binary file of 132Mb, like the programmer CH341a with an option to read the spare area does.
If you run David's backup builder you don't need to run seperate EEPROM backup.

DavidAlfa:
The eeprom is a small memory storing some calibration values, normally nothing writes to it, it's used by the scope after a factory flash to restore the generator calibration.
But not all scopes had it, early ones like mine came blank, with the calibration only stored in the system flash.
Hantek would tell everyone to flash the scope, but that would wipe the calibration, system info...
If your version had a the calibration data in the eeprom, nice, but if not, they simply wouldn't care.

So run DSOflash and BackupBuilder. There're no other tools, it's all it needs to be safe under all circumstances.
If the scope hangs or crashes, then restore with latest Platform-tools, afterwards apply your "not-FULL" backup, will restore the important bits and it'll be ready.
DSOFlash and EE backup should never require restoring, they're there just in case.
This is properly described in teh FAQ, please read it :)


About the new encoders:
Handling cursors/levels improved by much, its's very noticeable that the new encoders have twice the pulses per rotation.
A pair of quick turns and you're already at the other side!

...
Except in trigger-> pulse mode.

The pulse width adjustment works nicely all the way from 8ns to 10ms, up and down.
But from 10ms up, it randomly goes up/down when rotating too fast, so it barely moves.
I haven't found any other settign using V0 having this behaviour, so I'm wondering if this is a firmware bug or what?
It's clearly seen here:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod