The Pioneer Kit has got a PSoC 5LP as bridge between the PSoC4 and USB to allow debugging. When you want to debug your Prototype Kit you need a miniprog3 or you have to hack your Pioneer Kit and use it for debugging.
The programing is done by a USB bridge chip, not a full up
processor like on the Pioneer, so there is no debug capability
on the -049 stand alone.
From the user manual -
3.3 Programming the CY8CKIT-049-4xxx Kit
The CY8CKIT-049-4xxx kits are pre-programmed with firmware containing a bootloader. Therefore,
there are two methods of programming the onboard PSoC 4 device:
1. Perform UART bootload programming of the PSoC 4 device using the USB-Serial device as a
2. Use a CY8CKIT-002MiniProg3 to program and debug the target device directly.
The -49-42xx kit does not have an onboard debugger. Programming is done via a bootloader only.
todebug on this kit you have two options:
a) Use Arduino style debuging, printing values to the serial com. it not real debuger but atleast you will have some feedback.
b) Use an external debuger. The proper debuger is a miniprog3 but a modded Pioneer kit will work just fine.
Thanks for all the usefull reply. That make sense.
I found a post in the forum how to hack the pioneer kit for debugging external psoc.
i cannot even program it using creator 3.0
it says: port acuired failed
I see it in usb devices though !!!
under windows 8 here!
Under "Tools" you find the Bootloader Host. This you need to program your KIT-049-42xx. Look at the manual, press the switch as indicated.
the only thing showing in bootloader is COM1
and the usb device is detected as: Universal Serial Bus Controller (not Ports)
listed as: USB-Serial (Single-Channel) Vendor 1
Yes, COM1 or COM2 and that is exactly what you program the prototype kit with.
I solved the issue with not visible COM device by unistalling everything and installing again, maybe I was using wrong USB drivers. there are a few in the supported folder. COM1 is system reserved! 3 too. so by default it showed at my PC at 4, but I set it to 21 and 115200bitrate. (maybe that was the key to success, since the default is 9600 maybe too slow and times out?)
Anyhow, the real chaviar is the unexpected, at least for me, behavior that one needs to unplug the device between either operations: programm or verify! Otherwise it times out! I made it finally to work under windows.
Now to why the linux test util drive is does not enumerate the device, yet a message with compatible device found pops up on each pluging of it.... !???
Regarding CY8CKIT-049 under linux, I have found that my Ubuntu distribution mis-dentifies the device as cytherm (Cypress thermometer device) based on its USB identifiers. My workaround is to disable the cytherm driver:
sudo nano /etc/modprobe.d/blacklist
Add this line to the file:
The proto kit will then identify as a ttyACMx device the next time you restart.
Separate question on the CY8CKIT-049.
I have an app that uses flash as EEPROM. A side effect of this is that, after running the program, the flash contents have changed. Since the bootloader provided with CY8CKIT-049 checks flash checksum every time it starts up, it fails, and I cannot actually use my application.
I have installed a new bootloader, compiled with the "fast application validation" option, using the Miniprog 3, and everything is fine.
Is there a workaround that uses the "out-of-the-box" bootloader (e.g. setting some different parameters to cyelftool when building my app)?
Alternatively, Cypress might consider supplying a "fast validation" bootloader as the standard with the kit.
A bootloader only solution makes the dev board next to useless. I know the board was only $4 but I always thought the point of a development board was to provide a good development environment. Bootloaders are only useful if you like blinking LED examples. I'm not about to spend $100 on a MINIPROG3 just to do an eval.
Consider the following -
1) Contact local FAE or Cypress Sales manager or Cypress rep, discuss the problem.
2) Buy the Pioneer board, you get a debuggable PSOC 4, a PSOC 5LP that you can
program, and an Arduino shield pinout.
As a matter of fact, Cypress sells the kit under the name "Prototyping Kit" which does not imply debugging. I see your point and I would do as Dana suggested. Then you always have the choice to develop on the Pioneer board an transfer the project to the Prototype Kit freeing the Pioneer for the next project.
Btw: of course you can do mote than having an LED blink, it depends on what you connect the board to.