Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Don't underestimate the effort of designing a correct simulation of PIC hardware features for all processors. If you look at the various bugs produced by Proteus PIC simulation, you get an idea about it. Cooperation of MPLAB SIM with CCS is rather smoothly. If you prefer to use the CCS IDE, you need to import the *.cof file once in MPLAB, then it's automatically reloaded after compilation.
I also prefer MPLAB for in-system debugging of CCS generated code with PIC18 and PIC24.
hmm so the code is compiled in CCS C but the debugging is carried out using MPLAB. In system debugging means that we monitor the program as its progresses and this may require setting breakpoints and trace variable and register values as they change over the course of the program execution. Since the CCS program shall generated a hex file, how can one use that hex file and do in system debugging using the MPLAB IDE?
I mean when the C program is written in CCS C and then we set breakpoints and use its debug features, it all works as a unified system and does not only rely on the hex file it produced.
Debugging (hardware debugging as well as well simulator) uses *.cof file which contains symbolic information and reference to source code files. After importing *.cof, you can open the project source files in MPLAB and set source level break points. Just try.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
