Author Topic: Hantek MSO5074FG Firmware Upgrade Problem - *** Warning - bad CRC or NAND, using  (Read 18713 times)

0 Members and 1 Guest are viewing this topic.

Offline dtomazini

  • Contributor
  • Posts: 19
  • Country: br
and the log after the second reboot:

Code: [Select]
OM*** Warning - bad CRC, using default environment


 ##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; Press Space key to Download Mode.!

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
**************************normal start*******************************

NAND erase: device 0 offset 0x380000, size 0x80000
Erasing at 0x3e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x380000, size 0x800
Writing data at 0x380800 -- 100% complete.
 2048 bytes written: OK

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
Saving Environment to NAND...
Erasing Nand...
Warning: Erase size 0x00004000 smaller than one erase block 0x00020000
         Erasing 0x00020000 instead
Erasing at 0x80000 -- 100% complete.
Writing to Nand... done

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

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (liuqian@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009                                                                                                                               q1-176) ) #115 PREEMPT Mon Nov 10 10:24:50 CST 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=5 root=ubi0:rootfs rootfstype=ubifs init=/                                                                                                                               linuxrc console=ttySAC0 lcd=X480Y272
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59288k/59288k available, 6248k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc4800000 - 0xf6000000   ( 792 MB)
    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 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=1
