VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen

[rlohmann]

Hi there,

the mentioned scope is a 4 channel / 80MHz device sold by Conrad / Voltcraft in Germany. The device and specs look similar to  Hantek DSO4084B.

The unit I  have in hands does actually not start properly and get stuck on boot screen.

I attached a serial adapter and captured the terminal during boot. (attached)

It get stuck after:

                acq_dot_nm_of_timerange =4000,time_range=1600000000000,dso_acq.dot_factor =1,sample_rate =2500.000000
                dso_acq_control:1:2056, 2056,0
                dso_acq_control:2:2056, 2056
                dso_acq_control:3:102800000, 103600000
                dso_acq_control:4:after= 102800000, before= 103600000

... hitting enter i get back to the shell:

               unix:path=/tmp/dbus-2Gwvd7Fgoi,guid=78229ec33879218ea98a0b54386d509c
              [root@Hantek ~]#

Hope anybody can help me to figure out whats wrong with the unit and how to get it back to life. 

[rlohmann]

... looking closer at at the log, I#ve noticed:

                acq_dot_nm_of_timerange =4000,time_range=1600000000000,dso_acq.dot_factor =1,sample_rate =2500.000000

.. which appears strange to me.

So I looked for any config  and found /dso/etc/system.inf

Code: [Select]

code:
[machine]
       Model=dso1202l
       Vendor=hantek
       Product=FGen
       Manufacturer=hantek
       Serial=DSO4D143501107
[version]
       Pcb=1001
       Keyboard=11
[language]
       Lans=255
       Language=1
[add]
       Start=0
       Update=0

I guess the previous owner applied a wrong update ...

I've found few update files online:

                - dso4kb_20180831.upk  (Conrad/Voltcraft)
                - dso4kb_20181208.upk  (Hantek  DSO4000B)

Is here a way to apply the update form the shell or automatically during boot?

Or how to extract those files and hopefully replace the according files manually within unit?

Maybe someone out there with this scope could help me out with a tar of a working /dso folder ...

[tinhead]

sure, unpack first the update by

gpg --batch --passphrase-fd 0 dso4kb_20180831.upk

and give as password dso4000bc

and check what do_update.sh is doing (basically copying few files and setting +x permission)

[rlohmann]

Thanks a lot TinHead!      ... you made my day!

The cmd line did not work out for me for some reason. But it turned me into the right direction ...

with:  gpg -o out.tar -d dso4kb_20180831.upk

    ... extracting out.tar and the containing dso4kb.upk.tar I got "upend" and "package/"

Then I went through package/do_update.sh and manually updated all files manually ...
And merged config/root/system.inf with package/system.inf :

Code: [Select]

[machine]
       Model=80M$DSO1084E
       Vendor=voltcraft
       Product=DSO
       Manufacturer=hantek
       Serial=DSO4D143501107
[version]
       Pcb=1001
       Keyboard=11
[language]
       Lans=65535
       Language=6
[add]
       Start=389
       Update=0

On first reboot i got the same error, stuck at boot screen / same terminal output ...   

But I noticed  "#rm /dso/app/etc/aslf/*" in package/do_update.sh ... so I made a backup of aslf and removed /dso/app/etc/aslf/*...

Voila, the scope finally booted and and appears to work fine!   

[tinhead]

Thanks a lot

you welcome.

Out of curiosity, can you post picture of let say 50-100MHz sine one one channel with max sampling ?

I hope it does not looks like this one, which from 4000C model, which is based as the B Models on multiple AD9288



Your 4000B should looks much better, but i never had a chance to see them in action.

[rlohmann]

I would be pleased to help ...

Unfortunately, I don't own a signal generator.  Let me check if I can hold on one.

I'll get back to you as soon as I have a update. 

[KlausF]

Thanks a lot

you welcome.

Out of curiosity, can you post picture of let say 50-100MHz sine one one channel with max sampling ?

I hope it does not looks like this one, which from 4000C model, which is based as the B Models on multiple AD9288



Your 4000B should looks much better, but i never had a chance to see them in action.

Have you tried set the trace to average? Does the trace then get clear and crispy?
Did you terminate ?

@rlohmann
Well done, you got it back to working.
Wondering, whether the DSO-1084E is as "buggy" as is this similar looking one here

[rlohmann]

@KlausF 
This does not look promising ... till now my scope did not crash so far.
Need to check view examples, but as I updated the FW during the recovery, i'm confident at least few of them got fixed meanwhile.

 
@tinhead   
Just as a side note, I#m guessing the VOLTCRAFT DSO-1084E (aka Hantek DSO4084B) does have a identical PCB to Hantek DSO4000C ...
At least some of the wave gen stuff is on the PCB.

I'm meanwhile trying to figure out if I can get wave gen to work as well.

https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/new/?topicseen#new   

[tinhead]

Have you tried set the trace to average? Does the trace then get clear and crispy?
Did you terminate ?

Klaus it's not my pic, it is taken from here:

https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/

and no, it does not matter if signal has been terminated, when sampled data has been not sorted properly due to bad fpga design, clock issues or signal path skew -> which was the case in the past for some Hantek models. The DSO4xx4B/C seems however to use single ADC



instead of 8 of them



Interleaving is done within ADC, so one must be a real idiot to still screw this up - but who know, and that's why i'm asking for screenshot of such 4ch model (just check pictures from above thread).

And no, i don't wan't clean avg pics, this is not what i'm asking for.

[DK87]

Hey there,

I also own a DSO-1084E which has exactly the same problem.

Recently I told a friend about that issue and he told me to take a look at the EEVBLOG Forum and voila...I just found this thread 


Using another scope I inspected the mainboard for UART Pinouts, but I can only find pins that raise to 3,3V and none of them seems to be "alive" during boot.
@rlohmann..can you tell me where the UART Connector pins are?

In the attachment below is a picture of my pcb and the pins I probed.

Am I doing something wrong?


Thanks a lot 

[rlohmann]

Hi DK87,

welcome to the forum! 

If I remember correctly, the connector close to the RTC battery is the one I connected the FTDI adapter.

I'll open my scope and check the connections, once I'm back home on Sunday.

 

[DK87]

Hey rlohmann,

thank you


But you won't have to open it up anymore because
It's WORKING 


You were right, the UART pinouts are right beside the RTC battery, I think I have been too lazy in probing or I was just too late when I probed the pins.

After I found the right pins, I connected with my CP2102 UART USB Bridge at 115200 baud and the console
outputted almost the same as in your initial thread.

I decompressed the firmware image downloaded from the conrad website but i haven't updated the files, I just deleted /dso/app/etc/aslf/*
and it worked!

Thank you very very much!


By the way:
I have put my log in the attachment for interest. 
Parts with "##" are a new section because I messed up with vi and you don't wanna see that

[rlohmann]

Great to hear your scope is working again. 

Could you mark the serial connections in your initial photo and post it here for reference?
Just in case someone else is looking for this information ...

[DK87]

of cause I'll do that.

Here it is 

[tkoop]

I think there was a wrong firmware published at some point. I just received a used scope like this. The description said, that the firmware has to be reflashed in order to use it. I'll just leave the serial output here without any comments...

Code: [Select]

acq_dot_nm_of_timerange =4000,time_range=1600000000000,dso_acq.dot_factor =1,sample_rate =2500.000000
dso_acq_control:1:2056, 2056,0
dso_acq_control:2:2056, 2056
dso_acq_control:3:102800000, 103600000
dso_acq_control:4:after= 102800000, before= 103600000

unix:path=/tmp/dbus-2cwNKRB5GT,guid=f88b9ed89c06967a785f15695c8ae710
[root@Hantek ~]#cat /dso/etc/system.inf
[machine]
       Model=dso1202l
       Vendor=hantek
       Product=FGen
       Manufacturer=hantek
       Serial=DSO4D143501107
[version]
       Pcb=1001
       Keyboard=11
[language]
       Lans=255
       Language=1
[add]
       Start=0
       Update=0
[root@Hantek ~]#


[KlausF]

Is it possible to successfully update a Voltcraft scope with a Hantek firmware?
I mean, it is the same hardware, just a different label.

[tkoop]

This should be possible. At least it worked on my DSO

[Pluscrafter]

Did anyone know which Hantek Model the Voltcraft DSO-1104E is and if the DSO-1084E or DSO-1104E is hackable ?

[Microcheap]

Did anyone know which Hantek Model the Voltcraft DSO-1104E is and if the DSO-1084E or DSO-1104E is hackable ?

Apparently these Voltcraft are manufactured by Hantek with the name DSO4004C series (http://www.hantek.com/en/ProductDetail_3_12167.html) and yes they are hackable: https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/msg2095372/#msg2095372

@tinhead
I am curious, how do you get the passphrase from the .upk files? I've been looking at it during the weekend with no success until I found, by chance, that you had already posted it here. I wanted to create an update file to easily re-config the BW of these scopes without the need to open the case.

[tinhead]

@tinhead
I am curious, how do you get the passphrase from the .upk files? I've been looking at it during the weekend with no success until I found, by chance, that you had already posted it here. I wanted to create an update file to easily re-config the BW of these scopes without the need to open the case.

the first time (~10yrs ago) was hard, as i had to buy first proper tools to dump the NAND and read content (that was the famous 0571tekway password), later it was easier as i had lot of Tekway/Hantek gears on my desk. So generally i was always doing dumps, and guessing pwd as well - once they started to use model name as password (0571tekway, 111111, 949307, dso5000p, dso5000c, mso5074fg, dso1000e, dso4000bc, ...)

The rest of update file is easy step, just remember to tar/gzip under Linux (to get +x rights), or add it into "update" script.

Btw, not sure if this is still working with these models, did you checked it? -> https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313

[Pluscrafter]

Would you recommend this scope for a beginner?

[Microcheap]

Would you recommend this scope for a beginner?

huum... yes it is a nice scope but, you being in Europe and given the small price difference I would definitely recommend that you go either for the Rigol DS1054Z or Siglent SDS1104X-E that have better specs and more mature firmware. You can check Batronix in Germany or Batterfly in Italy for prices.
You can get the Hantek DSO4084C from Aliexpress cheaper than Conrad's but then you wont have local support.

[Pluscrafter]

So I bought the scope, but to hack it I have to unscrew it. Are these Inbusscrews inch screws ? It's too big for a 2.5 mm one and too small for a 2 mm one. And has anyone an idea to open it. I have tried it with flat screwdriver but then I would break the screw.

[Pluscrafter]

No need to help a glove for more grip.

[Pluscrafter]

Thanks it worked on the Voltcraft one you must type in 250M$DSO1254E. And is there a method to take a screenshot without to see the save menu or is this a bug? The key reuse function in the Display menu isn't there but mentioned in the Manual.
With this hack and the newest firmware of Hantek the bugs in the video does not appear.

[Space-Patrol]

Hi,

i got the same scope (DSO1084E with 4000B model. Does someone have a complete flash dump?
I do it the first time.

I attached a log file created by hterm for windows.

Thank you!

[archive]

Hello.
I have already received the second DSO1084E oscilloscope blocked on the Voltcraft logo. I don't know when both stopped working, I don't know if they were hacked.

UART normal boot:

OM*** Warning - bad CRC, using default environment


##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; Press Space key to Download Mode.!

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
**************************normal start*******************************

NAND erase: device 0 offset 0x380000, size 0x80000
Erasing at 0x3e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x380000, size 0x800
Writing data at 0x380800 -- 100% complete.
 2048 bytes written: OK

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
Saving Environment to NAND...
Erasing Nand...
Warning: Erase size 0x00004000 smaller than one erase block 0x00020000
         Erasing 0x00020000 instead
Erasing at 0x80000 -- 100% complete.
Writing to Nand... done

NAND read: device 0 offset 0x400000, 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) ) #22 PREEMPT Fri Oct 27 02:56:10 CST 2017
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
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=5 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272
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: 58948k/58948k available, 6588k 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 - 0xc03fc000   (4048 kB)
      .init : 0xc03fc000 - 0xc041b000   ( 124 kB)
      .data : 0xc041c000 - 0xc05b5200   (1637 kB)
       .bss : 0xc05b5224 - 0xc05d2fdc   ( 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: 0xc8, Chip ID: 0xd1 (Unknown NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Creating 9 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000003a00000 : "rootfs"
0x000003a00000-0x000004e00000 : "config"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd5 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:       225
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            50 MiB
UBI: number of good PEBs:        400
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             6
UBI: total number of reserved PEBs: 394
UBI: number of PEBs reserved for bad PEB handling: 4
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  -1218469377
UBI: background thread "ubi_bgt0d" started, PID 341
UBI: attaching mtd6 to ubi1
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:       1189
UBI: attached mtd6 to ubi1
UBI: MTD device name:            "config"
UBI: MTD device size:            20 MiB
UBI: number of good PEBs:        160
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 160
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 10/8
UBI: image sequence number:  0
UBI: background thread "ubi_bgt1d" started, PID 344
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.
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
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
S3C24XX_UDA134X SoC Audio driver
S3C24XX_UDA134X SoC Audio: l3 data pin already in use
s3c24xx_uda134x: probe of s3c24xx_uda134x.0 failed with error -16
ALSA device list:
  No soundcards found.
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:10:59 UTC (946685459)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   47869952 bytes (46748 KiB, 45 MiB, 377 LEBs)
UBIFS: journal size:       2412544 bytes (2356 KiB, 2 MiB, 19 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  2261015 bytes (2208 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 124K
Failed to execute /linuxrc.  Attempting defaults...
/bin/sh: can't access tty; job control turned off
~ #

UART after pressing F2 in recovery:
 F2.txt (49.76 kB - downloaded 112 times.)

[airwolf]

Hi,

I know this thread is rather old but I also have a problem with my Hantek DSO-4084B (its a real Hantek, not Vorltcraft). It worked fine for about 4 years until last week during a measurement it started to respond slowly to inputs on the buttons, so I switched it OFF and back ON and now its not fully booting any more.
Unfortunately I cannot use the serial terminal of the scope, although I did connect it to a 2102 some time ago I never got a response from the scope, not even when it was still in working condition.
Does anyone know if there is a way to restore/reset it whitout the terminal? Of course I am not sure if there isn't a hardware fault but as the screen is working and the buttons are lit it could be firmware lost or damaged.

[Oleh UA]

Hello.  How did you solve your problem?  🙂

[airwolf]

I finally could fix my scope, the problem with the serial connection was the UART I used (it was one with a micro USB connector, not sure if it was the type or it was just broken). I tried with another one (with a USB A connector) and the sonnection established immediately.

Now all I had to do was to delete all the files in /dso/app/etc/aslf (as described somewhere up in this thread) and the scope boots again as before. Seems to be a bug in this scope, but once you know its easy to fix.

I also updated the system.inf file to get 250 Mhz, works also fine, and afterwards I installed an upgrade to 1.1.2, no problem at all. So I think its not necessary to hack the eeprom as well.

By the way opening the scope I broke the power push button, and ordered 6 new ones instead of 2 (they came in sets of 3), so if anybody needs one just write me (if you are not too far away from me  - Austria, of course)

[twoexem]

Sorry for the bump, but this was the only usable thread I found. What config (data bytes, stop bytes, parity, baud etc.) did you all use to connect to the scope? I'm currently trying to connect to my DSO5202P and no matter which settings I choose, I always get garbled junk data. It might be an issue with my USB serial connector, though, but it worked fine before so I can't imagine it's that.

[airwolf]

I used 115.200 baud, 8 data bits, 1 stop bit no parity and no flow control.
As USB-serial converter I use a CP2102 based device, this kind always seems to work while the PL2303 based ones don't. I acutally installed the 2102 device in the scope (it has a standard USB A connector), and now I can connect the scope to a PC with a terminal program any time very easy.
Maybe you should try to exchange the USB-serial adapter, could save you a lot of time and headache (I should have done it as well).

[ubata]

I apologize for bringing up an old topic.
I have a Hantek DSO4202C Oscilloscope that sticks at boot screen.
below is the board pic

on the board there is 2 ports that maybe UART. I soldered some pins there, but I cannot connect to the scope with neither of them using CP2102 usb to serial, when connecting the CP2102 to either, the cp2102 gets hot. I used putty, and nothing show on the putty console. I used this topic help to determine the port pins.
https://www.eevblog.com/forum/testgear/voltcraft-dso-1084e-(hantek-dso4084b)-stuck-at-boot-screen
How can I identify the port pins? or Exactly How can I identify which port is UART?
Meanwhile, I once shared the problem of not booting with Hantek support; they sent me a compressed file containing several files with the ".bin" image and told me to make an SD memory card bootable with one of the sent bin files using a Chinese app they sent to me,  and copy the rest of the files to the root of the memory card; and place it inside the oscilloscope's memory card slot. Then, I turned it on while pressing the channel 1 vol/div knob. The oscilloscope should have entered programming mode, and the images would have been burned to the oscilloscope's internal memory. Unfortunately, this did not happen, and the screen was completely black with no message or response.
Here I uploaded the file sent by Hantek.
https://mega.nz/file/UfgHkBZI#jQJYnK6ivxzMsXdz_oPUENA21pFG302O94VgExwMqXM

[ubata]

no one can help me?

[Oscillator]

@ubata:

thanks for posting the sd-card image.

i have the same problem like you (scope is not booting) and was looking for these files a long time.   

so here you can see how to attach the USB serial converter:




see also first post here:  https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz



so please tell us about your further steps and results.

[ubata]

finally, I could connect serial connector, and below is the normal boot log

Code: [Select]

OM*** Warning - bad CRC, using default environment


##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; Press Space key to Download Mode.!

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
**************************normal start*******************************

NAND erase: device 0 offset 0x380000, size 0x80000
Erasing at 0x3e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x380000, size 0x800
Writing data at 0x380800 -- 100% complete.
 2048 bytes written: OK

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
Saving Environment to NAND...
Erasing Nand...
Warning: Erase size 0x00004000 smaller than one erase block 0x00020000
         Erasing 0x00020000 instead
Erasing at 0x80000 -- 100% complete.
Writing to Nand... done

NAND read: device 0 offset 0x400000, size 0x400000
 4194304 bytes read: OK
Boot with zImage

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #220 PREEMPT Thu Dec 13 08:12:38 CST 2018
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
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=5 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272
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: 59744k/59744k available, 5792k 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 - 0xc04ab000   (4748 kB)
      .init : 0xc04ab000 - 0xc04cb000   ( 128 kB)
      .data : 0xc04cc000 - 0xc04ee020   ( 137 kB)
       .bss : 0xc04ee044 - 0xc050bd7c   ( 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 116
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
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: 0xc8, Chip ID: 0xd1 (ISSI NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 483 at 0x000003c60000
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 mtd5 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:       174
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            70 MiB
UBI: number of good PEBs:        559
UBI: number of bad PEBs:         1
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             164
UBI: total number of reserved PEBs: 395
UBI: number of PEBs reserved for bad PEB handling: 5
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  1761812910
UBI: background thread "ubi_bgt0d" started, PID 329
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 2005-12-22 16:22:02 UTC (1135268522)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   47869952 bytes (46748 KiB, 45 MiB, 377 LEBs)
UBIFS: journal size:       2412544 bytes (2356 KiB, 2 MiB, 19 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  2261015 bytes (2208 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 128K
Failed to execute /linuxrc.  Attempting defaults...
/bin/sh: can't access tty; job control turned off
~ #

I think the problem was here:

Code: [Select]

Failed to execute /linuxrc.  Attempting defaults...
/bin/sh: can't access tty; job control turned off[code/]

[ubata]

@ubata:

thanks for posting the sd-card image.

i have the same problem like you (scope is not booting) and was looking for these files a long time.   

so please tell us about your further steps and results.

Thank you for reply
Please tell us that the SD card method worked for you or not. I'm still working on it

[ubata]

a little more try.
boot failures screenshot and files listed below



another pic



after boot failure and turn scope again. we have 3 options for boot and recover.

by pressing F2 the recovery process, the log attached at the end. before confirming recovery, the list of files is below



third option update recovery partition shows error



for last point the recover.sh file has been attached at the end. and I think can fix it having the recover*.up file in a usb disk, notice below command in recover.sh

Code: [Select]

/usr/gpg149arm/bin/gpg  --passphrase recoveruse  --output /tmp/update/recover.tar.gz -d /mnt/udisk/recover*.up


[Oscillator]

good that the serial connection is working now.

i can make some tests on my scope only at the weekend.
so i have to wait until saturday for making some tests.

maybe there is a corrupted config file which crashes the boot sequence.

so you might try to delete the broken files:

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

or try this from reply #29 in this topic:

Now all I had to do was to delete all the files in /dso/app/etc/aslf (as described somewhere up in this thread) and the scope boots again as before. Seems to be a bug in this scope, but once you know its easy to fix.

btw: your boot log looks the same like in reply #25:

Failed to execute /linuxrc.  Attempting defaults...
/bin/sh: can't access tty; job control turned off

[ubata]

maybe there is a corrupted config file which crashes the boot sequence.

so you might try to delete the broken files:

Now all I had to do was to delete all the files in /dso/app/etc/aslf (as described somewhere up in this thread) and the scope boots again as before. Seems to be a bug in this scope, but once you know its easy to fix.

unfortunately, there is not "etc/asfl" under "/dso/app path"
only files that shown at below pic is there:

Code: [Select]

/dso/app # ls
dsod         io_bank      show_pic     test_bkl
fpga_ctl     read_adc     test_beep    test_msp430

[ubata]

new update
I maked a 16GB SD card bootable and copied the image files, as Hantek suport said in email, turned on the scope simultaneously pressing Ch1 volt/div knob. Strangely, the Scope displayed the following inverted text on its monitor:

Code: [Select]

#OM
Card Initialization failed.

SD:File System init failed!
Reading kernel from sector 30955502 (8192 sectors)..

[airwolf]

I see that your motherboard looks very different to mine, although the front of the Oszilloskop looks very similar (mine is 4 channel however). Could be that the software is somewhat different too? Did you look if you can find an asfl folder somewhere else? Just look around in the scope using the terminal.
The problem with my scope really was only the corrupted files in that folder, deleting them fixed everything.

[Oscillator]

@airwolf:

its not the same scope like yours.

you have the 4084B.

but ubata has 4202C.

just look at the front panel. you dont have an sd-card slot and ubata dont have arrow keys next to the F1-F6 buttons.
so its completely different hardware!

i have the 4102C. today i was very curious and decided to open my scope to take a look inside.
i have exactly the same PCB like ubata. and my scope doesnt boot also.

in the coming days i will add my serial USB to check my boot logs.

[ubata]

I see that your motherboard looks very different to mine, although the front of the Oszilloskop looks very similar (mine is 4 channel however). Could be that the software is somewhat different too? Did you look if you can find an asfl folder somewhere else? Just look around in the scope using the terminal.
The problem with my scope really was only the corrupted files in that folder, deleting them fixed everything.

thanks for your reply
I searched the entire file system of the scope, but I couldn't find the folder and files you mentioned.

[ubata]

some other updates:

I saw the " Press Space key to Download Mod 0!" message when the scope booted, but I didn't think it would work.
But when I pressed the space bar, surprisingly it worked. The scope went into download mode and showed me the download menu in the terminal.
Now I don't know how to use these options to restore the device. Because Hantek sent me the image files and I uploaded them here:

https://mega.nz/file/UfgHkBZI#jQJYnK6ivxzMsXdz_oPUENA21pFG302O94VgExwMqXM

Below you can see the download mode menu:

Code: [Select]

#####    Boot for SKY2416/TQ2416 Main Menu      #####
#####     EmbedSky USB download mode     #####

[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download LOGO (logo.bin) to Nand Flash
[3] Erase the MISC partion
[4] Download Kernel (kernel.bin) to Nand Flash
[5] Download UBIFS image (rootfs.ubi) to Nand Flash
[6] Download Kernel_bk (kernel_bk.bin) to Nand Flash
[7] Download UBIFS image (recover.ubi) to Nand Flash
[8] normal start!
[9] recover start!
[0] Set the boot parameters
[f] Format the Nand Flash
[a] Download User Program
[c] Choice lcd type.
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection:
 download mode.gif (39.74 kB. 887x563 - viewed 9 times.)

[airwolf]

Sorry guys, you are right my scope is very different. Sorry that I can't help.

[ubata]

some other updates:

I saw the " Press Space key to Download Mod 0!" message when the scope booted, but I didn't think it would work.
But when I pressed the space bar, surprisingly it worked. The scope went into download mode and showed me the download menu in the terminal.
Now I don't know how to use these options to restore the device. Because Hantek sent me the image files . . .

I think we can fix it by copying the necessary images to a udisk and reburn them to NAND flash using download mode (The same thing was done in the method recommended by Hantek -using images and a bootable SD card-.), but I still afraid to brick the scope.

[Oscillator]

be careful!

as far as i understand this bootloader wants to download the binary image from the PC via USB connection and flash the contents to the NAND.

so dont fiddle with the uboot loader in NAND. this will brick your scope for sure!

btw: in which boot mode do you get the "space bar press" option?

is it the normal startup, recovery or sd-card boot?

[ubata]

btw: in which boot mode do you get the "space bar press" option?

is it the normal startup, recovery or sd-card boot?

I only pressed space button over the putty terminal window, in serial connection, in any type of boot, because the messages appear at top of any boot process.

[ubata]

below is a link to DSO4104C normal boot log
https://sigrok.org/wiki/Hantek_DSO4004C_series/Info

[Oscillator]

thanks for the "normal" boot log.

thats great!   

i noticed already before that in your boot log there is one partition missing:  "config"

i am not sure if this is related to different firmware versions, but most logs look like this:

Creating 9 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000003a00000 : "rootfs"
0x000003a00000-0x000004e00000 : "config"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"

[Oscillator]

okay, i didnt want to wait any longer and connected my scope to the serial bridge.

my logs look very similar to the logs from ubata.

i dont have a "config" partition too.

[Oscillator]

@ubata:

how did you write your sd-card?

- which windows version?
- which software?

i tried today without any success.

but i figured out how to transfer files from PC to the scope in usb download mode!

first you need this software:

SMDK2416.zip

it contains drivers for 32bit. it was working for me on win 7 32bit.

here are drivers for 64bit (but untested, refused to install on win 11 because of missing driver signature):

driver_x64.zip

start dnw.exe on the PC and make serial console settings first and then open a serial connection.

when you are in usb download mode you might press "t" for "Test Linux Image (zImage)"

then you are told to connect the scope to the PC with an usb cable. after plugging the cable windows wants to install the device driver for the scope.

finish the driver installation and go back to dnw.exe. now you can select "transmit" in the usb menu. select your kernel.bin file which comes with the hantek sd-card.
after sending this file to the scope the kernel.bin will be booted.

this is just for testing the whole setup.

if everything is working fine, you might send the individual files from the hantek recovery sd-card.
but dont send the uboot.bin! this can brick the booting of your scope!

but use flashing the NAND at your own risk!  i didnt try yet. ,-)

[Oscillator]

the day of success!!!





today i made the big step of flashing parts of the NAND.

according to my theory of my previous posting  i was using "dnw.exe" and some flash files from
the hantek recovery sd-card for flashing in usb-download mode of the scopes bootloader.

so i have flashed rootfs.ubi, recover.ubi and kernel.bin to the NAND. now my scope is booting fine again. 
 
and a nice side effect: it turns my OEM branded KKmoon DSO4102S into a Hantek DSO4202C.
so now i am able to get some firmware updates too! 

this is the boot log of the broken scope before flashing:

Code: [Select]

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

This Board: SDRAM is 64MB; Press Space key to Download Mode.!


NAND read: device 0 offset 0x380000, size 0x800

 2048 bytes read: OK

**************************recover start*******************************


NAND erase: device 0 offset 0x380000, size 0x80000


Erasing at 0x380000 --  25% complete.
Erasing at 0x3a0000 --  50% complete.
Erasing at 0x3c0000 --  75% complete.
Erasing at 0x3e0000 -- 100% complete.

OK

Saving Environment to NAND...

Erasing Nand...

Warning: Erase size 0x00004000 smaller than one erase block 0x00020000

         Erasing 0x00020000 instead


Erasing at 0x80000 -- 100% complete.

Writing to Nand... done


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

 4194304 bytes read: OK

Boot with zImage


Starting kernel ...


Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #219 PREEMPT Wed Dec 5 16:30:45 CST 2018
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
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=7 root=ubi0:recover rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272
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: 59744k/59744k available, 5792k 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 - 0xc04ab000   (4748 kB)
      .init : 0xc04ab000 - 0xc04cb000   ( 128 kB)
      .data : 0xc04cc000 - 0xc04ee020   ( 137 kB)
       .bss : 0xc04ee044 - 0xc050bd7c   ( 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 116
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
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: 0xc8, Chip ID: 0xd1 (ISSI NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 26 at 0x000000340000
Bad eraseblock 56 at 0x000000700000
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 mtd7 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:       512
UBI: attached mtd7 to ubi0
UBI: MTD device name:            "recover"
UBI: MTD device size:            46 MiB
UBI: number of good PEBs:        368
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 368
UBI: number of PEBs reserved for bad PEB handling: 3
UBI: max/mean erase counter: 5/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 329
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 05:05:22 UTC (946703122)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "recover"
UBIFS: file system size:   44441600 bytes (43400 KiB, 42 MiB, 350 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 128K

Please press Enter to activate this console. dso-iobank: install ok
0x505
gpio_major_n = 5, io_minor_n = 5, output 0
0x603
gpio_major_n = 6, io_minor_n = 3, output 0
0x309
gpio_major_n = 3, io_minor_n = 9, output 0
0x70a
gpio_major_n = 7, io_minor_n = 10, output 0
dso5000b fpga configure init
FPGA0_nCONFIG  set config = -15
FPGA0_nSTATUS  set config = -16
FPGA0_CONF_DONE  set config = -16
FPGA0_nCONFIG  set pull = 2
FPGA0_nSTATUS  set pull = 2
FPGA1_nCONFIG  set config = -15
FPGA1_nSTATUS  set config = -16
FPGA1_CONF_DONE  set config = -15
FPGA1_nCONFIG  set pull = 2
FPGA1_nSTATUS  set pull = 2
fpga0:status: 0x0
FPGA0 CONFIGURE DATA DOWN finish.
FPGA0 CONFIGURE Ok.
AFG3050 CFG fpga1 no cfg file
AFG3050_fpga_cfg: probe of spi0.1 failed with error -1
fpga bank 11811
input: dso_kbd as /devices/virtual/misc/fpga_mem/input1
fpga_mem: install ok
fpga_ctl_kbd_open:1:  (null)
fpga_ctl_kbd_open:2:c3ba22a0
dso keyboard: key (code 0xd) released.
dso keyboard: key (code 0x14) released.
dso keyboard: key (code 0x16) released.
dso keyboard: key (code 0x19) released.
dso keyboard: key (code 0x3) pressed.
dso keyboard: key (code 0x3) released.
dso keyboard: key (code 0x3) pressed.
dso keyboard: key (code 0x3) released.

[Oscillator]

and this is my new boot log after flashing parts of the NAND:

Code: [Select]

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

This Board: SDRAM is 64MB; Press Space key to Download Mode.!


NAND read: device 0 offset 0x380000, size 0x800

 2048 bytes read: OK

**************************normal start*******************************


NAND erase: device 0 offset 0x380000, size 0x80000


Erasing at 0x380000 --  25% complete.
Erasing at 0x3a0000 --  50% complete.
Erasing at 0x3c0000 --  75% complete.
Erasing at 0x3e0000 -- 100% complete.

OK


NAND write: device 0 offset 0x380000, size 0x800


Writing data at 0x380000 --   0% complete.
Writing data at 0x380800 -- 100% complete.

 2048 bytes written: OK


NAND read: device 0 offset 0x380000, size 0x800

 2048 bytes read: OK

Saving Environment to NAND...

Erasing Nand...

Warning: Erase size 0x00004000 smaller than one erase block 0x00020000

         Erasing 0x00020000 instead


Erasing at 0x80000 -- 100% complete.

Writing to Nand... done


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

Skipping bad block 0x00000000

 4194304 bytes read: OK

Boot with zImage


Starting kernel ...


Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #220 PREEMPT Thu Dec 13 08:12:38 CST 2018
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
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=5 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272
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: 59744k/59744k available, 5792k 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 - 0xc04ab000   (4748 kB)
      .init : 0xc04ab000 - 0xc04cb000   ( 128 kB)
      .data : 0xc04cc000 - 0xc04ee020   ( 137 kB)
       .bss : 0xc04ee044 - 0xc050bd7c   ( 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 116
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
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: 0xc8, Chip ID: 0xd1 (ISSI NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 26 at 0x000000340000
Bad eraseblock 56 at 0x000000700000
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 mtd5 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:       287
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            70 MiB
UBI: number of good PEBs:        560
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 560
UBI: number of PEBs reserved for bad PEB handling: 5
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 329
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 2009-01-01 00:11:17 UTC (1230768677)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   68567040 bytes (66960 KiB, 65 MiB, 540 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 128K
dso-iobank: install ok
0x505
gpio_major_n = 5, io_minor_n = 5, output 0
0x603
gpio_major_n = 6, io_minor_n = 3, output 0
0x309
gpio_major_n = 3, io_minor_n = 9, output 0
0x70a
gpio_major_n = 7, io_minor_n = 10, output 0
dso5000b fpga configure init
FPGA0_nCONFIG  set config = -15
FPGA0_nSTATUS  set config = -16
FPGA0_CONF_DONE  set config = -16
FPGA0_nCONFIG  set pull = 2
FPGA0_nSTATUS  set pull = 2
FPGA1_nCONFIG  set config = -15
FPGA1_nSTATUS  set config = -16
FPGA1_CONF_DONE  set config = -14
FPGA1_nCONFIG  set pull = 2
FPGA1_nSTATUS  set pull = 2
fpga0:status: 0x0
FPGA0 CONFIGURE DATA DOWN finish.
FPGA0 CONFIGURE Ok.
AFG3050 CFG fpga1 no cfg file
AFG3050_fpga_cfg: probe of spi0.1 failed with error -1
0x8090
0x1
fpga bank 11811dso-fpga: install ok
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: wrong id: 0x2b2a2928
dm9000 dm9000: not found (-19).
bkl tq2416-backlight initialized done...
dso-buzzer s3c2416-beep initialized done...
/etc/init.d/rcS: line 32: /dso/alsa_node.sh: not found
ifconfig: SIOCSIFADDR: No such device
bw_now = 200
make snd node.
--------------------------------------------------------------------------------
start
--------------------------------------------------------------------------------

Please press Enter to activate this console.
Erasing 128 Kibyte @ 0 -  0% complete.
Erasing 128 Kibyte @ 20000 - 25% complete.
Erasing 128 Kibyte @ 40000 - 50% complete.
Erasing 128 Kibyte @ 60000 - 75% complete.
Erasing 128 Kibyte @ 80000 - 100% complete.
mtd3: 00080000 00020000 "misc"

Erasing 128 Kibyte @ 0 -  0% complete.
Erasing 128 Kibyte @ 20000 - 25% complete.
Erasing 128 Kibyte @ 40000 - 50% complete.
Erasing 128 Kibyte @ 60000 - 75% complete.
Erasing 128 Kibyte @ 80000 - 100% complete.
<0>open /dev/adc: No such file or directory
*****set_value = 1
param_array[70] = 1
SetFpgaCh1VerticDac:value=23783
value1 = 15468
value2 = 15468
SetFpgaCh1VerticDac:value=23783
value1 = 15468
value2 = 15468


so there is still no extra "config" partition like in other firmwares but who cares?   

[ubata]

@Oscillator:

Thank you for your contribution. Flashing the NAND was worked for me too. But I have measurement problems, the voltage readings are not correct, and about 12% drifted down. I tried self calibration several times, but nothing changed. I think the "/config" partition may had some important calibration data, and now we lost them.
Do you have the same problem?

[Oscillator]

i have made the self calibration also.

i did only a short test with the built in 1khz test signal and the waveform generator.

the test signal shows 4.88V. (jumps to 4.96V from time to time)

when i set the generator to 3.0V then the measurement shows 2.96V.

i have no big experience with this scope but i think these values are okay.

[ubata]

Can you locate where the calibration data stored?
I haven't access to the scope now
Meanwhile, I had violent jitter on fast rising waves, even with scopes own generator. Like the picture posted by "tin head" here:


https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/?action=dlattach;attach=612976

[Oscillator]

i have closed my scope already.

so i cant check the directories anymore.

but i am pretty sure there is a config subdirectory in the rootfs.

btw: flashing with dnw.exe gives the same result as flashing with the recovery sd-card.
the files are the same! so you might ask the hantek support if it wipes your calibration.
i guess thats the way it is.

but if the config data is missing, the system will complain at startup for sure!

i can double check the measurements with another DSO in the evening.

[ubata]

i can double check the measurements with another DSO in the evening.

Thanks a lot

[Oscillator]

i am finished with my measurements.

i took a hantek DSO5072P for comparison.

first i made a self calibration on both scopes.

then i measured an 1,5v alkaline battery.
a plain digital multimeter schows 1,5 volts for this battery.

my flashed 4102C shows 1.28v and the 5072P shows 1.6v.

all other measurements give the same reuslts:
the 4102C has too low values and the 5072P has too high values.

to my surprise the voltage of the 1khz test signal doenst show the same like in the morning.
in the morning i had 4.8 volts which is not bad at all.

now in the evening after a new self calibration the 4102C only shows 4.4 volts. the 5072P shows 5.36 volts.
all measuremts were taken with the same probe!

and both scopes show a jittered signal from the wave generator in high frequencies.
there is no difference!

so a long story short:

i dont think the new software has broken the old calibration.

@ubata:

what voltage is shown in your scope for the test signal?

[ubata]

. . . .
so a long story short:

i dont think the new software has broken the old calibration.

@ubata:

what voltage is shown in your scope for the test signal?

I think you are right. new software has not broken the old calibration. meanwhile "/config" partition does not belong to DSO4xx2C and even DSO5000P series.

for the scope compensation test signal pk-pk is about 4.8V that's not very bad