Programming similar parts with different Device ID

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

cross mob
GrCa_1363456
Level 6
Level 6
50 likes received Beta tester First comment on KBA

What are some options to program similar versions of the same chip in a production process?

Scenario 1: A system can be built using a slow 67 MHz capable CY8C5268LTI-LP030, or for an upgrade, a fast 80 MHz capable CY8C5288LTI-LP090. How can these two parts be programmed automatically in a production line? Can the same .hex file be used? Can the clock tree be selected based on the Device ID?

Scenario 2: A system can be built using a device with embedded 32, 64, 128, or 256 KB Flash by selecting CY8C5265LTI-LP050, CY8C5266LTI-LP150, CY8C5267LTI-LP089, or CY8C5268LTI-LP030. How can these parts be programmed automatically in a production line? Can the same .hex file be used?

Can a field within the .hex file be used to select memory size of part, maybe by comparing to Device ID?

If it's not possible to create a dynamic program that can adjust to the specific part, Are there any programmers that can read Device ID before selecting which .hex file to use for programming? 

Whe creating a .hex file, can PSoC Creator be setup to create multiple .hex files to support all potential configurations of a part?

Greg

0 Likes
1 Solution
Rakshith
Moderator
Moderator
Moderator
250 likes received 1000 replies posted 750 replies posted

Hi Greg, 

It is not recommended to use a hex file of one device to program another device, especially in the production environment. Please recompile the project by selecting the appropriate device. You could also maintain multiple copies of the project for each device.

Programming a different hex file will void the warranty on the device and you would not be able to avail the warranty-related services.

If it's not possible to create a dynamic program that can adjust to the specific part, Are there any programmers that can read Device ID before selecting which .hex file to use for programming? 

The current programming tools do not support this functionality. However, you can use the example scripts provided in this directory - <PSoC Programmer Installation Directory>\Examples\Programming\PSoC3_5\SWD\Python_Ex as a reference to implement the functionality based on your requirement.

Whe creating a .hex file, can PSoC Creator be setup to create multiple .hex files to support all potential configurations of a part?

Unfortunately, a PSoC Creator project cannot be configured to generate hex files for multiple targets simultaneously.

Thanks and Regards,
Rakshith M B

View solution in original post

0 Likes
1 Reply
Rakshith
Moderator
Moderator
Moderator
250 likes received 1000 replies posted 750 replies posted

Hi Greg, 

It is not recommended to use a hex file of one device to program another device, especially in the production environment. Please recompile the project by selecting the appropriate device. You could also maintain multiple copies of the project for each device.

Programming a different hex file will void the warranty on the device and you would not be able to avail the warranty-related services.

If it's not possible to create a dynamic program that can adjust to the specific part, Are there any programmers that can read Device ID before selecting which .hex file to use for programming? 

The current programming tools do not support this functionality. However, you can use the example scripts provided in this directory - <PSoC Programmer Installation Directory>\Examples\Programming\PSoC3_5\SWD\Python_Ex as a reference to implement the functionality based on your requirement.

Whe creating a .hex file, can PSoC Creator be setup to create multiple .hex files to support all potential configurations of a part?

Unfortunately, a PSoC Creator project cannot be configured to generate hex files for multiple targets simultaneously.

Thanks and Regards,
Rakshith M B
0 Likes