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

0 Members and 1 Guest are viewing this topic.

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Hantek DSO1152S - Wont boot after firmware update
« on: July 13, 2014, 02:27:01 pm »
Hello,

I was just wondering if there is anyone on here who may be able to help.

My scope was running the stock factory firmware on my Hantek DSO1152S (Handheld 150Mhz isolated scope), and I noticed there was an update available as there were a few bugs I had found, such as the MEAS button not being able to measure any other channel other than CH1. So I thought I would try a firmware update.

I went on the Hantek website and downloaded the latest update. Put it on a USB drive, went to the update menu and placed the USB drive in the scope, waited for it to be detected and then clicked update.
It did 10/10 on the process update and then restarted. All looked fine.
Now I am in a boot loop and it will not get past the main start screens. The first shows the Handheld oscilloscope picture, and then the 2nd screen shows the Hantek name, website and the version number. It then restarts and repeats over and over.

Not sure what could have happened, unless the firmware was somehow corrupt?
Was plugged into AC, didn't touch it during the update.

Is there a way to force an update or restore it?

Any help would be appreciated. Currently dead in the water and urgently needing the scope working again

Kind Regards
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #1 on: July 13, 2014, 02:51:36 pm »
Seems someone else may have encountered a similar thing to me...

I couldnt get the hantek.org forum up, so I had to seek out a cached version, here: http://webcache.googleusercontent.com/search?q=cache:http://www.hantek.org/asken/iaskdetail.aspx?id=2014052620325673

Can someone please explain if they know the process to fix this. I am happy to open the case and connect a TTL to serial cable and do something with Linux if required.
I have a Ubuntu VM I could use, and have 3.3V TTL cables, may even find a 5V one...

If someone could help that would be highly appreciated

Kind Regards
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #2 on: July 13, 2014, 03:47:15 pm »
Here are some photos of the internals if this helps

I assume the UART header is the one marked J801, and the pin with the arrow marks the 3.3V pin, followed by GND, TXD and RXD ?

How do I connect to it, what program? What baud rate etc?
What do I need to do?

Any help would be appreciated

Thanks in advance

Regards
WanaGo
« Last Edit: July 13, 2014, 03:54:26 pm by WanaGo »
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #3 on: July 13, 2014, 04:03:31 pm »
OK Yip that seems to be the UART port.

Baud seems to be 115200

Here is the output after pressing power button ON.

Quote
*** 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 ([email protected]) (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=c3ae8a3c) 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)
Hantek GPIO(buzzer/speaker),(c)20110309
Try to bring eth0 interface up ...
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
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #4 on: July 13, 2014, 05:00:29 pm »
It talks about pressing Space at the start, to enter download mode
Would this then let me download an older firmware to correct this mess?

It talks about pressing Enter later on. I did this and it enters the Linux prompt.

Not sure what to do in either though
Regards
WanaGo
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 11127
  • Country: nz
    • Taupaki Technologies Ltd.
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #5 on: July 13, 2014, 05:22:56 pm »
It talks about pressing Space at the start, to enter download mode
Would this then let me download an older firmware to correct this mess?

It talks about pressing Enter later on. I did this and it enters the Linux prompt.

Not sure what to do in either though
Regards
WanaGo
Tinhead is our Hantek expert, be patient and he will spot your thread.
Maybe PM him?
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #6 on: July 13, 2014, 05:27:01 pm »
Yes thanks - have sent him a quick PM. Thank you.

Pressing Space resulted in this, which is the download option.

Not sure what I need though.

Quote
#####. Boot for Nand Flash Main Menu.#####

[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash

[2] Download Eboot to Nand Flash

[3] Download Linux Kernel to Nand Flash

[5] Download CRAMFS image to Nand Flash

[6] Download YAFFS image to Nand Flash

[7] Download Program (uCOS-II or TQ2440_Test) to SDRAM and Run it

[8] Boot the system

[9] Format the Nand Flash

  • Set the boot parameters
[a] Download User Program (eg: uCOS-II or TQ2440_Test)

Download LOGO Picture (.bin) to Nand  Flash

[l] Set LCD Parameters

[r] Reboot u-boot

[t] Test Linux Image (zImage)

[q] quit from menu

Enter your selection:
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #7 on: July 13, 2014, 07:07:22 pm »
More playing, but nothing discovered, just more questions..

Thought I would try to decrypt the update file. Found a bit of info on this site, but I didnt know the password for the up file.

> gpg -d dso1kb_2.01.1_DSO1152S\(140408.0\).up > dso1kb_2.01.1.gz
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: bad key
gpg: block_filter 0xaf0730: read error (size=16233,a->size=16233)
gpg: block_filter: pending bytes!

tried what I found on here, and guessed at a dozen more, but nothing seemed to work.

WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #8 on: July 13, 2014, 07:15:07 pm »
Had a bit of a look around in linux, but it seems after a very short time, maybe 30 seconds?... it reboots

Quote
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.
Restarting system.
« Last Edit: July 13, 2014, 07:29:57 pm by WanaGo »
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #9 on: July 13, 2014, 07:18:13 pm »
Quote from: Tinhead
killall dsod

From another post. Thank you. :)
 

Offline bwat

  • Frequent Contributor
  • **
  • Posts: 278
  • Country: se
    • My website
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #10 on: July 13, 2014, 07:25:51 pm »
More playing, but nothing discovered, just more questions..

Thought I would try to decrypt the update file. Found a bit of info on this site, but I didnt know the password for the up file.

> gpg -d dso1kb_2.01.1_DSO1152S\(140408.0\).up > dso1kb_2.01.1.gz
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: bad key
gpg: block_filter 0xaf0730: read error (size=16233,a->size=16233)
gpg: block_filter: pending bytes!

tried what I found on here, and guessed at a dozen more, but nothing seemed to work.

WanaGo

CAST uses 128-bit keys, so if you brute force it  expect to take 2^127 attempts. Also, many keys may end up giving you an executable binary, just not the right one. Note the universe is roughly 2^80 microseconds old. Source: The Block Cipher Companion, Knudsen and Robshaw.

If you want to save time, the key is somewhere in the machine doing the decryption and CAST is a symmetric cipher so you can encrypt with the same key if you want to load your own software.
"Who said that you should improve programming skills only at the workplace? Is the workplace even suitable for cultural improvement of any kind?" - Christophe Thibaut

"People who are really serious about software should make their own hardware." - Alan Kay
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #11 on: July 13, 2014, 07:32:16 pm »
yeah wasnt hopeful guessing would work, however the passwords I had seen on this forum and others were the model numbers of the scope, or the family models.

I tried:
dso1000
dso1000s
dso1152
dso1152s
etc

No joy.
In terms of hunting out the key on this machine - wouldnt know where to start to be honest.
 

Offline bwat

  • Frequent Contributor
  • **
  • Posts: 278
  • Country: se
    • My website
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #12 on: July 13, 2014, 07:47:03 pm »
Is it a linux process that decrypts the file? If you're lucky it'll be a script so they'll probably use the openssl command. I use a script like this:
Code: [Select]
#!/bin/sh
openssl des3 -d -salt -in secret_file.tar.gz.des3 -out secret_file.tar.gz
Somewhere on that machine will be a similar script using cast instead of des3. Maybe try an update and run "ps" at the same time to see what is doing the decryption. If it's a binary linked with the openssl libs then hexdump that binary looking for the password which you know will probably start with "dso" and be NUL terminated.

Edit: Maybe just build your own openssl libs that dump debug info giving you the passwords used on the machine. That would be quickest.
« Last Edit: July 13, 2014, 07:52:58 pm by bwat »
"Who said that you should improve programming skills only at the workplace? Is the workplace even suitable for cultural improvement of any kind?" - Christophe Thibaut

"People who are really serious about software should make their own hardware." - Alan Kay
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #13 on: July 13, 2014, 07:54:38 pm »
don't play too much, i will help you on that.
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 #14 on: July 13, 2014, 08:08:37 pm »
great, thanks!

Ready when you are.

Noticed when logged in to the linux console, after a few minutes one of the relay clicks on and off, and then again, and then again... and gets faster and faster. I shut it down after a couple of clicks as I dont know why its doing it.
Thought it was due to it getting hot, but I have put a big case fan above the scope board and its still doing it.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #15 on: July 13, 2014, 08:12:56 pm »
>cat sys.inf

[DST type]dst1202b
[soft version]2.01.1(121207.1)
[fpga version]0x555583e8
[start time]-1
[update time]0
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #16 on: July 13, 2014, 08:23:33 pm »
I have 2 firmware files, downloaded one a while back but didnt upgrade as I was looking at the 2.01.1 rather than the date.
Didnt think anything had changed.

dso1kb_2.01.1_DSO1152S(130129.0).up
dso1kb_2.01.1_DSO1152S(140408.0).up

Its that 2nd one that I tried today which got me into this mess.

Looks like I was running 121207.1 prior to that.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #17 on: July 13, 2014, 08:32:45 pm »
now thats interesting...

./dso.exe

scope booted and launched as per normal. beeper was beeping every 3 seconds or so, but I could navigate menus etc.
Utility button, and Sys Info shows its running 140408

Turned it off again.
will wait for instructions
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #18 on: July 13, 2014, 08:37:25 pm »
i'm on windows, so some steps might be different on windows:

1- go to Hantek OneDrive http://1drv.ms/1cA9vjg and download firmware for your model (DSO1152S_Firmware.zip)
2- unzip that file, you will get dso1kb_2.01.1_DSO1152S(140408.0).up
3- get gnupg, run in command prompt from directory with the *.up file like
 gpg -o fw.tar.tar.gz dso1kb_2.01.1_DSO1152S(140408.0).up
4- when asked type password: 111111
5- now you should have that file fw.tar.tar.gz created in this directory
6- open it with winrar, then the content again with winrar - you will see "tekwayup_client" directory, unpack it to harddrive
7- in that directoy there will be "update" script, in my opinion there is bug, there should be

[cmd] mv /tmp/tekwayup_client/dso.exe   /dso_update.exe

and not

[cmd] mv /tmp/tekwayup_client/dso.exe   /dso.exe

I don't know, maybe it's only me, but i never managed to overwrite dso.exe when it was started, it crashed or didn't got overwritten properly on linux 2.6.13 and 2.6.30 (that might work on 3.x, so on other models, but you have 2.6.30.4).
I think these guys from Hantek, they already forgot that  :palm: One can see in the bootlog "no update file to foud" which
is message coming from script which checks if there is /dso_update.exe in place and renames it to /dso.exe before this will be started (right after first rebot after fw update) .. anyway, maybe that's only me hehe, but i can kill all my s3c2440 dev boards
with all the DSO/MSO firmwares on it when i do what they did on latest S, B and BV models updates.

Anyway, copy that dso.exe to flash drive (and ensure windows copied it properly before you remove flash drive).

Now let' got to the linux console on your DSO. Luckily you did the major work already, so do following:

1- power up DSO
2- do not push any buttons or you will be in boot menu and we dont need that!
3- as soon you see "Please press Enter to activate this console" push ENTER and or CTRL+C and ENTER.
4- now tpe as fast you can following (and then ENTER)
 
  killall dsod

and then arrow key up (to reply last command) and ENTER, and again :) Until you get "dsod: no process killed".
The dsod is watchdog, rebooting your DSO over and over again because dso.exe not started. Normally one could check with ps x the process id and kill -9 processid, but killall dsod is faster typed (at least for my fat fingers).

Now you should be on the linux shell, without any reboot over and over again. Insert now the flash drive into DSO,
you should see now some messages that it got monted. Check that with

 ls /mnt/udisk/

You should see that copied before dso.exe. Copy it now to root of the DSO, like

 cp /mnt/udisk/dso.exe /dso.exe

then flush the cash with

 sync
 sync

and give executo rights

 chmod 777 /dso.exe

No check if your DSO is working. Go back to / ( cd / ), and type /dso.exe and enter. The firmwar should start now.
I assume you executed before that update file dso1kb_2.01.1_DSO1152S(140408.0).up anyway, so there is not need
to copy other files from that "tekway_client" directory. In case you applied different update, let me know this, then
you will have to copy other files as well.
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 #19 on: July 13, 2014, 08:41:50 pm »
thank you!

I am on windows too.
Only know how to drive linux as good as I can find answers on google. Assumed that would be the method to use.

Already downloaded the firmware, which got me in this mess in the first place, however will get it from where you stated.

Will report back shortly

Thank you!
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #20 on: July 13, 2014, 08:43:24 pm »
btw, when you DSO anyway open, can you please make pictures of the other side of the PCB as well ? I wish to see how they made the isolation, and all these parts from isolation (ADCs, FPGA and SoC as well - but they known) are of the other PCB side.

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 #21 on: July 13, 2014, 08:54:11 pm »
OK, did all the fix, however still got the boot loop.

Yes I updated the firmware as per the update menu on that latest update prior to all this, then got the boot loop.

copied the dso.exe file over as you said, restarted the unit and its still got a boot loop.

Any ideas?

Ill take photos of the other side while I await your reply

Regards
WanaGo
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #22 on: July 13, 2014, 08:56:50 pm »
so you copied the dso.exe, changed the execution rights and when you kill the dsod and run /dso.exe it reboot then still after few seconds? Try to do this as well:

rm /param/sav/run*

and then try to run the /dso.exe

EDIT: once dsod killed there should be no reboot. It would be interessting as well to see what message is coming right before reboot.
« Last Edit: July 13, 2014, 09:02:01 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 #23 on: July 13, 2014, 09:03:17 pm »
What I mean is, before I did what you said....

Start the unit up, Press Enter to get to linux prompt.
If I sit there it will reboot after about 20 seconds.
So to prevent that, I did the killall dsod.
I then put in the flash drive and copied over the dso.exe file I extracted from the up file.
i then did the rest of your instructions about the chmod etc, sync etc. running /dso.exe at this point starts the scope, no problem. All seems fine.
However rebooting the scope again, results in a boot loop like before.

Whatever is normally opening dso.exe it seems is not working.
I still get that same first warning message: "*** Warning - bad CRC or NAND, using default environment"
When I am looking at the UART.

Hope that makes sense

Opening scope now.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #24 on: July 13, 2014, 09:19:17 pm »
OK here are some photos, both sides.
If you want larger res, let me know. Made smaller for the forum, but still 1280x853. Got them 4752x3168.
Its night here, so if you want better quality ones, let me know and ill take some in the day light tomorrow.
 

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
[[email protected] /]# 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 ([email protected]) (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

[[email protected] /]# killall dsod
[[email protected] /]# killall dsod
killall: dsod: no process killed
[[email protected] /]# 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
[[email protected] /]#
 

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
[[email protected] /]# 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
[[email protected] /]#
 

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: 1800
  • 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 ([email protected]) (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: 1800
  • 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: 1800
  • 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 »
[[email protected] /]# chmod 777 *
[[email protected] /]#

hmm

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

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • 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 »
[[email protected] /]# chmod 777 *
[[email protected] /]#

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: 1800
  • 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
[[email protected] /]# ./dso.exe &
[[email protected] /]# 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
[[email protected] /]# ./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

[[email protected] /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[[email protected] /]# 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: 1800
  • 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

[[email protected] /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[[email protected] /]# 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: 1800
  • 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: 1800
  • 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

[[email protected] /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[[email protected] /]# 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: 1800
  • 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.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #50 on: July 14, 2014, 07:03:04 am »
Hi Guys

Tinhead - what is the password for the previous update I should try?
111111 doesn't work

Thanks
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #51 on: July 14, 2014, 07:19:53 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.

Most of the chips have been scrubbed! Thats not cool.

2 places there are smt passives which have been hand reworked and reconfigured with little jumpers etc - mistakes on the PCB I assume. :(

Ill get some photos up shortly, although it doesnt show much
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #52 on: July 14, 2014, 07:22:15 am »
Actually, all of the chips you pointed to... are scrubbed :S
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 11127
  • Country: nz
    • Taupaki Technologies Ltd.
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #53 on: July 14, 2014, 07:32:46 am »
Looks like you both will crack it in time.
Fascinating thread, watching with interest.
Think about tidying up later to make it an easy follow for anybody with similar problems.

link to another  :-BROKE Hantek .....a work still in progress.
http://www.eevblog.com/forum/testgear/hantek-dso1200-handheld-dead/msg452374/#msg452374
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #54 on: July 14, 2014, 07:54:23 am »
Tinhead - what is the password for the previous update I should try?
111111 doesn't work

no idea what you doing, but 111111 is for sure proper password.

Most of the chips have been scrubbed! Thats not cool.
Ill get some photos up shortly, although it doesnt show much

hmm, so i will try to recognize them from pictures

2 places there are smt passives which have been hand reworked and reconfigured with little jumpers etc - mistakes on the PCB I assume. :(

yeah, that looks bit funny, but as long it works ...
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 #55 on: July 14, 2014, 07:58:16 am »
Booted up the scope this morning via the UART to get into dso.exe
Couldn't extract the up files for the last release as the password didn't work, so I decided to update via the menu system in the dso itself using the up file on the USB Flash, and using the update feature.
That worked fine. Scope is now booting fine.

So yes, definitely something wrong with the last update.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #56 on: July 14, 2014, 07:59:42 am »
Hmm deffinitely didnt work for me Tinhead

Quote
> gpg -o fw2.tar.tar.gz dso1kb_2.01.1_DSO1152S\(130129.0\).up
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: block_filter 0x1dbf730: read error (size=12249,a->size=12249)
gpg: [don't know]: invalid packet (ctb=39)
gpg: [don't know]: invalid packet (ctb=07)
gpg: WARNING: message was not integrity protected
gpg: [don't know]: invalid packet (ctb=63)
gpg: block_filter: pending bytes!
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #57 on: July 14, 2014, 08:02:46 am »
dso.exe and English.lan attached, btw. decrypted with 111111. It is the file name, rename these (\ in _ or remove them.
« Last Edit: July 14, 2014, 08:17:01 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 WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #58 on: July 14, 2014, 08:33:52 am »
Nope, still doesnt like it

> gpg -o fw2.tar.tar.gz dso1kb_2.01.1.up

gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
File `fw2.tar.tar.gz' exists. Overwrite? (y/N) y
gpg: block_filter 0x1da96f0: read error (size=12249,a->size=12249)
gpg: [don't know]: invalid packet (ctb=39)
gpg: [don't know]: invalid packet (ctb=07)
gpg: WARNING: message was not integrity protected
gpg: [don't know]: invalid packet (ctb=63)
gpg: block_filter: pending bytes!

Maybe the file is corrupt... ill try again.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #59 on: July 14, 2014, 08:35:36 am »
Yup thats what it was. Copied it to my Linux VM again and all ok this time.

Thanks.

Photos coming, uploading.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #60 on: July 14, 2014, 08:38:28 am »
Ok here are all the photos I have taken.
Sorry not the best, some are a bit blurry.

Hope you get the gist.

Hantek Scope Pictures zipped LARGE

Cheers
WanaGo
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #61 on: July 14, 2014, 09:33:18 am »
thanks for the pictures, they are great. I do have now raw picture how they made it. Unfortunately you haven't made any picture of what under the channel shielding, in case you get some time to shot one i would be really thankful.
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 #62 on: July 14, 2014, 09:54:21 am »
oh damn... does it just clip off?

I've closed it all up now.
However I might have to get back in there...

Ill def get you a picture though.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #63 on: July 15, 2014, 03:27:18 pm »
I contacted Hantek and they promptly replied with this message to me:

Quote
Just uncompress packet file.
And store packet and emerg.do files to a USB drive, and plug the USB drive to DSO, turn on DSO.
If the DSO can reboot automatically when your upgraded the firmware last time, DSO can recall the factory setup.
Pls try.

With this file: http://www.taktik.co.nz/EEVBlog/packet.zip
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #64 on: July 15, 2014, 03:39:30 pm »
It looks like this contains fixes for the bad script before, but when I connected the USB drive with the packet folder and emerg.do files in the root of the USB drive, and started the scope up, it didnt seem to do anything differently.

Running the update program in the scope doesnt work either as it cannot find any updates on the drive.

So not 100% sure what to make of this.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #65 on: July 15, 2014, 06:08:10 pm »
emerg.do (and all the even newer recovery tricks) are implemented into dsod file. You remember, you renamed it to stop the boot loop. That file need to be there and loaded, and when the firmware is crashing (or not loaded or missing) the dsod will look for "magic" on flash drive. You can see the output/status mesages on uart.

Btw., on my dev board when i follow the instruction the dsod is looking for system*.up and not doing what it should do :P
So who knows what your handheld is doing (that depends on version of dsod)
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 #66 on: July 15, 2014, 06:31:31 pm »
OK interesting stuff.

They replied again when I said it didnt work.

Here is what they said

Quote
Since you could use UART connection, please use attached "uart_update" to solve the problem.

Steps as follows:
1. Just uncompress packet file.
And store packet and do_update files to a USB drive, and plug the USB drive to DSO, turn on DSO.
2. Connect DSO to PC by UART.
3. And input following commands in the UART tool on PC.
1?cd /mnt/udisk/
2) chmod +x /mnt/udisk/do_update
3) /mnt/udisk/do_update

and sent me the file I put here: http://www.taktik.co.nz/EEVBlog/uart_update.rar

Have an excuse to open it back up now and take that photo for you under the shield covers.
Will do that now

Regards
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #67 on: July 15, 2014, 06:47:09 pm »
Photos from under the cover are here. Also all scrubbed apart from the one near the opening.
Sorry if they are not very clear

http://www.taktik.co.nz/EEVBlog/DSO1152S-UnderCover.zip

Regards
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #68 on: July 15, 2014, 06:59:20 pm »
Followed their instructions...

Even worse now...
Display is now completely snow after the main start pages.

Here is the log

Quote
[[email protected] /]# cd /mnt/udisk
[[email protected] udisk]# chmod +x /mnt/udisk/do_update
[[email protected] udisk]# /mnt/udisk/do_update
kernel is 2.6.30.4
ln: /lib/libgif.so.6: File exists
rm: can't remove '/OurLanguages': Directory not empty
mkdir: can't create directory '/OurLanguages': File exists
save exit: isCheckpointed 0
umount: /dev/sda1 busy - remounted read-only
umount: tmpfs busy - remounted read-only
[[email protected] udisk]# umount: can't remount /dev/root read-only
umount: can't remount rootfs read-only
The system is going down NOW!
Sent SIGTERM to all processes
s3c2410-wdt s3c2410-wdt: Unexpected close, not stopping watchdog
Sent SIGKILL to all processes
Requesting system reboot
s3c2440-sdi s3c2440-sdi: powered down.
Restarting system.ΓΏ*** 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 ([email protected]) (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: setting system clock to 2009-01-01 00:01:39 UTC (1230768099)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
usb 1-1: new full speed USB device using s3c2410-ohci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
insmod: can't insert '/lib/cfbcopyarea.ko': No such file or directory
insmod: can't insert '/lib/cfbfillrect.ko': No such file or directory
insmod: can't insert '/lib/cfbimgblt.ko': No such file or directory
insmod: can't insert '/lib/s3c2410fb.ko': No such file or directory
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
<0>open LCD error: No such file or directory
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 c487a300,c487e304 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
insmod: can't insert '/dso/driver/usb-storage.ko': No such file or directory
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
scsi 0:0:0:0: Direct-Access     Lexar    JumpDrive        1100 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 15679488 512-byte hardware sectors: (8.02 GB/7.47 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
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
insmod: can't insert '/dso/driver/dso-adc.ko': No such file or directory
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

Please press Enter to activate this console. cannot open lcd
: No such file or directory
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
release
save exit: isCheckpointed 0
umount: tmpfs busy - remounted read-only
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 ([email protected]) (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: setting system clock to 2009-01-01 00:02:00 UTC (1230768120)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
usb 1-1: new full speed USB device using s3c2410-ohci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
insmod: can't insert '/lib/cfbcopyarea.ko': No such file or directory
insmod: can't insert '/lib/cfbfillrect.ko': No such file or directory
insmod: can't insert '/lib/cfbimgblt.ko': No such file or directory
insmod: can't insert '/lib/s3c2410fb.ko': No such file or directory
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
<0>open LCD error: No such file or directory
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 c487a300,c487e304 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
insmod: can't insert '/dso/driver/usb-storage.ko': No such file or directory
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
scsi 0:0:0:0: Direct-Access     Lexar    JumpDrive        1100 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 15679488 512-byte hardware sectors: (8.02 GB/7.47 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
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
insmod: can't insert '/dso/driver/dso-adc.ko': No such file or directory
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

Please press Enter to activate this console. cannot open lcd
: No such file or directory
s3c2440_clkcon=00FFFFF0
MachineFunctionLimitByBrandType
release
rm: can't remove '/param/sav/run*': No such file or directory
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #69 on: July 15, 2014, 07:15:09 pm »
Oh dear.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #70 on: July 15, 2014, 08:01:07 pm »
Im stuck.
Cant get it working no matter what I try.

Seems that first update has cleared out some essential files or something, it no longer knows how to use the LCD.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #71 on: July 15, 2014, 10:51:26 pm »
when you look exactly the "last" update copied some missing libs and the new dsod, everything else (meaning the "broken" dso.exe, which seems to be not broken btw.) is the same. A new rcS and /model (what are they doing with that? i see it is on latest benchtop model as well, hmm, will have to take look on that). Anyway, so far evrthing should be ok.

I'm wondering about two things:
1- the new rcS is loading run.sh, which starts then the dsod, but not dso.exe (so i assume the newest dsod is calling the dso.exe or dso_bin itself, haven't check that but i trust them here, a day old "B" model firmware is doing this exact the same way). I'm wondering only that they implemented this on such old "S" models as yours, but yeah, they should know what they doing.

2- what is with the lib and lcd drivers on your handheld? Look your bootlog:

insmod: can't insert '/lib/cfbcopyarea.ko': No such file or directory
insmod: can't insert '/lib/cfbfillrect.ko': No such file or directory
insmod: can't insert '/lib/cfbimgblt.ko': No such file or directory
insmod: can't insert '/lib/s3c2410fb.ko': No such file or directory
....
Please press Enter to activate this console. cannot open lcd


i did loaded "BV" model image, from 2011, so even older than your "S" model, then installed the first "S" model firmware - all working, and now used that manual update procedure - and everything works here. So it looks like the new dso.exe HAVE TO BE started by dsod (or manually, but not anymore from rcS, so that's why you got new one). Anyway, everything seems to be working (as far i can see on my dev board).

I your older bootlog there is no such problem with lib directory, so i assume you wiped that directory at some time (this is why i did checked myself if one of hantek's updates was responsibe for this, but it wasn't). I would say, send them that bootlog, they can easily compile for you zip file with all the missing files (i would do this for you, but i don't have any dump of "S" model and even if my dev board works, i can not guarante that my lib dir is complette, so better when Hantek compile for you this).

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 #72 on: July 16, 2014, 07:22:45 am »
Hmm

I haven't wiped anything manually.

I sent them the logs I posted here, will wait I suppose.
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #73 on: July 16, 2014, 01:40:50 pm »
Fixed, they send another update.

Attached.

Quote
[[email protected] /]# cd /mnt/udisk
[[email protected] udisk]# chmod +x /mnt/udisk/do_update
[[email protected] udisk]# /mnt/udisk/do_update
kernel is 2.6.30.4
save exit: isCheckpointed 0
umount: /dev/sdb1 busy - remounted read-only
umount: /dev/sda1 busy - remounted read-only
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 Kern                                                                     el to SDRAM done,NOW, Booting Linux......
Uncompressing Linux.............................................................                                                                     ................................................. done, booting the kernel.
Linux version 2.6.30.4 ([email protected]) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-1                                                                     76) ) #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: setting system clock to 2009-01-01 00:02:58 UTC (123076                                                                     8178)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
usb 1-1: new full speed USB device using s3c2410-ohci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
setting vert: up=11, low=11, sync=1
setting horz: lft=17, rt=135, sync=11
Console: switching to mono frame buffer device 80x30
fb0: s3c2410fb frame buffer device
bwscon:0x2201d110
fpga bank 221422
scsi 0:0:0:0: Direct-Access     USB 2.0  Flash Disk       2.10 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 2046456 512-byte hardware sectors: (1.04 GB/999 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda:dso-fpga: install ok
 sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
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=866123776
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 c488c300,c4890304 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
insmod: can't insert '/dso/driver/usb-storage.ko': No such file or directory
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
insmod: can't insert '/dso/driver/dso-adc.ko': No such file or directory
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

Please press Enter to activate this console. 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
******************no data cnt=-1************************
******************no data cnt=-1************************
***************************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************************
***************************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************************
***************************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************************
***************************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************************
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
***************************Stat_ShowBattery:1, 0
******************no data cnt=-1************************
***************************Stat_ShowBattery:1, 0

 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #74 on: July 16, 2014, 03:04:53 pm »
Quote
Very glad to hear this good news.

Our engineer have found the problem and will make up a firmware without this bug.
Many thanks for your below helpful datas.
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 11127
  • Country: nz
    • Taupaki Technologies Ltd.
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #75 on: July 16, 2014, 03:11:58 pm »
Quote
Very glad to hear this good news.

Our engineer have found the problem and will make up a firmware without this bug.
Many thanks for your below helpful datas.
Your new title: WanaGo, Hantek Software Support Technician.  :-DD  :-+
But you had us wondering for a good while.  :phew:
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #76 on: July 16, 2014, 03:15:48 pm »
Haha - glad we got to the bottom of it.
Big thanks to everyone involved.

I hope this has helped or will help someone with a Hantek scope. Hopefully no one else will fall into this trap now that Hantek is going to fix the updates.

Now, back to what I was trying to measure...
 

Offline rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #77 on: July 16, 2014, 05:45:47 pm »
i've upgraded my DSO1102B with the last FW from Hantek - and no issues. probably that bug was only for the S series you have.
i was hoping i will have a excuse to play with the uart on my scope ... but no "luck" - the upgrade went smoothly ;)
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #78 on: July 16, 2014, 06:51:34 pm »
i've upgraded my DSO1102B with the last FW from Hantek - and no issues. probably that bug was only for the S series you have.

it was combination of missing files in the update files and newer dsod, with mumore functionality than the one on other models. Actually on latest benchtop "B" models Hantek implemented exact the same large dsod with more functionality, so it seems they will move all models to that. For us it is good, one can use that dsod to restore/recover and maybe even backup functionality.

i was hoping i will have a excuse to play with the uart on my scope ... but no "luck" - the upgrade went smoothly ;)

this is what fuses are for, shot them and you have to open the enclosure :P As i was younger, i always tried like that, hehe.
Now i'm old and wise, so i can open everything and play with everything, to get eventually even wiser.
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: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #79 on: July 16, 2014, 06:53:09 pm »
Big thanks to everyone involved.

and i have to thanks for the pics!

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 rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #80 on: July 16, 2014, 07:02:43 pm »
i was hoping i will have a excuse to play with the uart on my scope ... but no "luck" - the upgrade went smoothly ;)

this is what fuses are for, shot them and you have to open the enclosure :P As i was younger, i always tried like that, hehe.
Now i'm old and wise, so i can open everything and play with everything, to get eventually even wiser.

actually i'm a linux guy since '95 - '96 and did a lot of embeded stuff in the past... but now i'm too lazy to play with anything what is in working condition.. once something doesn't work - then i have to play with it ;)
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #81 on: July 16, 2014, 07:32:40 pm »
This new update has quite a few new things... Would hope so too, coming from a factory 2012 update...

Save waveform, you now seem to be able to save an animation, other than just an image or CSV etc... thats kinda cool... need to try that.
The DMM readouts in the top right actually seem to work....
The help looks much more comprehensive too. I think.
No doubt more..

Are there any update change logs, to say what has been updated?

Now I am more comfortable with this scope physically.... Tinhead.... what upgrades can I do to it? Is this one capable of the 200Mhz upgrade, or does it not fall in the right range of serial numbers or whatever?
Has mention of Video in the utility menu, which is greyed out. whats that?
SD card - unsupported. whats that for? I saw the blank footprint for the uSD card socket.
Video - unsupported.
Net Card - supported - have used that before.
Store depth - 1M

Cheers
WanaGo
 

Offline WanaGo

  • Regular Contributor
  • *
  • Posts: 86
  • Country: nz
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #82 on: July 16, 2014, 07:40:04 pm »
Oh and now I can measure some signals on CH1 in MEAS as well as CH2 signals, at the same time.
Before I suppose I couldnt select CH2 so knew no better! hah. this is going to be handy. Like a real scope or something, rather than a toy.  :-DD
 

Offline rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #83 on: July 16, 2014, 07:51:26 pm »
it's strange - my DSO1102B is apparently an older model tha your DSO1152S , but both DDM & frequency in the top right corner were working just fine before and after upgrade. and same for the CH1 & CH2 at the same time in the measurements it worked before the update and still works after the update .
 

Offline commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #84 on: July 24, 2014, 12:40:15 am »
I noticed that Hantek has a firmware file (dso1kb_2.01.1_DSO1152S(140408.0).up) that is dated 7-14-2014.  Can someone confirm that this is the fixed version of the firmware that WanaGo was having trouble with?  I don't want to try it on my S series handheld until I'm sure it won't cause the same problems.  I don't have the equipment to access the ports on the inside, nor the linux experience to do what WanaGo has done (Thanks for catching the problem, by the way!). 
When something like this happens, is there any way to force a firmware downgrade through the USB port?
Thanks!
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #85 on: July 24, 2014, 02:04:37 am »
I noticed that Hantek has a firmware file (dso1kb_2.01.1_DSO1152S(140408.0).up) that is dated 7-14-2014.  Can someone confirm that this is the fixed version of the firmware that WanaGo was having trouble with? 
you mean on their onedrive? this is the same version, only extracted on 7-14-2014, but the same content. They deleted all
versions from web and onedrive, but seems that they forgot that extraced version.

So no, don't use that.

I will compile later today working version and post on my onedrive (it will be dated named custom_dso1kb_2.01.1_DSO1000S(140408.2).zip and only the up file dso1kb_2.01.1_DSO1000S(140408.2).up )

When something like this happens, is there any way to force a firmware downgrade through the USB port?

as long the dso.exe (dso_bin) is running - yes - because one can connect over lan or usb with that tool from Peter Dreisiebner

http://peter.dreisiebner.at/dso-usb-tool/

then go to shell tab and copy manually older files from flash drive to DSO. Then after reboot the DSO will use them.

However, when the dso.exe (or dso_bin) is not working, then there was no other way than the physical uart.

Now with the new dsod (watchdog) for benchtops and handhelds one will have a way to restore/downgrade DSO even
when dso.exe (or dso_bin) is crashing. It is somehow funny that the first firmware with the new dsod alread created
problems, because of the dsod. But yeah, something like that can happens when one forgot to copy files into update
or run test twice (where the system does have already files which are missing in update ...).
« Last Edit: July 24, 2014, 07:09:07 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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #86 on: July 24, 2014, 03:29:36 am »
Thank you, tinhead.  I will keep watch for it.  This is an interesting problem.  I'm so glad I saw this thread, as I check Hantek's onedrive regularly for firmware updates and would have blithely installed this defective one and ended up in the same boat as WanaGo, but without an easy way to fix it.
 

Offline rob77

  • Super Contributor
  • ***
  • Posts: 1848
  • Country: sk
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #87 on: July 24, 2014, 04:13:50 am »
it's strange - my DSO1102B is apparently an older model tha your DSO1152S , but both DDM & frequency in the top right corner were working just fine before and after upgrade. and same for the CH1 & CH2 at the same time in the measurements it worked before the update and still works after the update .

ups... early judgment.... the DMM & frequency in the top right corner are working... but only after pressing the measure button - but they keep working since then - even after menu off button pressed.. so not a big deal ;)
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #88 on: July 24, 2014, 08:29:00 pm »
here we go, on my onedrive http://1drv.ms/1hf4SgO in firmware->hw1.00.4 there is the custom_dso1kb_2.01.1_DSO1000S(140408.2).zip file. Inside that file you will find dso1kb_2.01.1_DSO1122S(140408.2).up and extra.zip. Copy that dso1kb_2.01.1_DSO1122S(140408.2).up to empty flash drive. Then unzip that extra.zip to that flash drive, you will see then "packet" directory. This is necessary due the lack of NAND space, the update procedure need always twice the size of decrypted update. So my custom update is copying part of reqiered files directly from flash drive, so that it can work even on low space models (like my test unit from 2011). Remove that flash drive from PC and insert into handheld, run now the firmware update from utility->f2->f4. Due amount of files it can take some extra time, my script is doind 10sec. loop to ensure that all files has been written. So wait until the led stopped to lit and the "plaese reboot" pops up on display. Some models, and this depends on what fw version already installed, will anyway do an automaticaly reboot, so that's fine as well.

After the reboot or power cycle you should see then 140408.0 as fw version.
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #89 on: July 24, 2014, 11:26:43 pm »
Thank you so much tinhead!  Later on, after I finish work, I will give this a try on my DSO1122S unit and report the results.  Once this is done, should the new DSOD functions work as Hantek had intended?  It would be nice to think there is some way, other than cracking open the case, to recover a scope with issues. :)
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #90 on: July 24, 2014, 11:39:25 pm »
Once this is done, should the new DSOD functions work as Hantek had intended? 

yes, i did tested this already, meaning when i kill dso.exe (tested with broken one and with none) then the dso display stays black and after some time it does reboot. When i then insert flash drive with e.g. system_restore.up a message popups "firmware update", where of course one have to have an system*.up file encrypted with special password (in this case "dsoduse"). There is as well the emergency way, where one have to copy "emerg.do" file to flash drive. That file is nothing else than encrypted update shell script, which can then do restore or backups or what so ever. This script need to be then encrypted with special password (in this case "949307"). There seems to be small "model check" implemented, i think to prevent people from installing wrong firmware on wrong model, haven't tested yet how this works in detail, all i saw is that the systemxxx.up or hantek.up need to contain "model" file in which the model name is stored (and that name have to be the same as on the DSO already). In case o the isolated handhelds this model name is "dso1000s", so it is universal for all models in own model category. Sometimes i think they have too much time at Hantek  >:D
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #91 on: July 26, 2014, 12:06:51 am »
Okay.  I downloaded and extracted tinheads  "custom_dso1kb_2.01.1_DSO1000S(140408.2).zip" file and followed the instructions earlier in this thread very carefully.  Something unexpected happened, though.  After starting the upgrade process through the menu (untility,>f2,>f4), things went as expected and the USB flash drive was blinking.  This was going on for a few moments.  I turned away to answer the phone and when I looked back, the screen was blank, but power was on.  The USB drive was no longer flashing.  To be certain it was hung, I left it go for 15 minutes, with no change.  I had the unit fully charged and plugged in to the AC adapter.  So, after nothing changed, I forced the unit off with the power button and restarted.  Now I get a looping first screen, second screen, blank and restart.  It seems similar to what WanaGo had happen.  I can't think what I could have done wrong.  I followed the procedure to a tee.  :-//

I'm not panicking about this.  I tried this with the full awareness that it is experimental.   I use this scope for measuring bridged output audio power amplifiers, and I have my Fluke 199C that works for the purpose, so I can still do my testing.  Screen and data captures are so much easier with the Hantek, which is why I got one (plus the screen is so much better).  I know that there is a solution in this thread, but I am scratching my head as to what happened.  I wish I hadn't turned away! As I said before, I'm not too well versed in the software aspects of this, but am willing to try, if I can get the proper hardware interface.  Thanks for any suggestions! :-BROKE
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #92 on: July 26, 2014, 01:00:57 am »
how crap is that, i did the installation on total 3 boards with 3 different images - and that with fw level from 2011, 2012,2013 and even the latest 2014 to ensure that an ANY stage of better said with any version of hw/fw the update is running. Any then the first DSO in field is crashing :\

Ok, i will help you with that. Copy dso1kb_2.01.1_DSO1122S(140408.2).up to empty fash drive and rename it to system1.up
Then insert it into and tell me if you see something on screen and/or if then led is blinking. I need to know at what stage your DSO is now ...
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #93 on: July 26, 2014, 01:43:59 am »
It was the FLASH DRIVE  |O  When I attempted to load the renamed firmware file onto the flash drive I've been using for this procedure, I got read/write errors.  First time that has ever happened to me, but lesson learned.  Don't use a $3.99 flash drive for firmware updates.  The files looked fine when I had copied them on yesterday, so the failure could have occurred anytime.
I loaded the renamed system1.up file to a fresh, name brand, flash drive and started the scope.  I still get the first "picture" screen, then a firmware version screen for a moment, then blank for about 10 seconds before a recycle.  The activity light on the flash drive flickers through all of the first cycle and part of the second and then goes out.  Nothing but recycling of the scope after that.  Does that mean some of the loading programs (like the DSOD) are corrupted?
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #94 on: July 26, 2014, 04:27:22 am »
What a crap. Did you remember what version was installed before the update? I will try then to find solution for you.
I did removed that custom fw from my onedrive, i will have to implement crc check inside, without it is too risky.
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #95 on: July 26, 2014, 04:46:46 am »
I was running the ver 2.01.1(140212.0) firmware previously.  Thank you for your efforts, tinhead.  I strongly suspect that the problem was hardware related at this end, rather than with any of your work.  Your analysis and discussions of Hantek hardware and firmware have been totally outstanding!
Should I start shopping around for one of those little USB to TTL interfaces?  I only have a USB to RS-232 variety right now, which I know is not electrically compatible. Thanks!
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #96 on: July 28, 2014, 09:16:46 am »
i did tested everything i could test, but without success. The only way is now to work over UART. I will of course guide you as soon you bought/build such adapter. Sorry for that.
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #97 on: July 28, 2014, 09:36:28 am »
I have a USB to TTL-serial interface on order. When I have the hardware set up, I'll drop back into this thread.  Thanks so much!
 

Offline commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #98 on: August 09, 2014, 06:07:07 am »
Greetings!
The USB to TTL uart interface arrived today and I got it hooked up.  When I started the scope, I received a string of messages exactly like the first one that Wanago received after his firmware update problem.  I've read this thread through several times, and some of the Linux commands started making sense to me.  The first thing I did actually accomplished two things:  It fixed the problem, and proved that my defective USB flash drive caused my scope trouble, not tinheads fixed (dso1kb_2.01.1_DSO1122S(140408.2).up) firmware. 
Okay, so I monitored the scope as it ran through the initialization loop to the pausing point, just before the auto restart. I then hit enter to enable the console.  After that, I typed "killall dsod". That stopped the restarts. I then simply entered "/dso.exe".  I think I was lucky, and the main program file was not corrupted/lost, because the scope came to life.  I wasted no time and inserted a good flash drive with tinheads modified firmware and files (as above, dso1kb_2.01.1_DSO1122S(140408.2).up) which I had kept.  I ran the updater right from the scope Utility menu as you would normally do a firmware upgrade.  It ran (a bit longer, as tinhead said it would with the extra files on the flash drive), and then restarted.  Voila!  The scope started normally and has been working ever since. 
To tinhead:  Thank you so very much for your dedicated interest in the Hantek/Tekway gear.  It saved me tons of grief.  I believe you should repost the dso1kb_2.01.1_DSO1122S(140408.2).up fixed firmware on your onedrive site for others to use.  It ultimately worked for me, and I have the benefits of the new firmware version, as Wanago has described.  I do wish Hantek would take that last copy of the bad firmware off of their onedrive site.  It sits like a land mine for unsuspecting "S" series scope owners (I wonder how many there are of us?).
Wanted to add: My DSO1122S has a hardware version of 1.02 dated 9-2012
« Last Edit: August 12, 2014, 12:02:08 am by commongrounder »
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #99 on: August 13, 2014, 05:17:58 pm »
you welcome! and of course good to hear that your handheld is back working.
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 aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #100 on: August 18, 2014, 06:34:32 am »
Hello. Here is my new DSO. The board is newer than posted in this topic, so attaching photos - may be interesting for anybody. FPGA is Cyclon IV, in WanaGo's held - Cyclon III






What is strange - the shields of input circuits are not soldered - what a bullshit?













UART has standart pinout


« Last Edit: August 18, 2014, 06:49:36 am by aerra »
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #101 on: August 18, 2014, 07:05:21 am »
Hello. Here is my new DSO. The board is newer than posted in this topic, so attaching photos - may be interesting for anybody.

thanks for these great pictures (any chance to get originals with better resolution via PM?)

FPGA is Cyclone IV, in WanaGo's held - Cyclone III

and that's really surprise!

Any chance that you made backup of the NAND and share with me ? (PM)

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 aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #102 on: August 18, 2014, 08:29:30 pm »
Yes, of'course. I outed the UART cable to battarey partition, so it's no problem to get backup (but i have to understand how to do it). Photos are 3MP, i'll sent them later.
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #103 on: August 18, 2014, 08:59:02 pm »
that's cool thanks!

Knowing now that the latest "S" models (hw1.00.4) are S3C2416 SoC and Cyclone IV based no wonder that there was issues with latest firmware updates on older "S" models (hw 1.00.1 and hw 1.00.2).
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 aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #104 on: August 20, 2014, 03:21:03 pm »
Trying to calibrate the  compensacion of probes using 1kHz scope's output  . Problem: native probes don't want to make a right meandr, in end position of probe's capacitor the meantr is still not right. I tried another probes and they are better. And one more - the meandr is bit different in AC and DC modes, on both channels. So it seems that input capacistances in AC and DC are different. Is it possible to regulate this? There are two variable capacitors in input circuit under the shield, turn them?
And is there a needence to solder the unsoldered sheelds of inputs?
(bad english, learning)
« Last Edit: August 20, 2014, 03:27:58 pm by aerra »
 

Offline aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #105 on: August 21, 2014, 02:37:06 am »
DC and AC
Backup sent to PM.
Maybe let's go to topic   "Hantek - Tekway - DSO hack - get 200MHz bw for free"  ?
« Last Edit: August 21, 2014, 02:52:43 am by aerra »
 

Offline tinhead

  • Super Contributor
  • ***
  • Posts: 1800
  • Country: 00
    • If you like my hacks, send me a donation
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #106 on: August 21, 2014, 04:21:18 am »
as i don't have isolated model, i can't answer. But maybe the other ppl here with "S" models can check it.
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 commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #107 on: August 22, 2014, 06:29:56 am »
@aerra  I set up my DSO1122S exactly the same way as your screen images (except I can't tell which averaging setting you were using, I chose 64).  I set the probe compensation on the supplied probes as usual for the flattest tops with minimal over or undershoot.  Below are screen shots of those, along with a couple using a faster timebase to show the leading edge a bit more clearly.  I personally think this is quite acceptable, considering the noise floor of the inputs.
Also, I would not touch the internal trimmers of the scope, or change anything about the shielding.  You could easily throw your scope out of calibration and have no reference to depend on for measurements.
The first two images are with DC coupling and the second two are with AC coupling.  Hope this is helpful.  :)
 

Offline aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #108 on: August 24, 2014, 06:06:14 am »
Thanks
 

Offline aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #109 on: January 07, 2016, 07:14:36 am »
good day all!
On Hantek website there is last firmware for 1000s dated 01.2015. Is it good? Did anybody tried to update on it? My current versions in attached log
« Last Edit: January 07, 2016, 08:13:46 am by aerra »
 

Offline commongrounder

  • Frequent Contributor
  • **
  • Posts: 255
  • Country: us
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #110 on: January 08, 2016, 01:59:29 am »
I did install the "dso1kb_2.01.1_DSO1122S(150108.0).up" firmware on my DSO-1122S a while back.  There were a few minor changes and spelling corrections.  I *think* it improved stability (fewer lockups), although that can sometimes just be wishful thinking.  ::)  One thing I need to figure out is memory handling.  It won't allow setting the waveform memory over 512K unless certain conditions are met.  I don't use long memory too often (slows down acquisition too much), so I can't remember what is required to enable the 1meg memory length. 
In any case the firmware upgrade process went without incident, so it seems safe to install.
Good Luck!
 :)
 

Offline aerra

  • Contributor
  • Posts: 10
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #111 on: October 01, 2017, 10:31:27 pm »
Good day.
Today the last update is dso1kb_2.01.1_DSO1152S(170801.0).up.
Have anybody try it?
 

Offline justincr83

  • Newbie
  • Posts: 3
  • Country: ro
Re: Hantek DSO1152S - Wont boot after firmware update
« Reply #112 on: January 13, 2018, 12:19:41 pm »
my dso is dead, i have no idea what's wrong with it. i'm trying to figure out what is wrong with it but without luck...
anyone knows where and if there is any uart port on this unit?

here's the link to the started thread. http://www.eevblog.com/forum/chat/hantek-dso8060-dead-possible-fix/

here's the pcb front and back pictures attached (DSO 8060)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf