| Products > Test Equipment |
| VOLTCRAFT DSO-1084E (Hantek DSO4084B) stuck at boot screen |
| << < (6/7) > >> |
| Space-Patrol:
Hi, i got the same scope (DSO1084E with 4000B model. Does someone have a complete flash dump? I do it the first time. I attached a log file created by hterm for windows. Thank you! |
| archive:
Hello. I have already received the second DSO1084E oscilloscope blocked on the Voltcraft logo. I don't know when both stopped working, I don't know if they were hacked. UART normal boot: --- Quote ---OM*** Warning - bad CRC, using default environment ##### EmbedSky BIOS for SKY2416/TQ2416 ##### This Board: SDRAM is 64MB; Press Space key to Download Mode.! NAND read: device 0 offset 0x380000, size 0x800 2048 bytes read: OK **************************normal start******************************* NAND erase: device 0 offset 0x380000, size 0x80000 Erasing at 0x3e0000 -- 100% complete. OK NAND write: device 0 offset 0x380000, size 0x800 Writing data at 0x380800 -- 100% complete. 2048 bytes written: OK NAND read: device 0 offset 0x380000, size 0x800 2048 bytes read: OK Saving Environment to NAND... Erasing Nand... Warning: Erase size 0x00004000 smaller than one erase block 0x00020000 Erasing 0x00020000 instead Erasing at 0x80000 -- 100% complete. Writing to Nand... done NAND read: device 0 offset 0x400000, size 0x400000 4194304 bytes read: OK Boot with zImage Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 3.2.35 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #22 PREEMPT Fri Oct 27 02:56:10 CST 2017 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine: SMDK2416 Ignoring unrecognised tag 0x54410008 Memory policy: ECC disabled, Data cache writeback CPU S3C2416/S3C2450 (id 0x32450003) S3C24XX Clocks, Copyright 2004 Simtec Electronics CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: noinitrd ubi.mtd=5 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272 PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 58948k/58948k available, 6588k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xc4800000 - 0xf6000000 ( 792 MB) lowmem : 0xc0000000 - 0xc4000000 ( 64 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .text : 0xc0008000 - 0xc03fc000 (4048 kB) .init : 0xc03fc000 - 0xc041b000 ( 124 kB) .data : 0xc041c000 - 0xc05b5200 (1637 kB) .bss : 0xc05b5224 - 0xc05d2fdc ( 120 kB) SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:107 irq: clearing subpending status 00000002 Calibrating delay loop... 198.45 BogoMIPS (lpj=496128) pid_max: default: 4096 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 S3C2416: Initializing architecture S3C2416: IRQ Support S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics DMA channel 0 at c4804000, irq 88 DMA channel 1 at c4804100, irq 89 DMA channel 2 at c4804200, irq 90 DMA channel 3 at c4804300, irq 91 DMA channel 4 at c4804400, irq 92 DMA channel 5 at c4804500, irq 93 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb s3c-i2c s3c2410-i2c: slave address 0x10 s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter Advanced Linux Sound Architecture Driver Version 1.0.24. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. s3c-adc s3c24xx-adc: attached adc driver msgmni has been set to 115 io scheduler noop registered (default) io scheduler cfq registered s3c-fb s3c-fb: window 0: fb s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5 s3c-fb s3c-fb: window 1: fb s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5 s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440 console [ttySAC0] enabled s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440 s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440 s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440 loop: module loaded S3C24XX NAND Driver, (c) 2004 Simtec Electronics info->cpu_type=3, tacls_max=8 s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns s3c24xx-nand s3c2416-nand: System booted from NAND s3c24xx-nand s3c2416-nand: NAND ECC disabled NAND device: Manufacturer ID: 0xc8, Chip ID: 0xd1 (Unknown NAND 128MiB 3,3V 8-bit) NAND_ECC_NONE selected by board driver. This is not recommended! Scanning device for bad blocks Creating 9 MTD partitions on "NAND": 0x000000000000-0x000000100000 : "uboot" 0x000000100000-0x000000180000 : "params" 0x000000180000-0x000000380000 : "logo" 0x000000380000-0x000000400000 : "misc" 0x000000400000-0x000000800000 : "kernel" 0x000000800000-0x000003a00000 : "rootfs" 0x000003a00000-0x000004e00000 : "config" 0x000004e00000-0x000005200000 : "kernel_bk" 0x000005200000-0x000008000000 : "recover" UBI: attaching mtd5 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 126976 bytes UBI: smallest flash I/O unit: 2048 UBI: VID header offset: 2048 (aligned 2048) UBI: data offset: 4096 UBI: max. sequence number: 225 UBI: attached mtd5 to ubi0 UBI: MTD device name: "rootfs" UBI: MTD device size: 50 MiB UBI: number of good PEBs: 400 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 6 UBI: total number of reserved PEBs: 394 UBI: number of PEBs reserved for bad PEB handling: 4 UBI: max/mean erase counter: 2/1 UBI: image sequence number: -1218469377 UBI: background thread "ubi_bgt0d" started, PID 341 UBI: attaching mtd6 to ubi1 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 126976 bytes UBI: smallest flash I/O unit: 2048 UBI: VID header offset: 2048 (aligned 2048) UBI: data offset: 4096 UBI: max. sequence number: 1189 UBI: attached mtd6 to ubi1 UBI: MTD device name: "config" UBI: MTD device size: 20 MiB UBI: number of good PEBs: 160 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 160 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 10/8 UBI: image sequence number: 0 UBI: background thread "ubi_bgt1d" started, PID 344 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected usbcore: registered new interface driver usblp usbcore: registered new interface driver uas Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. samsung-ts s3c2416-ts: driver attached, registering input device input: S3C24XX TouchScreen as /devices/virtual/input/input0 S3C24XX RTC, (c) 2004,2006 Simtec Electronics s3c-rtc s3c2410-rtc: rtc disabled, re-enabling s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0 i2c /dev entries driver S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz) mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA usbcore: registered new interface driver usbhid usbhid: USB HID core driver S3C24XX_UDA134X SoC Audio driver S3C24XX_UDA134X SoC Audio: l3 data pin already in use s3c24xx_uda134x: probe of s3c24xx_uda134x.0 failed with error -16 ALSA device list: No soundcards found. TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type s3c-rtc s3c2410-rtc: setting system clock to 2000-01-01 00:10:59 UTC (946685459) UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 0, volume 0, name "rootfs" UBIFS: file system size: 47869952 bytes (46748 KiB, 45 MiB, 377 LEBs) UBIFS: journal size: 2412544 bytes (2356 KiB, 2 MiB, 19 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 2261015 bytes (2208 KiB) VFS: Mounted root (ubifs filesystem) on device 0:10. Freeing init memory: 124K Failed to execute /linuxrc. Attempting defaults... /bin/sh: can't access tty; job control turned off ~ # --- End quote --- UART after pressing F2 in recovery: F2.txt (49.76 kB - downloaded 87 times.) |
| airwolf:
Hi, I know this thread is rather old but I also have a problem with my Hantek DSO-4084B (its a real Hantek, not Vorltcraft). It worked fine for about 4 years until last week during a measurement it started to respond slowly to inputs on the buttons, so I switched it OFF and back ON and now its not fully booting any more. Unfortunately I cannot use the serial terminal of the scope, although I did connect it to a 2102 some time ago I never got a response from the scope, not even when it was still in working condition. Does anyone know if there is a way to restore/reset it whitout the terminal? Of course I am not sure if there isn't a hardware fault but as the screen is working and the buttons are lit it could be firmware lost or damaged. |
| Oleh UA:
Hello. How did you solve your problem? 🙂 |
| airwolf:
I finally could fix my scope, the problem with the serial connection was the UART I used (it was one with a micro USB connector, not sure if it was the type or it was just broken). I tried with another one (with a USB A connector) and the sonnection established immediately. Now all I had to do was to delete all the files in /dso/app/etc/aslf (as described somewhere up in this thread) and the scope boots again as before. Seems to be a bug in this scope, but once you know its easy to fix. I also updated the system.inf file to get 250 Mhz, works also fine, and afterwards I installed an upgrade to 1.1.2, no problem at all. So I think its not necessary to hack the eeprom as well. By the way opening the scope I broke the power push button, and ordered 6 new ones instead of 2 (they came in sets of 3), so if anybody needs one just write me (if you are not too far away from me - Austria, of course) |
| Navigation |
| Message Index |
| Next page |
| Previous page |