How does everyone debug their code?


Closed Thread
Results 1 to 31 of 31

Hybrid View

  1. #1
    Join Date
    Jul 2003
    Posts
    2,358


    Did you find this post helpful? Yes | No

    Default

    The linkage is to your PBP Manual... use the really complex schematic provided in the DEBUG section.

  2. #2
    Join Date
    Mar 2009
    Posts
    653


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Melanie View Post
    The linkage is to your PBP Manual... use the really complex schematic provided in the DEBUG section.
    Whoop...there it is! (with a whopping one component count)

    Can someone talk me through the circuit? (just kiddin')

    I'm so excited, I'm actually thinking** about getting a round in.

    Many thanks,
    Hank.

    ** ....I've now thought about it - maybe next time!

  3. #3
    Join Date
    Jan 2008
    Location
    Pennsylvania
    Posts
    113


    Did you find this post helpful? Yes | No

    Default Debugging code

    Hank, it sounds like something similiar to what I have been working on as well with regards to working with an ADC in value. I've been using a serial connection to my 16F877/16F877A. Just like you at first I had a little LED turn on with my ADC value coming in from a pressure transducer. I set it up to turn on portc.0 at 1 psi then portc.1 at 3 psi etc... Like you said that just confirmed it worked. The real work was in taking the value and converting them to a PSI value. I got some great help with that calculation and ported my actual PSI to the serial port so I could see the actual value. I had a tone of SEROUT2 commands dumping everything to a hypertermial session.

    I have the schematic for the connection with the max232 rs232 chip if you need it.

    David

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


    Did you find this post helpful? Yes | No

    Default

    If you have PICKIT there's no need for any RS232 level shifter, no resistor either... use the USART tool.

    If you're a bit clever, you'll design your thingy to accept ICSP. And then you can also use those ICSP line for Debug with PICKIT.

    That's an handy tool for less than 50$.
    Steve

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

  5. #5
    Join Date
    Sep 2007
    Location
    USA, CA
    Posts
    271


    Did you find this post helpful? Yes | No

    Default

    I uses ISIS. It simulates the code right on the computer, complete with SPICE for the electrical schematic. With PBP, I've got to watch the compiler asm output, but I can see all of the variables change and i/o pins as fast as I want, with breakpoints. When I use Proton+, I get to step through the basic code, one basic line at a time. It even gives me the option to see the assembled code between each basic line, and step through that, too.

  6. #6
    Join Date
    Mar 2009
    Posts
    653


    Did you find this post helpful? Yes | No

    Default

    Well, I've after two solid nights battling to get my PIC 16F690 to talk to the outside world...I've got it working

    I decided I really did want some form of serout command (that I could call on demand), therefore last night I messed about with a MAX232 for a couple of hours....no success (I now realise that this was becuase I was feeding the MAX232 just 3V...sourced from the PICKIT2 VCC - it needs 5V - doh! Thanks to DavyJones for emailing me the schematics)

    Anyway, the post that mister_e madecaught my attention - & I've ended up going that route. I now have PIC program going outputing to the UART window (within the PICKIT app - altough it's a little clunky if you ask me). I 've actually pimped my PICKIT2 board by soldering on a little switch which allows me to quickly switch between the PICKIT as a 'programming device' & the PICKIT 2 as a 'serial interface device' ....so no need to change the PICKIT2 edge connector now :-)

    Anyway, I'm on the final straight...my query now relates to Terminal Window formatting (or rather whatever it takes to get the PICKIT 2 UART window to clear down!)

    Can anyone outline (in simple terms), how I can send simple 'clear screen', line feed commands etc using the HSEROUT command?

    here's a little of my code (you've not to laugh!)

    ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
    HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]


    The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

    Many thanks in anticipation.

    Hank.

  7. #7
    Join Date
    Aug 2006
    Location
    Look, behind you.
    Posts
    2,818


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by HankMcSpank View Post
    ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
    HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]


    The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

    Many thanks in anticipation.

    Hank.
    Try:
    [code]
    HSEROUT [254,1,"ADCIN Value = ", DEC DC_Level_IN]
    [code]
    If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
    .
    Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
    .
    There simply is no "Happy Spam" If you do it you will disappear from this forum.

  8. #8
    Join Date
    Aug 2006
    Location
    Look, behind you.
    Posts
    2,818


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by HankMcSpank View Post
    ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
    HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]


    The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

    Many thanks in anticipation.

    Hank.
    Try:
    Code:
    HSEROUT [254,1,"ADCIN Value =  ", DEC DC_Level_IN]
    If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
    .
    Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
    .
    There simply is no "Happy Spam" If you do it you will disappear from this forum.

Similar Threads

  1. N-Bit_MATH
    By Darrel Taylor in forum Code Examples
    Replies: 38
    Last Post: - 16th December 2010, 14:48
  2. debug not working with MPASM assempler
    By santamaria in forum mel PIC BASIC Pro
    Replies: 5
    Last Post: - 4th March 2009, 07:51
  3. How much code space do PBP statements use.
    By Darrel Taylor in forum Code Examples
    Replies: 5
    Last Post: - 13th February 2009, 21:31
  4. Loop with two motor and 2 sensors
    By MrRoboto in forum mel PIC BASIC
    Replies: 4
    Last Post: - 8th December 2008, 23:40
  5. Making Program Code Space your playground...
    By Melanie in forum Code Examples
    Replies: 15
    Last Post: - 19th July 2008, 08:26

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