NR_IRQS:107
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bi                                                                                                                               t)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 421 at 0x0000034a0000
Creating 8 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000004e00000 : "rootfs"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       302
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            70 MiB
UBI: number of good PEBs:        559
UBI: number of bad PEBs:         1
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 559
UBI: number of PEBs reserved for bad PEB handling: 5
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 330
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2009-01-01 00:11:52 UTC (1230768712)
UBIFS: recovery needed
UBIFS: recovery completed
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: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 132K
dso-iobank: install ok
0x505
gpio_major_n = 5, io_minor_n = 5, output 0
0x603
gpio_major_n = 6, io_minor_n = 3, output 0
0x309
gpio_major_n = 3, io_minor_n = 9, output 0
0x70a
gpio_major_n = 7, io_minor_n = 10, output 0
dso5000b fpga configure init
FPGA0_nCONFIG  set config = -15
FPGA0_nSTATUS  set config = -16
FPGA0_CONF_DONE  set config = -16
FPGA0_nCONFIG  set pull = 2
FPGA0_nSTATUS  set pull = 2
FPGA1_nCONFIG  set config = -15
FPGA1_nSTATUS  set config = -16
FPGA1_CONF_DONE  set config = -14
FPGA1_nCONFIG  set pull = 2
FPGA1_nSTATUS  set pull = 2
fpga0:status: 0x0
FPGA0 CONFIGURE DATA DOWN finish.
FPGA0 CONFIGURE Ok.
fpga1:status: 0x1
FPGA1 CONFIGURE DATA DOWN finish.
FPGA1 CONFIGURE Ok.
0x8090
0x1
fpga bank 11811dso-fpga: install ok
0x8090
0x1
fpga bank 11811dso-fpga-la: install ok
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: 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=26
pllset[0].data=0xc000
pllset[1].data=0xc001
pllset[2].data=0xc002
pllset[3].data=0xc003
pllset[4].data=0xc104
pllset[5].data=0xc105
pllset[6].data=0xc006
pllset[7].data=0xc107
pllset[8].data=0xc108
pllset[9].data=0xc009
pllset[10].data=0xc00a
pllset[11].data=0xc00b
pllset[12].data=0xc00c
pllset[13].data=0xc00d
pllset[14].data=0xc00e
pllset[15].data=0xc00f
pllset[16].data=0xc010
pllset[17].data=0xc111
pllset[18].data=0xc112
pllset[19].data=0xc013
pllset[20].data=0xc014
pllset[21].data=0xc015
pllset[22].data=0xc016
pllset[23].data=0xc017
pllset[24].data=0xc018
pllset[25].data=0xc019
pllset[26].data=0xc01a
pllset[27].data=0xc01b
pllset[28].data=0xc01c
pllset[29].data=0xc01d
pllset[30].data=0xc01e
pllset[31].data=0xc01f
pllset[32].data=0xc020
pllset[33].data=0xc021
pllset[34].data=0xc022
pllset[35].data=0xc023
pllset[36].data=0xc024
pllset[37].data=0xc025
pllset[38].data=0xc026
pllset[39].data=0xc027
pllset[40].data=0xc028
pllset[41].data=0xc029
pllset[42].data=0xc02a
pllset[43].data=0xc12b
pllset[44].data=0xc12c
pllset[45].data=0xc02d
pllset[46].data=0xc02e
pllset[47].data=0xc02f
pllset[48].data=0xc030
pllset[49].data=0xc031
pllset[50].data=0xc032
pllset[51].data=0xc033
pllset[52].data=0xc134
pllset[53].data=0xc135
pllset[54].data=0xc036
pllset[55].data=0xc037
pllset[56].data=0xc038
pllset[57].data=0xc039
pllset[58].data=0xc03a
pllset[59].data=0xc03b
pllset[60].data=0xc03c
pllset[61].data=0xc13d
pllset[62].data=0xc13e
pllset[63].data=0xc03f
pllset[64].data=0xc040
pllset[65].data=0xc041
pllset[66].data=0xc042
pllset[67].data=0xc043
pllset[68].data=0xc044
pllset[69].data=0xc045
pllset[70].data=0xc146
pllset[71].data=0xc147
pllset[72].data=0xc048
pllset[73].data=0xc049
pllset[74].data=0xc04a
pllset[75].data=0xc04b
pllset[76].data=0xc04c
pllset[77].data=0xc04d
pllset[78].data=0xc04e
pllset[79].data=0xc14f
pllset[80].data=0xc150
pllset[81].data=0xc051
pllset[82].data=0xc052
pllset[83].data=0xc053
pllset[84].data=0xc054
pllset[85].data=0xc055
pllset[86].data=0xc056
pllset[87].data=0xc057
pllset[88].data=0xc158
pllset[89].data=0xc159
pllset[90].data=0xc05a
pllset[91].data=0xc05b
pllset[92].data=0xc05c
pllset[93].data=0xc05d
pllset[94].data=0xc05e
pllset[95].data=0xc05f
pllset[96].data=0xc060
pllset[97].data=0xc161
pllset[98].data=0xc162
pllset[99].data=0xc063
pllset[100].data=0xc064
pllset[101].data=0xc065
pllset[102].data=0xc066
pllset[103].data=0xc067
pllset[104].data=0xc068
pllset[105].data=0xc069
pllset[106].data=0xc16a
pllset[107].data=0xc16b
pllset[108].data=0xc06c
pllset[109].data=0xc06d
pllset[110].data=0xc06e
pllset[111].data=0xc06f
pllset[112].data=0xc070
pllset[113].data=0xc071
pllset[114].data=0xc072
pllset[115].data=0xc173
pllset[116].data=0xc174
pllset[117].data=0xc075
pllset[118].data=0xc076
pllset[119].data=0xc077
pllset[120].data=0xc078
pllset[121].data=0xc079
pllset[122].data=0xc07a
pllset[123].data=0xc07b
pllset[124].data=0xc17c
pllset[125].data=0xc17d
pllset[126].data=0xc17e
pllset[127].data=0xc07f
pllset[128].data=0xc080
pllset[129].data=0xc081
pllset[130].data=0xc082
pllset[131].data=0xc083
pllset[132].data=0xc084
pllset[133].data=0xc085
pllset[134].data=0xc086
pllset[135].data=0xc087
pllset[136].data=0xc088
pllset[137].data=0xc089
pllset[138].data=0xc08a
pllset[139].data=0xc08b
pllset[140].data=0xc08c
pllset[141].data=0xc08d
pllset[142].data=0xc08e
pllset[143].data=0xc08f
filename=/lib/firmware/pll_100M.mif, filenamelen=26
pllset[0].data=0xa000
pllset[1].data=0xa001
pllset[2].data=0xa002
pllset[3].data=0xa003
pllset[4].data=0xa104
pllset[5].data=0xa105
pllset[6].data=0xa006
pllset[7].data=0xa107
pllset[8].data=0xa108
pllset[9].data=0xa009
pllset[10].data=0xa00a
pllset[11].data=0xa00b
pllset[12].data=0xa00c
pllset[13].data=0xa00d
pllset[14].data=0xa00e
pllset[15].data=0xa00f
pllset[16].data=0xa010
pllset[17].data=0xa111
pllset[18].data=0xa112
pllset[19].data=0xa013
pllset[20].data=0xa014
pllset[21].data=0xa015
pllset[22].data=0xa016
pllset[23].data=0xa017
pllset[24].data=0xa018
pllset[25].data=0xa019
pllset[26].data=0xa01a
pllset[27].data=0xa01b
pllset[28].data=0xa01c
pllset[29].data=0xa01d
pllset[30].data=0xa01e
pllset[31].data=0xa01f
pllset[32].data=0xa020
pllset[33].data=0xa021
pllset[34].data=0xa022
pllset[35].data=0xa023
pllset[36].data=0xa024
pllset[37].data=0xa025
pllset[38].data=0xa026
pllset[39].data=0xa027
pllset[40].data=0xa028
pllset[41].data=0xa029
pllset[42].data=0xa02a
pllset[43].data=0xa12b
pllset[44].data=0xa12c
pllset[45].data=0xa02d
pllset[46].data=0xa02e
pllset[47].data=0xa02f
pllset[48].data=0xa030
pllset[49].data=0xa031
pllset[50].data=0xa032
pllset[51].data=0xa033
pllset[52].data=0xa134
pllset[53].data=0xa135
pllset[54].data=0xa036
pllset[55].data=0xa037
pllset[56].data=0xa038
pllset[57].data=0xa039
pllset[58].data=0xa03a
pllset[59].data=0xa03b
pllset[60].data=0xa03c
pllset[61].data=0xa13d
pllset[62].data=0xa13e
pllset[63].data=0xa03f
pllset[64].data=0xa040
pllset[65].data=0xa041
pllset[66].data=0xa042
pllset[67].data=0xa043
pllset[68].data=0xa044
pllset[69].data=0xa045
pllset[70].data=0xa146
pllset[71].data=0xa147
pllset[72].data=0xa048
pllset[73].data=0xa049
pllset[74].data=0xa04a
pllset[75].data=0xa04b
pllset[76].data=0xa04c
pllset[77].data=0xa04d
pllset[78].data=0xa04e
pllset[79].data=0xa14f
pllset[80].data=0xa150
pllset[81].data=0xa051
pllset[82].data=0xa052
pllset[83].data=0xa053
pllset[84].data=0xa054
pllset[85].data=0xa055
pllset[86].data=0xa056
pllset[87].data=0xa057
pllset[88].data=0xa158
pllset[89].data=0xa159
pllset[90].data=0xa05a
pllset[91].data=0xa05b
pllset[92].data=0xa05c
pllset[93].data=0xa05d
pllset[94].data=0xa05e
pllset[95].data=0xa05f
pllset[96].data=0xa060
pllset[97].data=0xa161
pllset[98].data=0xa162
pllset[99].data=0xa063
pllset[100].data=0xa064
pllset[101].data=0xa065
pllset[102].data=0xa066
pllset[103].data=0xa067
pllset[104].data=0xa068
pllset[105].data=0xa069
pllset[106].data=0xa16a
pllset[107].data=0xa16b
pllset[108].data=0xa06c
pllset[109].data=0xa06d
pllset[110].data=0xa06e
pllset[111].data=0xa06f
pllset[112].data=0xa070
pllset[113].data=0xa071
pllset[114].data=0xa072
pllset[115].data=0xa173
pllset[116].data=0xa174
pllset[117].data=0xa075
pllset[118].data=0xa076
pllset[119].data=0xa077
pllset[120].data=0xa078
pllset[121].data=0xa079
pllset[122].data=0xa07a
pllset[123].data=0xa07b
pllset[124].data=0xa17c
pllset[125].data=0xa17d
pllset[126].data=0xa17e
pllset[127].data=0xa07f
pllset[128].data=0xa080
pllset[129].data=0xa081
pllset[130].data=0xa082
pllset[131].data=0xa083
pllset[132].data=0xa084
pllset[133].data=0xa085
pllset[134].data=0xa086
pllset[135].data=0xa087
pllset[136].data=0xa088
pllset[137].data=0xa089
pllset[138].data=0xa08a
pllset[139].data=0xa08b
pllset[140].data=0xa08c
pllset[141].data=0xa08d
pllset[142].data=0xa08e
pllset[143].data=0xa08f

Erasing 128 Kibyte @ 80000 - 100% complete..
mkdir: can't create directory '/param': File exists
mkdir: can't create directory '/param/sav': File exists
mkdir: can't create directory '/param': File exists
mkdir: can't create directory '/param/sav': File exists

p_pth->pthid[PTH_ID_SCAN_KEYBOARD]=1191261328
p_pth->pthid[PTH_ID_DISP_WAVE]=1182286992
p_pth->pthid[PTH_ID_ACQ]=1199649936
p_pth->pthid[PTH_ID_PC_UART]=1208808592

mount: mounting 192.168.1.22:/home/nfsroot on /mnt/nfs failed: No route to host

Humm i forgot to do the self calibration !!!
« Last Edit: February 04, 2015, 10:43:00 am by dtomazini »
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
Re: Hantek MSO5074FG Firmware Upgrade Problem - From Brick to Restore !!!
« Reply #26 on: February 04, 2015, 10:48:19 am »

Everything done !!, the oscilloscope is now working !!!.  :clap: :clap:

Awsome job fremen67 !!. Thanks a lot to You, Lauris and KL27x !!.

Hehe you are coming back from very far  ;)
Without Lauris' backup it would have been impossible to help you.
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
and the log after the second reboot:

Code: [Select]
OM*** Warning - bad CRC, using default environment


 ##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; Press Space key to Download Mode.!

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
**************************normal start*******************************

NAND erase: device 0 offset 0x380000, size 0x80000
Erasing at 0x3e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x380000, size 0x800
Writing data at 0x380800 -- 100% complete.
 2048 bytes written: OK

NAND read: device 0 offset 0x380000, size 0x800
 2048 bytes read: OK
Saving Environment to NAND...
Erasing Nand...
Warning: Erase size 0x00004000 smaller than one erase block 0x00020000
         Erasing 0x00020000 instead
Erasing at 0x80000 -- 100% complete.
Writing to Nand... done

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

Starting kernel ...

What 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: [Select]
int fs_test()
{
// printf("**************************111*******************************\n");
char flag = 1;
char cmdBuf[100];

run_command("nand read 0xc0008000 misc 1", 0);
strncpy(&flag, 0xc0008000, 1);
//printf("read flag is : %d\n", flag);
// printf("**************************222*******************************\n");
 #if 1
if (flag)
{
printf("**************************normal start*******************************\n");
 #if 1
run_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_APART
sprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=5 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");
 #else
sprintf(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_APART
sprintf(cmdBuf, "setenv bootargs noinitrd ubi.mtd=8 root=ubi0:recover rootfstype=ubifs init=/linuxrc console=ttySAC0;saveenv");
 #else
sprintf(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);
}
 #endif

printf("***************************start error!!!*********************************\n");

return 0;
}
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline Lauris

  • Contributor
  • Posts: 10
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
 

Offline dtomazini

  • Contributor
  • Posts: 19
  • Country: br
Code: [Select]
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: [Select]
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
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
 :)
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
Well, 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.
« Last Edit: February 05, 2015, 11:25:21 am by fremen67 »
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
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.
You 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.

Is there a way to make this backup, and leave it on the right partition ?.
Yes, 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  ;)
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline dtomazini

  • Contributor
  • Posts: 19
  • Country: br
That is right !!  :D
 

