Products > Test Equipment
Hantek - Tekway - DSO hack - get 200MHz bw for free
tv84:
You can investigate how to recreate something from the FW package but a NAND dump from another device would be the easiest way (or not).
Anybody can do a dump for you using the "classical prehistoric 1.1.6 U-Boot menu". Will take some hours but is perfectly doable.
So you still have 3 partitions:
0x00000000-0x00040000 : "EmbedSky_Board_uboot" OK
0x00200000-0x00400000 : "EmbedSky_Board_kernel" OK
0x00400000-0x03ff8000 : "EmbedSky_Board_yaffs2" ruined
Where is the FW package?
DC1MC:
You can put OK on the kernel partition as well, it boots completely but segfaults when no init is found, I don't have any usable firmware image unfortunately, this is what I'm searching for.
The update images that I could found are just some archives with the scope related apps, no OS that I cold find :'(.
EDIT: If after so much pain this shite MUST have some device specific and irreplaceable calibration file stored in the rootfs instead of EEPROM and without them it won't work I will go Office Space on it !!!
DC1MC:
It seems that there are more partitions that it meets the eye or so so says the U-Boot:
--- Code: ---EmbedSky> mtdparts
device nand0 <nandflash0>, # parts = 7
#: name size offset mask_flags
0: bios 0x00040000 0x00000000 0
1: params 0x00020000 0x00040000 0
2: toc 0x00020000 0x00060000 0
3: eboot 0x00080000 0x00080000 0
4: logo 0x00100000 0x00100000 0
5: kernel 0x00200000 0x00200000 0
6: root 0x03c00000 0x00400000 0
active partition: nand0,0 - (bios) 0x00040000 @ 0x00000000
defaults:
mtdids : nand0=nandflash0
mtdparts: mtdparts=nandflash0:256k@0(bios),128k(params),128k(toc),512k(eboot),1024k(logo),2m(kernel),-(root)
--- End code ---
tv84:
--- Quote from: DC1MC on November 02, 2021, 07:56:05 pm ---It seems that there are more partitions that it meets the eye or so so says the U-Boot:
--- End quote ---
Nice. It's all compatible with what I had displayed and fills the gaps that we had.
I would suggest you dump all the NAND up to 0x00400000. (4 MBytes)
Use "nand dump" or "nand read" and log all the displayed values in the terminal.
That way you have a reference base to verify if all is correct with those parts. Then the only thing missing will be the root FS.
BTW, a long shot would also be: if you are replacing the full root partition, maybe you can use one from a S/N greater than 15000. I mean the limitation for 15000 is for FW updates using only part of the files. Maybe you can get away with a full partition replacement.
DC1MC:
--- Quote from: tv84 on November 03, 2021, 12:09:22 am ---
--- Quote from: DC1MC on November 02, 2021, 07:56:05 pm ---It seems that there are more partitions that it meets the eye or so so says the U-Boot:
--- End quote ---
Nice. It's all compatible with what I had displayed and fills the gaps that we had.
I would suggest you dump all the NAND up to 0x00400000. (4 MBytes)
Use "nand dump" or "nand read" and log all the displayed values in the terminal.
That way you have a reference base to verify if all is correct with those parts. Then the only thing missing will be the root FS.
BTW, a long shot would also be: if you are replacing the full root partition, maybe you can use one from a S/N greater than 15000. I mean the limitation for 15000 is for FW updates using only part of the files. Maybe you can get away with a full partition replacement.
--- End quote ---
Right now I'm willing to try with anything that comes up, if ever...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version