Electronics > Repair
Voltcraft DSO-1084E stuck on boot screen
(1/1)
mateusz.kaczor:
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 stuck :(

I 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 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
 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
Bad eraseblock 726 at 0x000005ac0000
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:       71
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:  -1570950245
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:       2038
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: 15/13
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 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 2022-02-16 03:56:02 UTC (1644983762)
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...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

--- End code ---


Logs from "recovery" startup:

--- Code: ---vice 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@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=8 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: 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
Bad eraseblock 726 at 0x000005ac0000
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 mtd8 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:       334
UBI: attached mtd8 to ubi0
UBI: MTD device name:            "recover"
UBI: MTD device size:            46 MiB
UBI: number of good PEBs:        367
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:             0
UBI: total number of reserved PEBs: 367
UBI: number of PEBs reserved for bad PEB handling: 3
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 341
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 2022-02-16 07:03:39 UTC (1644995019)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: 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: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 124K

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
0x70a
gpio_major_n = 7, io_minor_n = 10, output 0
AFG3050 fpga configure init
fpga bank 11811
input: dso_kbd as /devices/virtual/misc/dso-fpga/input1
dso-fpga: install ok
user file is /lib/firmware/dn.rbf
nstatus0 :0x0
nstatus1 :0x1
fpga state :0x1
file len is 456524
FPGA CONFIGURE DATA DOWN finish.0x1, 0
FPGA CONFIGURE ok.
ls -la

-/bin/sh: source: line 10: can't open '/dso/etc/profile'
[root@Hantek ~]#
[root@Hantek ~]#ls -la
total 4
drwxr-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_history
drwx------    2 root     root           304 Aug 10  2021 .gnupg
drwxr-xr-x    2 root     root          6496 Mar  8  2018 bin
drwxr-xr-x    3 root     root             0 Feb 16 07:03 dev
drwxr-xr-x    2 root     root           160 Mar  8  2018 dso
drwxr-xr-x    4 root     root           816 Mar  8  2018 etc
drwxr-xr-x    4 root     root          3664 Mar  8  2018 lib
lrwxrwxrwx    1 root     root            11 Mar  8  2018 linuxrc -> bin/busybox
drwxr-xr-x    8 root     root           544 Feb 16 06:29 mnt
dr-xr-xr-x   48 root     root             0 Jan  1  1970 proc
drwxr-xr-x    4 root     root          1168 Feb 16 06:02 recover
drwxr-xr-x    2 root     root           232 Feb 16 04:49 root
drwxr-xr-x    2 root     root          4320 Mar  8  2018 sbin
drwxr-xr-x   11 root     root             0 Feb 16 07:03 sys
drwxr-xr-x    2 root     root             0 Feb 16 07:03 tmp
drwxr-xr-x    5 root     root           360 Mar  8  2018 usr
drwxr-xr-x    2 root     root             0 Feb 16 07:03 var
[root@Hantek ~]#
[root@Hantek ~]#
--- End code ---


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 /dso
total 0
drwxr-xr-x    2 root     root           160 Mar  8  2018 .
drwxr-xr-x   17 root     root          1256 Feb 16 04:04 ..
[root@Hantek ~]#
[root@Hantek ~]#
--- End code ---


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 argument
--- End code ---


This led me to a clue, so I started checking what's in the /mnt directory. And it looks like almost everything is empty or not mounted (?)

--- Code: ---ls -la
total 0
drwxr-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 config
drwxr-xr-x    2 root     root           160 Mar  8  2018 nfs
drwxr-xr-x    2 root     root           160 Aug 27  2018 rootfs
drwxr-xr-x    2 root     root           160 Mar  8  2018 sd
drwxr-xr-x    2 root     root           160 Mar  8  2018 udisk
drwxr-xr-x    2 root     root           160 Feb 16 06:29 usb
[root@Hantek /mnt]#
[root@Hantek /mnt]#ls -la config
total 0
drwxr-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 nfs
total 0
drwxr-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 rootfs
total 0
drwxr-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 udisk
total 0
drwxr-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]#
--- End code ---


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: 124K
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
mount: mounting /dev/mmcblk0p1 on /mnt/sd failed: Invalid argument
--- End code ---


I don't know what to do next. Maybe except that I found the script in the /recover directory:

--- Code: ---#!/bin/sh

#lcd show bin & file
LCD_BIN_SHOW=/recover/lcd-show-recover
DRIVER1=/recover/spidev.ko
DRIVER2=/recover/spi-s3c64xx.ko
DRIVER3=/recover/fpga_cfg.ko
DRIVER3_BIN=/recover/cfg_fpga
DRIVER4=/recover/keyboard.ko
DRIVER5=/recover/s3c2416-io_bank.ko
DRIVER5_BIN=/recover/io_bank

#partiton info
MISC_PARTITION=/dev/mtd3
KERNEL_PARTITION=/dev/mtd4
ROOTFS_PARTITION=/dev/mtd5
CONFIG_PARTITION=/dev/mtd6

#image file name
KERNEL_IMAGE_FILE=/recover/kernel.bin
ROOTFS_IMAGE_FILE=/recover/rootfs/rootfs.tar.bz
CONFIG_IMAGE_FILE=/recover/config/
UPDATE_FLAG_FILE=/recover/update_flag

#commond
INIT=init
RECOVER=recover

if [ $1 == $INIT ] ; then
 #install drivers
 if [ -f $DRIVER5 ] ; then
 insmod $DRIVER5
 fi
 if [ -f $DRIVER5_BIN ]; then
  $DRIVER5_BIN f5 o 0
  $DRIVER5_BIN g3 o 0
  $DRIVER5_BIN h10 o 0
 fi

 if [ -f $DRIVER2 ] ; then
 insmod $DRIVER1
 insmod $DRIVER2
 fi
 if [ -f $DRIVER3 ] ; then
 insmod $DRIVER3
 fi
 insmod $DRIVER4

 if [ ! -d /mnt/config ]; then
  mkdir /mnt/config
 fi

 if [ ! -d /mnt/rootfs ]; then
  mkdir /mnt/rootfs
 fi
 if [ -f $DRIVER3_BIN ]; then
 $DRIVER3_BIN /lib/firmware/dn.rbf
 fi
 sleep 1


 $LCD_BIN_SHOW

elif [ $1 == $RECOVER ] ; then
 if [ $2 -eq 0 ] ; then
  flash_eraseall $MISC_PARTITION
 elif [ $2 -eq 1 ] ; then
  #recover start
 
  if [ ! -f /recover/recover_end ]; then
   exit 1
  fi

  flash_eraseall $KERNEL_PARTITION
  nandwrite -p $KERNEL_PARTITION $KERNEL_IMAGE_FILE

  flash_eraseall $ROOTFS_PARTITION
  if ubiattach /dev/ubi_ctrl -m 5 ; then
   ls
  fi
  if ubimkvol /dev/ubi1 -N rootfs -s 49000000 ; then
   ls
  fi
  mount -t ubifs ubi1:rootfs /mnt/rootfs

  tar jxvf $ROOTFS_IMAGE_FILE -C /mnt/
  rm /mnt/root/system.inf

  if cat /proc/mtd | grep "config"; then
   flash_eraseall $CONFIG_PARTITION
   if cat /proc/mtd | grep "config"; then
    if ubiattach /dev/ubi_ctrl -m 6 ; then
     ls
    fi
    if ubimkvol /dev/ubi2 -N config -s 19000000 ; then
     ls
    fi
    mount -t ubifs ubi2:config /mnt/config
   fi
   cp $CONFIG_IMAGE_FILE/* /mnt/config -a
   rm /mnt/config/root/system.inf
  fi


  flash_eraseall $MISC_PARTITION

  #recover end
 elif [ $2 -eq 2 ] ; then
  #mount fs
  if ubiattach /dev/ubi_ctrl -m 5 ; then
   ls
  fi
  if ubimkvol /dev/ubi1 -N rootfs -s 49000000 ; then
   ls
  fi
  mount -t ubifs ubi1:rootfs /mnt/rootfs
  if cat /proc/mtd | grep "config"; then
   if ubiattach /dev/ubi_ctrl -m 6 ; then
    ls
   fi
   if ubimkvol /dev/ubi2 -N config -s 19000000 ; then
    ls
   fi
   mount -t ubifs ubi2:config /mnt/config
  fi
 
  #backup
    nanddump -o -b -f $KERNEL_IMAGE_FILE $KERNEL_PARTITION -l 3000000
   
  if [ ! -f /mnt/rootfs/linuxrc ]; then
   exit 1
  fi
 
  if [ -f $ROOTFS_IMAGE_FILE ]; then
   rm  -f $ROOTFS_IMAGE_FILE
  fi

  tar jcvf $ROOTFS_IMAGE_FILE rootfs -C /mnt

  if cat /proc/mtd | grep "config"; then
   cp /mnt/config/* $CONFIG_IMAGE_FILE -a
  fi
 elif [ $2 -eq 3 ] ; then
  rm -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* up
  tar 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.sh
 else
  exit 1
 fi
else
 exit 1
fi
--- End code ---


Analyzing 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 3
gpg: fatal: can't create directory `root/.gnupg': No such file or directory
secmem usage: 32/32 bytes in 1/1 blocks of pool 32/32768
tar: can't open '/tmp/update/recover.tar.gz': No such file or directory
tar: can't open '/tmp/update/recover*.tar': No such file or directory
chmod: /tmp/update/tekwayup_client/update.sh: No such file or directory
./recover.sh: line 156: /tmp/update/tekwayup_client/update.sh: not found
--- End code ---


Maybe someone with a similar oscilloscope is able to provide it to me? Although I do not know yet how to copy this backup there :)

Thanks in advance for your help and time
rugo100:
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



Navigation
Message Index
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod