CCS C: use MPLAB IDE or PCW IDE

[hilgert]

I have decided on getting the CCS C compiler PCB and PCM. Should I get the command line version or the Windows IDE version? My only concern is how well CCS integrates with MPLAB (free), and if the PCW IDE is worth the extra money. The PCB and PCM command line would be $250, while the PCW (PCB and PCM) would be $350.

Basically, I think the question is really what is the best IDE - MPLAB or PCW IDE?

Thoughts?

-Hilgert-

[Mr.RC-CAM]

I vote for MPLAB's IDE.

[stumax]

Hilgert, the project wizard in the CCS IDE is very good at setting things up for you until you get the hang of all the peripheral setups (be warned, however, that not all the peripheral setups actually work - see my thread on setting up the internal oscillator). However, for convenience whilst writing and compiling code, I use MPLAB as I can then compile and assemble (ie build) in one go. I guess once you become fully conversant with the built in commands for setting up peripherals you could just use the command line compiler.

Stu.

[Mr.RC-CAM]

I guess once you become fully conversant with the built in commands for setting up peripherals you could just use the command line compiler. MPLAB's IDE has a very sophisticated peripheral code generator (Tools | Visual Initializer). However, I never use it. I'd rather get out the data book and set the registers based on what I read; I'm an old school fellow. But for a beginner, it would be very handy. I suspect the output is in assy, so the initialization would probably need to go in as inline assy code.

[Comatose]

What do you want PCB for? We have PCWH with all the bells and whistles here, but I've never once used the 12 bit pics. All the Pic12fXXX pics are 14 bit cores and programmed with PCM.

I prefer CCS's IDE, though to be fair its been a number of years since I've used MPLAB's so it may have improved considerably since.

[hilgert]

What do you want PCB for? We have PCWH with all the bells and whistles here, but I've never once used the 12 bit pics. All the Pic12fXXX pics are 14 bit cores and programmed with PCM.
Not sure - still figuring out the different versions and stuff. Looks like if I want the CCS IDE I have to get PCB and PCM anyway (only way it comes from what I can see on their site). Or, I could just use the PCM command-line version and MPLAB's IDE. I hate different versions of software...

[jsirkia]

I've been using PCM for a while now but just moved to MPLAB this spring, at the same time I purchased the ICD-2, and I'm not going back. I still use PCM every once in a while, but just for the help section so I can look up syntax and commands when forgotten. For all coding I use MPLAB and ICD-2, works like a charm. I'd still say the CCS IDE is better for getting used to the compiler.

-Jussi

[Lakc]

MPLAB's IDE has a very sophisticated peripheral code generator (Tools | Visual Initializer). However, I never use it. I'd rather get out the data book and set the registers based on what I read; I'm an old school fellow. But for a beginner, it would be very handy. I suspect the output is in assy, so the initialization would probably need to go in as inline assy code.

I have played with the visual device initializer but it never seems to have support for the pic's I want to use. Still, they are adding more every release, and you cant beat the price. Meanwhile, I too find it easier to set it up in assembly code, as the last few pages of every section in the device docs are pretty good at arranging all the necessary registers you need to address.