Author Topic: Hantek DSO5102B hangs on boot after fw update  (Read 345 times)

0 Members and 1 Guest are viewing this topic.

Offline timshoeTopic starter

  • Newbie
  • Posts: 5
  • Country: us
Hantek DSO5102B hangs on boot after fw update
« on: December 06, 2024, 12:53:44 am »
I bought a used Hantek DSO5102b sn T 1G/0120188xx  scope from a fellow Ham who used it often. It worked ok until I updated the firmware from 3.30.0 (140815.0) using dso5kb_func_dso5102b20190830.up from the Hantek website. It seemed to take the update and asked me to restart. When I did, it hung at the white graphic Hantek logo screen. It won't go any further than that screen. How do I troubleshoot this problem? I have looked at the posts on this forum by Tinhead and others, which elude to connecting to a uart or jtag on the unit. I see some holes in the pcb but I am unsure how to connect to them. None of the pictures that I see on these boards match my unit. Attached is a picture of my main board. I understand it's Linux based and that I can trace the boot issues through the port. I  have spent several hours on this board looking for the method to connect the scope to my PC terminal program to fix the problem. I need some help getting started fixing this unit.
« Last Edit: December 06, 2024, 04:15:28 am by timshoe »
 

Offline timshoeTopic starter

  • Newbie
  • Posts: 5
  • Country: us
Re: Hantek DSO5102B hangs on boot after fw update
« Reply #1 on: December 06, 2024, 08:10:30 pm »
I managed to connect to the uart with putty and can see the scope booting up.
I just get the white logo screen at boot up and it hangs there. This started after I did a fw update and rebooted.

Here's what I see on bootup. Notice the error at the end when /dso.exe can't execute. I think that may be the problem.
Any ideas on how to proceed?

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



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

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

Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...

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

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@cjh-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #18 PREEMPT Fri Jul 5 14:39:32 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59772k/59772k available, 5764k 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 - 0xc03e9000   (3972 kB)
      .init : 0xc03e9000 - 0xc0409000   ( 128 kB)
      .data : 0xc040a000 - 0xc04e6e80   ( 884 kB)
       .bss : 0xc04e6ea4 - 0xc050417c   ( 117 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:99
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
s3c24xx_i2c_probe
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 65 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
s3c-fb s3c-fb: window 1: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 192 at 0x000001800000
Bad eraseblock 651 at 0x000005160000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       18414
UBI: attached mtd3 to ubi0
UBI: MTD device name:            "ROOTFS"
UBI: MTD device size:            121 MiB
UBI: number of good PEBs:        966
UBI: number of bad PEBs:         2
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: 966
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 25/19
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 306
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: 2 ports detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-01 00:54:34 UTC (946688074)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   119611392 bytes (116808 KiB, 114 MiB, 942 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
usb 1-1: new full-speed USB device number 2 using s3c2410-ohci
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
scsi0 : usb-storage 1-1:1.0
scsi 0:0:0:0: Direct-Access     LG       USB Drive        1100 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 3963904 512-byte logical blocks: (2.02 GB/1.88 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
dso-iobank: install ok
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
adc init
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
0x408
gpio_major_n = 4, io_minor_n = 8, output 1
dso5000b fpga configure init
fpga0:status: 0x0
mapped channel 4 to 0
mapped channel 3 to 1
FPGA0 CONFIGURE DATA DOWN finish.
FPGA0 CONFIGURE Ok.
0x8090
0x1
fpga bank 11811dso-fpga: install ok
bkl tq2416-backlight initialized done...
close beep now
dso-buzzer s3c2416-beep initialized done...
--------------------------------------------------------------------------------
start
--------------------------------------------------------------------------------

Please press Enter to activate this console. hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
/dso.exe: error while loading shared libraries: libgstreamer-1.0.so.0: cannot open shared object file: No such file or directory
hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB device on port 2

[root@Hantek ~]#

Please press Enter to activate this console. /dso.exe: error while loading shared libraries: libgstreamer-1.0.so.0: cannot open shared object file: No such file or directory
 

Offline timshoeTopic starter

  • Newbie
  • Posts: 5
  • Country: us
Re: Hantek DSO5102B hangs on boot after fw update
« Reply #2 on: December 26, 2024, 03:35:36 am »
Still no joy in getting this scope to boot into the shell and update the software image. Does anyone know how to initiate the reflash of the software from the linux shell? I can get in through the serial port and move around in linux, but I haven't figured out how to start the reflash from the USB drive that Hantek sent me and I flashed onto a USB drive. The scope is stuck in the white logo screen. Shorting the P5 pads and starting the unit make no difference, it still comes up into the Logo graphic and hangs. From the dump in my last post, it looks like dso.exe is where it is hanging. It's strange that shorting the P5 pads don't cause it to boot into update mode. I've tried it many times with no joy.

Anyone have any ideas on how I can get this unit to reflash the files from the factory supplied ones on the USB drive? This was a working unit until I tried to update the firmware with the factory update files that should have been for this unit. Any ideas would be appreciated. Other than sending me the files to flash on the USB, Hantek has not responded to my emails.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf