Electronic Engineer Discuss

Title: 6254BD SPI Decoder [Print this page]

Author: QMESAR Time: 2021-6-18 20:19
Title: 6254BD SPI Decoder
Dear Hantek Team,
Can you please help me with a document how to use the SPI and I2C Proptocol decoders
I could not find any information in the help file.

If I use my bench Scope with it SPI Decoder it is working prefectly as shown in PIC1
You decoder show some silly binary numbers that make no sense ,

How do I set the decoding to show Hex and the table view also does not show any data when a single capture is done and in Normal mode it shows the incorrced values and as I said I know
what the Hex values should be as I programmed my micro ou output 0xB7 and 0xBB which it does but the Hantek decoder shows some value

[attach]4407[/attach][attach]4406[/attach]

Hope to get some sort of help on this
Thank you
QMESAR

Author: QMESAR Time: 2021-6-21 13:15
Edited by QMESAR at 2021-6-21 13:17

Hi Team

I have now tried everything with the decoder SW it not working correctly .
I have set the triggers to SDA (CH1) and CH2 on SCL and also changed it around this Trigger on SCL(CH2 ) and SDA on (CH1) it always show on the Screen the strange binary values and in the Table view the wrong hex value.
As you will see from the above screen prints the signal itself is correct the Rigol decoder decode correctly and the Hantek decode decode wrongly ,

Can you please assist to get this working I am in the middle of a SPI project for a customer .

Author: amy Time: 2021-6-23 08:27
Please provide the product information to study.
"Help->About"

Author: QMESAR Time: 2021-6-23 13:19
Edited by QMESAR at 2021-6-23 13:24

Dear Amy
Please see screen prints
Question why is the Trigger always on the SCL line I cannot select the trigger on SDA ,if you change the trigger from edge to SPI it auto select the SCL line ?I send photos by email I canot get them to upload
Thank you

Author: amy Time: 2021-6-23 16:56
Refer this to update the FPGA software.

[attach]4415[/attach]

Both the data channel and the clock channel use the same trigger level. Please make the two channels in the same position to try.

Author: QMESAR Time: 2021-6-23 23:52
Title: u
Edited by QMESAR at 2021-6-24 13:34

Dear Amy.

Thank you for the update files However I still have no success ,
I have send you a screen print to your support email as the forum does not allow me to upload photos ,I dont why this is so.
I am sorry that I send you and email

Regards

Author: QMESAR Time: 2021-6-26 15:06
Dear Amy.

Do you think that we will find a solution for this problem.?
Thanks for sharing some info on this

Author: amy Time: 2021-6-29 16:54
Sorry, please wait for some times, I will test and reply this week.

Author: QMESAR Time: 2021-6-29 22:34
Thank you Amy

Author: amy Time: 2021-7-3 10:31

The unit of overtime should be ns, and the software does not show it. Please set the overtime to be greater than or equal to the clock period. Such as 3000ns.

[attach]4421[/attach]

When replying to the post, select "Advanced Mode" to upload the attachment.

[attach]4422[/attach]

Author: QMESAR Time: 2021-7-3 14:12
Edited by QMESAR at 2021-7-5 20:05

Dear Amy.
Thank you this is working in the scope window it shows the correct hex values

However the data in the Table view is incorrcet regardles of the trigger slope (+ or- ) is always shows 7F 80 which as you will notice in the scope
window it is correct B7 BB ,

Can you help me understand how to use the table correctly as if we send a transaction of a number of bytes it is prefered to see the transaction in the Table view
secondly what is the function of the hex control ?
Thank you for all the support I have received from you.
[attach]4426[/attach]

[attach]4427[/attach]

Author: QMESAR Time: 2021-7-7 13:40
Dear Team,

Please can you give some indication to what the issue can be as there is no documentation(manual) for using the SW it hard to understand what to do
this issue is now long time in discussion can we please solve this or tell us that it not working and you will not fix it ,then we buy a new scope from another manufacturer and I do not waste
your time and you do not waste my time

Thank you

Author: amy Time: 2021-7-14 16:12
Sorry, our engineer is solving this problem. Please wait for some times.

Author: QMESAR Time: 2021-7-14 20:18
Edited by QMESAR at 2021-7-14 22:58

Dear Amy.
Thank you very much for your message,
We have new problemn with this scope

,one of our engineers was working with it at a customer location in another city and he was working seriouly
the scope was connceted to the USB for around 4Hours when it stopped to work ,

(1)Pluging the scope into a the PC always result in that windows does  not recognise the scope (note it was working alwways on this PC so drivers are good) .Also no Red Led coming ON

as you see here

I then installed the drivers new on another PC and that still shows unknown device

The Engineer told me that the scope was not hot but had normal temperature as it was working for 4 hours (connected tp USB)
I opend the scope and I do not see any burned componets , as shown on the pictures

[attach]4440[/attach][attach]4441[/attach]


I also tried to connect with the FPGA update tool to connect to the scope the tools reports " No device was found".

[attach]4443[/attach]

It looks to me one of the following
1 - USB chip broken
2 - FPGA is broken
3 Power supply 3.3V is broken

is there away you can help me solve the problem as to send the scope to the factory for repairs cost more that another scope and secondly take a long time
Thank you so much

Author: amy Time: 2021-7-15 16:33
Please check the PID/VID.

Please connect the scope to your computer and right click the unknown device in device manager, select Properties.

And give me a screenshot of the Hardware ID as the following picture.

[attach]4446[/attach]

Author: QMESAR Time: 2021-7-15 18:58
Edited by QMESAR at 2021-7-15 19:10

Dear Amy

Thank you for your asistance much appreciated.
the screen print as requested.

[attach]4449[/attach]

Author: amy Time: 2021-7-16 10:21
Please refer to the attachment to operate.

[attach]4450[/attach]

Author: QMESAR Time: 2021-7-16 12:35
Dear Amy .
Thank you for document and files.

I am not sure what must I do here ,
must I right click and install the win 10 drivers ?
[attach]4454[/attach]

Author: amy Time: 2021-7-16 15:41
Yes. The driver files are in CyConsole folder.

Author: QMESAR Time: 2021-7-16 19:04
Edited by QMESAR at 2021-7-16 19:06

Dear Amy.

Thank you very much, you helped me so much the scope is working as before ,Thank you so much I appreciate your help and support

Question why did it loose the EEPROM Code will this happen again ? if we use it for long period of time like 4 Hour testing periods ?

[attach]4456[/attach]

Author: amy Time: 2021-7-31 09:17
It may be that the power supply of the computer USB port is unstable and the code is lost. It is recommended to connect the red end of the USB cable to a 5V@2A power adapter.
And the new software:
[attach]4489[/attach]

Author: QMESAR Time: 2021-7-31 12:59
Hi Amy.

It may be that the power supply of the computer USB port is unstable and the code is lost. It is recommended to connect the red end of the USB cable to a 5V@2A power adapter.

This makes absolute sense
Thank you for the information I will instruct our people to make sure they use the scope correctly powered ,Also many thanks for the new software much appreciated

Regards

Author: QMESAR Time: 2021-8-1 14:34
Dear Amy.

Thank you to you and the HANTEK team the SPI decoder is working fine now

Should I test the UART and IIC or do you know if your team has tested this also ??

Thank you so much again

Welcome to Electronic Engineer Discuss (https://www.eediscuss.com/)