Thats the one im already using
Can you please go to Help > About PSoC Programmer? Provide a screenshot of the dialog box which mentions all the versions so that I can get more clarity on your software setup.
Also, the hex file (poofCID.hex) you are trying to flash, did you create it using PSoC Creator? Which version of Creator do you have?
Please note: You can only flash hex files generated using PSoC Creator in PSoC Programmer.
My dialog box is same as the one you provided, everything is updated
hex was created with psoc creator 18.104.22.16810, two years ago, and it worked fine
i now have 22.214.171.1241 version which is latest,
could it be capacitor issue?
i got a bit high readings 2-4 uF
PSoC Programmer follows the Programming Specification for programming devices. You can find it here.
In Step2, it does a Silicon ID Check where it verifies that the device corresponds to the hex file. It reads the silicon ID from the hex file and compares it with the ID obtained from the target.
For PSoC4, your hex file should read the following values:
But in your case, the detected silicon ID is 0x00 which is incorrect. Can you please verify if you have generated your hex file for the PSoC 4 family itself? Maybe open your project in PSoC Creator 4.2, update components to the latest versions, generate the hex file and then try.
You can't skip the silicon ID check.
hex is built for silicon id 04 B6 11 93 which is CY8C4245LQI-483 so, the software side is ok
detected silicon id is 00 00 21 93, which does not exists in database
so the solution would be to add this silicon id to database or to find out why does the chip sends this (wrong?) silicon id
everything is connected ok, voltage is also ok,
is this connection ok?
I have two suggestions.
What is the VDD voltage you are using? 1.8V? If possible please use 3.3V instead.
Please try to add some pull-up resistors (~4.7k) to the SWD lines. This workaround was effective when 5.0V power supply is used with MiniProg3.
neither 1.8v or 3.3v works,
is there any recommendation for third party programmer which can skip silicon id check?
i really need to finish this as soon as possible
I feel a little bit uneasy seeing "XRES" not connected.
May be you've already connected it but in case you have not,
would you try connecting XRES, SWDCLK(P3_3), SWDIO(P3_2), GND and/or VTARGET with MiniProg3?
And also, I'd like to try Programming Mode "Reset" instead of "Power Cycle"
The programming specification is described in following document.
CY8C4xxx, CYBLxxxx Programming Specifications
There is a flow chart in the "Programming Algorithm" section.
The silicon ID is check at step 2. If a third party programming tool follows this document, the silicon ID will be checked.
same error message with XRES connected
is it possible that the silicon id was not set correctly at factory?
I'm sorry that my guess did not work.
But if your board allows, I recommend you to keep XRES connected to the ICE.
Are you getting same "silicon id" every time?
If this changes, we can suspect un-stable hardware by some reason.
And how many devices (or boards) do you have to test?
> is it possible that the silicon id was not set correctly at factory?
IMHO, any device can have some error rate, so if another device shows correct silicon id,
then that particular device might have problem.
And if some or many devices shows the same "strange" silicon ID, either the lot had the problem
or there may be still something wrong with your system, which none of us has been able to reveal.
BTW, this is just yet another idea, but how about lowering the clock speed of MiniProg3?