Closed usern1983 closed 6 years ago
thanks for the detailed report. @OliverHaag knows that part better. But it seems the model is not detected right. The 2250 is actually supported. You also have usb read/write access as far as I can see (at least if SELINUX, AppArmor or posix ACL is not interfering our communication).
You should notice that dso udev rules points to a file named dso2550-firmware.hex not dso2250x86_firmware.hex. Update 90-hantek.rules or rename you hex file. Also if you are extracting x86.sys for x86 systems, and use 64.sys (that is not supported by current extractfw) for 64 systems.
You should notice that dso udev rules points to a file named dso2550-firmware.hex not dso2250x86_firmware.hex. Update 90-hantek.rules or rename you hex file.
It's clear [Это понятно].
Also if you are extracting x86.sys for x86 systems, and use 64.sys (that is not supported by current extractfw) for 64 systems.
I thought so [ я так и думал]. is there any way to get the x64 firmware? [Есть ли способ получить x64 прошивку?]
I didn't dig into firmware extractor but probably there is a way to extract x64 firmware, the current software simply don't know how to do it. For now you can workaround this installing and compiling this program in x86 arch, that might get you some work (and a lot of libraries to install).
Now I use a vbox+win7x64. It is surprising that a guest I bring usb device after use udev (which firmware x86) and win-native program works great. We must try chroot32.
[Сейчас я использую vbox+win7x64. Удивительно, что гостю я передаю usb устройство после работы udev (а это прошивка x86) и родная win-программа прекрасно работает.
Надо попробовать chroot32.]
=======my_OS: http://www.calculate-linux.ru/ ================================
я изменил файл udev:
=========without udev rule for 2250========================================
http://www.hantek.com.cn/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO2000%2fDSO2250_Driver.zip