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

PSoC™ 5, 3 & 1 Forum Discussions

Mikes6032
Level 1
Level 1
First reply posted First question asked Welcome!

We use your CY8C3446LTI-085. We recently received a batch of these parts, with the same major part number as just stated, that will not flash. Looking for guidance as to why.

Good parts stamped as follows:
CY8C3446LTI-085
1401 A 04
CYP 601225
TWN

Bad batch stamped as follows:
CY8C3446LTI-085
1430 A 04
CYP 648315
PHI

0 Likes
1 Solution
AlenAn14
Moderator
Moderator
Moderator
500 replies posted 100 solutions authored 250 replies posted

Hi @Mikes6032 ,

Apologies for the delay on the response for this query.

I checked with the internal team about the device with the Silicon ID of 0E_05_50_69 and seems like you received a set of engineering samples which are not suitable for productions purposes from your distributor.

I would recommend you to contact your distributor and get a replacement for these devices as the parts with the Silicon ID of 1E_05_50_69 are the authentic devices that is to be used for production.

Warm Regards
Alen

View solution in original post

0 Likes
9 Replies
alintz
Level 1
Level 1
First reply posted Welcome!

Further information on the same issue. See attached photos of markings.

When trying to connect with MiniProg3 and PSOC Programmer, we get:

| Programming Terminated
ERROR! --> | The hex file does not match with the acquired device, please check the device
Device set to CY8C3446LTI-085 at 8:15:58 AM | 65536 FLASH bytes
Device Family set to CY8C3xxx at 8:15:58 AM |
| Automatically Detected Device: CY8C3446LTI-085
| JtagID: 0E 05 50 69
Program Requested at 8:15:57 AM |
Power On at 8:15:50 AM | MiniProg3/1229DD0014BA
Successfully Connected to MiniProg3/1229DD0014BA at 8:15:42 AM | MiniProg3 version 2.05 [3.11/2.10]

In Creator, with MiniProg3, Select Debug Target, we get:  "The device was recognized, but PSOC Creator does not support using it at this time."

The JtagID appears correct for the CY8C3446LTI-085. We tried some Command Line Interface commands, and we could acquire the device, and read the JtagID again, but we didn't know how else to troubleshoot. We want to  determine if this is counterfeit, or protected memory, or some other problem.

(Yes, this batch of parts was purchased from a broker, who has supplied good parts in the past.  But we are desperate to get parts now.)

 

0 Likes

Hello.

"The JtagID appears correct"
Does the JTAG ID of the new batch match the JTAG ID of the previous batch?

If yes, then PSoC Programmer is pointing to the wrong hex file (according to the error message).

0 Likes

Yesterday I thought the JtagID was identical. But, on double-checking today, I see this when I program an old batch PSOC:

| Programming Succeeded
| Doing Checksum
| Doing Protect
| Programming of Flash Succeeded
| > Transfer rate: 32.56 KB/sec. 64512 bytes transferred (252 blocks x 256 bytes) in 1935 ms
| Programming of Flash Starting...
| Erase Succeeded
Device set to CY8C3446LTI-085 at 8:54:19 AM | 65536 FLASH bytes
Device Family set to CY8C3xxx at 8:54:19 AM |
| Automatically Detected Device: CY8C3446LTI-085
| JtagID: 1E 05 50 69

The first byte of the JTAGID is 1 for a good PSOC, and 0 for a bad PSOC. But, Programmer resolves that JTAGID to the same PSOC device CY8C3446LTI-085.

0 Likes
alintz
Level 1
Level 1
First reply posted Welcome!

I learned how to read all of memory from Programmer by hitting F7. When I do that, I get :

Good board: User NVL Array ID: 80 Data: 00 00 00 05

Bad board: User NVL Array ID: 80 Data: 00 00 00 0B

If I am reading the datasheet properly, that means the good board is set for SWD debug and ECC disabled.

And the bad board is set for JTAG debug and ECC enabled.

Our Creator project was set to for ECC enabled.

 

0 Likes
alintz
Level 1
Level 1
First reply posted Welcome!

One more fact. These PSOC were assembled onto PCBs that has been in production without change for at least 2 years. One PSOC was desoldered and a CY8C3446LTI-085 from an older lot was resoldered. And the board programmed normally, suggesting that this lot of PCBs is good, but the PSOC are not good. We have replacement PSOC on order, but who knows how long it will take to receive.  We just want to determine if there is anything we can do to make these usable, or if they are just totally useless and must be removed.   

0 Likes
Mikes6032
Level 1
Level 1
First reply posted First question asked Welcome!

We have CY8C3446LTI-085 chips with JTAG IDs (0E055069) that are contradictory to the information provided by Infineon (see attached image; 1E055069). What is going on with these chips? And how do we a) fix them so they flash or, b) tell our fab shop what to look (or not look) for?

0 Likes
AlenAn14
Moderator
Moderator
Moderator
500 replies posted 100 solutions authored 250 replies posted

Hi @Mikes6032 ,

I am able to understand the issue you are facing and the cause is because you have selected for the CY8C3446LTI-085 which has the ID "1E_05_50_69".

AlenAn14_0-1653030082056.png

Because of this, the .hex file is generated using this ID instead of the id "0E_05_50_69" reported by your new batch of devices.

Because of this mismatch, PSoC Programmer prevents you from programming your hex file into the new batch of devices.

I will look more into this and get back to you on the same.

Warm Regards
Alen

0 Likes
AlenAn14
Moderator
Moderator
Moderator
500 replies posted 100 solutions authored 250 replies posted

Hi @Mikes6032 ,

Apologies for the delay on the response for this query.

I checked with the internal team about the device with the Silicon ID of 0E_05_50_69 and seems like you received a set of engineering samples which are not suitable for productions purposes from your distributor.

I would recommend you to contact your distributor and get a replacement for these devices as the parts with the Silicon ID of 1E_05_50_69 are the authentic devices that is to be used for production.

Warm Regards
Alen

0 Likes
DennisS_46
Employee
Employee
50 solutions authored 50 sign-ins 100 replies posted

Mike:
Further checking by Failure Analysis group in Product Engineering in San Jose indicates that the bad parts
were from a scrapped lot. Somehow, the wafers got out of the factory somehow and were not packaged at
one of our authorized contractors. This is now being investigated by our counterfeit investigation team.
---- Dennis Seguine, PSoC Apps Engineer

0 Likes