Announcements

Help us improve the Power & Sensing Selection Guide. Share feedback

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

cross mob
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Dear Cypress,

 

One of our customer has been using CY8C4025LQI-S412,

but because of availability of the device,

they wonder if they can use CY8C4045LQI-S412

with the binary file of CY8C4025LQI-S412.

 

I would think that the usual programmer will refuse to program a 4025 binary to 4045.

But I wonder if there is/are way/method to apply  CY8C4025LQI-S412 binary to CY8C4045LQI-S412.

 

Best Regards,

8-Jun-2021

Motoo Tanaka

0 Likes
1 Solution
BiBi_1928986
Level 7
Level 7
First comment on blog 500 replies posted 250 replies posted

Hello Motoo.

I think it should be possible using customized HSSP.  The customization needs to ignore the Device ID during Device Acquire.
App Note AN73054, shows KIT-059 as SWD HSSP programmer.
KBA93541, shows KIT-049-42 as HSSP programmer, but could be adapted for other KITs.

Another somewhat un-documented method, is Mass Storage Programmer using KIT-059.  Oddly enough, this mode does not require F-Ram to be installed (documented in KIT-044 and KITprog pdf's).  It works on CY8C4013 (8k flash), so might work on other devices.  However, I suspect you'd need to alter the binary for the target Device ID.

Here are things to investigate:
The number of flash bytes per row need to be similar in each device (otherwise FLASHing and emEEPROM might not work properly).

The default CPU clock speed might be different.

The PLL constants might be different.

If target s/w reads Device ID, that would break.

If target s/w performs checksum, that could break.  Not likely, but possible.

I think this gives you a starting point.

I appreciate all your contributions to the community.

regards,
Bill

View solution in original post

2 Replies
BiBi_1928986
Level 7
Level 7
First comment on blog 500 replies posted 250 replies posted

Hello Motoo.

I think it should be possible using customized HSSP.  The customization needs to ignore the Device ID during Device Acquire.
App Note AN73054, shows KIT-059 as SWD HSSP programmer.
KBA93541, shows KIT-049-42 as HSSP programmer, but could be adapted for other KITs.

Another somewhat un-documented method, is Mass Storage Programmer using KIT-059.  Oddly enough, this mode does not require F-Ram to be installed (documented in KIT-044 and KITprog pdf's).  It works on CY8C4013 (8k flash), so might work on other devices.  However, I suspect you'd need to alter the binary for the target Device ID.

Here are things to investigate:
The number of flash bytes per row need to be similar in each device (otherwise FLASHing and emEEPROM might not work properly).

The default CPU clock speed might be different.

The PLL constants might be different.

If target s/w reads Device ID, that would break.

If target s/w performs checksum, that could break.  Not likely, but possible.

I think this gives you a starting point.

I appreciate all your contributions to the community.

regards,
Bill

MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Dear Bill-san,

Thank you very much for your information/suggestion!

Although there seem to be plenty of check points to be safe,

those methods seem to be promising.

I will inform the customer this information.

Still I would recommend them to use re-compiled target specific binary, though 😉

Best Regards,

8-Jun-2021

Motoo Tanaka

0 Likes