Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Clocks Forum Discussions

dratte
Level 1
Level 1
First solution authored First reply posted First question asked

We have recently switched to in-house programming of our clock chips rather than having them pre-programmed by distribution prior to shipment.

My JEDEC file for the CY22381 was created with CyberClocks R3.10.00. When we use this file with our Xeltek SuperPro 7500 programmer we get an error that the "device ID is not correct - programming failed" (see log below)

In speaking with Xeltek they examined the JED file and found no errors. They indicated that they have heard similar reports some other customers and it was resolved after consulting with the IC manufacturer.

I have also regenerated the file with the current version of CyberClocks 3.21.00 and the resulting jedec file is a binary match. 

Not sure where to go from here.

08:57:56.627   Loading File X:\CY22381F_BF_Clk.jed
08:57:56.637   0, File Type:Jed, Load mode:0, Buffer offset:0, File offset:0
08:57:56.754   Load File Success!
08:57:56.799   Calculating checksum...
08:57:56.806   Type:Pld
08:57:56.811   Buffer checksum(0):0x00000B65
08:57:56.826   Device Checksum: 0xB65
09:14:51.659   Calculating checksum...
09:14:51.665   Type:Pld
09:14:51.670   Buffer checksum(0):0x00000B65
09:15:37.827   Send PAR...
09:15:38.240   Send PAR OK
09:15:38.247   Send ALGO...
09:15:38.669   Send ALGO OK
09:15:38.676   Send FPGA...
09:15:39.100   Send FPGA OK
09:15:39.111   Send Command
09:15:40.526   Batching...
09:15:40.590   Programming...
09:15:40.735   Device ID doesn't match
09:15:41.317   Program failed!(1)
09:15:41.324   Address:00000000
Chip data:00000000
Buffer data:00000000

 

0 Likes
1 Solution
dratte
Level 1
Level 1
First solution authored First reply posted First question asked

This is resolved. It was that the program was generated as commercial but the device was industrial. Updating the program to industrial allows it to program correctly.

Also, a binary diff of the output changes the file by a single bit, presumably the device ID.

View solution in original post

0 Likes
4 Replies
PradiptaB_11
Moderator
Moderator
Moderator
500 replies posted 250 solutions authored 250 replies posted

Hi @dratte ,

We do not have enough info to comment on the issue fully. Can you share the JEDEC files with us, also what program specifications is followed and what is the procedure followed by the software. Potential issues can be as below

1) The JEDEC and device temperature grade do not match. The device might be a Industrial device and the JEDEC file can be for a commercial one.

2) The programming specs followed are not suitable to the device.

3) The software is expecting a different device ID, this depends on the software and need to check what value the programmer is expecting. 

Thanks,

Pradipta.

0 Likes

Jedec file attached inside zip file.

Device is CY22381FXI

I can't tell from the .jed file which device is the intended device (commercial or industrial).

0 Likes
PradiptaB_11
Moderator
Moderator
Moderator
500 replies posted 250 solutions authored 250 replies posted

Hi @dratte ,

It is difficult to say whether JEDEC is Industrial or not. I see you were able to generate the Cyber Clocks software to generate a similar file from the newer version. The Cyber Clocks allows for the selection of Commercial or Industrial grade. Can you generate two JEDEC files one for commercial and one for Industrial and check if any of the JEDEC files resolves your issue. If it does not resolve the issue we can rule out point 1 from the potential reasons list and move to other points for the debug. In the interim can you also check with the software developers (software you are using to program the devices) as to how exactly the device ID is checked. (For example in our software one device ID is picked from the JEDEC file and matched with the device ID read from the adapter board used to program the device. If a similar concept is being used there we can check if the JEDEC file/programmer board has a similar ID or not )

Thanks,

Pradipta.

0 Likes
dratte
Level 1
Level 1
First solution authored First reply posted First question asked

This is resolved. It was that the program was generated as commercial but the device was industrial. Updating the program to industrial allows it to program correctly.

Also, a binary diff of the output changes the file by a single bit, presumably the device ID.

0 Likes