Offline mg.glodek@gmail.com

  • Contributor
  • Posts: 8
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: [Select]
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...

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

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@cjh-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #31 PREEMPT Tue Jul 16 16:02:21 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59024k/59024k available, 6512k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc4800000 - 0xf6000000   ( 792 MB)
    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc03e9000   (3972 kB)
      .init : 0xc03e9000 - 0xc0409000   ( 128 kB)
      .data : 0xc040a000 - 0xc05a2680   (1634 kB)
       .bss : 0xc05a26a4 - 0xc05bf97c   ( 117 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:99
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c24xx_i2c_probe
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 65 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c-fb s3c-fb: window 1: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 39 at 0x0000004e0000
Bad eraseblock 814 at 0x0000065c0000
Bad eraseblock 833 at 0x000006820000
Bad eraseblock 924 at 0x000007380000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       764
UBI: attached mtd3 to ubi0
UBI: MTD device name:            "ROOTFS"
UBI: MTD device size:            121 MiB
UBI: number of good PEBs:        965
UBI: number of bad PEBs:         3
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 965
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 3/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 306
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-07 10:38:25 UTC (947241505)
UBIFS: recovery needed
Internal error: Oops - undefined instruction: 0 [#1] PREEMPT
Modules linked in:
CPU: 0    Not tainted  (3.2.35 #31)
PC is at ubifs_wbuf_sync_nolock+0x58/0x180
LR is at do_commit+0xa0/0x7b4
pc : [<c0133740>]    lr : [<c013b5a8>]    psr: 60000013
sp : c381fc70  ip : c381fca0  fp : c381fc9c
r10: c3b68000  r9 : c3b68000  r8 : 00000000
r7 : 00000002  r6 : c3b68000  r5 : c38ee2c0  r4 : c38ee298
r3 : 00000000  r2 : 00000001  r1 : 00000000  r0 : c38ee2e0
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 0005317f  Table: 30004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc381e270)
Stack: (0xc381fc70 to 0xc3820000)
fc60:                                     c381e000 00000001 c3b68184 c38ee298
fc80: c38ee2c0 00000098 00000002 00000000 c381fd1c c381fca0 c013b5a8 c01336f8
fca0: 00000000 c0018a60 c381fccc c381fcb8 c381fcdc c381fcc0 c000c7b4 c000b4e8
fcc0: c381e000 00000001 c3b68184 00000000 c381fd04 c381fce0 c000b544 c000c7a0
fce0: c381fd3c c381fd20 c0018a60 c013bd6c 00000000 c0018a60 c381e000 c3b68000
fd00: c3b68184 00000000 00000000 c38ee600 c381fd3c c381fd20 c013bd84 c013b518
fd20: 00000000 0000013a c3b68000 00000000 c381fd6c c381fd40 c0145354 c013bccc
fd40: 00000000 00000020 00000000 c0174ac4 000066c3 c3b68000 00000000 c38ee200
fd60: c381fdac c381fd70 c01453bc c01452f8 00000000 00000000 c381fdac 00000000
fd80: 0001ef3f 05308578 00000000 00000000 00000000 00001800 00000000 00000000
fda0: c381fe34 c381fdb0 c0130498 c0145368 c3b68790 c3804684 c3804680 0000000a
fdc0: c381fdec c381fdd0 c000c7b4 00800000 0001f000 00000000 00000000 00008000
fde0: c041b368 c38ec440 c3b687d4 c3b68008 0001f000 00000000 0000000c 00000000
fe00: c3810640 c38ec6c5 c38ec840 c38ec6c0 c3810640 c041b368 c041b368 00000000
fe20: c381fec8 00008000 c381fe5c c381fe38 c0082b9c c012f288 c38ec6c0 00008000
fe40: c041b368 c38ec6c0 c3810640 00008000 c381fe84 c381fe60 c009fb10 c0082b90
fe60: 00008000 c38ec6c0 00000000 c38ec6e0 c041b368 c381fec8 c381feac c381fe88
fe80: c009fba8 c009fac8 00000000 00008000 c38ec6c0 c38ec6e0 00000020 c381fec8
fea0: c381fefc c381feb0 c009fd8c c009fb7c 0000000c 00000000 c381fee4 c381fec8
fec0: c0067c64 c0067b70 c38100a0 c3401280 c0403584 00000000 c380f000 c0403584
fee0: 00008000 c0403584 c040c108 c0403578 c381ff34 c381ff00 c00a0414 c009fc50
ff00: 00000000 00000000 00000000 00000000 c38ec6c0 c38ec6e0 c380c000 c380c000
ff20: 00008000 00000013 c381ff5c c381ff38 c03e9ad4 c00a0384 00000000 c0403584
ff40: c0403578 c380c000 c380c000 00008000 c381ffac c381ff60 c03e9c00 c03e9abc
ff60: c381ff7c c381ff70 c0040fb4 c0040dd8 c381ffac c381ff80 c01a6a34 c0040fa8
ff80: c0040238 c0403584 c0403578 c04087cc 00000013 00000000 00000000 00000000
ffa0: c381ffd4 c381ffb0 c03e9f28 c03e9b80 00000000 00000000 c381ffd4 c04087cc
ffc0: c040848c c04087cc c381fff4 c381ffd8 c03e9304 c03e9eb8 00000000 c03e9204
ffe0: c0021e38 00000013 00000000 c381fff8 c0021e38 c03e9214 fff3f7bf effe5ff7
Backtrace:
[<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:c38ec6c0
r4:00008000
[<c009fb6c>] (do_kern_mount+0x0/0xd4) from [<c009fd8c>] (do_mount+0x14c/0x734)
 r9:c381fec8 r8:00000020 r7:c38ec6e0 r6:c38ec6c0 r5:00008000
r4: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:00000000
Code: 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
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
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: [Select]
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...

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

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@cjh-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #31 PREEMPT Tue Jul 16 16:02:21 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59024k/59024k available, 6512k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc4800000 - 0xf6000000   ( 792 MB)
    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc03e9000   (3972 kB)
      .init : 0xc03e9000 - 0xc0409000   ( 128 kB)
      .data : 0xc040a000 - 0xc05a2680   (1634 kB)
       .bss : 0xc05a26a4 - 0xc05bf97c   ( 117 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:99
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c24xx_i2c_probe
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 65 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c-fb s3c-fb: window 1: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 39 at 0x0000004e0000
Bad eraseblock 814 at 0x0000065c0000
Bad eraseblock 833 at 0x000006820000
Bad eraseblock 924 at 0x000007380000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       764
UBI: attached mtd3 to ubi0
UBI: MTD device name:            "ROOTFS"
UBI: MTD device size:            121 MiB
UBI: number of good PEBs:        965
UBI: number of bad PEBs:         3
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 965
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 3/1
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 306
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-07 10:38:25 UTC (947241505)
UBIFS: recovery needed
Internal error: Oops - undefined instruction: 0 [#1] PREEMPT
Modules linked in:
CPU: 0    Not tainted  (3.2.35 #31)
PC is at ubifs_wbuf_sync_nolock+0x58/0x180
LR is at do_commit+0xa0/0x7b4
pc : [<c0133740>]    lr : [<c013b5a8>]    psr: 60000013
sp : c381fc70  ip : c381fca0  fp : c381fc9c
r10: c3b68000  r9 : c3b68000  r8 : 00000000
r7 : 00000002  r6 : c3b68000  r5 : c38ee2c0  r4 : c38ee298
r3 : 00000000  r2 : 00000001  r1 : 00000000  r0 : c38ee2e0
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 0005317f  Table: 30004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc381e270)
Stack: (0xc381fc70 to 0xc3820000)
fc60:                                     c381e000 00000001 c3b68184 c38ee298
fc80: c38ee2c0 00000098 00000002 00000000 c381fd1c c381fca0 c013b5a8 c01336f8
fca0: 00000000 c0018a60 c381fccc c381fcb8 c381fcdc c381fcc0 c000c7b4 c000b4e8
fcc0: c381e000 00000001 c3b68184 00000000 c381fd04 c381fce0 c000b544 c000c7a0
fce0: c381fd3c c381fd20 c0018a60 c013bd6c 00000000 c0018a60 c381e000 c3b68000
fd00: c3b68184 00000000 00000000 c38ee600 c381fd3c c381fd20 c013bd84 c013b518
fd20: 00000000 0000013a c3b68000 00000000 c381fd6c c381fd40 c0145354 c013bccc
fd40: 00000000 00000020 00000000 c0174ac4 000066c3 c3b68000 00000000 c38ee200
fd60: c381fdac c381fd70 c01453bc c01452f8 00000000 00000000 c381fdac 00000000
fd80: 0001ef3f 05308578 00000000 00000000 00000000 00001800 00000000 00000000
fda0: c381fe34 c381fdb0 c0130498 c0145368 c3b68790 c3804684 c3804680 0000000a
fdc0: c381fdec c381fdd0 c000c7b4 00800000 0001f000 00000000 00000000 00008000
fde0: c041b368 c38ec440 c3b687d4 c3b68008 0001f000 00000000 0000000c 00000000
fe00: c3810640 c38ec6c5 c38ec840 c38ec6c0 c3810640 c041b368 c041b368 00000000
fe20: c381fec8 00008000 c381fe5c c381fe38 c0082b9c c012f288 c38ec6c0 00008000
fe40: c041b368 c38ec6c0 c3810640 00008000 c381fe84 c381fe60 c009fb10 c0082b90
fe60: 00008000 c38ec6c0 00000000 c38ec6e0 c041b368 c381fec8 c381feac c381fe88
fe80: c009fba8 c009fac8 00000000 00008000 c38ec6c0 c38ec6e0 00000020 c381fec8
fea0: c381fefc c381feb0 c009fd8c c009fb7c 0000000c 00000000 c381fee4 c381fec8
fec0: c0067c64 c0067b70 c38100a0 c3401280 c0403584 00000000 c380f000 c0403584
fee0: 00008000 c0403584 c040c108 c0403578 c381ff34 c381ff00 c00a0414 c009fc50
ff00: 00000000 00000000 00000000 00000000 c38ec6c0 c38ec6e0 c380c000 c380c000
ff20: 00008000 00000013 c381ff5c c381ff38 c03e9ad4 c00a0384 00000000 c0403584
ff40: c0403578 c380c000 c380c000 00008000 c381ffac c381ff60 c03e9c00 c03e9abc
ff60: c381ff7c c381ff70 c0040fb4 c0040dd8 c381ffac c381ff80 c01a6a34 c0040fa8
ff80: c0040238 c0403584 c0403578 c04087cc 00000013 00000000 00000000 00000000
ffa0: c381ffd4 c381ffb0 c03e9f28 c03e9b80 00000000 00000000 c381ffd4 c04087cc
ffc0: c040848c c04087cc c381fff4 c381ffd8 c03e9304 c03e9eb8 00000000 c03e9204
ffe0: c0021e38 00000013 00000000 c381fff8 c0021e38 c03e9214 fff3f7bf effe5ff7
Backtrace:
[<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:c38ec6c0
r4:00008000
[<c009fb6c>] (do_kern_mount+0x0/0xd4) from [<c009fd8c>] (do_mount+0x14c/0x734)
 r9:c381fec8 r8:00000020 r7:c38ec6e0 r6:c38ec6c0 r5:00008000
r4: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:00000000
Code: 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
You 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 ...?
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline mg.glodek@gmail.com

  • Contributor
  • Posts: 8
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 the http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D site? 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)?
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
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 the http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D site? 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)?
You 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/#msg451021
and the next post here for Win7x64:
https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let%27s-see!/msg451081/#msg451081
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline mg.glodek@gmail.com

  • Contributor
  • Posts: 8
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
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
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
This 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.
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline mg.glodek@gmail.com

  • Contributor
  • Posts: 8
Quote
This 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.

As 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.
 

Offline fremen67

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: fr
Quote
This 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.

As 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.
1 - 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 USB
3 - choose "t" option (test linux image)
4 - install drivers on your PC
5 - 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...
I'm a machine! And I can know much more! I can experience so much more. But I'm trapped in this absurd body!
 

Offline mg.glodek@gmail.com

  • Contributor
  • Posts: 8
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.
 

Offline akeia

  • Newbie
  • Posts: 2
  • Country: de
I have accidentally overwritten my root partition and need to flash a backup dump. But is has the wrong format.

How is it possible to transform a dump file (root.bin) into a flashable root.ubi?

ok. figured it out:

1) install ubi_reader from https://github.com/jrspruitt/ubi_reader
2) 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 flash
4) use option 5 ("Download UBIFS image (root.ubi) to NAND flash") in u-boot on hantek
5) restart scope

