PBP, 16F1827, FSR, and Error 113


Closed Thread
Results 1 to 12 of 12
  1. #1
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263

    Question PBP, 16F1827, FSR, and Error 113

    I've looked at several discussions/comments about Error 113, but haven't yet found one that applies.

    At compile, I get:

    Error[113]c:\ff501\ccf717~1.asm 295 : Symbol not previously defined (FSR)
    Error[113]c:\ff501\ccf717~1.asm 324 : Symbol not previously defined (FSR)

    I made the corrections at http://www.picbasic.co.uk/forum/showthread.php?t=12628 and don't think I overlooked anything.

    I am using DT_INTS.

    The original PBP application ran on a 16F88.
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

  2. #2
    Join Date
    Feb 2006
    Location
    Gilroy, CA
    Posts
    1,530


    Did you find this post helpful? Yes | No

    Default

    The 16f88 has a single FSR register. The PIC16F1827 has FSR0 and FSR1 registers.

  3. #3
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by scalerobotics View Post
    The 16f88 has a single FSR register. The PIC16F1827 has FSR0 and FSR1 registers.
    Yes, I see that in the 1827 manual.

    Where do I look to diagnose the cause of the message and solve the problem?
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

  4. #4
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263


    Did you find this post helpful? Yes | No

    Default

    Okay.

    As an experiment, I commented out everything having to do with the interrupts: Both "includes", the associated ASM block, and both the enable and disable commands ('@').

    It now compiles with no errors.

    It won't run, of course, because I need the INT_INT.

    Darrel, can you chime in on this one, please?
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

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


    Did you find this post helpful? Yes | No

    Default

    Russ,

    Are you using DT_INTS-14 version 1.0?
    http://www.darreltaylor.com/DT_INTS-14/intro2.html

    File is at the bottom of the page.

    It was updated for the 16F1 chips, and adds many INT sources.
    <br>
    DT

  6. #6
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263


    Did you find this post helpful? Yes | No

    Red face

    Quote Originally Posted by Darrel Taylor View Post
    Are you using DT_INTS-14 version 1.0?
    DOH! My "favorites" link still brings up the old page. I did look . . . apparently not well enough.

    Thanks!
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

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


    Did you find this post helpful? Yes | No

    Default

    Yeah ... sorry.

    I haven't updated the main page yet, because I've received ZERO feedback from the people that I know downloaded it.

    I could assume that means it worked for them, or they would have complained.
    But until I get some idea if there's problems, I don't want that to be the file everyone downloads their first time.

    Love to know how you get along with it.

    Thanks,
    DT

  8. #8
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263


    Did you find this post helpful? Yes | No

    Default

    If my "blinky" is any indication, it works fine for INT_INT, which is the only one I'm using at the moment. I also tested it (INT_INT) in the full program, and it is working, both on the output and driving a "heartbeat" indicator at the same time. (It's a zero-crossing detector.)

    The rest of the program is problematic. As I mentioned, it worked on the 16F88, but only one channel works correctly on the 16F1827. I have to assume I have overlooked something in terms of managing and/or definining pins/ports, since each channel's code is identical.

    I may be yelling for help yet this evening.
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by RussMartin View Post
    If my "blinky" is any indication, it works fine for INT_INT, ...
    That's a start.
    Thanks!

    I may be yelling for help yet this evening.
    OK.

    Don't forget ...

    ANSELA = 0
    ANSELB = 0

    <br>
    DT

  10. #10
    Join Date
    Aug 2006
    Location
    Omaha, Nebraska USA
    Posts
    263


    Did you find this post helpful? Yes | No

    Default

    I'll be working with TMR1 and IOC interrupts during the next few/several days (going back to the "reverse Simon says" project) and will let you know how those fare. NRN.
    Russ
    N0EVC, xWB6ONT, xWN6ONT

    "Easy to use" is easy to say.

  11. #11
    Join Date
    Feb 2006
    Location
    Gilroy, CA
    Posts
    1,530


    Did you find this post helpful? Yes | No

    Thumbs up ver 1.00 of DT_INTS

    Quote Originally Posted by Darrel Taylor View Post
    I haven't updated the main page yet, because I've received ZERO feedback from the people that I know downloaded it.
    Darrel, your interrupt version 1.00 gets a thumbs up from me. I have only tried a few different types of interrupts with it, but it works great.

  12. #12
    Join Date
    Mar 2005
    Location
    CROATIA
    Posts
    38


    Did you find this post helpful? Yes | No

    Default Re: ver 1.00 of DT_INTS

    post deleted
    wrong treed
    i fond problem,
    my wrong file name save
    Last edited by ShoKre; - 13th January 2014 at 09:13.

Members who have read this thread : 1

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