Hello,
On 04/05/16 16:16, Uwe Hermann wrote:
>> And also included de firmware:
>> $ ls -l /opt/git-repos/openhantek/fw
>> total 20
>> -rw-r--r-- 1 root root 14042 Oct 5 2015 hantek6022be-firmware.hex
>> -rw-r--r-- 1 root root 2304 Oct 5 2015 hantek6022be-loader.hex
>
> This is not the correct firmware. For 6022BE we have an extra file
> (hantek-6022be.fw) in the git version of sigrok-firmware-fx2lafw repo
> (not part of any tarball release yet):
>
> http://sigrok.org/gitweb/?p=sigrok-firmware-fx2lafw.git;a=summary
>
> For the 6022BL there's no such file yet, but it would be a slight
> modification of the 6022BE file with the CTL0/2 change I mentioned.
>
> The files you mention above are not meant to be used with libsigrok and
> if they happen to work (a little) that's pure coincidence.
Yes, I had already guessed this wouldn't work, it was just an experiment.
I already build the latest sigrok-firmware-fx2lafw snapshot and I have
the firmware already installed at /usr/share/sigrok-firmware. I also
installed the udev rules z60_libsigrok.rules, adapted to 6022BL:
# Hantek 6022BE
#ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="6022", MODE="664",
GROUP="plugdev", TAG+="uaccess"
#ATTRS{idVendor}=="04b5", ATTRS{idProduct}=="6022", MODE="664",
GROUP="plugdev", TAG+="uaccess"
# MyMod Hantek 6022BL
ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="602a", MODE="664",
GROUP="plugdev", TAG+="uaccess"
ATTRS{idVendor}=="04b5", ATTRS{idProduct}=="602a", MODE="664",
GROUP="plugdev", TAG+="uaccess"
once that my 6022BL, before the firmware upload:
$ lsusb
Bus 001 Device 009: ID 04b4:602a Cypress Semiconductor Corp.
But I can't understand how the firmware is uploaded when the device is
connected. It is not by udev rule like in the openhantek case that has a
RUN command to do it. And there isn't any daemon, is there? And
libsigrok isn't running yet, is it?
So, where is it done?
I would like to upload the firmware to test what you said about the
CTL0/2 change. After all, after loading the firmware, 6022BL has exactly
the same id's of the 6022BE:
$ lsusb
Bus 001 Device 010: ID 04b5:6022 ROHM LSI Systems USA, LLC
So, shouldn't it behave exactly the same?
JSS
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
