1 of 1 people found this helpful
Try the following:
Disconnect the USB from your board.
Use Creator to program the project
Set the miniprog to SWD and 5V.
Easiest debugging will be done under Creator IDE
thanks for helping me out!
-If I disconnect USB then it complains that device is not powered
-When I select 5V, I get this
We design a board that has a PSoC5 on it. It will have SWD interface to the PSoC5 processor. So I am trying to learn how to program it connecting directly via SWD. The goal is to use MiniProg3 connected to the board on one side and workstation with PSoC Creator on the other for programming and debugging. At this moment, with this setup, I cannot program the processor neither with PSoC Creator nor PSoC Programmer.
Do you have any ideas what am I doing wrong here?
The dialog is warning you if the device connected to the MiniProg3 is either CY8C6xxx or CYRF89xxx, you will burn the device.
But the device you are trying to connect is CY8C5868LTI-LP039, so it should be OK to proceed.
Meantime, please note that if you change the firmware on the PSoC 5LP of CY8CKIT-046, the KitProg function will be lost till you restore the firmware.
I tried 5V setting with SWD and with JTAG, but the result is not different than before.
I was able to program this PSoC5 processor in the Bootloader mode via USB connector, and then was able to restore KitProg back. Now I need to learn how to program a PSoC5 processor via SWD since this is how our custom board is designed. So our plan is to connect MiniProg3 to our board and program/debug from PSoC Creator.
The eval board that I have on hands has two JTAG headers: J6 and J7. J6 is for PSoC 4200L Programming and J7 is for PSoC 5LP programming (actually, we attached the header to the J7 pins ourselves).
When I attach MiniProg3 to J6 (PSoC4's header) then I can successfully program the board's PSoC4 processor. However, when I connect MiniProg3 to J7 to program the board's PSoC5 processor, then I am having issues described above.
Do you have any ideas what can be wrong here?
Meanwhile, we are buying PSoC5 eval board to see if we are more successful with it. But even if we are then I still want to know what's wrong here in case we have the same problem with our custom made board.
Thank you for help!
1 of 1 people found this helpful
Would you try
(1) As Bob-san wrote earlier, I think that you need to disconnect USB-Mini cable from the board.
(2) From the menu Debug > Select Debug Target...
select Port Setting in the "Select Debug Target"
and let the MinProg3 provide power
on the board as you are selecting 3.3V for I/O may be providing 3.3V is better
(3) Try program 5LP
3 of 3 people found this helpful
I assembly a 10-pin header on J7 of 046 kit, also try to program P5LP devices through Miniprog3 +PSoC Programmer, i get different test result with you.
Step1: Open PSoC Programmer, connect 046 Kit to PC and also connect Miniprog3 with J7 and PC. Choose Miniprog3 in 'Port Selection' windows of PSoC Programmer, then click JTAG tab and press 'Scan Bus' button to scan the JTAG chain. Without this step, sometimes Miniprog3 cannot detect the JTAG devices on JTAG chain successful.
Step2: Switch to Programmer Tab and click Program Icon to program the device, the P5LP device can be programmed successful. Only Miniprog3 can be emulated in port selection window, Kitprog will be emulated also until you unplug and plug the USB cable from J10.
Step3: Choose SWD interface, press Program icon can program the P5 LP device directly. No errors.
My test platform:
OS: Win10 Pro
PSoC Programmer: Version 188.8.131.5254
P46 Kit: Rev06
Thank you, everybody, for your help!
I have made some great progress and now can program the PSoC5 processor on the board! But I still cannot use debugger with the PSoC5 code.
I followed the advice from Motoo-san and from the Select Debug Target dialog box
opened Port Setting
and changed Power to "3.3 V" from "External". This alone let me program the processor.
Also, I tried to do what user VisionZ_71 suggested, but the Scan Bus button was grayed out (see below). Device Family and Device settings are selected for PSoC4. I wonder if this is the reason why the Scan Bus button is disabled. However, I cannot change the settings to PSoC 5 since they are also grayed out.
Also, I can program the chip now, but I cannot use debugger: the debug option is grayed out in PSoC Creator. Any ideas why?
Again, thank you, everybody, for your help!
I think that to use scan-bus feature, you need to select "JTAG" instead of "SWD"
This is the reason why we needed to tweak SWD signals in the previous discussion,
as SWD is not supporting multiple devices.
You may also want to try "JTAG" protocol for debugging if the tool allows us to do so.