Author Topic: Fixing a borked Hantek DSO5102P  (Read 3578 times)

0 Members and 1 Guest are viewing this topic.

Offline aijiiTopic starter

  • Newbie
  • Posts: 3
  • Country: au
Fixing a borked Hantek DSO5102P
« on: February 17, 2016, 08:17:37 am »
Hi guys,

First up, what a great resource this forum is.

My father in law has a of DSO5102P.. that doesn't work. I'm trying to fix it. It worked once, then wasn't used for a year, then now it doesn't boot, just a boot loop with a blue screen.

I've read through Tinhead's extensive thread covering the hantek hacking business... connected a usb-uart to the serial por and can see the following:

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


##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...

...


And then I get the following later on:

UBIFS error (pid 420): ubifs_decompress: cannot decompress 2753 bytes, compresso
r lzo, error -22
UBIFS error (pid 420): read_block: bad data node (block 195, inode 649)
UBIFS error (pid 420): do_readpage: cannot read page 195 of inode 649, error -22
Bus error
[root@Hantek ~]#
[root@Hantek ~]#
[root@Hantek ~]#
[root@Hantek ~]#
[root@Hantek ~]# hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB device on port 2

[root@Hantek ~]# df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
ubi0:rootfs             107572     17476     90096  16% /
[root@Hantek ~]# umount: tmpfs busy - remounted read-only
umount: tmpfs busy - remounted read-only
The system is going down NOW!
watchdog: S3C2410 Watchdog: watchdog did not stop!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
UBIFS error (pid 1): ubifs_decompress: cannot decompress 2753 bytes, compressor
lzo, error -22
UBIFS error (pid 1): read_block: bad data node (block 195, inode 649)
UBIFS error (pid 1): do_readpage: cannot read page 195 of inode 649, error -22
Kernel panic - not syncing: Attempted to kill init!

...

I'm hoping that the NANDflash memory isn't toast and I can recover it. The problem is, I don't have anything to recover it from. I'm struggling to find a whole NAND dump on the web that I can download and try out, just individual firmware upgrades which I read aren't enough for a complete recovery.

Any suggestions ? Not sure what to do..
 

Offline aijiiTopic starter

  • Newbie
  • Posts: 3
  • Country: au
Re: Fixing a borked Hantek DSO5102P
« Reply #1 on: February 21, 2016, 11:30:15 pm »
Bump - are there any owners of a dso5102p that would be able to help me out please ?

would be much appreciated.. haven't heard anything back from Hantek
 

Offline supercilious

  • Contributor
  • Posts: 41
  • Country: gb
Re: Fixing a borked Hantek DSO5102P
« Reply #2 on: February 23, 2016, 02:33:39 am »
Check your PMs
 

Offline jcbmca

  • Newbie
  • Posts: 1
  • Country: ar
Re: Fixing a borked Hantek DSO5102P
« Reply #3 on: January 04, 2023, 01:43:39 am »
hi aijii, i have the same problem with my Hantek DSO5102.
Were you able to repair your DSO5102,
Could you help me with mine? thank you
 

Offline DenCraw

  • Contributor
  • Posts: 41
  • Country: es
Re: Fixing a borked Hantek DSO5102P
« Reply #4 on: February 24, 2023, 01:32:02 pm »
did you solve it?
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf