| Products > Test Equipment |
| New Hantek DSO2X1X models? |
| << < (349/388) > >> |
| DavidAlfa:
Better copy dso_builder to c:\cygwin64\home\your_user. Then just open the cygwin terminal and do cd dso_builder. Yeah this will never work under Windows, that's why cygwin is used in first place! Why the mess if we could simply run it in windows? :). It's a tool that let us run linux stuff without installing a Linux VM or second OS. Will add this to the readme, but let me say that if you're struggling with this, what you're going to play with won't be any easier! |
| carlonb:
--- Quote from: DavidAlfa on December 27, 2023, 11:10:39 am ---Better copy dso_builder to c:\cygwin64\home\your_user. Then just open the cygwin terminal and do cd dso_builder. Yeah this will never work under Windows, that's why cygwin is used in first place! Why the mess if we could simply run it in windows? :). It's a tool that let us run linux stuff without installing a Linux VM or second OS. Will add this to the readme, but let me say that if you're struggling with this, what you're going to play with won't be any easier! --- End quote --- Tanks for the hint. Regarding the readme, it is not necessary to explain why cygwin is used and why it doesn't work with Windows, it would be enough just indicate that (Windows Environment): 1) Install cygwin with the gnupg package (Select Packages -> Not installed -> Search: gnupg -> Change gnupg from "skip" to latest version). 2) The dso_builder "extract.sh" file must be copied in the directory where the "dso3kb_MyPackage.upk" file to be extracted resides. 3) Open the cygwin terminal and from the $ prompt with CD move to the folder where the "dso3kb_MyPackage.upk" file to extract resides (point 2). NOTE: The path must not contain spaces and use "\" separators instead of the standard windows "/". 5) From the $ prompt type ./extract.sh "dso3kb_MyPackage.upk" to execute the extraction. I definitely have no intention of playing with these scripts, this is just curiosity. I will limit myself to using what you have already prepared only when everything is clear to me. I don't usually operate on things I don't know about. Thank you for your work and as soon as I receive my DSO I will definitely have more questions (after re-reading everything on the FAQ page again). |
| DavidAlfa:
The readme in every package and the giant FAQ aren't clear enough? :-// |
| carlonb:
@DavidAlfa, Ohhh, don't worry, you have done a huge job to improve this scope. It's probably just my problem since (Improving the Hantek) is a new topic for me. Ciao |
| carlonb:
Today arrived my dso2c10, the strange thing is that it arrived via a courier appointed by Amazon??? I kept an eye on the tracking of the Spanish Aliexpress supplier but it was always in transit between Spain and France. I was convinced of a serious delay due to the Christmas holidays but unexpectedly it was delivered today with just one day delay compared to the forecast, total of 15 days from the order. :)) Freshly turned on out of the box: SW version: 1.0.3.0.0(230327.00) FW version: 3205 PCB No.: 003.002.001.000.000.000.000.000 I soon made the backup with dso3kb_backup_builder.upk: All OK. DSOflash: After connecting the USB cable to the back, turning on the DSO with the FEL button pressed, Windows 10 automatically installed its own driver (without asking me) but the name was "undefined device #1". In any case I started Zadig and saw that USB ID:1f3a and PID:efe8 were correct, so I installed the driver. Then I launched read.bat and after about 26 minutes it completed the backup. Now I have a doubt, do you think that this backup is correct? I attach the screenshot about it. If you confirm it I will proceed to find out if the conversion to 2D15 gives me the AWG. Bye and thanks. |
| Navigation |
| Message Index |
| Next page |
| Previous page |