Problem with Hantek dso5072p - Page 1
Forum section: electronics / testgear

author: diegostreetbob
author_rank: Newbie
timestamp: January 25, 2014, 10:31:50 am
content: Hello,I have a Hantek ds5072P with serial number T1G/035000316 and I never tried to update,etc... 70mhz it,s sufficient for me.Since 2 weeks when I power up the scope, the welcome window appears but does not continue.Yesterday I have connected the scope to hyperterminal and this is the log when I push space in pc:Thanks in advance##### EmbedSky BIOS for SKY2416/TQ2416 #####This Board: SDRAM is 64MB; LCD display size is: 800 X 480Press Space key to Download Mod 0!SD:File System init failed!##### Boot for SKY2416/TQ2416 Main Menu ########## EmbedSky USB download mode ##### Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash Download Eboot (eboot.nb0) to Nand Flash Download Linux Kernel (zImage.bin) to Nand Flash Download LOGO Picture (logo.bin) to Nand Flash Download UBIFS image (root.ubi) to Nand Flash Download YAFFS image (root.bin) to Nand Flash Download Program to SDRAM and Run it Boot the system Format the Nand FlashSet the boot parameters Download User Program Enter TFTP download mode menu Reboot u-boot Test Linux Image (zImage)Enter your selectionIf I don,t push space in pc, this is the log*** Warning - bad CRC or NAND, using default environment##### EmbedSky BIOS for SKY2416/TQ2416 #####This Board: SDRAM is 64MB; LCD display size is: 800 X 480Press Space key to Download Mode.!SD:File System init failed!Start Linux ...NAND read: device 0 offset 0x300000, size 0x4000004194304 bytes read: OKBoot with zImageStarting 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) ) #1 PREEMPT Thu Mar 7 08:15:30 CST 2013CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: SMDK2416Memory 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=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64MPID 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: 59024k/59024k available, 6512k 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 - 0xc03e9000 (3972 kB).init : 0xc03e9000 - 0xc0409000 ( 128 kB).data : 0xc040a000 - 0xc05a2680 (1634 kB).bss : 0xc05a26a4 - 0xc05bf97c ( 117 kB)SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1NR_IRQS:99irq: 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 usbs3c24xx_i2c_probes3c-i2c s3c2410-i2c: slave address 0x10s3c-i2c s3c2410-i2c: bus frequency set to 65 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: 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 blocksBad eraseblock 274 at 0x000002240000Bad eraseblock 609 at 0x000004c20000Bad eraseblock 810 at 0x000006540000Creating 4 MTD partitions on "NAND":0x000000000000-0x000000100000 : "Bootloader"0x000000100000-0x000000300000 : "LOGO"0x000000300000-0x000000700000 : "Kernel"0x000000700000-0x000008000000 : "ROOTFS"UBI: attaching mtd3 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: 1291UBI: attached mtd3 to ubi0UBI: MTD device name: "ROOTFS"UBI: MTD device size: 121 MiBUBI: number of good PEBs: 965UBI: number of bad PEBs: 3UBI: 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: 965UBI: number of PEBs reserved for bad PEB handling: 9UBI: max/mean erase counter: 4/2UBI: image sequence number: 0UBI: background thread "ubi_bgt0d" started, PID 306ohci_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: 2 ports 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.g_serial gadget: Gadget Serial v2.4g_serial gadget: g_serial readys3c-hsudc s3c-hsudc: bound driver g_serialsamsung-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 ADMAS3C24XX_UDA134X SoC Audio driverUDA134X SoC Audio Codecasoc: uda134x-hifi <-> s3c24xx-iis mapping okALSA device list:#0: S3C24XX_UDA134XTCP cubic registeredNET: Registered protocol family 17Registering the dns_resolver key types3c-rtc s3c2410-rtc: setting system clock to 2000-01-01 00:02:58 UTC (946684978)UBIFS: recovery neededUBIFS: recovery completedUBIFS: mounted UBI device 0, volume 0, name "rootfs"UBIFS: file system size: 119484416 bytes (116684 KiB, 113 MiB, 941 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: 128KUBIFS error (pid 1): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 1): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 1): ubifs_read_node: expected node type 9Failed to execute /linuxrc. Attempting defaults...UBIFS error (pid 367): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 367): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 367): ubifs_read_node: expected node type 9dso-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 00x408gpio_major_n = 4, io_minor_n = 8, output 1dso5000b fpga configure initfpga0:status: 0x0mapped channel 4 to 0mapped channel 3 to 1FPGA0 CONFIGURE DATA DOWN finish.FPGA0 CONFIGURE Ok.0x80900x1fpga bank 11811dso-fpga: install okbkl tq2416-backlight initialized done...dso-buzzer s3c2416-beep initialized done...--------------------------------------------------------------------------------start--------------------------------------------------------------------------------Please press Enter to activate this console. UBIFS error (pid 407): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 407): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 407): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid 420): ubifs_check_node: bad node at LEB 135:57680UBIFS error (pid 420): ubifs_read_node: expected node type 9UBIFS error (pid 420): ubifs_readdir: cannot find next direntry, error -117UBIFS error (pid 420): ubifs_check_node: bad CRC: calculated 0x9779e5ed, read 0x176d5781UBIFS error (pid

author: quarros
author_rank: Regular Contributor
timestamp: January 26, 2014, 11:35:47 am
content: Hi! You should post that in the BIG Hantek topic. So tinhead could find it easier.https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/But as far as I see it, there are afew bits that got flippedin the NAND and you need to reflash it.Correction: 3 Phisical blocks in the NAND gone bad.

author: rosasharn
author_rank: Regular Contributor
timestamp: March 14, 2014, 05:26:51 am
content: I guess it's the flash chip on the hardware damaged and replace a new programmed flash chip will make it work.