... boom ... scope works again
 

Offline tamagotono

  • Newbie
  • Posts: 2
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: [Select]
Open On-Chip Debugger 0.9.0 (2015-09-02-10:42)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
RCLK - adaptive
openocd.cfg:4: Error: invalid command name "board"
in procedure 'script'
at file "embedded:startup.tcl", line 60
at file "openocd.cfg", line 4
Info : J-Link ARM V8 compiled Sep  2 2011 17:54:36
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 80000
Info : J-Link hw type J-Link
Info : J-Link max mem block 9528
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0xffffffff
Info : Vref = 3.267 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 1 TRST = 1
Info : J-Link JTAG Interface ready
Error: 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 1583
in procedure 'init_reset' called at file "embedded:startup.tcl", line 74
in procedure 'jtag' called at file "embedded:startup.tcl", line 91
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
embedded:startup.tcl:21: Error:
in procedure 'jtag_init' called at file "core.c", line 1583
in procedure 'init_reset' called at file "embedded:startup.tcl", line 74
in procedure 'jtag' called at file "embedded:startup.tcl", line 91
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21

Anyone have suggestions on what I am doing wrong or links to a walk-through?
 

Offline Rogerm

  • Newbie
  • Posts: 3
  • Country: es
Hello:
You have got the flash file for the dso-1062d?.
« Last Edit: November 07, 2017, 12:32:43 pm by Rogerm »
 

Offline hasjon

  • Contributor
  • Posts: 5
  • Country: th
Hi All

I 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
 

Offline krisfromhell

  • Newbie
  • Posts: 2
  • Country: de
hi ;)

ist it possible to get the dump file for the "voltcraft dso 1062d" too. i need to restore it
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf