Hantek MSO5074FG Firmware Upgrade Problem - *** Warning - bad CRC or NAND, using - Page 1
Forum section: electronics / testgear

author: dtomazini
author_rank: Contributor
timestamp: January 31, 2015, 05:03:11 am
content: Hi Guys,I'm a eletronic hobbyst, familiarized with PIC, ARM, and another microcontrollers. These days, finaly i bought this Hantek MSO5074FG osciloscipe.After some time usage, tests, and reading the user manual, the same behavior that described by other collegues: Some freezing, dificult with the trigger, etc.. So i decided to apply the firmware upgrade provided by the Equipment Seller from aliexpress. The seller told-me that this firmware was provided by Hantek, and the upgrade is very easy to do.After reading the user manual:"Update FirmwareI insert a USB disk with upgrade program and the disk icon at the top left corner is highlighted. Press the Firmware Update button and the Software Upgrade dialog pops up. Push F5 to confim upgrade or push F2 to cancel. "I follow the instructions, save the attached file "dst1kb_func_hantek_mso5074fg_20141110.0.up" on a USB drive, and start the firmware upgrade process.This is the file:https://drive.google.com/file/d/0B3cM-n_wYzNmVHN2ZXRGcXNUbDg/view?usp=sharingThe upgrade process occurs normally, take around 5 minutes and a dialog pops up on screen confirming the sucess of upgrade, and asking to restart the equipment.After the restart, the screen still black (with a low bright), and nothing occurs. The oscope didn't start.Reading this big topic, i found some help to try undertand why is wrong:https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg472938/#msg472938KL27x kindly send me the hantek rescue tool (that uses de USB port) and a stock version of the firmware. However unfortunately the computer doesn't recognize the oscilloscope using the USB port.Using the internal serial port of the osciloscope, a Serial <-> USB adapter connected, and the Putty terminal for windows, i could retrieve this log from the equipment:Code:*** 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 200 9q1-176) ) #62 PREEMPT Mon Aug 19 13:58: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: 59772k/59772k available, 5764k 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 - 0xc04e6ea0 ( 884 kB).bss : 0xc04e6ec4 - 0xc050419c ( 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 116io 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=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-bi t)NAND_ECC_NONE selected by board driver. This is not recommended!Scanning device for bad blocksBad eraseblock 421 at 0x0000034a0000Creating 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: 2UBI: attached mtd3 to ubi0UBI: MTD device name: "ROOTFS"UBI: MTD device size: 121 MiBUBI: number of good PEBs: 967UBI: number of bad PEBs: 1UBI: number of corrupted PEBs: 0UBI: max. allowed volumes: 128UBI: wear-leveling threshold: 4096UBI: number of internal volumes: 1UBI: number of user volumes: 0UBI: available PEBs: 954UBI: total number of reserved PEBs: 13UBI: number of PEBs reserved for bad PEB handling: 9UBI: max/mean erase counter: 2/1UBI: image sequence number: -737010380UBI: background thread "ubi_bgt0d" started, PID 304ohci_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-02 01:49:30 UTC (946777770)VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)Please append a correct "root=" boot option; here are the available partitions:1f00 1024 mtdblock0 (driver?)1f01 2048 mtdblock1 (driver?)1f02 4096 mtdblock2 (driver?)1f03 123904 mtdblock3 (driver?)Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)So, i believe now that i need to flash the stock firmware using a JTAG (or something), that's wright ?.Any help will be apreciated.CheersDaniel

author: fremen67
author_rank: Frequent Contributor
timestamp: January 31, 2015, 03:57:57 pm
content: Quote from: dtomazini on January 31, 2015, 05:03:11 amIt can't as linux is not running on the deviceQuote from: dtomazini on January 31, 2015, 05:03:11 amThat's the good news: the bootloader is still OK so you can try flashing rootfs via USB. That depends on the size and the type of your stock firmware. If it's a nand dump (about 128Mb) you can't as this feature is limited by the size of the RAM (64Mb on your scope). You would then need to flash it via JTAG.If your firmware file is about 60MB that will be OK. You will need another PC connected via USB, the transfer tool program (DNW) plus the drivers for your system (special ones).What OS do you have on your PC?To enter download mode you need to switch on and stop the boot process by pressing space key (you may have to try several times to find the right timing).

author: dtomazini
author_rank: Contributor
timestamp: January 31, 2015, 10:29:12 pm
content: Hi fremen67,Here is the files size:"dst1kb_func_hantek_mso5074fg_20141110.0.up" - 4.288.512 bytes (4,08 MB) - This one i receive from the Seller (and brick the oscope after uptade)"dst1kb_mso5074fg_fact140616.0.up" - 1.503.232 bytes (1,43 MB) - This one i receive from KL27xBooth files are in my google drive:https://drive.google.com/folderview?id=0B3cM-n_wYzNmfk81RmxqandGOHBkWldKYU0tbDhqZTFQWDZUS0V2U2VFSlRsTmFONXJsRE0&usp=sharingI have one J-Link from Segger that i use with ARM micro-controller boards, but i have no idea how to use in this oscilloscope. I can use 2 PCs with Windows 7.Please, this is the DNW tool that you said:http://www.friendlyarm.net/downloads?.Follow attached some pictures from inside the MSO5074FG.RegardsDaniel

author: dtomazini
author_rank: Contributor
timestamp: January 31, 2015, 11:35:55 pm
content: Booting the osciloscope, ans pressing the "space key", i got this menu:Code:*** 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 Mod 0!SD and FAT initialize success!sizeof(LineC)=160Without this filereturn -1c=255Without EmbedSky.ini !##### 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 Flash Set the boot parameters Download User Program Enter TFTP download mode menu Reboot u-boot Test Linux Image (zImage)Enter your selection:Hoewever don't know how to transform the "dst1kb_mso5074fg_fact140616.0.up" file in a linux image.Att;Daniel

author: fremen67
author_rank: Frequent Contributor
timestamp: February 01, 2015, 01:44:57 am
content: Quote from: dtomazini on January 31, 2015, 10:29:12 pmHi Daniel,The 2 files are not firmware files but only firmware update files. They just include some updated files for your MSO. They are useless for your problem as it does not come from a faulty file but from a faulty file system.The file you need is the UBIFS image for your system (root.ubi). I doubt Hantek will provide it to you. So the best solution would be to find someone with the same model and hardware than yours who would be able to provide you with a nand dump of his rootfs file system (root.bin, 121MB). Than you will have to convert it to a UBIFS file , which you should be able to flash with the bootloader (using DNW and the USB connection). I can help you later on with the root.bin to root.ubi file conversion and for the flashing part but at the moment you need a full backup of a similar MSO.Maybe KL27x or Lauris (https://www.eevblog.com/forum/testgear/hantek-mso5074fg/msg593315/#msg593315) would be able to provide you with a dump of their rootfs partition... All they have to do is to insert an USB stick and type "nanddump -l 0x7900000 -f /mnt/udisk/root.bin /dev/mtd3" (be careful that some version of nandump are not working so they may have to use another version of it)The JTAG port is J901 but you don't need it at the moment.

author: dtomazini
author_rank: Contributor
timestamp: February 01, 2015, 02:31:54 am
content: Now i clearly understood, thank you. Perhaps that i have a serious trouble here. How Hantek can made this crap upgrade routine ??. This is oscilloscope is my first and my last Hantek.I will send a message for KL27x or Lauris asking if they could get the dump.After install the USB drivers for DNW and test it, i believe that everything is ok to made the download. Please look these logs:DWN:Code:===== USB DEVICE STATUS =====USB_CONFIGURATION_DESCRIPTORbLength = 0x9, decimal 9bDescriptorType = 0x2 ( USB_CONFIGURATION_DESCRIPTOR_TYPE )wTotalLength = 0x20, decimal 32bNumInterfaces = 0x1, decimal 1bConfigurationValue = 0x1, decimal 1iConfiguration = 0x0, decimal 0bmAttributes = 0x80 ( USB_CONFIG_BUS_POWERED )MaxPower = 0x19, decimal 25-----------------------------USB_INTERFACE_DESCRIPTOR #0bLength = 0x9bDescriptorType = 0x4 ( USB_INTERFACE_DESCRIPTOR_TYPE )bInterfaceNumber = 0x0bAlternateSetting = 0x0bNumEndpoints = 0x2bInterfaceClass = 0xffbInterfaceSubClass = 0x0bInterfaceProtocol = 0x0bInterface = 0x0-----------------------------USB_ENDPOINT_DESCRIPTOR for Pipe00bLength = 0x7bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )bEndpointAddress= 0x81 ( INPUT )bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )wMaxPacketSize= 0x200, decimal 512bInterval = 0x0, decimal 0-----------------------------USB_ENDPOINT_DESCRIPTOR for Pipe01bLength = 0x7bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )bEndpointAddress= 0x3 ( OUTPUT )bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )wMaxPacketSize= 0x200, decimal 512bInterval = 0x0, decimal 0-----------------------------Putty Terminal:Code:##### 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 Flash Set the boot parameters Download User Program Enter TFTP download mode menu Reboot u-boot Test Linux Image (zImage)Enter your selection: aNow, Please connect to USB cable and USB interface!USB cable Connected!Thks;Daniel

author: Lauris
author_rank: Contributor
timestamp: February 01, 2015, 09:18:49 am
content: As I wrote to dtomazini, taking root dump would be possible in my case, just need more info on entering dump command. Is it done only over inside UART port or there are more ways?Lauris

author: fremen67
author_rank: Frequent Contributor
timestamp: February 01, 2015, 02:55:02 pm
content: Quote from: dtomazini on February 01, 2015, 02:31:54 amIt seems to be OK. If you want to go a step further and really want to try to send a file from DNW , use the "t" option (Test Linux Image) on the hdg side.Don't go on with the "a" option as you did as if the tranfer succeeds than the next step would be a nand format. The "a" option writes a test program on the nand, which you don't want !For the "t" option, it doesn't matter the file you send for the test. You will see the tranfer and of course your HDG won't recognize this file as a valid one but it won't erase nor write on the flash. You will get an error like:"Wrong Image Format for bootm commandERROR: can't get kernel image!"You will be sure that the file tranfer is working.

author: dtomazini
author_rank: Contributor
timestamp: February 01, 2015, 03:33:34 pm
content: Thanks for the advise, now i will use the "t" option before anything.About the Lauris doubt, is there a way to get the roots image using the USB connection ?, or another way without disassemble the equipment ?.I read this articlehttp://embdev.net/articles/Tekway_MSO#MSO_firmware_backup, here the authors make a back-up using the MSO Back-up Tools.Tks;Daniel

author: fremen67
author_rank: Frequent Contributor
timestamp: February 01, 2015, 09:13:59 pm
content: Quote from: dtomazini on February 01, 2015, 03:33:34 pmYes this was written by Tinhead who started "Hantek - Tekway - DSO hack - get 200MHz bw for free" but it will not work on your scope. You need a special tool for MSO5074FG.I had a look in the 2 upgrade files you posted and I doubt there were made for your model.The partition layout of your scope is the standard one for Hantek/Tekway DSO/MSO as you can see in your logs, that is 4 partitions:0x000000000000-0x000000100000 : "Bootloader"0x000000100000-0x000000300000 : "LOGO"0x000000300000-0x000000700000 : "Kernel"0x000000700000-0x000008000000 : "ROOTFS"Rootfs is usually mounted using /dev/mtd3In your upgrade packages, the usual special "update" script calls 2 scripts:- do_update.sh- do_update_general.shThe surprising thing is the content of do_update_general.sh:Code:#!/bin/bashflash_eraseall /dev/mtd4nandwrite -p dev/mtd4 /tmp/tekwayup_client/zImagecp -rf /tmp/tekwayup_client/dso/ /cp -rf /tmp/tekwayup_client/etc/ /cp -rf /tmp/tekwayup_client/icon/ /cp -rf /tmp/tekwayup_client/lib/ /mv /tmp/tekwayup_client/tdc/* /tar xvf /tmp/tekwayup_client/lib.tar.gz -C /#tar xvf /mnt/udisk/arm.tar.bz2 -C /usr/syncsyncIt starts erasing the /dev/mtd4 partition that you do not have, so I would guess destroying instead your /dev/mtd3 partition. That would explain why your scope doesn't boot anymore.So I suppose Hantek changed the partition layout on the last MSO5074FG, as they did on the HDG2000 AWG series. They added new partitions to ease the update and recovery process.We could try rebuilding your scope using dumps from another MSO5074FG but the hardware has to match too.I will package and post a backup tool compatible with your MSO5074fg that dumps up to 9 partitions, that should be enough.

author: fremen67
author_rank: Frequent Contributor
timestamp: February 02, 2015, 12:57:26 am
content: Quote from: Lauris on February 01, 2015, 09:18:49 amYou can backup your MSO5074FG via the backup tool attached so you don't have to open it.- Unzip the file and copy dst1kb_backup_tool_mso5074fg.up to the root directory of a USB stick- Check that you don't have other files beginning with "dst1kb" on the root directory of your USB stick- Connect the USB stick to your scope- Go to Utility Menu- Select Update Firmware- ConfirmThis will last some minutes and your scope will reboot at the end.You will find the backup files in the /dump directory of the USB stick. Just zip this directory and post it somewhere we can download it.Thanks!

author: Lauris
author_rank: Contributor
timestamp: February 02, 2015, 06:50:34 am
content: Hello,Here are dump from my scope:Google_drive_dirhope it will help.My scope info:Model: MSO5074FGSW version: 3.2.35(141110.0)HW version: 10020x5402820510002

author: dtomazini
author_rank: Contributor
timestamp: February 02, 2015, 12:12:28 pm
content: Thanks a lot Lauris !!

author: fremen67
author_rank: Frequent Contributor
timestamp: February 02, 2015, 12:56:30 pm
content: Quote from: Lauris on February 02, 2015, 06:50:34 amThanks a lot! That was quickThis is indeed a new partition layout with a recovery partition like the HDG2000.One partition is missing and this is the most important, the "recover" one. I had a quick look in the uboot dump (mtd0.bin) and the layout is as follows:mtdparts=nandflash0:1024k@0(uboot),512k(params),2048K(logo),512k(misc),4m(kernel),70m(rootfs),4m(kernel_bk),46m(recover)The missing file is mtd7.bin which should have a size of 46Mb (All files together should be 128Mo)In order to have a clean recovery of the system, we need mtd0.bin (uboot), mtd6.bin (kernel_bk) and mtd7.bin (recover)Maybe I made a tipo in the backup script...I will check this evening when back home.Edit: or maybe the MSO rebooted before the write on the USB sticks was completely finished.. I could also add some syncs at the end of the script...

author: dtomazini
author_rank: Contributor
timestamp: February 02, 2015, 02:41:19 pm
content: Nice job, i'm impressed with all this knowledge !!.Let me ask, looking on the first error log:Code:...NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bi t)NAND_ECC_NONE selected by board driver. This is not recommended!Scanning device for bad blocksBad eraseblock 421 at 0x0000034a0000Creating 4 MTD partitions on "NAND":0x000000000000-0x000000100000 : "Bootloader"0x000000100000-0x000000300000 : "LOGO"0x000000300000-0x000000700000 : "Kernel"0x000000700000-0x000008000000 : "ROOTFS"...Perhaps the error is in the Kernal partition ( 0x000000300000-0x000000700000 : "Kernel" ) on "Bad eraseblock 421 at 0x0000034a0000".So if i try to flhash the kernel again, using the mtd4.bin file (4mb), can i leave the situation worst than it is now ? , is better i wait for the a new dump, including the mtd7.bin ?.[]'sDaniel

author: fremen67
author_rank: Frequent Contributor
timestamp: February 02, 2015, 08:04:02 pm
content: Quote from: dtomazini on February 02, 2015, 02:41:19 pmI don't think so. Uboot is the only partition where you are not supposed to find bad blocks (at least where it could cause a problem). Having bad blocks elsewhere on a nand flash is normal. it's annoying as you can't simply clone a nand to another one. Is does not always work. That's why you need things like a .ubi file. It does not only contain the data but also a file system in it and uboot deals with bad blocks when writing such files to the nand.Quote from: dtomazini on February 02, 2015, 02:41:19 pmIt won't do any good as the partition layout has changed and anyway the kernel partition will be recreated during the recovery process. But on the other hand, it will allow you to test the DNW transfer process without taking to many risks (you can also check dnw with the test kernel option). If the flash fails when updating uboot you will have to use the JTAG solution.At the moment 2 of the 3 partitions could be flashed:- You can update uboot with mtd0.bin (using DNW) by choosing option , and then reboot and stop again with space bar- You will have new options in the menu, choose this one: " Download Kernel_bk (kernel_bk.bin)" and send mtd6.bin with DNWThe next step would be to choose " Download UBIFS image (recover.ubi) to Nand Flash" and send the recover.ubi file that I will create with mtd7.bin ... when I have it.And the last step would be to choose " recover start!" that will recreate all the other partitions from scratch.I will post a modified script so that we can get the missing file.

author: fremen67
author_rank: Frequent Contributor
timestamp: February 02, 2015, 08:30:33 pm
content: Quote from: Lauris on February 02, 2015, 06:50:34 amHello LaurisCould you run another backup with the attached modified script? I swaped the partition backup order so that it starts now with mtd7.bin and added a 10 sec sleep at the end of the script to allow some time for the usb stick to finish ongoing writes. Let's hope it will be OK now...Thank you !

author: dtomazini
author_rank: Contributor
timestamp: February 02, 2015, 10:45:25 pm
content: Hi Guys,I'm validating the DNW test mode, with the "mtd4.bin", and the result LOG is this:Code:##### 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 Flash Set the boot parameters Download User Program Enter TFTP download mode menu Reboot u-boot Test Linux Image (zImage)Enter your selection: tNow, Please connect to USB cable and USB interface!USB cable Connected!Now, Waiting for DNW to transmit data.Now, Downloading [ADDRESS:0xc0008000,TOTAL:0x400000]Please waiting ................................................................Download Done!!Download Address: 0xc0008000, Download Filesize:0x400000Now, Checksum calculation....Checksum O.K !!!Boot with zImageIs this Checksum O.K a indication that booth MSO5074FG are the same model and hardware ?. I can get a bit less worried ?QuoteOk, all updates with Checksum O.K . The new option "6" cames after the uboot update.

author: fremen67
author_rank: Frequent Contributor
timestamp: February 03, 2015, 12:37:30 am
content: Quote from: dtomazini on February 02, 2015, 10:45:25 pmNo it just says that you did not get the data corrupted during the tranfer from DNW to the MSOQuote from: dtomazini on February 02, 2015, 10:45:25 pmGood news!One step left to go ...BTW do you know the Firmware and Hardware versions you had?

author: dtomazini
author_rank: Contributor
timestamp: February 03, 2015, 01:05:18 am
content: No i didn't remenber the firmware and hardware version. I wrote it on a piece of paper to compare with the firmware upgrade file, but i lost this paper... .Is there a way to retrieve this information from the oscilloscope ?.On the XILINX board there is a number: "DDS V1.00.2"PS.: Using the "GNU Privacy Assistant" for Windows, now i understood (just a litle bit) and could retrieve the content of .up files !!!. Thanks again EEV forum.

author: Lauris
author_rank: Contributor
timestamp: February 03, 2015, 07:09:58 am
content: Hello,New dump, same folder dump_2015_02_03.rar archive. Hope this will work better, if not - will be possible to take new dump next week.Lauris

author: dtomazini
author_rank: Contributor
timestamp: February 03, 2015, 12:20:30 pm
content: Quote from: Lauris on February 03, 2015, 07:09:58 amThanks again Lauris !!!Tonight i will test it.Att;Daniel

author: fremen67
author_rank: Frequent Contributor
timestamp: February 03, 2015, 08:04:14 pm
content: Quote from: Lauris on February 03, 2015, 07:09:58 amThank you, it is a full dump now

author: fremen67
author_rank: Frequent Contributor
timestamp: February 03, 2015, 08:38:06 pm
content: Quote from: fremen67 on February 02, 2015, 08:04:02 pm@dtomazini: OK Daniel, we have to move from plan A to plan B.The recover partition has not been updated with roofs+kernel backup by Hantek so it is useless at the moment and we can't launch the recovery process.Plan B:mtd0: uboot: you already restored it -> OKmtd1: params: when unavailable, uboot will take default parameters (backup already empty anyway) -> Nothing to domtd2: logo: empty but you can restore it -> Restore with option  and mtd2.binmtd3: misc: to be erased -> Erase with option mtd4: kernel: need to be restored -> Restore with option  and mtd4.binmtd5: rootfs: need to be restored -> Restore with option  androotfs.ubiyou will get from memtd6: kernel_bk: need to be restored -> Restore with option  and mtd6.binmtd7: restore: need to be restored -> Restore with option  andrecover.ubiyou will get from meAfter that just do a normal start with option  and cross your fingers.I your hardware is the same as Lauris, then you are goodI PM you the link to download rootfs.ubi and recover.ubi.Good luck!

author: dtomazini
author_rank: Contributor
timestamp: February 03, 2015, 11:29:29 pm
content: Everything done !!, the oscilloscope is now working !!!.Awsome job fremen67 !!. Thanks a lot to You, Lauris and KL27x !!.Here is the log, after de reboot:Code:NAND read: device 0 offset 0x400000, size 0x4000004194304 bytes read: OKBoot with zImageStarting kernel ...Uncompressing Linux... done, booting the kernel.Linux version 3.2.35 (liuqian@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #115 PREEMPT Mon Nov 10 10:24:50 CST 2014CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: SMDK2416Ignoring unrecognised tag 0x54410008Memory 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=5 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272PID 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: 59288k/59288k available, 6248k 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 - 0xc03f1000 (4004 kB).init : 0xc03f1000 - 0xc0412000 ( 132 kB).data : 0xc0412000 - 0xc0560020 (1337 kB).bss : 0xc0560044 - 0xc057dd7c ( 120 kB)SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1NR_IRQS:107irq: clearing subpending status 00000003irq: 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 usbs3c-i2c s3c2410-i2c: slave address 0x10s3c-i2c s3c2410-i2c: bus frequency set to 9 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=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 421 at 0x0000034a0000Creating 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 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: 268UBI: attached mtd5 to ubi0UBI: MTD device name: "rootfs"UBI: MTD device size: 70 MiBUBI: number of good PEBs: 559UBI: number of bad PEBs: 1UBI: 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: 559UBI: number of PEBs reserved for bad PEB handling: 5UBI: max/mean erase counter: 2/1UBI: image sequence number: 0UBI: background thread "ubi_bgt0d" started, PID 330ohci_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: 1 port 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-05 22:09:32 UTC (947110172)UBIFS: mounted UBI device 0, volume 0, name "rootfs"UBIFS: file system size: 68440064 bytes (66836 KiB, 65 MiB, 539 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: 132Kg_serial gadget: high-speed config #1: Generic Serial configdso-iobank: install ok0x505gpio_major_n = 5, io_minor_n = 5, output 00x603gpio_major_n = 6, io_minor_n = 3, output 00x309gpio_major_n = 3, io_minor_n = 9, output 00x70agpio_major_n = 7, io_minor_n = 10, output 0dso5000b fpga configure initFPGA0_nCONFIG set config = -15FPGA0_nSTATUS set config = -16FPGA0_CONF_DONE set config = -16FPGA0_nCONFIG set pull = 2FPGA0_nSTATUS set pull = 2FPGA1_nCONFIG set config = -15FPGA1_nSTATUS set config = -16FPGA1_CONF_DONE set config = -14FPGA1_nCONFIG set pull = 2FPGA1_nSTATUS set pull = 2fpga0:status: 0x0FPGA0 CONFIGURE DATA DOWN finish.FPGA0 CONFIGURE Ok.fpga1:status: 0x1FPGA1 CONFIGURE DATA DOWN finish.FPGA1 CONFIGURE Ok.0x80900x1fpga bank 11811dso-fpga: install ok0x80900x1fpga bank 11811dso-fpga-la: install okdm9000 Ethernet Driver, V1.31dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfigeth0: dm9000b at c4988300,c498a308 IRQ 48 MAC: ba:b2:87:0d:4c:7e (random)bkl tq2416-backlight initialized done...dso-buzzer s3c2416-beep initialized done...make snd node.dm9000 dm9000: eth0: link down--------------------------------------------------------------------------------start--------------------------------------------------------------------------------filename=/lib/firmware/pll_125M.mif, filenamelen=26pllset.data=0xc000pllset.data=0xc001pllset.data=0xc002pllset.data=0xc003pllset.data=0xc104pllset.data=0xc105pllset.data=0xc006pllset.data=0xc107pllset.data=0xc108pllset.data=0xc009pllset.data=0xc00apllset.data=0xc00bpllset.data=0xc00cpllset.data=0xc00dpllset.data=0xc00epllset.data=0xc00fpllset.data=0xc010pllset.data=0xc111pllset.data=0xc112pllset.data=0xc013pllset.data=0xc014pllset.data=0xc015pllset.data=0xc016pllset.data=0xc017pllset.data=0xc018pllset.data=0xc019pllset.data=0xc01apllset.data=0xc01bpllset.data=0xc01cpllset.data=0xc01dpllset.data=0xc01epllset.data=0xc01fpllset.data=0xc020pllset.data=0xc021pllset.data=0xc022pllset.data=0xc023pllset.data=0xc024pllset.data=0xc025pllset.data=0xc026pllset.data=0xc027pllset.data=0xc028pllset.data=0xc029pllset.data=0xc02apllset.data=0xc12bpllset.data=0xc12cpllset.data=0xc02dpllset.data=0xc02epllset.data=0xc02fpllset.data=0xc030pllset.data=0xc031pllset.data=0xc032pllset.data=0xc033pllset.data=0xc134pllset.data=0xc135pllset.data=0xc036pllset.data=0xc037pllset.data=0xc038pllset.data=0xc039pllset.data=0xc03apllset.data=0xc03bpllset.data=0xc03cpllset.data=0xc13dpllset.data=0xc13epllset.data=0xc03fpllset.data=0xc040pllset.data=0xc041pllset.data=0xc042pllset.data=0xc043pllset.data=0xc044pllset.data=0xc045pllset.data=0xc146pllset.data=0xc147pllset.data=0xc048pllset.data=0xc049pllset.data=0xc04apllset.data=0xc04bpllset.data=0xc04cpllset.data=0xc04dpllset.data=0xc04epllset.data=0xc14fpllset.data=0xc150pllset.data=0xc051pllset.data=0xc052pllset.data=0xc053pllset.data=0xc054pllset.data=0xc055pllset.data=0xc056pllset.data=0xc057pllset.data=0xc158pllset.data=0xc159pllset.data=0xc05apllset.data=0xc05bpllset.data=0xc05cpllset.data=0xc05dpllset.data=0xc05epllset.data=0xc05fpllset.data=0xc060pllset.data=0xc161pllset.data=0xc162pllset.data=0xc063pllset.data=0xc064pllset.data=0xc065pllset.data=0xc066pllset.data=0xc067pllset.data=0xc068pllset.data=0xc069pllset.data=0xc16apllset.data=0xc16bpllset.data=0xc06cpllset.data=0xc06dpllset.data=0xc06epllset.data=0xc06fpllset.data=0xc070pllset.data=0xc071pllset.data=0xc072pllset.data=0xc173pllset.data=0xc174pllset.data=0xc075pllset.data=0xc076pllset.data=0xc077pllset.data=0xc078pllset.data=0xc079pllset.data=0xc07apllset.data=0xc07bpllset.data=0xc17cpllset.data=0xc17dpllset.data=0xc17epllset.data=0xc07fpllset.data=0xc080pllset.data=0xc081pllset.data=0xc082pllset.data=0xc083pllset.data=0xc084pllset.data=0xc085pllset.data=0xc086pllset.data=0xc087pllset.data=0xc088pllset.data=0xc089pllset.data=0xc08apllset.data=0xc08bpllset.data=0xc08cpllset.data=0xc08dpllset.data=0xc08epllset.data=0xc08ffilename=/lib/firmware/pll_100M.mif, filenamelen=26pllset.data=0xa000pllset.data=0xa001pllset.data=0xa002pllset.data=0xa003pllset.data=0xa104pllset.data=0xa105pllset.data=0xa006pllset.data=0xa107pllset.data=0xa108pllset.data=0xa009pllset.data=0xa00apllset.data=0xa00bpllset.data=0xa00cpllset.data=0xa00dpllset.data=0xa00epllset.data=0xa00fpllset.data=0xa010pllset.data=0xa111pllset.data=0xa112pllset.data=0xa013pllset.data=0xa014pllset.data=0xa015pllset.data=0xa016pllset.data=0xa017pllset.data=0xa018pllset.data=0xa019pllset.data=0xa01apllset.data=0xa01bpllset.data=0xa01cpllset.data=0xa01dpllset.data=0xa01epllset.data=0xa01fpllset.data=0xa020pllset.data=0xa021pllset.data=0xa022pllset.data=0xa023pllset.data=0xa024pllset.data=0xa025pllset.data=0xa026pllset.data=0xa027pllset.data=0xa028pllset.data=0xa029pllset.data=0xa02apllset.data=0xa12bpllset.data=0xa12cpllset.data=0xa02dpllset.data=0xa02epllset.data=0xa02fpllset.data=0xa030pllset.data=0xa031pllset.data=0xa032pllset.data=0xa033pllset.data=0xa134pllset.data=0xa135pllset.data=0xa036pllset.data=0xa037pllset.data=0xa038pllset.data=0xa039pllset.data=0xa03apllset.data=0xa03bpllset.data=0xa03cpllset.data=0xa13dpllset.data=0xa13epllset.data=0xa03fpllset.data=0xa040pllset.data=0xa041pllset.data=0xa042pllset.data=0xa043pllset.data=0xa044pllset.data=0xa045pllset.data=0xa146pllset.data=0xa147pllset.data=0xa048pllset.data=0xa049pllset.data=0xa04apllset.data=0xa04bpllset.data=0xa04cpllset.data=0xa04dpllset.data=0xa04epllset.data=0xa14fpllset.data=0xa150pllset.data=0xa051pllset.data=0xa052pllset.data=0xa053pllset.data=0xa054pllset.data=0xa055pllset.data=0xa056pllset.data=0xa057pllset.data=0xa158pllset.data=0xa159pllset.data=0xa05apllset.data=0xa05bpllset.data=0xa05cpllset.data=0xa05dpllset.data=0xa05epllset.data=0xa05fpllset.data=0xa060pllset.data=0xa161pllset.data=0xa162pllset.data=0xa063pllset.data=0xa064pllset.data=0xa065pllset.data=0xa066pllset.data=0xa067pllset.data=0xa068pllset.data=0xa069pllset.data=0xa16apllset.data=0xa16bpllset.data=0xa06cpllset.data=0xa06dpllset.data=0xa06epllset.data=0xa06fpllset.data=0xa070pllset.data=0xa071pllset.data=0xa072pllset.data=0xa173pllset.data=0xa174pllset.data=0xa075pllset.data=0xa076pllset.data=0xa077pllset.data=0xa078pllset.data=0xa079pllset.data=0xa07apllset.data=0xa07bpllset.data=0xa17cpllset.data=0xa17dpllset.data=0xa17epllset.data=0xa07fpllset.data=0xa080pllset.data=0xa081pllset.data=0xa082pllset.data=0xa083pllset.data=0xa084pllset.data=0xa085pllset.data=0xa086pllset.data=0xa087pllset.data=0xa088pllset.data=0xa089pllset.data=0xa08apllset.data=0xa08bpllset.data=0xa08cpllset.data=0xa08dpllset.data=0xa08epllset.data=0xa08fErasing 128 Kibyte @ 80000 - 100% complete..mkdir: can't create directory '/param': File existsmkdir: can't create directory '/param/sav': File existsmkdir: can't create directory '/param': File existsmkdir: can't create directory '/param/sav': File existsThu Jan 1 00:00:00 UTC 2009p_pth->pthid=1189733520p_pth->pthid=1180914832p_pth->pthid=1198122128p_pth->pthid=1207301264mount: mounting 192.168.1.22:/home/nfsroot on /mnt/nfs failed: No route to hostAtt;Daniel

author: dtomazini
author_rank: Contributor
timestamp: February 03, 2015, 11:36:17 pm
content: and the log after the second reboot:Code: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 0x8002048 bytes read: OK**************************normal start*******************************NAND erase: device 0 offset 0x380000, size 0x80000Erasing at 0x3e0000 -- 100% complete.OKNAND write: device 0 offset 0x380000, size 0x800Writing data at 0x380800 -- 100% complete.2048 bytes written: OKNAND read: device 0 offset 0x380000, size 0x8002048 bytes read: OKSaving Environment to NAND...Erasing Nand...Warning: Erase size 0x00004000 smaller than one erase block 0x00020000Erasing 0x00020000 insteadErasing at 0x80000 -- 100% complete.Writing to Nand... doneNAND read: device 0 offset 0x400000, size 0x4000004194304 bytes read: OKBoot with zImageStarting kernel ...Uncompressing Linux... done, booting the kernel.Linux version 3.2.35 (liuqian@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009 q1-176) ) #115 PREEMPT Mon Nov 10 10:24:50 CST 2014CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: SMDK2416Ignoring unrecognised tag 0x54410008Memory 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=5 root=ubi0:rootfs rootfstype=ubifs init=/ linuxrc console=ttySAC0 lcd=X480Y272PID 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: 59288k/59288k available, 6248k 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 - 0xc03f1000 (4004 kB).init : 0xc03f1000 - 0xc0412000 ( 132 kB).data : 0xc0412000 - 0xc0560020 (1337 kB).bss : 0xc0560044 - 0xc057dd7c ( 120 kB)SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1NR_IRQS:107irq: 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 usbs3c-i2c s3c2410-i2c: slave address 0x10s3c-i2c s3c2410-i2c: bus frequency set to 9 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=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-bi t)NAND_ECC_NONE selected by board driver. This is not recommended!Scanning device for bad blocksBad eraseblock 421 at 0x0000034a0000Creating 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 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: 302UBI: attached mtd5 to ubi0UBI: MTD device name: "rootfs"UBI: MTD device size: 70 MiBUBI: number of good PEBs: 559UBI: number of bad PEBs: 1UBI: 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: 559UBI: number of PEBs reserved for bad PEB handling: 5UBI: max/mean erase counter: 2/1UBI: image sequence number: 0UBI: background thread "ubi_bgt0d" started, PID 330ohci_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: 1 port 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 2009-01-01 00:11:52 UTC (1230768712)UBIFS: recovery neededUBIFS: recovery completedUBIFS: mounted UBI device 0, volume 0, name "rootfs"UBIFS: file system size: 68440064 bytes (66836 KiB, 65 MiB, 539 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: 132Kdso-iobank: install ok0x505gpio_major_n = 5, io_minor_n = 5, output 00x603gpio_major_n = 6, io_minor_n = 3, output 00x309gpio_major_n = 3, io_minor_n = 9, output 00x70agpio_major_n = 7, io_minor_n = 10, output 0dso5000b fpga configure initFPGA0_nCONFIG set config = -15FPGA0_nSTATUS set config = -16FPGA0_CONF_DONE set config = -16FPGA0_nCONFIG set pull = 2FPGA0_nSTATUS set pull = 2FPGA1_nCONFIG set config = -15FPGA1_nSTATUS set config = -16FPGA1_CONF_DONE set config = -14FPGA1_nCONFIG set pull = 2FPGA1_nSTATUS set pull = 2fpga0:status: 0x0FPGA0 CONFIGURE DATA DOWN finish.FPGA0 CONFIGURE Ok.fpga1:status: 0x1FPGA1 CONFIGURE DATA DOWN finish.FPGA1 CONFIGURE Ok.0x80900x1fpga bank 11811dso-fpga: install ok0x80900x1fpga bank 11811dso-fpga-la: install okdm9000 Ethernet Driver, V1.31dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfigeth0: dm9000b at c4988300,c498a308 IRQ 48 MAC: 56:c9:ce:77:45:d9 (random)bkl tq2416-backlight initialized done...dso-buzzer s3c2416-beep initialized done...make snd node.dm9000 dm9000: eth0: link down--------------------------------------------------------------------------------start--------------------------------------------------------------------------------filename=/lib/firmware/pll_125M.mif, filenamelen=26pllset.data=0xc000pllset.data=0xc001pllset.data=0xc002pllset.data=0xc003pllset.data=0xc104pllset.data=0xc105pllset.data=0xc006pllset.data=0xc107pllset.data=0xc108pllset.data=0xc009pllset.data=0xc00apllset.data=0xc00bpllset.data=0xc00cpllset.data=0xc00dpllset.data=0xc00epllset.data=0xc00fpllset.data=0xc010pllset.data=0xc111pllset.data=0xc112pllset.data=0xc013pllset.data=0xc014pllset.data=0xc015pllset.data=0xc016pllset.data=0xc017pllset.data=0xc018pllset.data=0xc019pllset.data=0xc01apllset.data=0xc01bpllset.data=0xc01cpllset.data=0xc01dpllset.data=0xc01epllset.data=0xc01fpllset.data=0xc020pllset.data=0xc021pllset.data=0xc022pllset.data=0xc023pllset.data=0xc024pllset.data=0xc025pllset.data=0xc026pllset.data=0xc027pllset.data=0xc028pllset.data=0xc029pllset.data=0xc02apllset.data=0xc12bpllset.data=0xc12cpllset.data=0xc02dpllset.data=0xc02epllset.data=0xc02fpllset.data=0xc030pllset.data=0xc031pllset.data=0xc032pllset.data=0xc033pllset.data=0xc134pllset.data=0xc135pllset.data=0xc036pllset.data=0xc037pllset.data=0xc038pllset.data=0xc039pllset.data=0xc03apllset.data=0xc03bpllset.data=0xc03cpllset.data=0xc13dpllset.data=0xc13epllset.data=0xc03fpllset.data=0xc040pllset.data=0xc041pllset.data=0xc042pllset.data=0xc043pllset.data=0xc044pllset.data=0xc045pllset.data=0xc146pllset.data=0xc147pllset.data=0xc048pllset.data=0xc049pllset.data=0xc04apllset.data=0xc04bpllset.data=0xc04cpllset.data=0xc04dpllset.data=0xc04epllset.data=0xc14fpllset.data=0xc150pllset.data=0xc051pllset.data=0xc052pllset.data=0xc053pllset.data=0xc054pllset.data=0xc055pllset.data=0xc056pllset.data=0xc057pllset.data=0xc158pllset.data=0xc159pllset.data=0xc05apllset.data=0xc05bpllset.data=0xc05cpllset.data=0xc05dpllset.data=0xc05epllset.data=0xc05fpllset.data=0xc060pllset.data=0xc161pllset.data=0xc162pllset.data=0xc063pllset.data=0xc064pllset.data=0xc065pllset.data=0xc066pllset.data=0xc067pllset.data=0xc068pllset.data=0xc069pllset.data=0xc16apllset.data=0xc16bpllset.data=0xc06cpllset.data=0xc06dpllset.data=0xc06epllset.data=0xc06fpllset.data=0xc070pllset.data=0xc071pllset.data=0xc072pllset.data=0xc173pllset.data=0xc174pllset.data=0xc075pllset.data=0xc076pllset.data=0xc077pllset.data=0xc078pllset.data=0xc079pllset.data=0xc07apllset.data=0xc07bpllset.data=0xc17cpllset.data=0xc17dpllset.data=0xc17epllset.data=0xc07fpllset.data=0xc080pllset.data=0xc081pllset.data=0xc082pllset.data=0xc083pllset.data=0xc084pllset.data=0xc085pllset.data=0xc086pllset.data=0xc087pllset.data=0xc088pllset.data=0xc089pllset.data=0xc08apllset.data=0xc08bpllset.data=0xc08cpllset.data=0xc08dpllset.data=0xc08epllset.data=0xc08ffilename=/lib/firmware/pll_100M.mif, filenamelen=26pllset.data=0xa000pllset.data=0xa001pllset.data=0xa002pllset.data=0xa003pllset.data=0xa104pllset.data=0xa105pllset.data=0xa006pllset.data=0xa107pllset.data=0xa108pllset.data=0xa009pllset.data=0xa00apllset.data=0xa00bpllset.data=0xa00cpllset.data=0xa00dpllset.data=0xa00epllset.data=0xa00fpllset.data=0xa010pllset.data=0xa111pllset.data=0xa112pllset.data=0xa013pllset.data=0xa014pllset.data=0xa015pllset.data=0xa016pllset.data=0xa017pllset.data=0xa018pllset.data=0xa019pllset.data=0xa01apllset.data=0xa01bpllset.data=0xa01cpllset.data=0xa01dpllset.data=0xa01epllset.data=0xa01fpllset.data=0xa020pllset.data=0xa021pllset.data=0xa022pllset.data=0xa023pllset.data=0xa024pllset.data=0xa025pllset.data=0xa026pllset.data=0xa027pllset.data=0xa028pllset.data=0xa029pllset.data=0xa02apllset.data=0xa12bpllset.data=0xa12cpllset.data=0xa02dpllset.data=0xa02epllset.data=0xa02fpllset.data=0xa030pllset.data=0xa031pllset.data=0xa032pllset.data=0xa033pllset.data=0xa134pllset.data=0xa135pllset.data=0xa036pllset.data=0xa037pllset.data=0xa038pllset.data=0xa039pllset.data=0xa03apllset.data=0xa03bpllset.data=0xa03cpllset.data=0xa13dpllset.data=0xa13epllset.data=0xa03fpllset.data=0xa040pllset.data=0xa041pllset.data=0xa042pllset.data=0xa043pllset.data=0xa044pllset.data=0xa045pllset.data=0xa146pllset.data=0xa147pllset.data=0xa048pllset.data=0xa049pllset.data=0xa04apllset.data=0xa04bpllset.data=0xa04cpllset.data=0xa04dpllset.data=0xa04epllset.data=0xa14fpllset.data=0xa150pllset.data=0xa051pllset.data=0xa052pllset.data=0xa053pllset.data=0xa054pllset.data=0xa055pllset.data=0xa056pllset.data=0xa057pllset.data=0xa158pllset.data=0xa159pllset.data=0xa05apllset.data=0xa05bpllset.data=0xa05cpllset.data=0xa05dpllset.data=0xa05epllset.data=0xa05fpllset.data=0xa060pllset.data=0xa161pllset.data=0xa162pllset.data=0xa063pllset.data=0xa064pllset.data=0xa065pllset.data=0xa066pllset.data=0xa067pllset.data=0xa068pllset.data=0xa069pllset.data=0xa16apllset.data=0xa16bpllset.data=0xa06cpllset.data=0xa06dpllset.data=0xa06epllset.data=0xa06fpllset.data=0xa070pllset.data=0xa071pllset.data=0xa072pllset.data=0xa173pllset.data=0xa174pllset.data=0xa075pllset.data=0xa076pllset.data=0xa077pllset.data=0xa078pllset.data=0xa079pllset.data=0xa07apllset.data=0xa07bpllset.data=0xa17cpllset.data=0xa17dpllset.data=0xa17epllset.data=0xa07fpllset.data=0xa080pllset.data=0xa081pllset.data=0xa082pllset.data=0xa083pllset.data=0xa084pllset.data=0xa085pllset.data=0xa086pllset.data=0xa087pllset.data=0xa088pllset.data=0xa089pllset.data=0xa08apllset.data=0xa08bpllset.data=0xa08cpllset.data=0xa08dpllset.data=0xa08epllset.data=0xa08fErasing 128 Kibyte @ 80000 - 100% complete..mkdir: can't create directory '/param': File existsmkdir: can't create directory '/param/sav': File existsmkdir: can't create directory '/param': File existsmkdir: can't create directory '/param/sav': File existsp_pth->pthid=1191261328p_pth->pthid=1182286992p_pth->pthid=1199649936p_pth->pthid=1208808592mount: mounting 192.168.1.22:/home/nfsroot on /mnt/nfs failed: No route to hostHumm i forgot to do the self calibration !!!

author: fremen67
author_rank: Frequent Contributor
timestamp: February 03, 2015, 11:48:19 pm
content: Quote from: dtomazini on February 03, 2015, 11:29:29 pmHehe you are coming back from very farWithout Lauris' backup it would have been impossible to help you.

author: fremen67
author_rank: Frequent Contributor
timestamp: February 04, 2015, 12:23:07 am
content: Quote from: dtomazini on February 03, 2015, 11:36:17 pmWhat you see now before the kernel is loaded is the way Hantek has implemented the recover mechanism.The whole "misc" partition is used as a flag !! The bootloader reads it, if the first byte is not null, then it erases the partition, load the kernel and starts.The firwmware is supposed to write to the first byte of this partition on normal stop of the MSO. If something goes wrong it won't, then on next reboot, the partition will still be empty and the bootloader will then boot on the recovery partition which allows you to choose to rebuilt the kernel and rootfs partition from backup.If you manually starts with the recover partition (from bootloader), you will be able to backup kernel&rootfs Inside the recover partition... that's what was not done on Lauris' MSO. Hantek should have done that at the factory. Should a problem happen, the recovery would be useless.The principle is good but the way it is written is far from being clean... They have shared the sources as uboot is GPL licenced. Just look how they modified the original code. There are still useless test lines Inside (reading back the partition after erasing it for nothing) :Code:int fs_test(){//printf("**************************111*******************************\n");char flag = 1;char cmdBuf;run_command("nand read 0xc0008000 misc 1", 0);strncpy(&flag, 0xc0008000, 1);//printf("read flag is : %d\n", flag);//printf("**************************222*******************************\n");#if 1if (flag){printf("**************************normal start*******************************\n");#if 1run_command("nand erase misc", 0);flag = 0;strncpy(0xc0008000, &flag, 1);run_command("nand write 0xc0008000 misc 1", 0);run_command("nand read 0xc0008000 misc 1", 0);strncpy(&flag, 0xc0008000, 1);//printf("read flag2 is : %d\n", flag);#endif#ifdef CONFIG_ROOTFS_APARTsprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=5 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");#elsesprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=5 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");#endif//printf("cmdbuf: %s\n", cmdBuf);run_command(cmdBuf, 0);sprintf(cmdBuf, "nand read 0xc0008000 kernel;bootm 0xc0008000");//printf("cmdbuf: %s\n", cmdBuf);run_command(cmdBuf, 0);}else{printf("**************************recover start*******************************\n");run_command("nand erase misc", 0);//sprintf(cmdBuf, "setenv bootargs noinitrd root=/dev/mtdblock9 rootfstype=jffs2 init=/linuxrc console=ttySAC0;saveenv");//sprintf(cmdBuf, "setenv bootargs root=/dev/mtdblock8 rootfstype=jffs2 rw init=/linuxrc console=ttySAC0,115200;saveenv");#ifdef CONFIG_ROOTFS_APARTsprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=8 root=ubi0:recover rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");#elsesprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=7 root=ubi0:recover rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");#endif//printf("cmdbuf: %s\n", cmdBuf);run_command(cmdBuf, 0);sprintf(cmdBuf, "nand read 0xc0008000 kernel_bk;bootm 0xc0008000");//printf("cmdbuf: %s\n", cmdBuf);run_command(cmdBuf, 0);}#endifprintf("***************************start error!!!*********************************\n");return 0;}

author: Lauris
author_rank: Contributor
timestamp: February 04, 2015, 08:25:22 am
content: Ok, now wait one second. you are saying that I'm sitting on ticking bomb too? Any way to prevent that? Since for me scope is not yet that clear as PC, so I would like to have working recovery for it.Lauris

author: dtomazini
author_rank: Contributor
timestamp: February 04, 2015, 05:23:09 pm
content: Code:The whole "misc" partition is used as a flag !! The bootloader reads it, if the first byte is not null, then it erases the partition, load the kernel and starts.The firwmware is supposed to write to the first byte of this partition on normal stop of the MSO. If something goes wrong it won't, then on next reboot, the partition will still be empty and the bootloader will then boot on the recovery partition which allows you to choose to rebuilt the kernel and rootfs partition from backup.It's a good idea for recovery solution after an upgrade. But if they don't put a verification routine inside the firmware script, this recovery didn't work. Like my case, the upgrade routine has finished with sucessfull, but it's make a complete mass in the rootfs.Code:If you manually starts with the recover partition (from bootloader), you will be able to backup kernel&rootfs Inside the recover partition... that's what was not done on Lauris' MSO. Hantek should have done that at the factory. Should a problem happen, the recovery would be useless.Is there a way to make this backup, and leave it on the right partition ?.Daniel

author: fremen67
author_rank: Frequent Contributor
timestamp: February 05, 2015, 12:07:10 am
content: Quote from: Lauris on February 04, 2015, 08:25:22 amWell, it's not really a ticking bomb. Your MSO has a new layout which would allow a simple recovery of its system when needed. It's just that this recovery would not work, not that you will have problems. Daniel's problem was that he upgraded his "4 partitions layout style" MSO with a script that was made for the new "8 partitions layout style" MSOs and which destroyed the rootfs partition...All you have to do is to launch yourself the backup process and you will be good.When the MSO boots in recovery mode, it shows for 10 seconds a screen where you can read:"Press F1 to reboot the system""Press F2 to recover the system""Press F3 to update the recover partition""Press F4 to backup the system(For developers)"The last option (F4) only appears if the initial backup is not on the recover partition (which should be your case). It's also a way to know wether you have to do this backup or not.If you don't do anything, the MSO will reboot the normal way.So you have to press F4 within10 seconds and the MSO will starts its backup (the one Hantek should have done at the factory). This is quiet long, it will last for some minutes.... and that's it!You can enter the recover menu via the serial console by stopping the bootloader and choosing the correct option... or you can use the attached "update" script which will force the MSO to boot in recovery mode once (If you are not quick enough, just do it again)Edit: once your are done, I would advice that you run once again the backup script I posted (the last you used) so that you have an uptodate backup of your system with you... I find it saver to have a backup outside the MSO.

author: fremen67
author_rank: Frequent Contributor
timestamp: February 05, 2015, 12:22:54 am
content: Quote from: dtomazini on February 04, 2015, 05:23:09 pmYou MSO had no recover partition when you run the update. That's why it failed (and of course because the script did not check on what kind of MSO it was running). Now the next updates should works as it is now uptodate.Quote from: dtomazini on February 04, 2015, 05:23:09 pmYes, you can access the recover menu from the bootloader or via the script I just posted and run the backup from there.But anyway, should you have another problem, you now have all the Tools and backups to handle it

author: dtomazini
author_rank: Contributor
timestamp: February 05, 2015, 03:44:22 am
content: That is right !!

author: mg.glodek@gmail.com
author_rank: Newbie
timestamp: March 11, 2015, 08:31:57 am
content: Hi,I think that I have very simmilar problam that dtomazini has. I will be really greatfull if You could help me with comming back to life my Voltcraft DSO-1062D. This is the copy of the Hantek/Tekeway scopes, uses same firmware.The scope I have received crashes at the very begining after start, shoving only Volcraft logo. After connecting via UART to my laptop with Putty software I have noticed that linux faild to start with"Kernel panic - not syncing: Attempted to kill init!"error.Full log below.Can I ask You to help me solving the problem? What I shold repair/upload using boot menu? I think that botloader is working corectly as I can go to boot menu and probably make use of DWN upload method (didn't tasted as i do not have tq2416 driver required for that connection).Code:##### 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 0x400000Skipping bad block 0x000000004194304 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) ) #31 PREEMPT Tue Jul 16 16:02:21 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=ttySAC0PID 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 39 at 0x0000004e0000Bad eraseblock 814 at 0x0000065c0000Bad eraseblock 833 at 0x000006820000Bad eraseblock 924 at 0x000007380000Creating 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: 764UBI: 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: 3/1UBI: 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-07 10:38:25 UTC (947241505)UBIFS: recovery neededInternal error: Oops - undefined instruction: 0 [#1] PREEMPTModules linked in:CPU: 0 Not tainted (3.2.35 #31)PC is at ubifs_wbuf_sync_nolock+0x58/0x180LR is at do_commit+0xa0/0x7b4pc : [<c0133740>] lr : [<c013b5a8>] psr: 60000013sp : c381fc70 ip : c381fca0 fp : c381fc9cr10: c3b68000 r9 : c3b68000 r8 : 00000000r7 : 00000002 r6 : c3b68000 r5 : c38ee2c0 r4 : c38ee298r3 : 00000000 r2 : 00000001 r1 : 00000000 r0 : c38ee2e0Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernelControl: 0005317f Table: 30004000 DAC: 00000017Process swapper (pid: 1, stack limit = 0xc381e270)Stack: (0xc381fc70 to 0xc3820000)fc60: c381e000 00000001 c3b68184 c38ee298fc80: c38ee2c0 00000098 00000002 00000000 c381fd1c c381fca0 c013b5a8 c01336f8fca0: 00000000 c0018a60 c381fccc c381fcb8 c381fcdc c381fcc0 c000c7b4 c000b4e8fcc0: c381e000 00000001 c3b68184 00000000 c381fd04 c381fce0 c000b544 c000c7a0fce0: c381fd3c c381fd20 c0018a60 c013bd6c 00000000 c0018a60 c381e000 c3b68000fd00: c3b68184 00000000 00000000 c38ee600 c381fd3c c381fd20 c013bd84 c013b518fd20: 00000000 0000013a c3b68000 00000000 c381fd6c c381fd40 c0145354 c013bcccfd40: 00000000 00000020 00000000 c0174ac4 000066c3 c3b68000 00000000 c38ee200fd60: c381fdac c381fd70 c01453bc c01452f8 00000000 00000000 c381fdac 00000000fd80: 0001ef3f 05308578 00000000 00000000 00000000 00001800 00000000 00000000fda0: c381fe34 c381fdb0 c0130498 c0145368 c3b68790 c3804684 c3804680 0000000afdc0: c381fdec c381fdd0 c000c7b4 00800000 0001f000 00000000 00000000 00008000fde0: c041b368 c38ec440 c3b687d4 c3b68008 0001f000 00000000 0000000c 00000000fe00: c3810640 c38ec6c5 c38ec840 c38ec6c0 c3810640 c041b368 c041b368 00000000fe20: c381fec8 00008000 c381fe5c c381fe38 c0082b9c c012f288 c38ec6c0 00008000fe40: c041b368 c38ec6c0 c3810640 00008000 c381fe84 c381fe60 c009fb10 c0082b90fe60: 00008000 c38ec6c0 00000000 c38ec6e0 c041b368 c381fec8 c381feac c381fe88fe80: c009fba8 c009fac8 00000000 00008000 c38ec6c0 c38ec6e0 00000020 c381fec8fea0: c381fefc c381feb0 c009fd8c c009fb7c 0000000c 00000000 c381fee4 c381fec8fec0: c0067c64 c0067b70 c38100a0 c3401280 c0403584 00000000 c380f000 c0403584fee0: 00008000 c0403584 c040c108 c0403578 c381ff34 c381ff00 c00a0414 c009fc50ff00: 00000000 00000000 00000000 00000000 c38ec6c0 c38ec6e0 c380c000 c380c000ff20: 00008000 00000013 c381ff5c c381ff38 c03e9ad4 c00a0384 00000000 c0403584ff40: c0403578 c380c000 c380c000 00008000 c381ffac c381ff60 c03e9c00 c03e9abcff60: c381ff7c c381ff70 c0040fb4 c0040dd8 c381ffac c381ff80 c01a6a34 c0040fa8ff80: c0040238 c0403584 c0403578 c04087cc 00000013 00000000 00000000 00000000ffa0: c381ffd4 c381ffb0 c03e9f28 c03e9b80 00000000 00000000 c381ffd4 c04087ccffc0: c040848c c04087cc c381fff4 c381ffd8 c03e9304 c03e9eb8 00000000 c03e9204ffe0: c0021e38 00000013 00000000 c381fff8 c0021e38 c03e9214 fff3f7bf effe5ff7Backtrace:[<c01336e8>] (ubifs_wbuf_sync_nolock+0x0/0x180) from [<c013b5a8>] (do_commit+0xa0/0x7b4)r8:00000000 r7:00000002 r6:00000098 r5:c38ee2c0 r4:c38ee298[<c013b508>] (do_commit+0x0/0x7b4) from [<c013bd84>] (ubifs_run_commit+0xc8/0x174)[<c013bcbc>] (ubifs_run_commit+0x0/0x174) from [<c0145354>] (grab_empty_leb+0x6c/0x70)r7:00000000 r6:c3b68000 r5:0000013a r4:00000000[<c01452e8>] (grab_empty_leb+0x0/0x70) from [<c01453bc>] (ubifs_rcvry_gc_commit+0x64/0x110)r6:c38ee200 r5:00000000 r4:c3b68000[<c0145358>] (ubifs_rcvry_gc_commit+0x0/0x110) from [<c0130498>] (ubifs_mount+0x1220/0x14b4)r8:00000000 r7:00000000 r6:00001800 r5:00000000 r4:00000000[<c012f278>] (ubifs_mount+0x0/0x14b4) from [<c0082b9c>] (mount_fs+0x1c/0xe4)[<c0082b80>] (mount_fs+0x0/0xe4) from [<c009fb10>] (vfs_kern_mount+0x58/0x94)r6:00008000 r5:c3810640 r4:c38ec6c0[<c009fab8>] (vfs_kern_mount+0x0/0x94) from [<c009fba8>] (do_kern_mount+0x3c/0xd4)r9:c381fec8 r8:c041b368 r7:c38ec6e0 r6:00000000 r5:c38ec6c0r4:00008000[<c009fb6c>] (do_kern_mount+0x0/0xd4) from [<c009fd8c>] (do_mount+0x14c/0x734)r9:c381fec8 r8:00000020 r7:c38ec6e0 r6:c38ec6c0 r5:00008000r4:00000000[<c009fc40>] (do_mount+0x0/0x734) from [<c00a0414>] (sys_mount+0xa0/0xd0)[<c00a0374>] (sys_mount+0x0/0xd0) from [<c03e9ad4>] (do_mount_root+0x28/0xc4)r7:00000013 r6:00008000 r5:c380c000 r4:c380c000[<c03e9aac>] (do_mount_root+0x0/0xc4) from [<c03e9c00>] (mount_block_root+0x90/0x234)r6:00008000 r5:c380c000 r4:c380c000[<c03e9b70>] (mount_block_root+0x0/0x234) from [<c03e9f28>] (prepare_namespace+0x80/0x190)[<c03e9ea8>] (prepare_namespace+0x0/0x190) from [<c03e9304>] (kernel_init+0x100/0x144)r6:c04087cc r5:c040848c r4:c04087cc[<c03e9204>] (kernel_init+0x0/0x144) from [<c0021e38>] (do_exit+0x0/0x6f8)r7:00000013 r6:c0021e38 r5:c03e9204 r4:00000000Code: e89da9f0 e3c33002 e5c03078 e2800048 (fffc2af9)---[ end trace d45263bc4b91060f ]---Kernel panic - not syncing: Attempted to kill init!g_serial gadget: high-speed config #1: Generic Serial config

author: fremen67
author_rank: Frequent Contributor
timestamp: March 11, 2015, 11:46:24 pm
content: Quote from: mg.glodek@gmail.com on March 11, 2015, 08:31:57 amYou would need a backup from the same DSO or at least from a similar one like a Hantek DSO5062D, DSO5102D or DSO5202D.You may find someone who could post one for you if you ask in this thread:https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/With that backup, I could create a root.ubi file that you will be able to flash on your DSO.The kernel seems to load correctly and the problem seems to be related to the Rootfs partition.What kind of OS do you have on your PC? Win7 x32, Win7 x64 ...?

author: mg.glodek@gmail.com
author_rank: Newbie
timestamp: March 12, 2015, 07:15:26 am
content: Thank You for quick answer. I have Win7x32 and Win7x64 on the other computer. I have just post a reqest on the topic You have mentioned.Can I ask You to look on thehttp://voltcraftdownload.info/Default.aspx?modelno=DSO-1062Dsite? There is a Source Code (GPL2.0) for my scope (>300MB). Is this something that we can use?Can You please indicate where can I find propoer USB driver for DWN (tq2416 driver)?

author: fremen67
author_rank: Frequent Contributor
timestamp: March 12, 2015, 12:50:03 pm
content: Quote from: mg.glodek@gmail.com on March 12, 2015, 07:15:26 amYou won't find something usefull in those GPL sources for your problem.You will find DNW and the tq2416 drivers here for Win7x32:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let%27s-see!/msg451021/#msg451021and the next post here for Win7x64:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let%27s-see!/msg451081/#msg451081

author: mg.glodek@gmail.com
author_rank: Newbie
timestamp: March 16, 2015, 12:36:18 am
content: Thank You for the links.In the meantime I have received some DSO-1062D dump file from someone who have seen my post on the second topic. As this file has only 4 MB I do not know if this is something that I can use or should I ask for whole backup?Link to the file:https://drive.google.com/folderview?id=0Bzn-cY170kZkN05OTGoyU3drNmc&usp=sharing

author: fremen67
author_rank: Frequent Contributor
timestamp: March 16, 2015, 12:50:49 pm
content: Quote from: mg.glodek@gmail.com on March 16, 2015, 12:36:18 amThis is a dump from the kernel. I would bet the partition which is corrupted is the last one (mtd3=rootfs).If this kernel dump comes from an identical machine, you can try flashing it to yours and then you will be sure but as you usually don't write on this kernel partition, there are few chances that it gets corrupted.

author: mg.glodek@gmail.com
author_rank: Newbie
timestamp: March 16, 2015, 02:10:37 pm
content: QuoteAs I do not have any Linux experience can I kindly ask You to briefly describe how to do that flash? I know that I can do it via DWN but do not know any details.

author: fremen67
author_rank: Frequent Contributor
timestamp: March 16, 2015, 05:07:37 pm
content: Quote from: mg.glodek@gmail.com on March 16, 2015, 02:10:37 pm1 - Stop the boot process of your device by pressing space key when connected vi serial console (you will get the uboot menu shown in the previous posts)2 - connect your PC to DSO vi USB3 - choose "t" option (test linux image)4 - install drivers on your PC5 - launch DNW and send a small file (your kernel backup f.e.). It is just to test DNW, nothing will be written on the DSO flash.If everything is OK (you will see dashes on your serial console if it works), you can do it again but this time select the kernel option (3?) and send your kernel backup.That's it!PS: read again this thread, this should help also...

author: mg.glodek@gmail.com
author_rank: Newbie
timestamp: March 17, 2015, 03:19:53 pm
content: It is finally working. You had right that it was a problem with kernel. DSO started after kernel test (t from boot menu) but than I had to flash with 3-rd boot option to make this change permament.Thank You very much for the support. I hope that it will never happen once again.

author: akeia
author_rank: Newbie
timestamp: April 23, 2016, 09:16:21 am
content: Quote from: akeia on April 22, 2016, 04:42:39 pmok. figured it out:1) install ubi_reader fromhttps://github.com/jrspruitt/ubi_reader2) extract root.bin nanddump backup file with "ubureader_extract_images -l root.bin"3) the resulting ubifs file "root.ubifs" is the correct format to flash4) use option 5 ("Download UBIFS image (root.ubi) to NAND flash") in u-boot on hantek5) restart scope... boom ... scope works again

author: tamagotono
author_rank: Newbie
timestamp: July 03, 2016, 11:19:59 pm
content: Can anyone point me to a walkthrough for recovering this oscope via JTAG?I had a bad update, which got fixed. Since I was all set up, I decided to poke around a bit and messed up the system again. No problem, I have all the tools ready to go...Here's the stupid part... I was flashing the partitions back, via the bootloader and somehow hit "A"(which is for uploading a program to the full chip) instead of "7"(for uploading the recovery partition). Unfortunately, I didn't notice this error until after I sent the recovery image. This is a very bad thing...So, now I get no output from the serial port, no backlight, and all of the buttons light up. I have a backup of my system, but I am not sure how to proceed with recovering via JTAG.Luckily, I have been wanting to learn about JTAG for awhile, so have a few programmers on hand and understand the very basics, but not much more. I went ahead and soldered in a set of header pins on J901 (which I believe is the JTAG port). I have tried talking to the board with openocd, but with no luck. I am getting the following error message:Code:Open On-Chip Debugger 0.9.0 (2015-09-02-10:42)Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmlInfo : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.RCLK - adaptiveopenocd.cfg:4: Error: invalid command name "board"in procedure 'script'at file "embedded:startup.tcl", line 60at file "openocd.cfg", line 4Info : J-Link ARM V8 compiled Sep 2 2011 17:54:36Info : J-Link caps 0xb9ff7bbfInfo : J-Link hw version 80000Info : J-Link hw type J-LinkInfo : J-Link max mem block 9528Info : J-Link configurationInfo : USB-Address: 0x0Info : Kickstart power on JTAG-pin 19: 0xffffffffInfo : Vref = 3.267 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 1 TRST = 1Info : J-Link JTAG Interface readyError: jlink_tap_execute failed, result 1 (adaptive clocking timeout)Info : RCLK (adaptive clock speed)Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!!Error: jlink_tap_execute failed, result 1 (adaptive clocking timeout)Error: jlink_tap_execute failed, result 1 (adaptive clocking timeout)embedded:startup.tcl:21: Error:in procedure 'init'in procedure 'ocd_bouncer'in procedure 'jtag_init' called at file "core.c", line 1583in procedure 'init_reset' called at file "embedded:startup.tcl", line 74in procedure 'jtag' called at file "embedded:startup.tcl", line 91in procedure 'ocd_bouncer'at file "embedded:startup.tcl", line 21embedded:startup.tcl:21: Error:in procedure 'jtag_init' called at file "core.c", line 1583in procedure 'init_reset' called at file "embedded:startup.tcl", line 74in procedure 'jtag' called at file "embedded:startup.tcl", line 91in procedure 'ocd_bouncer'at file "embedded:startup.tcl", line 21Anyone have suggestions on what I am doing wrong or links to a walk-through?

author: Rogerm
author_rank: Newbie
timestamp: November 06, 2017, 09:41:50 pm
content: Hello:You have got the flash file for the dso-1062d?.

author: hasjon
author_rank: Newbie
timestamp: January 16, 2018, 01:19:51 pm
content: Hi AllI have been reading this post and I'm hoping that someone could help.Please see the attached pictures.I have successfully made serial connection with my Hantek DSO5102P, via USB to serial and the direct USB connection. Attempted to reflash. However after the reflash, the oscilloscope hangs after the reboot. Upon power up, the Hantek logo displays and after that nothing happens.Please see the attached screens shots from 'EmbedSkyDownLoadTool_V1.0'' and the terminal Running Information after transferring the file 'wh5 root_dso5102p3.ubi'.I believe I may have the wrong .ubi file. I may have a partition error and thus would also require a working backup from another DSO5102P. Please can someone provide a backup and help to convert to the correct .ubi file so that I can attempt a successful firmware reflash.Thank you

author: krisfromhell
author_rank: Newbie
timestamp: June 21, 2018, 07:47:59 am
content: hiist it possible to get the dump file for the "voltcraft dso 1062d" too. i need to restore it

author: R4T
author_rank: Newbie
timestamp: February 22, 2020, 07:26:38 pm
content: mg.glodek I am also trying to repair a DSO-1062D (that has never worked) and I suspect I have a very similar problem to the one you had - it hangs in a slightly different place but with a similar message. Please may I have access to the kernel dump that you used? Thanks! Richard