Hantek - Tekway - DSO hack - get 200MHz bw for free

[chinoy]

Tried to find the full nand backup for dso5072p everywhere in the forum but no luck.. would be much appreciate if anyone willing to share their full backup of dso5072p.. my dso5072p firmware is corrupted.. and stuck in the boot logo screen. And  would try to fix the firmware with all the guideline available in this forum..

I am pretty sure I saw some backups for the dso5072p on tinheads microsoft cloud drive. I heard he has also shared some files on his google drive. You can also find schematics for most of these scopes on his cloud.

[ricsne2010]

The way in which the backup .txt HELP description should read is as follows: (since english was not his first language, this is what I was able to determine and I have tested and it works)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note - the backup will create a dump of all "or" specified "mtd" (aka Mounted) partitions, using the following .TXT files and or params:

- If you create an empty .TXT file with the file name 'oob.txt' on the root of the flash drive, a dump of the OOB file(s) will be created. If you create a empty TXT file named 'omitoob.txt', then an OOB file will NOT be created. (if you break down the .txt file name, the first 4 letters of the second file name is "OMIT" aka "ignore")

-  If you create an empty .TXT file with the file name 'dumpbad.txt'  on the root of the flash drive, a dump of the file(s) PEBs will be created. If you create a empty TXT file named 'omitbad.txt' the the PEB file(s) will NOT be created.

- If you create an empty .TXT file with the file name 'mtd.txt', a 'grep -f mtd.txt' will be used as filter for /proc/mtd output. (meaning the system will look with this txt file to see what partitions you want to copy to the USB drive). If you DON'T create a file called 'mtd.txt', then ALL MTD partition found in the /proc/mtd directory will be dumped. (meaning, DON'T create this .txt file, so that you will copy all the MOUNTED drives into your USB)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Keep in mind, each of these files that you create (oob.txt, and dumpbad.txt) must be in the root of the USB drive where your backup script file is located. When you execute the "Firmware Update" feature on any DSO5000 device, the backup script will look for these files and take the predefined action. I did this on my device (a DSO5102P) just last night and I got all the necessary files I needed to conduct a restore should I need to do one via UART/USB.....

Hope this helps in claifying what the file "options" are when doing the backup of the scope's files.

Cheers
Rich

[chinoy]

dam i love this community.
Thanks so much Rich. That clears up all my doubts.
It would be a big help if you also mentioned what options you used to get your back up. Along with what options will give us the safest and most comprehensive back up.
My original plan was to take backups using all the options and hope that if things went south one of the backups would save me.
But reading your post it would seem you only used the options oob.txt, and dumpbad.txt
Keep us posted on your progress.

[ricsne2010]

Look at the bottom of this threaded post... you will see a link to a file called "Tools_P_models.zip" - the instructions for use are the same as other models.... see a previous post in this thread (on page 128) where I clear up the information regarding the use of the .txt files needed to appear on the blank USB drive (along with the backup script file)

https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg264194/#msg264194

Cheers
Rich

[ricsne2010]

Yes, this hack is still functional for all models of the Hantek DSO's....  on the first page of this thread you will find the necessary information about the various hacks as well as some other features that your scope may be able to do....

[chinoy]

Thanks.

Here is the info related to Scope Name / Serial / HW Version
https://drive.google.com/file/d/15Pm-G6RVFpDAAb4ZEi4SiN4tTDGaiS8v/view?usp=sharing

Here is a Zip file of my 4 file backup.
This is for a fresh out of the Box 5102P purchased in 2022. English. 

https://drive.google.com/file/d/1HbhIHkBzDSekn16malZbwauEgkLgOmG9/view?usp=sharing

Here is the backup of my 7 file Backup using the new script. With files with oob.txt and dumpbad.txt
I have a feeling this did not backup the last partition as others have reported in earlier posts.
If one of the experts could have a look. I too feel the file sizes maybe too small.

https://drive.google.com/file/d/1VYzGK4KdRO1FzGTx_WZTktcgsCdotpS6/view?usp=sharing


If you can not boot saying unit was not shut down right and get a black screen with 3 options. Use this to restore your Scope. (Previous link up top may have been for chinese. This version was given to me by hantek for my serial number and english interface. Copy these files to USB and press F3 option.

https://drive.google.com/file/d/1WJPtlqj6fAkvDJjJCMwuILxINMryFLEr/view?usp=sharing


I cant find the file DSO-BW-Changer.exe
If somebody can message me a link. If its cant be posted on open forum.
The video above uses it. To change the Speed. I have searched the forum for this file. Still searching.

You can grab the file here. Along with the files you will need to create a backup. Thanks to tonyalbus and his video.

https://www.youtube.com/redirect?event=video_description&redir_token=QUFFLUhqbmJvVkJsUmE3N0pzQjc1MTNwWkNnTWdGeGhJZ3xBQ3Jtc0ttN24yTjN4dy1FMXc1YTJLVTg2d3Y2cTNUTnJJYlVTVWR2Wk0wajM1b29tQzMzTnk1MUdJQ3hZRGx1Nkota1lONjVPX0RLVHlVdVYzckhRLVlMVm5QV3lSa01iZXhmN3pKU3JPeU4tQ0lNUl9zOUU5cw&q=https%3A%2F%2Fwww.tonyplaza.nl%2Fdownload%2FYT259%2FDSO5072Ppack.zip

Link to Tinmans MS Cloud one drive a treasure trove of info. I heard he has a google drive also. (Link for his Debunked Tool)
http://1drv.ms/1hf4SgO

Another thing we need to thank tonyalbus  for is the fact. That he was the first guy to clear up the fact that just because you had a 2ms time scale did not mean you had an upgraded scope. Pages of posts were this was discussed. He was the first guy to prove that theory wrong.

One last mystery I still need to solve is how did he manage to find that file that does the firmware change via windows. DSO-BW Changer.

[Bruno02]

Hello from France,
I am trying to backup the content of my DSO5072P (firmware v3.40.0) with the tool dso5kp_backuptool2.up. I tried with a USB key formatted in FAT then in exFat then in FAT32. Each time the backup fails with an error code 0xfe.
Can someone please advise me?
Thank you!

[Bruno02]

Nobody?

[Tugo]

I have the same HW and SW as you (DSO5072P with firmware v3.40.0).
From my backup folder I believe I used 2 different backup tools (old and new - well they were new at the time - November 2019).
Old version got me 4 files (boot, kernel, logo and root) which were just 1MB, 2MB and twice 512kB.
I managed to get 8 partitions I just forgot how I did that.
They are about 127MB all (largest just below 70MB).

I suggest you to check everything chinoy put in the post.

[Bruno02]

Hi,
Thank you Tugo.
I finally found the problem this morning, it was the USB key that was the problem. With 2 other keys, it works without problem
If other people are wondering, the key must be formatted in FAT32.
And now the 200MHz hack

I add that it is absolutely necessary that the key has a formatted capacity of at least 4GB, otherwise it does not work. That was my problem.

[Tugo]

And what was procedure for your oscilloscope and what did you do to hack it to 200MHz?
I didn't hack it because I didn't know if it can be done with newer HW.
I believe we have the same HW and SW version.

And how did you test it to know that you really have 200MHz now?
Did you do just software hack or also HW?

[Bruno02]

Hi Tugo,

For the backup of the 8 elements, you need a key that contains in the root :
- dso5kp_backuptool2.up
- dumpbad.txt (empty file)
- oob.txt (empty file)
The saved files will be in the "dump" directory.
The operation takes a few minutes.

For the hack, I used the software "DSO-BW-Changer.exe" via the USB link (with the rear connector). Note that the oscilloscope does not restart itself as indicated, it must be rebooted.

I tested the hack with a VHF generator (which does not go higher than 160MHz), it works.

I just compared 2 backups (before and after the hack) with WinMerge, there are many differences between the 2 files "mtd5-rootfs.bin". The others are identical.

[Tugo]

Did you do any HW mod like removing 2 SMD capacitors?

[Bruno02]

No hardware modification, I didn't even open the case.

[McJanDK77]

Is it possible to use this DSO BW Changer software for my DSO4104C ?

[markhen]

I followed the instructions above and successfully converted my DSO5072P to 200MHz - thanks to all!!

I also have a Hantek MSO5074FG - has any one successfully upgraded this model? I see some references in the thread, and I've tried the tools that are possibly common, but no joy (at all). I'd love to upgrade this 4 chan scope!!

Cheers

Mark

[StuBudd]

A late night play:
New DSO5072P
SW 3.40.0 (210308.0)
HW 1010xffff8108
Power Board DSO5000 Series Power Data 2020/08 Ver 2.1
Has a "card reader" hardware between CR2032 and beeper.
Mainboard 2015/5/26 Ver 1.01 DSO5000C Serial MB

Windows 8.1
USB driver had to be installed booting into "Disable Driver Signature Enforcement"
Could not connect to device (no idea ~ SW version!?!)

Upgraded SW to 3.40.0 (210225.0) dso5kp_func_dso5072p20210225.up ~ No backup created prior to upgrade

This upgrade is from Hantek ~ no idea why an earlier SW version.

Can now connect to device. Scope software run in compatibility mode Windows 8.

DSO-BW-Changer.exe worked after installing C++ Redistribution for missing DLL. Think 2010 version. 2015 may not work.

DSO-BW-Changer.exe seems to work although I have no idea how to test. Software shows DSO200MB.

Device functions. 

But then I am new to oscilloscopes

Got some 200MHz probes coming 

Thanks and now off to sleep.

[tehnics]

Hello,
I am new here and I have a problem with my Hantek 5072P. Was working fine but not used for about half year. Last week wanted to use it and logo appear and freeze.
Well, I do not have a back-up done, I never though will be a problem with it.
So I started to search on internet about issue and most of the google research leads to this topic.

I used  DNW.Exe and via serial I was able to see all message on start-up boot.

Boot log file is below

Code: [Select]

*** Warning - bad CRC or NAND, using default environment

##### EmbedSky BIOS for SKY2416/TQ2416 #####

This Board: SDRAM is 64MB; LCD display size is: 800 X 480

Press Space key to Download Mode.!

SD:File System init failed!

Start Linux ...


NAND read: device 0 offset 0x300000, size 0x400000

 4194304 bytes read: OK

Boot with zImage


Starting kernel ...


Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #10 PREEMPT Thu Feb 9 10:40:49 CST 2017
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 58996k/58996k available, 6540k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc4800000 - 0xf6000000   ( 792 MB)
    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc03f0000   (4000 kB)
      .init : 0xc03f0000 - 0xc0410000   ( 128 kB)
      .data : 0xc0410000 - 0xc05a9140   (1637 kB)
       .bss : 0xc05a9164 - 0xc05c6e9c   ( 120 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:107
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c-fb s3c-fb: window 1: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 103 at 0x000000ce0000
Bad eraseblock 242 at 0x000001e40000
Creating 8 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000004e00000 : "rootfs"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       0
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd3
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0  (driver?)
1f01             512 mtdblock1  (driver?)
1f02            2048 mtdblock2  (driver?)
1f03             512 mtdblock3  (driver?)
1f04            4096 mtdblock4  (driver?)
1f05           71680 mtdblock5  (driver?)
1f06            4096 mtdblock6  (driver?)
1f07           47104 mtdblock7  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)



I press space key right away pressing power button and I enter in download mode (see attached image). All drivers installed and was no problem to access oscilloscope via USB.
BUT from here I am lost .
I look to some video and I understand I should update "rootfs.ubi" *F5 option in menu*, it was done successfully but noting changed, still same problem with freeze logo

Looking more, also I found this topic https://www.eevblog.com/forum/testgear/hantek-dso5102b-need-kernel-zimage-not-booting/
where might be a problem with Linux kernel and need "zImage.bin" to be uploaded. Does anyone has this file ? What could be problem ?

I have to say that I am not newbie in electronic, but I am totally lost in Linux things, so please be patient with me to make my osciloscope alive.

[tehnics]

I look more in the log file and what jumped in my eye is the last part:

VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0  (driver?)
1f01             512 mtdblock1  (driver?)
1f02            2048 mtdblock2  (driver?)
1f03             512 mtdblock3  (driver?)
1f04            4096 mtdblock4  (driver?)
1f05           71680 mtdblock5  (driver?)
1f06            4096 mtdblock6  (driver?)
1f07           47104 mtdblock7  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

after this I run again in download mode and press

• Set the boot parameters and [5] View the parameters (too see all booting parameters)

This is I get as result

Code: [Select]

Enter your selection: 5

Name(enter to view all paramters):

bootargs=noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M

bootcmd=nand read.jffs2 c0008000 kernel;bootm c0008000

bootdelay=1

baudrate=115200

ethaddr=10:23:45:67:89:ab

ipaddr=192.168.1.6

serverip=192.168.1.8

gatewayip=192.168.1.2

netmask=255.255.255.0

stdin=serial

stdout=serial

stderr=serial

ethact=dm9000

mtdids=nand0=nandflash0

mtdparts=mtdparts=nandflash0:512k@0(bios),512k(params),2048K(logo),4m(kernel),-(root)

partition=nand0,0

mtddevnum=0

mtddevname=bios


Environment size: 504/16380 bytes
as far as I can see,  root=ubi0:rootfs , that is correct or wrong ?

That makes me feel that when linux try to load do not find boot root location/partition. I understand correct ?
How to correct this ? Any idea ?

I had most as same problem as this quy (same error issue) in this topic: https://www.eevblog.com/forum/testgear/hantek-mso5074fg-firmware-upgrade-problem/msg598724/#msg598724
So my solution is to somehow someone to send me a DSO5102P or 5072P back-up file...

[Tugo]

Hi!
I will not be able to help you with anything beside an advise: how about contacting Hantek directly to tell them what happened when you turned it on after half year of no usage. Later you can tell them more but I wouldn't do that in my first message to them.
And please let us know how it went. Maybe somebody else will also need the same help.
Good luck 

Edit: Or you can go to their forum -> https://www.eediscuss.com/forum.php

[An-162]

For the backup of the 8 elements, you need a key that contains in the root :
- dso5kp_backuptool2.up
- dumpbad.txt (empty file)
- oob.txt (empty file)
The saved files will be in the "dump" directory.
The operation takes a few minutes.

Thanks a lot!
Without these two text files, I was able to backup only 4 small files, as already mentioned above.
And now 132 MB are saved!
------------------------------------------
Спасибо огромное!
Без этих двух текстовых файлов у меня получалось сделать бекап лишь 4-х небольших файлов, как выше уже писали.
А теперь сохранилось 132 Мб!

[Gologan]

Hello friends !
I have a Hantek oscilloscope DSO5202B , I downloaded the latest firmware from the official Hantek website and I failed to update.
Please help me with the latest software version for my hardware.
Thank you.

[DC1MC]

OK, let's go quickly over the procedure:

1) you downloaded and extracted the firmware a file, like:
dso5kb_func_dso5202b20190830.up

