Voltcraft DSO-1084E stuck on boot screen - Page 1
Forum section: electronics / repair

author: mateusz.kaczor
author_rank: Newbie
timestamp: February 16, 2022, 08:33:15 pm
content: Hello,At first I would like to say hi to everyone, I am completely new to this forum (although I have been watching Dave videos for years)I would like to ask for help in repairing the VOLTCRAFT DSO-1084E oscilloscope (Hantek DSO4084B). I bought it for a penny (already damaged) hoping that I would be able to do something with it. Unfortunately, I got stuckI checked other threads on the forum and I found nothing similar to this.Oscilosope is stuck on Logo/Boot screean or after "hard reset" in recovery screan with information "System is not shut down properly..."Logs from "normal" startup:Code:system reboot“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 0x8002048 bytes read: OK**************************normal start*******************************NAND erase: device 0 offset 0x380000, size 0x80000Erasing at 0x380000 -- 25% complete.Erasing at 0x3a0000 -- 50% complete.Erasing at 0x3c0000 -- 75% complete.Erasing at 0x3e0000 -- 100% complete.OKNAND write: device 0 offset 0x380000, size 0x800Writing data at 0x380000 -- 0% complete.Writing data at 0x380800 -- 100% complete.2048 bytes written: OKNAND read: device 0 offset 0x380000, size 0x8002048 bytes read: OKSaving Environment to NAND...Erasing Nand...Warning: Erase size 0x00004000 smaller than one erase block 0x00020000Erasing 0x00020000 insteadErasing at 0x80000 -- 100% complete.Writing to Nand... doneNAND read: device 0 offset 0x400000, size 0x4000004194304 bytes read: OKBoot with zImageStarting 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 2017CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: SMDK2416Ignoring unrecognised tag 0x54410008Memory policy: ECC disabled, Data cache writebackCPU S3C2416/S3C2450 (id 0x32450003)S3C24XX Clocks, Copyright 2004 Simtec ElectronicsCPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHzCPU: EPLL on 96.000 MHz, usb-bus 48.000 MHzBuilt 1 zonelists in Zone order, mobility grouping on. Total pages: 16256Kernel command line: noinitrd ubi.mtd=5 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272PID 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 totalMemory: 58948k/58948k available, 6588k reserved, 0K highmemVirtual 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=1NR_IRQS:107irq: clearing subpending status 00000002Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)pid_max: default: 4096 minimum: 301Mount-cache hash table entries: 512CPU: Testing write buffer coherency: okNET: Registered protocol family 16S3C2416: Initializing architectureS3C2416: IRQ SupportS3C24XX DMA Driver, Copyright 2003-2006 Simtec ElectronicsDMA channel 0 at c4804000, irq 88DMA channel 1 at c4804100, irq 89DMA channel 2 at c4804200, irq 90DMA channel 3 at c4804300, irq 91DMA channel 4 at c4804400, irq 92DMA channel 5 at c4804500, irq 93bio: create slab <bio-0> at 0SCSI subsystem initializedusbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbs3c-i2c s3c2410-i2c: slave address 0x10s3c-i2c s3c2410-i2c: bus frequency set to 9 KHzs3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapterAdvanced Linux Sound Architecture Driver Version 1.0.24.NET: Registered protocol family 2IP 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 registeredNET: Registered protocol family 1RPC: 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 drivermsgmni has been set to 115io scheduler noop registered (default)io scheduler cfq registereds3c-fb s3c-fb: window 0: fbs3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5s3c-fb s3c-fb: window 1: fbs3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440console  enableds3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440loop: module loadedS3C24XX NAND Driver, (c) 2004 Simtec Electronicsinfo->cpu_type=3, tacls_max=8s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22nss3c24xx-nand s3c2416-nand: System booted from NANDs3c24xx-nand s3c2416-nand: NAND ECC disabledNAND 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 blocksBad eraseblock 726 at 0x000005ac0000Creating 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 ubi0UBI: physical eraseblock size: 131072 bytes (128 KiB)UBI: logical eraseblock size: 126976 bytesUBI: smallest flash I/O unit: 2048UBI: VID header offset: 2048 (aligned 2048)UBI: data offset: 4096UBI: max. sequence number: 71UBI: attached mtd5 to ubi0UBI: MTD device name: "rootfs"UBI: MTD device size: 50 MiBUBI: number of good PEBs: 400UBI: number of bad PEBs: 0UBI: number of corrupted PEBs: 0UBI: max. allowed volumes: 128UBI: wear-leveling threshold: 4096UBI: number of internal volumes: 1UBI: number of user volumes: 1UBI: available PEBs: 6UBI: total number of reserved PEBs: 394UBI: number of PEBs reserved for bad PEB handling: 4UBI: max/mean erase counter: 2/1UBI: image sequence number: -1570950245UBI: background thread "ubi_bgt0d" started, PID 341UBI: attaching mtd6 to ubi1UBI: physical eraseblock size: 131072 bytes (128 KiB)UBI: logical eraseblock size: 126976 bytesUBI: smallest flash I/O unit: 2048UBI: VID header offset: 2048 (aligned 2048)UBI: data offset: 4096UBI: max. sequence number: 2038UBI: attached mtd6 to ubi1UBI: MTD device name: "config"UBI: MTD device size: 20 MiBUBI: number of good PEBs: 160UBI: number of bad PEBs: 0UBI: number of corrupted PEBs: 0UBI: max. allowed volumes: 128UBI: wear-leveling threshold: 4096UBI: number of internal volumes: 1UBI: number of user volumes: 1UBI: available PEBs: 0UBI: total number of reserved PEBs: 160UBI: number of PEBs reserved for bad PEB handling: 2UBI: max/mean erase counter: 15/13UBI: image sequence number: 0UBI: background thread "ubi_bgt1d" started, PID 344ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Drivers3c2410-ohci s3c2410-ohci: S3C24XX OHCIs3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000hub 1-0:1.0: USB hub foundhub 1-0:1.0: 1 port detectedusbcore: registered new interface driver usblpusbcore: registered new interface driver uasInitializing USB Mass Storage driver...usbcore: registered new interface driver usb-storageUSB Mass Storage support registered.samsung-ts s3c2416-ts: driver attached, registering input deviceinput: S3C24XX TouchScreen as /devices/virtual/input/input0S3C24XX RTC, (c) 2004,2006 Simtec Electronicss3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0i2c /dev entries driverS3C2410 Watchdog Timer, (c) 2004 Simtec Electronicss3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabledsdhci: Secure Digital Host Controller Interface driversdhci: Copyright(c) Pierre Ossmans3c-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 ADMAusbcore: registered new interface driver usbhidusbhid: USB HID core driverS3C24XX_UDA134X SoC Audio driverS3C24XX_UDA134X SoC Audio: l3 data pin already in uses3c24xx_uda134x: probe of s3c24xx_uda134x.0 failed with error -16ALSA device list:No soundcards found.TCP cubic registeredNET: Registered protocol family 17Registering the dns_resolver key types3c-rtc s3c2410-rtc: setting system clock to 2022-02-16 03:56:02 UTC (1644983762)UBIFS: recovery neededUBIFS: recovery completedUBIFS: 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: lzoUBIFS: reserved for root: 2261015 bytes (2208 KiB)VFS: Mounted root (ubifs filesystem) on device 0:10.Freeing init memory: 124KFailed to execute /linuxrc. Attempting defaults...Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.Logs from "recovery" startup:Code:vice 0 offset 0x4e00000, size 0x4000004194304 bytes read: OKBoot with zImageStarting 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 2017CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: SMDK2416Ignoring unrecognised tag 0x54410008Memory policy: ECC disabled, Data cache writebackCPU S3C2416/S3C2450 (id 0x32450003)S3C24XX Clocks, Copyright 2004 Simtec ElectronicsCPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHzCPU: EPLL on 96.000 MHz, usb-bus 48.000 MHzBuilt 1 zonelists in Zone order, mobility grouping on. Total pages: 16256Kernel command line: noinitrd ubi.mtd=8 root=ubi0:recover rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272PID 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 totalMemory: 58948k/58948k available, 6588k reserved, 0K highmemVirtual 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=1NR_IRQS:107irq: clearing subpending status 00000002Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)pid_max: default: 4096 minimum: 301Mount-cache hash table entries: 512CPU: Testing write buffer coherency: okNET: Registered protocol family 16S3C2416: Initializing architectureS3C2416: IRQ SupportS3C24XX DMA Driver, Copyright 2003-2006 Simtec ElectronicsDMA channel 0 at c4804000, irq 88DMA channel 1 at c4804100, irq 89DMA channel 2 at c4804200, irq 90DMA channel 3 at c4804300, irq 91DMA channel 4 at c4804400, irq 92DMA channel 5 at c4804500, irq 93bio: create slab <bio-0> at 0SCSI subsystem initializedusbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbs3c-i2c s3c2410-i2c: slave address 0x10s3c-i2c s3c2410-i2c: bus frequency set to 9 KHzs3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapterAdvanced Linux Sound Architecture Driver Version 1.0.24.NET: Registered protocol family 2IP 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 registeredNET: Registered protocol family 1RPC: 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 drivermsgmni has been set to 115io scheduler noop registered (default)io scheduler cfq registereds3c-fb s3c-fb: window 0: fbs3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5s3c-fb s3c-fb: window 1: fbs3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440console  enableds3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440loop: module loadedS3C24XX NAND Driver, (c) 2004 Simtec Electronicsinfo->cpu_type=3, tacls_max=8s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22nss3c24xx-nand s3c2416-nand: System booted from NANDs3c24xx-nand s3c2416-nand: NAND ECC disabledNAND 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 blocksBad eraseblock 726 at 0x000005ac0000Creating 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 mtd8 to ubi0UBI: physical eraseblock size: 131072 bytes (128 KiB)UBI: logical eraseblock size: 126976 bytesUBI: smallest flash I/O unit: 2048UBI: VID header offset: 2048 (aligned 2048)UBI: data offset: 4096UBI: max. sequence number: 334UBI: attached mtd8 to ubi0UBI: MTD device name: "recover"UBI: MTD device size: 46 MiBUBI: number of good PEBs: 367UBI: number of bad PEBs: 1UBI: number of corrupted PEBs: 0UBI: max. allowed volumes: 128UBI: wear-leveling threshold: 4096UBI: number of internal volumes: 1UBI: number of user volumes: 1UBI: available PEBs: 0UBI: total number of reserved PEBs: 367UBI: number of PEBs reserved for bad PEB handling: 3UBI: max/mean erase counter: 2/1UBI: image sequence number: 0UBI: background thread "ubi_bgt0d" started, PID 341ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Drivers3c2410-ohci s3c2410-ohci: S3C24XX OHCIs3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000hub 1-0:1.0: USB hub foundhub 1-0:1.0: 1 port detectedusbcore: registered new interface driver usblpusbcore: registered new interface driver uasInitializing USB Mass Storage driver...usbcore: registered new interface driver usb-storageUSB Mass Storage support registered.samsung-ts s3c2416-ts: driver attached, registering input deviceinput: S3C24XX TouchScreen as /devices/virtual/input/input0S3C24XX RTC, (c) 2004,2006 Simtec Electronicss3c-rtc s3c2410-rtc: rtc disabled, re-enablings3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0i2c /dev entries driverS3C2410 Watchdog Timer, (c) 2004 Simtec Electronicss3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabledsdhci: Secure Digital Host Controller Interface driversdhci: Copyright(c) Pierre Ossmans3c-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 ADMAusbcore: registered new interface driver usbhidusbhid: USB HID core driverS3C24XX_UDA134X SoC Audio driverS3C24XX_UDA134X SoC Audio: l3 data pin already in uses3c24xx_uda134x: probe of s3c24xx_uda134x.0 failed with error -16ALSA device list:No soundcards found.TCP cubic registeredNET: Registered protocol family 17Registering the dns_resolver key types3c-rtc s3c2410-rtc: setting system clock to 2022-02-16 07:03:39 UTC (1644995019)UBIFS: recovery neededUBIFS: recovery completedUBIFS: mounted UBI device 0, volume 0, name "recover"UBIFS: file system size: 44314624 bytes (43276 KiB, 42 MiB, 349 LEBs)UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)UBIFS: media format: w4/r0 (latest is w4/r0)UBIFS: default compressor: lzoUBIFS: reserved for root: 0 bytes (0 KiB)VFS: Mounted root (ubifs filesystem) on device 0:10.Freeing init memory: 124KPlease press Enter to activate this console. dso-iobank: install ok0x505gpio_major_n = 5, io_minor_n = 5, output 00x603gpio_major_n = 6, io_minor_n = 3, output 00x70agpio_major_n = 7, io_minor_n = 10, output 0AFG3050 fpga configure initfpga bank 11811input: dso_kbd as /devices/virtual/misc/dso-fpga/input1dso-fpga: install okuser file is /lib/firmware/dn.rbfnstatus0 :0x0nstatus1 :0x1fpga state :0x1file len is 456524FPGA CONFIGURE DATA DOWN finish.0x1, 0FPGA CONFIGURE ok.ls -la-/bin/sh: source: line 10: can't open '/dso/etc/profile'[root@Hantek ~]#[root@Hantek ~]#ls -latotal 4drwxr-xr-x 17 root root 1256 Feb 16 04:04 .drwxr-xr-x 17 root root 1256 Feb 16 04:04 ..-rw------- 1 root root 3008 Feb 16 07:03 .ash_historydrwx------ 2 root root 304 Aug 10 2021 .gnupgdrwxr-xr-x 2 root root 6496 Mar 8 2018 bindrwxr-xr-x 3 root root 0 Feb 16 07:03 devdrwxr-xr-x 2 root root 160 Mar 8 2018 dsodrwxr-xr-x 4 root root 816 Mar 8 2018 etcdrwxr-xr-x 4 root root 3664 Mar 8 2018 liblrwxrwxrwx 1 root root 11 Mar 8 2018 linuxrc -> bin/busyboxdrwxr-xr-x 8 root root 544 Feb 16 06:29 mntdr-xr-xr-x 48 root root 0 Jan 1 1970 procdrwxr-xr-x 4 root root 1168 Feb 16 06:02 recoverdrwxr-xr-x 2 root root 232 Feb 16 04:49 rootdrwxr-xr-x 2 root root 4320 Mar 8 2018 sbindrwxr-xr-x 11 root root 0 Feb 16 07:03 sysdrwxr-xr-x 2 root root 0 Feb 16 07:03 tmpdrwxr-xr-x 5 root root 360 Mar 8 2018 usrdrwxr-xr-x 2 root root 0 Feb 16 07:03 var[root@Hantek ~]#[root@Hantek ~]#I am able to execute linux commands only after starting in recovery mode.I found most directories are just empty, for example/dso:Code:[root@Hantek ~]#ls -la /dsototal 0drwxr-xr-x 2 root root 160 Mar 8 2018 .drwxr-xr-x 17 root root 1256 Feb 16 04:04 ..[root@Hantek ~]#[root@Hantek ~]#Then I noticed that it is impossible to mount the pendrive (FAT32), I only get the message:Code:mount: mounting /dev/sda1 on /mnt/usb failed: Invalid argumentThis led me to a clue, so I started checking what's in the/mntdirectory. And it looks like almost everything is empty or not mounted (?)Code:ls -latotal 0drwxr-xr-x 8 root root 544 Feb 16 06:29 .drwxr-xr-x 17 root root 1256 Feb 16 04:04 ..drwxr-xr-x 2 root root 160 Aug 27 2018 configdrwxr-xr-x 2 root root 160 Mar 8 2018 nfsdrwxr-xr-x 2 root root 160 Aug 27 2018 rootfsdrwxr-xr-x 2 root root 160 Mar 8 2018 sddrwxr-xr-x 2 root root 160 Mar 8 2018 udiskdrwxr-xr-x 2 root root 160 Feb 16 06:29 usb[root@Hantek /mnt]#[root@Hantek /mnt]#ls -la configtotal 0drwxr-xr-x 2 root root 160 Aug 27 2018 .drwxr-xr-x 8 root root 544 Feb 16 06:29 ..[root@Hantek /mnt]#[root@Hantek /mnt]#ls -la nfstotal 0drwxr-xr-x 2 root root 160 Mar 8 2018 .drwxr-xr-x 8 root root 544 Feb 16 06:29 ..[root@Hantek /mnt]#[root@Hantek /mnt]#ls -la rootfstotal 0drwxr-xr-x 2 root root 160 Aug 27 2018 .drwxr-xr-x 8 root root 544 Feb 16 06:29 ..[root@Hantek /mnt]#[root@Hantek /mnt]#ls -la udisktotal 0drwxr-xr-x 2 root root 160 Mar 8 2018 .drwxr-xr-x 8 root root 544 Feb 16 06:29 ..[root@Hantek /mnt]#[root@Hantek /mnt]#After that, I also tried to insert the microSD card and see what will happen (currently I don't even know how to copy something to the oscilloscope). The oscilloscope would freeze then endlessly attempting to mount the card:Code:VFS: Mounted root (ubifs filesystem) on device 0:10.Freeing init memory: 124Kmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentmount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argumentI don't know what to do next. Maybe except that I found the script in the/recoverdirectory:Code:#!/bin/sh#lcd show bin & fileLCD_BIN_SHOW=/recover/lcd-show-recoverDRIVER1=/recover/spidev.koDRIVER2=/recover/spi-s3c64xx.koDRIVER3=/recover/fpga_cfg.koDRIVER3_BIN=/recover/cfg_fpgaDRIVER4=/recover/keyboard.koDRIVER5=/recover/s3c2416-io_bank.koDRIVER5_BIN=/recover/io_bank#partiton infoMISC_PARTITION=/dev/mtd3KERNEL_PARTITION=/dev/mtd4ROOTFS_PARTITION=/dev/mtd5CONFIG_PARTITION=/dev/mtd6#image file nameKERNEL_IMAGE_FILE=/recover/kernel.binROOTFS_IMAGE_FILE=/recover/rootfs/rootfs.tar.bzCONFIG_IMAGE_FILE=/recover/config/UPDATE_FLAG_FILE=/recover/update_flag#commondINIT=initRECOVER=recoverif [ $1 == $INIT ] ; then#install driversif [ -f $DRIVER5 ] ; theninsmod $DRIVER5fiif [ -f $DRIVER5_BIN ]; then$DRIVER5_BIN f5 o 0$DRIVER5_BIN g3 o 0$DRIVER5_BIN h10 o 0fiif [ -f $DRIVER2 ] ; theninsmod $DRIVER1insmod $DRIVER2fiif [ -f $DRIVER3 ] ; theninsmod $DRIVER3fiinsmod $DRIVER4if [ ! -d /mnt/config ]; thenmkdir /mnt/configfiif [ ! -d /mnt/rootfs ]; thenmkdir /mnt/rootfsfiif [ -f $DRIVER3_BIN ]; then$DRIVER3_BIN /lib/firmware/dn.rbffisleep 1$LCD_BIN_SHOWelif [ $1 == $RECOVER ] ; thenif [ $2 -eq 0 ] ; thenflash_eraseall $MISC_PARTITIONelif [ $2 -eq 1 ] ; then#recover startif [ ! -f /recover/recover_end ]; thenexit 1fiflash_eraseall $KERNEL_PARTITIONnandwrite -p $KERNEL_PARTITION $KERNEL_IMAGE_FILEflash_eraseall $ROOTFS_PARTITIONif ubiattach /dev/ubi_ctrl -m 5 ; thenlsfiif ubimkvol /dev/ubi1 -N rootfs -s 49000000 ; thenlsfimount -t ubifs ubi1:rootfs /mnt/rootfstar jxvf $ROOTFS_IMAGE_FILE -C /mnt/rm /mnt/root/system.infif cat /proc/mtd | grep "config"; thenflash_eraseall $CONFIG_PARTITIONif cat /proc/mtd | grep "config"; thenif ubiattach /dev/ubi_ctrl -m 6 ; thenlsfiif ubimkvol /dev/ubi2 -N config -s 19000000 ; thenlsfimount -t ubifs ubi2:config /mnt/configficp $CONFIG_IMAGE_FILE/* /mnt/config -arm /mnt/config/root/system.inffiflash_eraseall $MISC_PARTITION#recover endelif [ $2 -eq 2 ] ; then#mount fsif ubiattach /dev/ubi_ctrl -m 5 ; thenlsfiif ubimkvol /dev/ubi1 -N rootfs -s 49000000 ; thenlsfimount -t ubifs ubi1:rootfs /mnt/rootfsif cat /proc/mtd | grep "config"; thenif ubiattach /dev/ubi_ctrl -m 6 ; thenlsfiif ubimkvol /dev/ubi2 -N config -s 19000000 ; thenlsfimount -t ubifs ubi2:config /mnt/configfi#backupnanddump -o -b -f $KERNEL_IMAGE_FILE $KERNEL_PARTITION -l 3000000if [ ! -f /mnt/rootfs/linuxrc ]; thenexit 1fiif [ -f $ROOTFS_IMAGE_FILE ]; thenrm -f $ROOTFS_IMAGE_FILEfitar jcvf $ROOTFS_IMAGE_FILE rootfs -C /mntif cat /proc/mtd | grep "config"; thencp /mnt/config/* $CONFIG_IMAGE_FILE -afielif [ $2 -eq 3 ] ; thenrm -rf /tmp/update || echo "error ignored"mkdir /tmp/update/usr/gpg149arm/bin/gpg --passphrase recoveruse --output /tmp/update/recover tar gz -d /mnt/udisk/recover* uptar xvzf /tmp/update/recover tar gz -C /tmp/update/tar xvf /tmp/update/recover* tar -C /tmp/update/chmod +x /tmp/update/tekwayup_client/update.sh/tmp/update/tekwayup_client/update.shelseexit 1fielseexit 1fiAnalyzing it, I came to the conclusion that it might be possible to restore the oscilloscope from backup, but unfortunately there is no backup:Code:sh ./recover.sh recover 3gpg: fatal: can't create directory `root/.gnupg': No such file or directorysecmem usage: 32/32 bytes in 1/1 blocks of pool 32/32768tar: can't open '/tmp/update/recover.tar.gz': No such file or directorytar: can't open '/tmp/update/recover*.tar': No such file or directorychmod: /tmp/update/tekwayup_client/update.sh: No such file or directory./recover.sh: line 156: /tmp/update/tekwayup_client/update.sh: not foundMaybe someone with a similar oscilloscope is able to provide it to me? Although I do not know yet how to copy this backup thereThanks in advance for your help and time

author: rugo100
author_rank: Contributor
timestamp: December 04, 2024, 10:07:45 pm
content: Hi,I just would like to ask if you have any success to recover your scope?I am in the (almost) same shoe, my dso is Voltcraft DSO-1202D and after booting nothing work on it.I able to connect to it via UART and I see linux is running on it. Even mounts the pendrive (I am able to copy files from pendrive)I have run the recovery, no success. Also I have tried manually update the firmware without success.So currently I do not know what else can I do.Probably I full backup from another (working) device would be useful.regards