MPASM error message


Closed Thread
Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107

    Default MPASM error message

    When compiling, I'm getting the MPASM error message

    Error [110] pbppic18.lib 832:unmatched

    I can't see any errors in the ASM files or the .MAC files. Can someone tell me how I can track down the error to a particular line of PBP?
    Charles Linquist

  2. #2
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    Is this a complex program? Is this PBPL or PBP? Which PIC?

    MPASM help file says...
    110 Unmatched )
    An close parenthesis did not have a matching open parenthesis. For example,
    DATA 1+2).
    Maybe somewhere in your code or in a Specific PBP(L) macro.
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  3. #3
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default

    PBP 2.47 (no PBPL)
    18F8720
    Long and complex program

    It would take me many hours to comment out sections to see which one was the offender.
    Charles Linquist

  4. #4
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    If you select another PIC.. say 18F8722.. is the problem always there? if so... maybe a faulty lib... may worth to try a fresh PBP installation.

    Never ever had this message here
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  5. #5
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default

    It seems that I'll never have to find out what the problem was. It compiles and assembles "clean" in PBP 2.50a.
    Charles Linquist

  6. #6
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default

    ERROR: ERROR: Wrong answer! I can't count.

    Nevermind!
    Last edited by Darrel Taylor; - 3rd April 2008 at 06:47. Reason: DOH!
    DT

  7. #7
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default

    The code runs as expected. I would like to find the problem, though. Things like that usually come back to bite me eventually. I suspect that I'm equating a bit variable with a byte

    That is the trouble with the bigger chips - there are so many places for bad code to hide!
    Charles Linquist

Similar Threads

  1. 16F914 and MPASM
    By jderson in forum mel PIC BASIC Pro
    Replies: 10
    Last Post: - 7th February 2009, 03:21
  2. 12F675 MCLR directive MPASM
    By OLDSCHOOL in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 4th May 2008, 01:29
  3. MPASM 18F4550 getting started
    By BrianT in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 4th September 2007, 23:59
  4. 18F8722 and MPASM confusion!
    By Jackson in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 2nd April 2006, 01:24
  5. Converting to MPASM
    By btaylor in forum mel PIC BASIC Pro
    Replies: 11
    Last Post: - 4th November 2005, 01:35

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts