Pbp + Mplab + Icd2


Closed Thread
Results 1 to 10 of 10

Hybrid View

  1. #1
    Join Date
    Jun 2009
    Posts
    17


    Did you find this post helpful? Yes | No

    Question How about this one

    Bruce

    I didnt get to test the debugger mode of ICD2 using your recommendation coz my proto board was not working well maybe need to recheck the connections.

    But anyway...I just observed the format on how the 876 & 877 series ICDDEFS code vs the Program/data memory used was coded..see below.

    Any thought about this why? I understand the "reserving 12 bytes of RAM from 0x1F4-0x1FF" on the PIC18F2550 series" but this one seems different.
    Am I correct that it is 11bytes of ram was reserved? Why it is written "ICDRESERVED1 & ICDRESERVED11".

    Just some curiosity Bruce hope you can answer my questions in here still.

    Thanks in Advance

    Chris

    '************************************************* ***************
    '* ICDDEFS.BAS *
    '* *
    '* By : Leonard Zerman, Jeff Schmoyer *
    '* Notice : Copyright (c) 2003 microEngineering Labs, Inc. *
    '* All Rights Reserved *
    '* Date : 05/28/03 *
    '* Version : 2.44 *
    '* Notes : Reserve space for ICD variables - 16F876(A)/877(A)*
    '************************************************* ***************

    DEFINE ICD_USED 1

    ICDRESERVED1 VAR BYTE $70
    ICDRESERVED11 VAR BYTE(11) $1E5

    '*----------------------* EOF ICDDEFS.BAS *---------------------*


    from the help file:

    PIC16F876/876A 0x70, 0xF0
    PIC16F877/877A 0x1F00-0x1FFF 0x170, 0x1F0 0x1E5-0x1EF

  2. #2
    Join Date
    Jul 2003
    Posts
    2,405


    Did you find this post helpful? Yes | No

    Default

    Hi Chris,

    Check with meLabs on this one. Like I mentioned before, I have an ICD2, but I haven't
    used it in several years.

    I find it a lot less trouble & work to just build the circuit & test it directly rather than use
    some in-circuit debug hardware that eats up my time/resources.

    I'm not saying in-circuit debug is a bad thing - it's just that I've never been able to justify
    the additional time, effort, or cost requirements VS simply testing my code on the physical
    hardware in real-time operation, on the target hardware.

    I have just never had a reason to step line-by-line through any code that I already know
    what it's supposed to be doing. I think it's great for learning, but it's just not something I
    need for what I do here.

    I will run some sections of code through MPSIM just to find precise timing for some routines
    or functions, but I just don't need ICD, so I don't use it, and can't offer much help...;o}
    Regards,

    -Bruce
    tech at rentron.com
    http://www.rentron.com

  3. #3
    Join Date
    Jun 2009
    Posts
    17


    Did you find this post helpful? Yes | No

    Thumbs up Thank you

    Thanks Bruce....

    I got your point & with the idea you presented seems was logical enough coz right now I find it easy to plug the chip into the demo board to debug the program.
    Your insight just supported my thought on ICD debugging.

    Regards

    Chris

Similar Threads

  1. MPLab and Picstart plus with PBP...
    By gregcan in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 8th October 2009, 15:36
  2. MPLAB and PBP ...
    By Acetronics2 in forum Off Topic
    Replies: 4
    Last Post: - 28th August 2008, 21:51
  3. pbp --> mplab broken again
    By kenif in forum mel PIC BASIC Pro
    Replies: 6
    Last Post: - 11th December 2006, 19:57
  4. PBP in MPLAB
    By zagisrule! in forum mel PIC BASIC Pro
    Replies: 5
    Last Post: - 29th December 2005, 02:58
  5. Newby- PBP wont compile for 18F (MPLAB)
    By jd76duke in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 18th December 2005, 00:30

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