Hantek 6254BD 250MHz 1GSa/s PC/USB DSO

[Microcheap]

I only have FW for fpga, attached to this message. Not yet figured out how to read cy7c68013 eeprom.

The cypress chip has no internal eeprom, the FW is stored in a eeprom chip 24LC64 (IC U807) on the other side of the board, and it is loaded to the MCU during power up.
Which version of the HT6xx4 do you have? If you can damp yours EEPROM content and post it here it would be nice.

There is no hardware difference among the models, the BW is limited in software.

[Neekeetos]

If you can damp yours EEPROM content and post it here it would be nice.

Attached to my previous message, so you potentially could find out which my scope model is...

Just wonder if anybody can upload the eeprom from 6254bd model

[Microcheap]

Just wonder if anybody can upload the eeprom from 6254bd model

That is what I asked. I have the eeprom from a 6074bc and I would like to compare it to the 6254bd model, maybe the BW configuration is in there as the hardware are the same.

[Neekeetos]

Spent some time reversing pcb,  so here are my recent findings regarding fpga pinout:

Code: [Select]

// ADC  HMCAD1511
CSn B2
SDATA A2
SCLK B3
RESETn A3
PD C3

DP1A B5
DN1A A5
DP1B B6
DN1B A6
DP2A C7
DN2A A7
DP2B B8
DN2B A8
LCLKP C9
LCLKN A9
FCLKP B10
FCLKN A10
DP3A  C11
DN3A  A11
DP3B  B12
DN3B  A12
DP4A  C13
DN4A  A13
DP4B  B14
DN4B  A14

// DAC902
CLK E16
PD  J14

DB11 F15
DB10 F16
DB9 G14
DB8 G16
DB7 H15
DB6 H16
DB5 J16
DB4 K15
DB3 K16
DB2 L16
DB1 M15
DB0 M16

// leds
nLED_green B1
nLED_red C1

// out square 1k
OUT1K E3

// main fpga clock 24M coming from quartz oscillator near cypress.
CLK24M_IN K14
// ADF4360 ref clock in 10M , fpga outputs this....
CLK10M_OUT E15

// OFFSET PWM  1.9khz for channels 1-4
OFFSET_CH1 T13
OFFSET_CH2 T15
OFFSET_CH3 R16
OFFSET_CH4 T14

// ADF4360/HC595 SPI
CLK/SRCLK B16
DATA/SER D16
RCLK C16
LE B15
MUXOUT E12

// J7 socket
J7_0 K1
J7_1 J1
J7_2 F1
J7_3 E1
J7_4 E2
J7_5 D1

// CY7C68013A
CY_NRST G3
SLRD F3
SLWR F4
SLOE K2
PKTEND G1
FIFOADR1 H2
FIFOADR0 H1
FLAGC M4
FLAGB N4
FLAGA P4
IFCLK F2
INT0 L3


Managed to run DAC , but the main part which is pll init and adc read is not yet done.

[Appocalypse_br]

Hey many thanks for the firmware, i am little noob in these i2c field can any of you guys help me trough the process of backup and write the firmware in my unit, many thanks, if you have some link to tutorial video or make a quick one will be great.
(mine is bricked itself no red light blink anymore)
thanks a lot.

[EDIT]
Just found these hey great work!
https://sigrok.org/wiki/Hantek_6022BE

https://sigrok.org/wiki/Hantek_6254BD (seems same of 6xxxBC mine 6104bc is same)

https://sigrok.org/wiki/Hantek_6052BE

[Neekeetos]

Slight update on HW initialization details. The PLL is initialized every time scope software starts and never changes. There is a lock output from ADF4360 (muxout) connected to fpga pin , but it is not used. Init sequence is as follows:
Full init sequence

Word 1

Word 2

Word 3


There is also a chain of hc595 registers sharing SPI CLK/SRCLK and DATA/SER pins with ADF4360, however RCLK is independent( so as LE on PLL). Each register connects to own oscilloscope channel sharing the same functions which are :

QH	LPF_ENABLE
QF/QG	ATT2_RELAY
QD/QE	ATT1_RELAY
QC	AC_DC_RELAY
QB	ADC_DRIVER_ENABLE

Some example bus data:


Word 1

Word 2

[eevblogfan1]

I managed to score a 6254BD for $80 on ebay and while I await it to arrive, and cross my fingers I didn't get bamboozled, I decided to research everything I could find about the device, and I found your forum and the hantek support forum in the process. In particular I noticed the below:

Previously, when bricking my scope, I had to ask Hantek for a file (DSO6106BD20160601.iic), but I'm unable to redistribute it since I haven't got permission.

And I also noticed a person on Hantek support forum had an issue with the usb device having the wrong id

I have a problem with the Hantek6254BD oscilloscope. The DRIVER does not install -- but the actual scope software does install.
Can you supply the correct driver? I downloaded the latest software from the Product page for Hantel 6004 page.
Description:
The PID and Device ID appear to be wrong...
So the Scope software installs -- but the driver does not install. If I change the strings to match -- of course the driver is rejected by windows since it does not match the security string in the CAT file.
My device has:
04B5 and 8613 for the two codes -- not the o4B5 and PI_6CDE
My string in the USB identifier -- read from the SCOPE shows as
USB\VID_04B4&PID_8613
Your software is looking for this code.
[Device]
%VID_04B5&PID_6CDE.DeviceDesc% = Section, USB\VID_04B5&PID_6CDE
;for windows 2000 non intel platforms

Which is quite common, so it seems they finally got tired of emailing out that iic firmware to fix usb device issues and their employee Amy just attached it to a to their post in reply.  You have to register to see attachments, but it can be done in less than a minute, I have also attached it to the end of this post.  Perhaps it will help some people out here.  The iic itself seems to be the same for 0x13FD bytes as the cy_eeprom_dso6074bc.zip firmware posted by neeketos, but neeketos seems to have additional data beyond that.

Screenshot of forum post and partial file listing


If anybody would like to decode the iic file, one way would be to go to section 3.4.3 Serial EEPROM Present, First Byte is 0xC2 of the manual here.  Although there might be better ways, perhaps sigrok has some utilities that automate the process, I don't really know to much about the project other than it seems they are fx2 gurus.

When I get some more free time, I'll continue investigating and will keep you up to date (even if I spend another 2h organizing my findings and writing this post lol). With some luck, I'll clean up the mess of code I've written and will publish it.

While I am on the topic of rgon's post, did you ever publish anything or do any more investigation work?

[Appocalypse_br]

Hi every one, mine 6104bc bricked it self in normal day to day use, so i desolder the 24lc64 and writed the 6074bc firmware dump provided in this forum. YAY! device is working now!

BUT when i set in milivolts and the relay activates the signals of the channel gets mixed with the others, any clue why that is happening? i will try to program the original firmware back.

Thanks to the users that are helping me.

[Appocalypse_br]

Problem 1
Before writting the original dump back in i tried the program posted above seems to write via EZ-USB.
But when i click the EZ-USB shows the next screen, in that screen i can't click in any button, you guys have any clue why is that?
Maybe because i have the eproom with data in it, the program do not works?
Should i erase the data and try trought the EZ-USB to fix the milivolts problem?

Problem 2
Attached the pictures of the problem.
1x Probe, 100mv div, DC, measure the 2vpp test point (AC no problem)(10x PROBE no problem)

[Microcheap]

I'm not sure if I understood your 2nd problem, but there was a bug in the software version 2.2.4 (the one you are using) that I helped Hantek to identify and that introduced an offset error in the oscilloscope's channels. You need to update the software to Ver2.2.5 or downgrade to version 2.1.36 and run the self-calibration again.

https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=14725&pid=18097&fromuid=26055

[Neekeetos]

The iic itself seems to be the same for 0x13FD bytes as the cy_eeprom_dso6074bc.zip firmware posted by neeketos, but neeketos seems to have additional data beyond that.

Bet this data is calibration and nothing interesting. I tested your version of cypress fw, but i see no changes in features, no functional gen appeared and bw not improved. It seems to me that functional cap is done via different fpga fw for particular models of scope. But, great that there is no need in dedicated programmer for cypress, as it flashes itself via usb....

If anybody would like to decode the iic file, one way would be to go to section 3.4.3 Serial EEPROM Present, First Byte is 0xC2 of the manual here.  Although there might be better ways, perhaps sigrok has some utilities that automate the process, I don't really know to much about the project other than it seems they are fx2 gurus.

The great need in this "anybody" who knows cypress well and can extract info on how fw works. This is due to my findings - fpga eeprom is connected directly to cypress pins , thus could be read and programmed!
Pins are (PD* are cypress port pins ) :

• PD0 : flash_nCS
• PD1 : flash_CLK
• PD2 : flash_SI
• PD3 : flash_SO
• PD4 : flash_nWP

There are also 3 unsoldered jumpers nearby:

• PD5 : R197
• PD6 : R198
• PD7 : R199

[Appocalypse_br]

I'm not sure if I understood your 2nd problem, but there was a bug in the software version 2.2.4 (the one you are using) that I helped Hantek to identify and that introduced an offset error in the oscilloscope's channels. You need to update the software to Ver2.2.5 or downgrade to version 2.1.36 and run the self-calibration again.

https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=14725&pid=18097&fromuid=26055

Ok, but is not an offset problem, i have only proble 3 connected, no input signal in other channels, but as you can see the signal in channel 3 over shoot the screen and affect the other channels. Even in v2.2.5 screenshot down.

[Microcheap]

...

Ah, ok I managed to reproduce the problem. I first thought it could be coupled noise in the inputs but it looks like it just another bug in the software, it happens when using a x1 probe and the vertical scale is set to 100mV or smaller and the signal is >= 2Vpp so it gets out of the screen area.

Not really an issue since that, for a 2Vpp signal, you will have to set the volt/div to a scale greater than 100mV to be able to see the waveform correctly anyway.

[Appocalypse_br]

Yes thanks for the 2.2.5 info, but its a bug confirmed.

[PointLess]

Anyone ran into a problem that 6254 stopped displaying signal waveform in software and solved that? I've already tried restarting/reinstalling/etc, even other PC, still no luck...
I use Windows 10 x64 1909 and latest 2.2.5 software, it shows 6254 connected, turning voltage knob makes relay clicking noises.
Need help badly if anyone knows any suggestions.
I got a eeprom programmer so reading/writing all 24/25/etc eeproms is not a problem.

PS Problem solved. Looks like the 3.3v PWM dc-dc is a weak point in schematics, so changing it to a typical linear LDO 3.3v stabilizer like 1117-3.3 closes the case forever. I was really surprised why they used PWM instead of linear dc-dc because it makes little sense in minimizing noise over power supply lines for such sensitive equipment.

[Hantek]

i have an   Hantek 6254BD 250MHz 1GSa/s PC/USB DSO
can anyone tell me what is the part number of a square tiny chip with 10 leads/legs U38,  seats next to the 2r2 inductor on the right side of the usb port, the metal spring facing up.
  started to get overheated and soon it blew up.
i cannot read the part number. and if you know what it is for please let me know.
thank you

[Microcheap]

The U38 IC is a TPS63000 (marking code BPT). It's a buck-boost converter from TI. You can easily buy it from many sources, it's cheap.

https://www.ti.com/lit/ds/symlink/tps63001.pdf

[Hantek]

thank you very much.

[danman]

There's a recurring loop that does the following:

Code: [Select]

controlWrite(0x40, 179, 0, 0, WEIRD_BYTE_ARRAY) always followed by controlRead(0xC0, 178, 0, 0, 10)


I've managed to load the FX2 firmware into ghidra and the above block seems to be resetting EP buffers and signalling something to PORTA (FPGA?).
I'll keep investigating the code. My device is about to come on Friday.

[danman]

I have really basic opensource python version working here:
https://github.com/danielkucera/pyhantek

Contributions are welcome!

[mrfrenzy]

This looks really promising!

Do you have any roadmap on what is needed to make it usable?
I might want to get a 6254 and try some contributions.

[danman]

I put it aside a little bit because I made the original software work under Wine: https://github.com/danielkucera/hantek-wine-driver



There is a lot of things to discover and implement in the python driver:
- the whole configuration:
  - triggers
  - offsets
  - timebase
  - v/div
  - ...
- calibration
etc, etc,...

There are some hints in the provided SDK with windows .dll but it needs a lot of time and development.

[mrfrenzy]

Thankyou for your effort.

I understand there is quite a lot to be done. I am basically looking for a software alternative that can be automated from the command line to auto start and save measurements from every trigger.
I might get the 6254 and do this temporarily with AutoIT for this project, later if I get time I will try to contribute some testing of different configuration parameters.

[daro19862]

Hello
Is it possible to make the oscilloscope work with pulseview?