Hantek6022API: Fix erased EEPROM #395
-
EDIT Ho-Ro: I tried program Scopevis.py for plotting image, encountered error of (attribute error and segmentation fault) when the device is connected and reconnected during program run.This fault was attempted by running reset_eeprom_6022.py.As it was working, the code was appended with scopevis.py,However when i runned the new code the epprom was reseted partially as result the Hanatek is not reponding to basic program. In order to make Hantek workable, it is required to reprogram it(resetting of its EEPROM bits). Looking forward for your guidance. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 9 replies
-
Who told you to do so?
How do you know this? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Thank you for your valuable reply:
2.I had tried another suggested method to fix Where did you get the info to use this tool, who told you to do so? |
Beta Was this translation helpful? Give feedback.
-
Yes it is detected after unplugging and replugging.
…On Wed, 14 Feb, 2024, 7:16 pm Martin, ***@***.***> wrote:
Is it detected also after unplugging and replugging?
—
Reply to this email directly, view it on GitHub
<#395 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQZS7LSPL6LW2EKJCTRGQJTYTS55BAVCNFSM6AAAAABDEVAZSCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DINRWGAYTO>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the remark 😊
I will take care of the above mentioned points.
1.Will not use reset_eeprom_6022.py file,unless required.
2.Will never try to execute *.o files .
…On Wed, 14 Feb, 2024, 9:27 pm Martin, ***@***.***> wrote:
Two more remarks:
I wanted to refresh same graph so, I used the code of reset_eeprom_6022.py
in while along with matplotlib function.
Ok, you have a lessons learned:
*DO NOT USE reset_eeprom_6022.py UNLESS YOU KNOW WHAT YOU ARE DOING!*
fx2upload.o (removing .o extension) while executing command
NEVER try to execute *.o files. These are *object* files that cannot be
executed.
You link them to the startup and libraries to create the *executable*
file (without any extension) - but that's just a convention with no
technical necessity. You can call it whatever you want, but you create
maximum confusion.
—
Reply to this email directly, view it on GitHub
<#395 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQZS7LTXMATCII2U3DI2VT3YTTNGDAVCNFSM6AAAAABDEVAZSCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DINRXG4ZTQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Hi @Ho-Ro as earlier discussed, I'm working on the example program scopevis.py. I have two queries regarding the same. 1.scopevis.py runs properly for channel-1 but after configuring it for channel-2 according to the lib file PyHT6022.LibUsbScope.I am unable to plot a graph for channel 2.
Looking forward to your help and guidance. |
Beta Was this translation helpful? Give feedback.
Ok, I see two issues
0x04B4/0x8613
come directly from the FX2 chip when no valid EEPROM is seen. OH needs the Hantek values (0x04B4/0x6022
for DSO6022-BE, or0x04B4/0x602A
for the -BL variant).Then you can give the dangerous script
reset_eeprom_6022.py
another try, but make sure that the fileeeprom_6022.dat
is in the same directory.Another posibility to fix the EEPROM content is to use my fx2…