I have many succesful PSoC 3 and 5 projects under the belt, including some quite complex designs.
However I have never used PSoC 1 - yet!
So what's the best way to get to know PSoC 1? Which dev kit would you recommend?
That's an easy-to-answer-question: ANY
You'll REALLY need an ICE-Cube to get more debugging features than only Lamp-on-Lamp-off.
Get a 3270 Kit or use the -001 board with the universal PSoC1 processor module, the former has the advantage of the PSoC1 coming in a DIL-package making it easy to handle even on breadboards while the latter has the necessary debug-hardware integrated and doesn't need a pod to connect to the ICE.
Thanks for the reply
I don't mind handling SOIC or even QFN - So no worries there 🙂
I'll look at the 001 kit - sounds interesting.
I forgot to mention:
When ordering an ICE-Cube, the standard POD delivered is for the CY8C29466-PXI which comes in a DIL-Package. So when you are using that you'll go best with a 3210 dev Kit.
TAKE CARE!!! I killed my -001 board when I tried to remove the processor module. One of the connectors went off (port 2 for the LCD)
I can't find an '001' kit at my usual supplier (Farnell, UK).
I'm a bit scared to order from the cypress store in case I get hit with loads of import duty like last time.
Farnell had an uncomplete description. Check at the Cypress site Buy -> Development Kits for the Kit-001b there you can see that it is designerd for PSoC1 as well. Farnell forgot that.
Keep in mind when using ICE CUBE depending on package you
need different pod feet to mate up to your package choice. The
ICE is a basic emulator, so the end of the emulation cable has to
be terminated in the adapters/feet to be used in your proto/board.
You do not need a POD to connect the ICE to a PSoC1 processor module for the Kit-001. There is already a connector where the ICE is plugged in and the PSoC1 device is a special one that already has got the necessary debug-capabilities like the chip in the POD.
To make sure there is no confusion. For the kit, -001, there is a specific
processor used for PSOC 1, with a specific amount of FLASH, I/O, etc.. So
you can debug that w/o pod feet, as your target is the -001, and that processor.
But once you decide to develop your own project you need the pod and feet
applicable to the part/package you choose.
Sorry for a delay in replying, you may have already purchased your desired kit. But I wanted to add that the simplest and the most cost efficienct way to get started with PSoC 1 is but the CY3210-PSoCEval1 kit - http://www.cypress.com/?rID=2541. This kit comes with CY8C29466-24PXI and CY8C27443-24PX samples. It has plenty of breadborad space which you can use for your design. In addition to this if you are looking for debugging capabilities you can purchase an ICE-Cube (CY3215-DK).
The PSoCEval1 kit is available in UK Farnell store - http://uk.farnell.com/cypress-semiconductor/cy3210-psoceval1/development-kit-basic-psoc/dp/1321702
Correct me, if you think I'm wrong: You do need debug capabilities when designing professionally. The mentioned development board connects to a PC but it does not allow to set breakpoints or inspect variables etc.
Nonetheless it is a very cheap breakout board.
This is a nice discussion, since I'm also looking to start with PSoC development, especially PSoC 1 given it's analog flexibility and low cost.
I was told 3210 PSOCEVAL is the way to go, and is the cheapest Cypress kit that is a full development kit. Also found tons of examples for the chips it comes with (+Plastic DIP package is great for my needs)
Only problem is it almost is never in stock in the Cypress website (too many buying it eh 🙂 )
As I'm waiting for my board to arrive, I'm thinking why I would need an ICE debugger (I have read the debugging manual, it was fantastic). But would everyone need such an expensive and advanced method for debugging?
Welcome to the world of PSoC!
I appreciate your thoughts on debugging approaches. You are right about different approaches to debugging.
The ICE (In-Circuit Emulator) is a powerful piece of hardware for debugging advanced logic, for e.g., it can dynamic breakpoints by hardware compare, and does not affect timing of code execution in your chip.
Still, there are other options such as UART/I2C based debugging. I2C interface along with the Bridge Control Panel software has been used for a long time to debug CapSense applications. The debugging appnote gives some examples on how UART and I2C can be used as an ICE alternative for watching registers/ reading data for debugging.
The ICE generally makes you more productive, due to trace, memory
views, logical trace capability.
Simple debugging via UART, I2C bridge, or writing variables to LCD
is workable, but not as flexible. It could be made more flexible by
writing an extensive API for both sides of the link.
PSOC 3 / 5 debugging is bases on USB connector, or Miniprog3 which
can be used as a bridge or as debug or programmer. Note this is largely
facilitated by onchip debug logic in PSOC 3/5. One limitation of 3/5,
that exists in PSOC 1, is no pods/feet for use in end user design
proto socket. 3/5 the dev board is your platform, some pins, HW comitted,
but generally this is not a show stopper. Actually can be very enabling
not having to create your own basic proto test bed. In fact 3/5 board
approach can save you $$ overall.
There are videos on PSOC debugging, for 1 go here (otherwise just go to
www.cypress.com, video section for 3/5).