PCD - ready for prime time yet OR C18 to C30?

[JK]

I need to do a PIC24 product. I'm satisfied with CCS for my PIC18 projects but I have heard of issues with PCD still. I've e-mailed CCS but can't get a response to discuss the maturity of the product.

Short term, I can develop on the PIC18 but need a known solid upgrade path to the PIC24. If PCD is not here yet, my other alternative is C18 to C30, so I am looking for comments on that code migration path as well.

Would prefer PCH>PCD, but not gettting the warm fuzzies for a commercial product.

[Gary Smithson]

I am doing a PCD project that has a USB composite HID mouse/keyboard and a few PWM channels as its major features. I might also mention it makes use of Peripheral Pin Select and Master I2C.

With the exception of generating Configuration Bits that cause MPLab to display error messages, the compiler is working well enough for this project. With that said, there was a period of at least three weeks where I reported multiple bugs per week.

Silly little things like port_a_pullups not being recognized as a valid function are still happening so I am having to do a few direct register writes.

Hope that helps,
Gary

[Guest]

I've been using pcd since first release. There were many problems at the start but ccs has been working at resolving them. There are very few problems now. I developed an engine control module with a 30f4011 with no current problems. As of 4.092 all my issues have been solved by ccs.

So changing to microchips compiler would be a new learning curve you don't really need. The code between pch and pcd is very similar. So there is really no such thing as mature, because they are always changing the code to improve it, causing a problem somewhere else.

Mature for ccs is if there are no changes for 2 weeks, this means there are no major problems with their last version. They sometimes release a version and two days later they release a fix for that previous version. So wait 2 weeks before using the current version.