Announcement

Collapse
No announcement yet.

To compile or not to compile

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • To compile or not to compile

    I've thought many ways to say this and not look too duhhhh but here goes. Must I compile my PBP program before I do the simulation for any changes to take effect? I assumed, you know what is said about that, once I told Protues where the program was located, named it, wrote the program and ran the sim that Proteus would compile it, grab the hex file(I think that's the file it uses) and execute my newly modified program. Maybe it's another one of those nuances or checkboxes I'm missing but if there's a way to do that I'd like to know.

    OBTW thanks for the tip on having two copies of PBP going when I use it as my source editor. I almost got into trouble with that happening.

  • #2
    Proteus uses the .COF file.
    When it sees that the Source code is newer than the .COF file, it will automatically compile it before running the simulation.

    If you compiled it with MicroCode Studio, it won't compile it again from proteus since the .COF is newer than the Source code.

    If you don't compile it in MicroCode, you have to remember to save it, so Proteus can see the changes.
    Otherwise, you're still running an older version.

    And you're Welcome!
    PBP3 Manual : Microchip Datasheets - 10F, 12F, 16F, 18F
    Never download a PIC datasheet from anywhere but microchip.com

    Comment

    Working...
    X