Thank you for reply, and your patience in waiting for my response.
I have tried updating the firmware as you suggest ( I had already tried this,
but have repeated the process to make sure ). The actions and results panel is as follows:
| KitProg Version 2.10
Firmware Update Finished at 17:10:47 |
Firmware Upgrade Started at 17:10:34 |
Firmware Upgrade Requested at 17:10:34 |
Successfully Connected to KitProg/0D1A140900163400 at 16:59:05 | KitProg Version 2.10
Opening Port at 16:59:04 |
Device set to CY7C65215-32LTXI at 16:59:04 | 32768 FLASH bytes
Device Family set to CY7C65210 at 16:59:04 |
Active HEX file set at 16:59:03 |
| Users must be aware that the following PSoC device should not be powered or programmed at 5V. Doing so will cause damage to the device: CYRF89xxx
Session Started at 16:59:03 | PPCOM Version 18.0
You can see that it all seems to be successful, and the status bar at the bottom shows
"PASS", "Powered", "Connected", all in green.
However, I am puzzled by the fact that although the devices on the CY8CKIT-042 are:
PSoC4 chip: CY8C4245AXI-483, family: PSoC 4200
PSoC5 chip: CY8C5868LTI-LP039, family: CY8C58LPxxx
this is NOT what the programmer sets.
The drop-down selection boxes for device family and device are showing
Device set to CY7C65215-32LTXI
| 32768 FLASH bytes
Device Family set to CY7C65210
and are grey, so cannot be changed.
Is there something wrong here?
Another worry: Under Programming Parameters the File Path entry shows "File is not present",
and it is red text, as if indicating a problem.
Does this have any relevance to my problem?
Thanks again, Ken.
Ken, maybe the best thing to do for expediency is file a CASE
so that Cypress can do a desktop session with your machine.
To create a technical or issue case at Cypress -
“Create a Case”
You have to be registered on Cypress web site first.
Yes, I will do that. I have filed a case in the past, so know the procedure.
Many thanks for your help. I will close this thread now. Ken.
Did you ever get this resolved? I'm getting the exact same issue with the CY8CKIT-042 and v2.10 of the KitProg firmware.
Yes, I did eventually resolve the problem -- it appears that the board was faulty!
The suppliers (Farnell) replaced it free of charge, and the replacement is fine.
I have no idea what I did to damage the board, but these things sometimes happen.
So a dud board might be your problem -- perhaps you could borrow another to try.
Interesting. That's not the issue with my setup. A Segger J-Link Lite for Cortex-M0 works with it just fine.