Author Topic: Hantek DSO1152S - Wont boot after firmware update  (Read 19240 times)

0 Members and 1 Guest are viewing this topic.

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #25 on: July 13, 2014, 09:31:41 pm »
Here is the output after doing a reboot command from the UART terminal.

Quote
[root@Hantek /]# reboot
save exit: isCheckpointed 0
umount: tmpfs busy - remounted read-only
The system is going down NOW!
s3c2410-wdt s3c2410-wdt: Unexpected close, not stopping watchdog
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
s3c2440-sdi s3c2440-sdi: powered down.
*** Warning - bad CRC or NAND, using default environment



##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #125 Sat Jun 30 17:13:48 CST 2012
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
NR_IRQS:85
irq: clearing pending ext status 00000300
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttySAC0] enabled
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: 61260KB available (3160K code, 346K data, 100K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 296 bytes
NET: Registered protocol family 16
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
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
cfg80211: Calling CRDA to update world regulatory domain
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
yaffs Jun 30 2012 14:45:29 Installing.
msgmni has been set to 119
alg: No test for stdrng (krng)
io scheduler noop registered (default)
backlight initialized
s3c2440-uart.0: tq2440_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2440-uart.1: tq2440_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: tq2440_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand s3c2440-nand: Tacls=2, 20ns Twrph0=3 30ns, Twrph1=2 20ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"
0x000000400000-0x000003ff8000 : "EmbedSky_Board_yaffs2"
0x000000100000-0x000000200000 : "EmbedSky_Board_logo"
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
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
Linux video capture interface: v2.00
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: starting watchdog timer
s3c2410-wdt s3c2410-wdt: watchdog active, reset abled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
s3c2440-sdi s3c2440-sdi: powered down.
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
__init s3c24xxfb_probe
=======================================
map_video_memory(fbi=c3af0a3c) map_size 614400
map_video_memory: clear ffc42000:00096000
map_video_memory: dma=33100000 cpu=ffc42000 size=00096000
setting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
Console: switching to mono frame buffer device 80x30
fb0: s3c2410fb frame buffer device
hwclock: settimeofday: Invalid argument
bwscon:0x2201d110
fpga bank 221422
dso-fpga: install ok
dso-spi initialized
Init spi success!
New Log Write OK Length:21
s3c2440_clkcon=00FE7FF0
fpga download file_name :dn.rbf
copy-from-user ok
dn_file_name:dn.rbf
fpga_down_load file name : dn.rbf.
data DOWN finish.
dso-spi:FPGA_DOWNLOAD ok.
release
var.xres=640
var.yres=480
var.bits_per_pixel=16
var.xres_virtual=640
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_start=856686592
fix.smem_len=614400
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fix.ywrapstep=0
fix.line_length=1280
argv[1]=16
var.xres=640    var.yres=480    var.bits_per_pixel=16
show logo,video_buf_size = 614400
dm9000 Ethernet Driver, V1.31
Now use the default MAC address: 10:23:45:67:89:ab
eth0 (dm9000): not using net_device_ops yet
eth0: dm9000e at c49b8300,c49bc304 IRQ 53 MAC: 10:23:45:67:89:ab (EmbedSky)
Try to bring eth0 interface up ...
Hantek GPIO(buzzer/speaker),(c)20110309
Hantek-gpio initialized
speaker on
Beep
dso-buzzer initialized
ifconfig eth0 hw ether 10:23:45:67:89:ab
eth0: link down
ifconfig eth0 192.168.1.55 netmask 255.255.255.0 up
/sbin/net_set: line 5: route: not found
add default gw 192.168.1.2
Done
i2c /dev entries driver
s3c2440-i2c s3c2440-i2c: slave address 0x10
pdata->frequency=6000
s3c2440-i2c s3c2440-i2c: bus frequency set to 9 KHz
s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
s3c2410_udc: debugfs dir creation failed -19
s3c2440-usbgadget s3c2440-usbgadget: S3C2440: increasing FIFO to 128 bytes
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
lcd_init
dso-lcd1 initialized
tq2440_ts: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
TQ2440 TouchScreen successfully loaded
input: TQ2440 TouchScreen as /devices/virtual/input/input0
Power-Ctrl initialized
no update file to foud
now run app .....
var.xres=640
var.yres=480
var.bits_per_pixel=16
var.xres_virtual=640
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_stsetting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
art=856686592
fix.smem_len=614400
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fix.ywrapstep=0
fix.line_length=1280
argv[1]=8
var.xres=640    var.yres=480    var.bits_per_pixel=8

Please press Enter to activate this console. setting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1

[root@Hantek /]# killall dsod
[root@Hantek /]# killall dsod
killall: dsod: no process killed
[root@Hantek /]# ls
OurLanguages      fpgabank.conf     lost+found        sys.inf
bin               help.db           mnt               tdc.log
chk_base_volt     home              msg               tdc_edge125M
cur_acq.type      i2c.log           mult_adc.log      tdc_overtime125M
dev               icon              opt               tdc_pulse125M
disk_sta.info     keyprotocol.inf   param             tmp
disp              language.img      proc              tmpdst
dn.rbf            lib               protocol.inf      usr
dso               linuxrc           root              var
dso.exe           logo              sbin
dst1202b          logotype          sendspi
etc               logotype.dis      sys
[root@Hantek /]#
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #26 on: July 13, 2014, 09:36:53 pm »
Note quite sure about these dates, as I dont know if the scope knows dates unless on a LAN...?

But some more info:

Quote
[root@Hantek /]# ls -l
total 6549
drwxr-xr-x    1 root     root           512 Jul 13  2014 OurLanguages
drwxr-xr-x    1 root     root           512 Jul  4  2012 bin
-rw-r--r--    1 root     root           275 Jan  1  2009 chk_base_volt
-rw-r--r--    1 root     root             4 Jan  1 00:00 cur_acq.type
drwxrwxrwt    7 root     root          2800 Jan  1 00:00 dev
-rw-r--r--    1 root     root           247 Jul 13  2014 disk_sta.info
-rwxr-xr-x    1 root     root        622551 Aug 24  2012 disp
-rwxrw-rw-    1 root     root        143305 Jul 16  2012 dn.rbf
drwxr-xr-x    1 root     root           512 Jul  4  2012 dso
-rwxrwxrwx    1 root     root       4948860 Jan  1  2009 dso.exe
-rw-r--r--    1 root     root             0 Jan  1  2009 dst1202b
drwxr-xr-x    1 root     root           512 Jul  4  2012 etc
-rw-r--r--    1 root     root             6 Jul  4  2012 fpgabank.conf
-rw-r--r--    1 root     root             0 Jan  1 00:01 frequency=6000
-rw-r--r--    1 1000     root        900096 Jul  2  2013 help.db
drwxr-xr-x    1 root     root           512 Jul  4  2012 home
-rw-r--r--    1 root     root          8192 Jan  1  2009 i2c.log
drwxr-xr-x    1 root     root           512 Jul 13  2014 icon
-rw-r--r--    1 root     root           873 Jul  4  2012 keyprotocol.inf
-rw-r--r--    1 root     root            13 Jan  1  2009 language.img
drwxr-xr-x    1 root     root           512 Jul 13  2014 lib
lrwxrwxrwx    1 root     root            11 Jul  4  2012 linuxrc -> bin/busybox
drwxr-xr-x    1 root     root           512 Jul  4  2012 logo
-rw-r--r--    1 root     root             8 Jan  1 00:00 logotype
-rwxr-xr-x    1 root     root            16 Oct 11  2012 logotype.dis
drwx------    1 root     root           512 Jan  1 00:00 lost+found
drwxr-xr-x    1 root     root           512 Jul  4  2012 mnt
-rw-r--r--    1 root     root             0 Jan  1  2009 msg
-rw-r--r--    1 root     root         50122 Jan  1  2009 mult_adc.log
drwxr-xr-x    1 root     root           512 Jul  4  2012 opt
drwxr-xr-x    1 root     root           512 Jan  1 00:00 param
dr-xr-xr-x   33 root     root             0 Jan  1 00:00 proc
-rw-r--r--    1 root     root          3838 Jul  4  2012 protocol.inf
drwxr-xr-x    1 root     root           512 Jul  4  2012 root
drwxr-xr-x    1 root     root           512 Jul 13  2014 sbin
-rwxrwxrwx    1 root     root          6594 Jul  4  2012 sendspi
drwxr-xr-x   11 root     root             0 Jan  1 00:00 sys
-rw-r--r--    1 root     root           104 Jan  1  2009 sys.inf
-rw-r--r--    1 root     root          2400 Jan  1  2009 tdc.log
-rw-r--r--    1 root     root          1113 Jan 14  2009 tdc_edge125M
-rw-r--r--    1 root     root          1115 Jan  1  2009 tdc_overtime125M
-rw-r--r--    1 root     root          1084 Jan 14  2009 tdc_pulse125M
drwxrwxrwt    2 root     root            80 Jan  1 00:00 tmp
-rw-r--r--    1 root     root            10 Jul 13  2014 tmpdst
drwxr-xr-x    1 root     root           512 Jan  1  2009 usr
drwxr-xr-x    1 root     root           512 Jan  1 00:00 var
[root@Hantek /]#
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #27 on: July 13, 2014, 09:44:53 pm »
Is the solution to this going to be to fix the script, and re-encode the up file and get the scope to update itself again?
or should I manually do each of the steps in the update file, but fix the dso.exe manually at the end?

Looking in the update file, it has:

Quote
[DST type]dso1000b
[soft version]2.01.1(999999.0)
[type]123
[cmd] mv /tmp/tekwayup_client/dso.exe   /dso.exe
[cmd] mv /tmp/tekwayup_client/help.db /help.db
[cmd] mv /tmp/tekwayup_client/DMM_ALERT_RANGER_CHANGE.ico /icon
[cmd] mv /tmp/tekwayup_client/brand.ico /icon
[cmd] mv /tmp/tekwayup_client/dso-buzzer.ko   /dso/driver/
[cmd] mv /tmp/tekwayup_client/dso-spi.ko   /dso/driver/
[cmd] rm /OurLanguages/*.lan
[cmd] mv /tmp/tekwayup_client/OurLanguages/*.lan /OurLanguages/
[cmd] mv /tmp/tekwayup_client/amixer   /sbin/
[cmd] rm /lib/libasound.so -r
[cmd] rm /lib/libasound.so.2 -r
[cmd] mv /tmp/tekwayup_client/libasound.so.2.0.0 /lib/
[cmd] ln -s /lib/libasound.so.2.0.0 /lib/libasound.so
[cmd] ln -s /lib/libasound.so.2.0.0 /lib/libasound.so.2
[cmd] cp /tmp/tekwayup_client/local /usr/ -rf
[cmd] chmod 777 /sbin/amixer
[cmd] chmod 777 /sbin/mplayer
[cmd] mv /tmp/tekwayup_client/libgif.so.6.0.1 /lib/
[cmd] ln -s /lib/libgif.so.6.0.1 /lib/libgif.so.6
[cmd] rm /sys.inf
[cmd] mv /tmp/tekwayup_client/sys.inf /sys.inf
[cmd] sync
[cmd] sync
[cmd] sync
[end]
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #28 on: July 13, 2014, 10:03:15 pm »
ok, i've installed handheld image, updated to their latest zimage, installed that update for S models and my dev board is now boot looping as well. Good (at least i have same shit now).

Try following:
- on the shell go to /dso/app/ directory
- rename the dsod in that dir to dsod.old (mv dsod dsod.old)
- reboot DSO
« Last Edit: July 13, 2014, 10:04:50 pm by tinhead »
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #29 on: July 13, 2014, 10:04:13 pm »
Ran the update again while monitoring the serial port, this is what resulted

(Took out the rubbish in between which padded it out, normal talk when dso.exe is running)

Quote
rm: can't remove '/tmp': Device or resource busy
mkdir: can't create directory '/tmp/': File exists
gpg: directory `/root/.gnupg' created
gpg: can't open `/work/handheld_scope/project_handheld_dso/dso_handheld_env/third_part/4.3.3/arm-none-linux-gnueabi/libc/usr/share/gnupg/options.skel': No such file or directory
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: WARNING: message was not integrity protected
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: WARNING: message was not integrity protected
dso1kb_2.01.1_.up.tar
tekwayup_client/
tekwayup_client/special
tekwayup_client/sys.inf
tekwayup_client/local/
tekwayup_client/local/share/
tekwayup_client/local/share/smixer.conf
tekwayup_client/local/share/pcm/
tekwayup_client/local/share/pcm/dsnoop.conf
tekwayup_client/local/share/pcm/center_lfe.conf
tekwayup_client/local/share/pcm/side.conf
tekwayup_client/local/share/pcm/dmix.conf
tekwayup_client/local/share/pcm/surround71.conf
tekwayup_client/local/share/pcm/surround40.conf
tekwayup_client/local/share/pcm/rear.conf
tekwayup_client/local/share/pcm/front.conf
tekwayup_client/local/share/pcm/iec958.conf
tekwayup_client/local/share/pcm/dpl.conf
tekwayup_client/local/share/pcm/surround50.conf
tekwayup_client/local/share/pcm/surround51.conf
tekwayup_client/local/share/pcm/default.conf
tekwayup_client/local/share/pcm/surround41.conf
tekwayup_client/local/share/pcm/modem.conf
tekwayup_client/local/share/pcm/hdmi.conf
tekwayup_client/local/share/cards/
tekwayup_client/local/share/cards/aliases.conf
tekwayup_client/local/share/cards/VXPocket440.conf
tekwayup_client/local/share/cards/FM801.conf
tekwayup_client/local/share/cards/CMI8338-SWIEC.conf
tekwayup_client/local/share/cards/ENS1370.conf
tekwayup_client/local/share/cards/VX222.conf
tekwayup_client/local/share/cards/VIA8233.conf
tekwayup_client/local/share/cards/VXPocket.conf
tekwayup_client/local/share/cards/ICH.conf
tekwayup_client/local/share/cards/GUS.conf
tekwayup_client/local/share/cards/Audigy.conf
tekwayup_client/local/share/cards/PS3.conf
tekwayup_client/local/share/cards/VIA686A.conf
tekwayup_client/local/share/cards/USB-Audio.conf
tekwayup_client/local/share/cards/SI7018.conf
tekwayup_client/local/share/cards/ICE1724.conf
tekwayup_client/local/share/cards/ATIIXP-MODEM.conf
tekwayup_client/local/share/cards/CMI8738-MC6.conf
tekwayup_client/local/share/cards/NFORCE.conf
tekwayup_client/local/share/cards/CA0106.conf
tekwayup_client/local/share/cards/ENS1371.conf
tekwayup_client/local/share/cards/ICH4.conf
tekwayup_client/local/share/cards/ATIIXP.conf
tekwayup_client/local/share/cards/EMU10K1.conf
tekwayup_client/local/share/cards/si7018/
tekwayup_client/local/share/cards/si7018/sndoc-mixer.alisp
tekwayup_client/local/share/cards/si7018/sndop-mixer.alisp
tekwayup_client/local/share/cards/RME9652.conf
tekwayup_client/local/share/cards/ATIIXP-SPDMA.conf
tekwayup_client/local/share/cards/CS46xx.conf
tekwayup_client/local/share/cards/CMI8338.conf
tekwayup_client/local/share/cards/ICH-MODEM.conf
tekwayup_client/local/share/cards/PC-Speaker.conf
tekwayup_client/local/share/cards/Audigy2.conf
tekwayup_client/local/share/cards/Maestro3.conf
tekwayup_client/local/share/cards/TRID4DWAVENX.conf
tekwayup_client/local/share/cards/VIA8233A.conf
tekwayup_client/local/share/cards/ES1968.conf
tekwayup_client/local/share/cards/RME9636.conf
tekwayup_client/local/share/cards/EMU10K1X.conf
tekwayup_client/local/share/cards/SB-XFi.conf
tekwayup_client/local/share/cards/PMacToonie.conf
tekwayup_client/local/share/cards/VIA8237.conf
tekwayup_client/local/share/cards/AU8820.conf
tekwayup_client/local/share/cards/Aureon51.conf
tekwayup_client/local/share/cards/AU8830.conf
tekwayup_client/local/share/cards/CMI8788.conf
tekwayup_client/local/share/cards/AACI.conf
tekwayup_client/local/share/cards/CMI8738-MC8.conf
tekwayup_client/local/share/cards/HDA-Intel.conf
tekwayup_client/local/share/cards/YMF744.conf
tekwayup_client/local/share/cards/PMac.conf
tekwayup_client/local/share/cards/aliases.alisp
tekwayup_client/local/share/cards/ICE1712.conf
tekwayup_client/local/share/cards/Aureon71.conf
tekwayup_client/local/share/cards/AU8810.conf
tekwayup_client/local/share/sndo-mixer.alisp
tekwayup_client/local/share/alsa.conf
tekwayup_client/help.db
tekwayup_client/libgif.so.6.0.1
tekwayup_client/DMM_ALERT_RANGER_CHANGE.ico
tekwayup_client/dn.rbf
tekwayup_client/dso-buzzer.ko
tekwayup_client/brand.ico
tekwayup_client/amixer
tekwayup_client/OurLanguages/
tekwayup_client/OurLanguages/English.lan
tekwayup_client/OurLanguages/Chinese.lan
tekwayup_client/OurLanguages/Tridchn.lan
tekwayup_client/dso.exe
tekwayup_client/update~
tekwayup_client/update
tekwayup_client/.sys.inf.swp
tekwayup_client/rcS~
tekwayup_client/dso-spi.ko
tekwayup_client/libasound.so.2.0.0
upend

RIGHT VERSION TO UPDATE!

rm: can't remove '/lib/libasound.so': Directory not empty
rm: can't remove '/lib/libasound.so.2': Directory not empty
ln: /lib/libasound.so: File exists
ln: /lib/libasound.so.2: File exists
ln: /lib/libgif.so.6: File exists

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

##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #125 Sat Jun 30 17:13:48 CST 2012

etc etc, as it reboots...
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #30 on: July 13, 2014, 10:06:45 pm »
ok, i've installed handheld image, updated to their latest zimage, installed that update for S models and my dev board is now boot looping as well. Good (at least i have same shit now).

Try following:
- on the shell go to /dso/app/ directory
- rename the dsod in that dir to dsod.old (mv dsod dsod.old)
- reboot DSO

Nope, sadly still not working
its not boot looping now, but its just stuck waiting to do something, it doesnt load dso.exe itself

Quote
no update file to foud
now run app .....
/etc/init.d/rcS: line 63: /dso/app/dsod: not found
« Last Edit: July 13, 2014, 10:08:58 pm by WanaGo »
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #31 on: July 13, 2014, 10:12:45 pm »
/etc/init.d/rcS: line 63: /dso/app/dsod: not found

that's ok, you renamed the dsod so there have to be an error. The next line in rcS is loading the dso.exe,which is the DSO app itself. You can check your rcS (scroll down with cursor down)

 vi /etc/init.d/rcS

to see this. There should be line

 /dso.exe


Anyway, when it is not running check the /dso.exe rights, or simply do chmod 777 * in /.
Now run the /dso.exe, do default setup, autosetup, then change e.g. timebase and wait 10sec. The dso fw should now
stored the profile. Reboot not the dso (powercycle, not reboot command) and tell my what is doing after reboot.
« Last Edit: July 13, 2014, 10:17:59 pm by tinhead »
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #32 on: July 13, 2014, 10:16:17 pm »
If I try to run /dso.exe now, I get this

Quote
> /dso.exe
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
InitLcdShowBasic:0x40b92000
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
***************************Stat_ShowBattery:0, 0
release
release
Segmentation fault

ok inside vi /etc/init.d/rcS I see this:

Quote
> vi /etc/init.d/rcS
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
runlevel=S
prevlevel=N
umask 022
export PATH runlevel prevlevel
#
#       Trap CTRL-C &c only in this shell so we can interrupt subprocesses.
#
insmod /dso/driver/cfbcopyarea.ko
insmod /dso/driver/cfbfillrect.ko
insmod /dso/driver/cfbimgblt.ko
insmod /dso/driver/s3c2410fb.ko
mount -a
mkdir -p /dev/pts
mount -t devpts devpts /dev/pts
echo /sbin/mdev > /proc/sys/kernel/hotplug
mdev -s
mkdir -p /var/lock
mkdir /dev/fb /dev/v4l
ln -s /dev/fb0 /dev/fb/0
ln -s /dev/fb0 /dev/dso-lcd
ln -s /dev/video0 /dev/v4l/video0
- /etc/init.d/rcS 1/65 1%
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #33 on: July 13, 2014, 10:18:32 pm »
check again what i wrote, i'v edited while you was typing
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #34 on: July 13, 2014, 10:20:57 pm »
What I wrote didnt seem to be complete.

I did a cat instead of vi this time:

Quote
cat /etc/init.d/rcS
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
runlevel=S
prevlevel=N
umask 022
export PATH runlevel prevlevel
#
#       Trap CTRL-C &c only in this shell so we can interrupt subprocesses.
#
insmod /dso/driver/cfbcopyarea.ko
insmod /dso/driver/cfbfillrect.ko
insmod /dso/driver/cfbimgblt.ko
insmod /dso/driver/s3c2410fb.ko
mount -a
mkdir -p /dev/pts
mount -t devpts devpts /dev/pts
echo /sbin/mdev > /proc/sys/kernel/hotplug
mdev -s
mkdir -p /var/lock
mkdir /dev/fb /dev/v4l
ln -s /dev/fb0 /dev/fb/0
ln -s /dev/fb0 /dev/dso-lcd
ln -s /dev/video0 /dev/v4l/video0
ln -s /dev/ts0 /dev/h3600_tsraw
rm -f /dso/driver/driver.log
touch /dso/driver/driver.log
hwclock -s
EmbedSky_wdg &
insmod /dso/driver/dso-fpga-1000b.ko
insmod /dso/driver/dso-spi.ko
./sendspi f dn.rbf
./disp 16 1
insmod /dso/driver/dm9000.ko
ifconfig lo 127.0.0.1
net_set &
#/etc/rc.d/init.d/httpd start
insmod /dso/driver/hantek_gpio.ko
insmod /dso/driver/dso-buzzer.ko
#insmod /dso/driver/usb-storage.ko
#insmod /dso/driver/usblp.ko
insmod /dso/driver/i2c-core.ko
insmod /dso/driver/i2c-dev.ko
insmod /dso/driver/i2c-s3c2410.ko
insmod /dso/driver/s3c2410_udc.ko
insmod /dso/driver/g_serial.ko
#insmod /dso/driver/dso-iobank.ko
insmod /dso/driver/lcd.ko
insmod /dso/driver/dso-ts.ko
insmod /dso/driver/dso-power.ko
mkdir /dev/misc
ln -s /dev/i2c-0 /dev/dso-i2c
ln -s /dev/ttyGS0 /dev/misc/usb-char
ln -s /dev/dso-spi /dev/dso-spi1
mkdir /dev/snd
ln -s /dev/pcmC0D0c /dev/snd/pcmC0D0c
ln -s /dev/pcmC0D0p /dev/snd/pcmC0D0p
ln -s /dev/timer /dev/snd/timer
mknod /dev/snd/controlC0 c 116 0
mknod /dev/snd/hwC0D0 c 116 4
mknod /dev/snd/seq c 116 1
/etc/checkdso /dso_update.exe
/bin/hostname -F /etc/sysconfig/HOSTNAME
/dso/app/dsod
./disp 8
./dso.exe &

Checking what you wrote now
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #35 on: July 13, 2014, 10:23:31 pm »
[root@Hantek /]# chmod 777 *
[root@Hantek /]#

hmm

Also in that rcS file, it looks like it is still looking for dso_update.exe ?
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #36 on: July 13, 2014, 10:29:07 pm »
[root@Hantek /]# chmod 777 *
[root@Hantek /]#

hmm

Also in that rcS file, it looks like it is still looking for dso_update.exe ?

this is exactly what i sadi, Hantek implemented that check into rcS but since i don't know when exactly, they overwriting the running dso.exe with new one during firmware update (which never works on my systems). anyway, this is not the point here, leave that as it is.

All you can do now is try again to:
- kill dsod (in case still there, but you renamed it so should be ok now)
- kill dso.exe
- copy the new dso.exe into /
- in / chmod 777 *
- rm /param/sav/r*
- power cycle DSO and watch what is doing

in principle it have to work now. If now tell me what you see (segfault again? is something on screen/key reaction?)
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #37 on: July 13, 2014, 10:34:44 pm »
Its still the same.

Boots the first logo, 2nd logo, then goes black screen.

UART just outputs the same stuff:

Quote
tq2440_ts: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
TQ2440 TouchScreen successfully loaded
input: TQ2440 TouchScreen as /devices/virtual/input/input0
Power-Ctrl initialized
no update file to foud
now run app .....
/etc/init.d/rcS: line 63: /dso/app/dsod: not found
var.xres=640
var.yres=480
var.bits_per_pixel=16
var.xres_virtual=640
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_stasetting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
rt=856686592
fix.smem_len=614400
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fix.ywrapstep=0
fix.line_length=1280
argv[1]=8
var.xres=640    var.yres=480    var.bits_per_pixel=8

Please press Enter to activate this console. setting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1

Sits there, black screen. Doesnt boot into dso.exe
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #38 on: July 13, 2014, 10:39:27 pm »
hmm, do you want to try to downgrade te firmware?

here on my onedrive http://1drv.ms/1hf4SgO
you will find in "DSO hacks->firmware->hw1.00.4" older fw versions.

While downgrading all you have to do is to copy to your DSO is then the dso.exe and English.lan from the older
firmware version (so you have to use gpg, winrar again to get them).

killall dso.exe
cd /
cp /mnt/udisk/dso.exe /dso.exe
rm /OurLanguages/*
cp /mnt/udisk/Engish.lan /OurLanguages/
chmod 777 *

I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #39 on: July 13, 2014, 10:39:56 pm »
Ran the last command from the rcS file manually, to see what happens

Quote
[root@Hantek /]# ./dso.exe &
[root@Hantek /]# setting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1

Which is what I get on the UART when it does it itself.

running ./dso.exe works fine.
it running ./dso.exe & however doesnt work fine

Quote
[root@Hantek /]# ./dso.exe
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
InitLcdShowBasic:0x40b92000
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
***************************Stat_ShowBattery:0, 0
***************************Stat_ShowBattery:0, 0
save exit: isCheckpointed 0
INIT SYS OK!
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
******************no data cnt=-1************************
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
******************no data cnt=-1************************
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
******************no data cnt=-1************************
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #40 on: July 13, 2014, 10:43:19 pm »
Mr Google said
Quote
If a command is terminated by the control operator &, the shell executes the command in the background in a subshell. The shell does not wait for the command to finish, and the return status is 0.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #41 on: July 13, 2014, 10:50:02 pm »
I can certainly try the old firmware.
So I should do that rather than using the update utility from inside the dso.exe app when its running?
Or does that FW have the same script issue?

111111 didn't seem to open the file. Is the password different?

Just thinking...
What if I ran the script when dso wasn't running. All the errors I got during the update, I assume are all due to the things running. Would that solve it?
Still what is strange how dso.exe wouldn't run in the background as per the startup file, but would when manually executed as a normal executable.
 

Offline rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #42 on: July 13, 2014, 10:56:55 pm »
Still what is strange how dso.exe wouldn't run in the background as per the startup file, but would when manually executed as a normal executable.

probably it needs a terminal to run => the dso.exe in the new firmware is "broken" if it doesn't work the way it should.

try to start it with outputs and input redirected (in fact daemonise) 

./dso.exe > /dev/null 2>/dev/null < /dev/null &

and see if it works - if works then edit your init script accordingly (if that's on a persistent filesystem).

i was planning to update my DSO1102B in the next days.. but reading your troubles after upgrade.... i will rather connect a serial line and find a way how to backup first ;)
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #43 on: July 13, 2014, 11:05:21 pm »
Have no idea what that does, but I tried it, and the scope ran

[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[root@Hantek /]# s3c2440_clkcon=00FFFFF0
s3c2440_clkcon=00FFFFF0
save exit: isCheckpointed 0

seems like its functional.

1am here, I need to get some sleep.

Will continue this tomorrow!

Thank you very much for the help guys, much appreciated.
I hope this helps some people at some stage.

Tinhead, do you have contacts at Hantek to get this solved, or should I make contact with them and tell them the findings?

Goodnight all, will catchup on chat in the morning

Regards
WanaGo
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #44 on: July 13, 2014, 11:57:10 pm »
Have no idea what that does, but I tried it, and the scope ran

[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[root@Hantek /]# s3c2440_clkcon=00FFFFF0
s3c2440_clkcon=00FFFFF0
save exit: isCheckpointed 0


well yes, when started manually it will run, but not when started from rcS. It looks like the dso.exe from 2.01.1_(140408.0) is not initializing properly when runned from rcS (i can't connect via USB to my dev board, so it deos NOT run properly). When killed and started manually it does works. So there must be general problem with that executable version.

I did tested it now with older version, 2.01.1_(140214.0) and there are no issues, runs from rcS or manually and it allows USB connection/access. I did tested (just for sake) 2.01.1_(140408.0) but from B and not S model, and guess what, it works as well. So it seems to be specific problem with dso.exe for S model, version 2.01.1_(140408.0).

So i would say do the downgrade as described. Don't play with other scripts, you will run in trouble during next update, so leave them all as they are. Replace only the English.lan (and different languages if necessary) in /OurLanguages/ directory and the /dso.exe in root, chmod 777 * in root and power cycle.


Tinhead, do you have contacts at Hantek to get this solved, or should I make contact with them and tell them the findings?

feel free to contact them, you have such handheld - i don't. Tests on dev boards, like i'm doing, are good but sometimes not sufficient (especially when firmware is waiting for soemthing missing on dev board).
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #45 on: July 14, 2014, 12:00:28 am »
regards pictures, thank you very much!. Sure, when you have time you can uplaod higher res somewhere. It would be cool if you would try to check what numbers/name/logo on these ICs in attachement.
« Last Edit: July 14, 2014, 12:49:42 am by tinhead »
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #46 on: July 14, 2014, 12:51:29 am »
i've checked your pictures and it seems that you have hardware revision hw1.00.1 and not hw1.00.4, like on current "S" models:

http://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg433286/#msg433286

On your PCB the date is 2012-04, so that really old one. I remember Hantek introduced S models long time ago, but i never ever saw any from that time, you the first one. On hw 1.00.4 they improved the PCB a bit (moved some passive parts to top, isolation clearance better on DMM, smaller LAN IC), howeve the funtion should be the same.
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 

Offline othello

  • Contributor
  • Posts: 25
  • Country: nl
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #47 on: July 14, 2014, 01:48:44 am »
The CRC warning he gets, could that mean some kind of corruption is in their firmware for that model causing these problems ?
 

Offline rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #48 on: July 14, 2014, 02:44:56 am »
Have no idea what that does, but I tried it, and the scope ran

[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[root@Hantek /]# s3c2440_clkcon=00FFFFF0
s3c2440_clkcon=00FFFFF0
save exit: isCheckpointed 0


well yes, when started manually it will run, but not when started from rcS. It looks like the dso.exe from 2.01.1_(140408.0) is not initializing properly when runned from rcS (i can't connect via USB to my dev board, so it deos NOT run properly). When killed and started manually it does works. So there must be general problem with that executable version.


apparently yes, the binary is broken.. tha's why i suggested to daemonize the executable from shell.
my guess is that when running from a tty - it's in some kind of "debug" mode - dumping messages to the tty . and the guys messed up the binary and it doesn't turn itself into a daemon properly when started from initscript - therefore doesn't run from init scripts.
if it works ok when redirecting stdout, stderr and stdin descriptors (the workaround i suggested), then the "solution" is just to modify the startup script (add the redirections to /dev/null) and wait for a new version from Hantek.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1801
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #49 on: July 14, 2014, 04:01:03 am »
The CRC warning he gets, could that mean some kind of corruption is in their firmware for that model causing these problems ?

the "*** Warning - bad CRC or NAND, using default environment" can be ignored, it does not have anything to do with firmware but only with env for bootloader.
I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf