Products > Test Equipment

Hacking the DSO2X1X

<< < (132/134) > >>

Aldo22:

--- Quote from: nokin on September 30, 2024, 10:59:45 am ---I even didn't believe in its measurement results

--- End quote ---

What measuring range/type are you talking about?
I actually find it quite accurate wherever I can check it.
E.g. here a few days ago.

Up to 20MHz I think it's quite OK.
Above that I don't really have a reference.
I wouldn't believe the amplitude at 100MHz either, but I'm not interested in that anyway.  ;)

kokodin:
Hello, i been mocking around my scope and i would like to share, my stupid discoveries.

I made myself 4 transistor logic level shifter placed it as a hat on ch341a programmer in ttl mode, and connected 3 wires to the scope pcb. GND to D2 , rx and tx lines to one pad of resistors r51 and r49. I set terminal to 115200 and listen. And uboot showed up with the main console right after.
And since i am using real terminal not the sideloaded usb one i have access to front usb port.

Things i was able to confirm so far is thet usb hub support is fully implemented. and most of usb devices is recognized.
you can even go this way and copy things from usb flash drive onto the runing scope or out from mnt/udisk where most recently connected usb disk is mounted, inserting 2 unmount first and mount the new one in it's place.
sadly the thinkg i was hoping the most didn't work
Usb network card is recognized as usb device but is not assigned as network interface.

I might try pluging in more things and see if the scope knows what they are.

DavidAlfa:
We know. This kernel lacks networking and supports very few USB drivers, remember this is an embedded device with only 64MB of ram.
You have the kernel sources, you can build your own and test.
You also have fully configured Virtualbox machine so you don't have to mess with dependendies and such.

kokodin:
Yes i know. with the virtual machine and all it is very generous of you and people who helped. It is not very self explanatory to a person who don't know what to do with it though. For me it looks like just another desktop linux with no idea how it works, not to mention how to compile a source code.

I am just happyly poking around learning things, run top in the bacground , not changing anything. I was panicking that my scope was broken from the factory because back usb was breaking up but i figured out that it was just faulty cable provided with my scope, and well got caried away. I should check it first, but oh well it was new cable.

As for ram, 64mb is quite a lot, my first computer had 1mb, and scope doesn't even use half of it, cpu though it should be faster as default because buttons on main panel works all the time instead of almost half the time you press them without oc.

I am old stupid and have no idea what i am doing, best combination. If i learn how to compile things maybe i be able to run them. For now i am just happy with hacking in terminal old fashioned way without taking entire scope apart and repopulating the max232 circuit, because i presume those 2 pullip resistors (rx13 r187) are on the bottom, i can't find them on top. And for stupid fun of knowing what happens if i plug things in i just plug them in.
And i am fully aware most of it was done before, for god sake this scope has some 2 years of good hacking history.

DavidAlfa:
You need some background to do this. Just like trying to launch a rocket into orbit, there isn't a magic please work button  :).
But that VM has everything setup already so you won't need to install everything.
Also I fixed the kernel sources to compile there without major hassle - just follow the instructions in the kernel sources readme.
I'm not a programmer, let alone a Linux kernel dev.
So that's where I got and where I decided to stop, realizing custom kernels won't fix all the issues this device has.

Basically you only need to download and unpack the kernel sources and apply "fix_arm-linux-gnueabi.tar.bz2" (Extract to the same folder, overwriting everything).
To add drivers and other functionalities, open a console in "linux" folder, run "make menuconfig", do whatever changes you need and compile afterwards.
You can search using the "/" key in your numeric pad, for example "Network", it will show the path and the description of all matching entries.
When browsing the menu, you can get a description of any item by typing "?".
To build the kernel go to linux folder and run "build.sh" (./build.sh from the terminal).
The files will be placed in the "build" folder next to the others (linux, uboot, etc).

I found a script I made when I was testing this, which I'm attaching (For Windows!). Make sure FEL drivers are installed as stated in the FAQ.
Place "uImage" and "hantek_dso2dxx.dtb" into "test" folder, then:

flash_ori.bat: Flash the original files.
flash_kernel.bat: Flash the test kernel.
flash_kernel_dtb.bat: Flash the test kernel and dtb (Normally not required).
You can't break anything, if it doesn't work just run flash_ori.bat.

As always, before doing anything, make sure you did a backup using Dsoflash.

Edit: I forgot to add some required binaries to the zip file. Fixed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod