Author Topic: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen  (Read 19625 times)

0 Members and 1 Guest are viewing this topic.

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #50 on: January 30, 2025, 03:26:32 pm »
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:

Quote
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"
« Last Edit: January 30, 2025, 03:30:53 pm by Oscillator »
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #51 on: January 30, 2025, 06:49:36 pm »
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.

 
The following users thanked this post: ubata

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #52 on: January 31, 2025, 07:24:11 pm »
@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. ,-)
« Last Edit: January 31, 2025, 07:36:02 pm by Oscillator »
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #53 on: February 01, 2025, 04:58:54 pm »
the day of success!!!


2493171-0


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!  ;D

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.

« Last Edit: February 03, 2025, 08:51:02 am by Oscillator »
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #54 on: February 03, 2025, 08:51:20 am »
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?   8)
 

Offline ubata

  • Contributor
  • Posts: 23
  • Country: ir
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #55 on: February 05, 2025, 02:44:40 am »
@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?
« Last Edit: February 05, 2025, 02:50:37 am by ubata »
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #56 on: February 05, 2025, 07:02:55 am »
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.
 

Offline ubata

  • Contributor
  • Posts: 23
  • Country: ir
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #57 on: February 05, 2025, 07:25:41 am »
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:

2495345-0
https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/?action=dlattach;attach=612976
« Last Edit: February 05, 2025, 07:37:59 am by ubata »
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #58 on: February 05, 2025, 07:38:44 am »
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.
« Last Edit: February 05, 2025, 07:40:52 am by Oscillator »
 

Offline ubata

  • Contributor
  • Posts: 23
  • Country: ir
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #59 on: February 05, 2025, 09:30:08 am »
i can double check the measurements with another DSO in the evening.
Thanks a lot
 

Offline Oscillator

  • Contributor
  • Posts: 12
  • Country: de
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #60 on: February 05, 2025, 07:04:24 pm »
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?
 

Offline ubata

  • Contributor
  • Posts: 23
  • Country: ir
Re: VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen
« Reply #61 on: February 09, 2025, 01:44:38 pm »
. . . .
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  ;)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf