How can I establish what RAM I need...and therefore which PIC.


Closed Thread
Results 1 to 24 of 24

Hybrid View

  1. #1
    Join Date
    Nov 2003
    Location
    Wellton, U.S.A.
    Posts
    5,924


    Did you find this post helpful? Yes | No

    Default

    Say you have your code working on the 690. Look at the *.lst file near the end and see how much of what the code uses. Then dig through the specs from other chips to see what one is large enough.
    Dave
    Always wear safety glasses while programming.

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


    Did you find this post helpful? Yes | No

    Default

    I use MicroCode Studio Plus... I think it tells you the memory used in the Status Bar.

  3. #3
    Join Date
    May 2004
    Location
    NW France
    Posts
    3,653


    Did you find this post helpful? Yes | No

    Default

    ...

    and MPLAB has the " memory usage gauge " ... in the " view " menu ...

    Alain
    ************************************************** ***********************
    Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
    ************************************************** ***********************
    IF there is the word "Problem" in your question ...
    certainly the answer is " RTFM " or " RTFDataSheet " !!!
    *****************************************

  4. #4
    Join Date
    Mar 2009
    Posts
    653


    Did you find this post helpful? Yes | No

    Default

    Firstly my apologies....I thought I'd thanked you all, just come back to this thread to find I hadn't so Thank You!

    Ok, so it seem 4096 words being used seems to be the 'significant' number wrt using a 16f690 ....anything more & I get compilation error messages.

    So I started commenting out a few lines of code to see which commands are eating the word count.

    By taking out about six (long) lines inserted randomly throughout my code as follows,.....

    Code:
    IF debug_active= 1 then DEBUG "below     pwm= ", DEC pwm_width," Target= ",DEC target," Sig= ", DEC signal_in, " Mode_status =", DEC mode, " On_Status = ", dec on_status, " AGC Status= ", dec Agc_on_status, 13, 10
    (debug_active is just variable I use to erhmm activate/deactivate debug info out the debug port/pin)

    ......the words count used in my program plummets from around 4080-ish to about 1700 words?!!!

    Can anyone explain why? (or have a good pop & accounting for the word plummet?!)

    & while I'm on, which are the most hungry commands from using up the word space?

    cheers,
    Hank.

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