2) you have found the most miserable, obsolete USB stick, 2GB ideally, (4GB works, for me nothing over 8GB ever worked) and formatted FAT32 and nothing else, no NTFS, no exFAT and such, keep in mind the current version of windoze do not offer FAT32 anymore, they need to be specially convinced, check for yours how do format FAT32.

3) you have copied the extracted firmware file. and NOTHING else on the POS stick freshly formatted.

4) you've repeated the fw update procedure and either works or look back on 1-3 to see what have you done wrong  .


 Cheers,
 DC1MC

[Gologan]

Thank you for answer.
I did exactly as you said.
After your post, I tried with other USB sticks, the result is the same.
Firmware failed.

[An-162]

And now 132 MB are saved!

Here are the files. Take whoever needs it.
https://drive.google.com/drive/folders/13WVNZfH3aSLwlMV2sJot-DUVy6DNGvMl?usp=share_link
Oscilloscope model in the photo.
Before creating a backup, it is updated with the latest firmware at the moment.
Bandwidth expansion is yet to come.
Now I'm working on a very high slew rate edge generator based on a tunnel diode and a transistor...
-------------------------------------------------------------------
Вот эти файлы. Берите, кому нужно.
https://drive.google.com/drive/folders/13WVNZfH3aSLwlMV2sJot-DUVy6DNGvMl?usp=share_link
Модель осциллографа на фото.
Перед созданием бекапа он обновлен самой последней на данный момент прошивкой.
Расширение полосы пропускания еще предстоит.
Сейчас работаю над генератором фронта с очень большой скоростью нарастания, на основе туннельного диода и транзистора...