Announcement

Collapse
No announcement yet.

Simple Program

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

  • Simple Program

    Following Darrel Taylor's advice.

    OUTPUT PORTB.0

    I went to compile this and it threw and error.

    'Bad Expression'

    What went wrong?

    I selected first PIC in Experimenter's Edition. 12F683.

  • #2
    Okay.

    Changed device to 16F88.

    It compiled. A one line program. This PBP is interesting.

    Looked at ASM file.Sure is a lot in there!

    ;After you compile it, you'll find a .ASM .MAC and .LST file in the folder that the original program was in.
    Start with the .ASM;'

    Could not find LST file.

    Will go back and look at MAC file.

    Comment


    • #3
      The 12F683 doesn't have a PORTB register - that's why OUTPUT PORTB.0 fails. It does however have a GPIO register so OUTPUT GPIO.0 should work.
      I have no idea why you don't see the .lst file, take a second look.

      /Henrik.

      Comment


      • #4
        Oh, Never mind, I was thinking about the real OLD version of the compiler...
        Dave Purola,
        N8NTA
        EN82fn

        Comment


        • #5

          Thank you Henrick and David

          There is no LST file.

          Here's something.

          In the ASM and MAC files I see 'no list'.

          Could this have something to do with it?

          Comment


          • #6
            If you're using MicroCodeStudio then go to View -> Compile & Program Options and check the MPASM Listing File checkbox - see if that does it.

            /Henrik.

            Comment


            • #7

              Thank you Henrik

              That was already checked.

              Why is it generating something called C Project File and C/ASM file?

              Comment


              • #8
                The compiler and assembler generates a whole bunch of files that, combined with even more files from the PBP and MPASM system directories, makes up the final program that the assembler then turns into a .hex file for programming into the target device.

                I don't think any of them is an actual "C Project File" (whatever that is) - it just happen to have the same file extension as the file association for a "C Project File" has on your particular system.

                Comment

                Working...
                X