Read the newbee threads, 16F877A no go.


Closed Thread
Results 1 to 40 of 40

Hybrid View

  1. #1
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default Reply on help.

    Hi Ralph, Thanks for taking the time to respond.
    I do have the pull up in, and saw Melanie's post on configuration fuses.

    Her thread wasn't completely clear to me as to where those lines would be entered. The Microcode Studio doesn't provide for switches, nor did the MPASM I tried selecting within Studio.

    I did see another thread on editing the .inc file, and I changed it from xt to hs in two places. Hoping that was what he had in mind.

    From some other posts it appears that the configuration switches end up embedded in the .hex file. I hope this is correcct as it should be easy to read them out of the file resulting from compiling the short example program in the first msg. I just have to find out what the bits (placement) of that line is supposed to read.

    I'm ok with BASIC, but trying to learn PICs and PBP.


    Best Regards,
    Bobby

  2. #2
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default More on the configuration bits.

    Looking further into the configuration bits only confuses things more. From Melanie's thread on setting them up, I looked at the .inc for entries matching the datasheet's Special Features section. The datasheet calls out many configuration bit switches that are not addressed in the .inc file.
    I'm really hoping these bits are not important to be set or cleared, otherwise it doesn't inspire confidence. I still have little idea on what the configuration bits should be set to. Learning more every day...

    Bobby

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


    Did you find this post helpful? Yes | No

    Default

    Did you read the whole thread??? I post some info myself too
    here

    So can we assume that something is working now on your side???
    Steve

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

  4. #4
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default It lives.

    The short test program included in my first email will run now.
    A number of changes were made, including editing the \PBP\xxxxxx.inc file.
    Also turned off the watchdog timer, I may turn it back on to check effect.
    Somewhere along the way I've hosed up the MPASM configuration and now
    will have to get it working again. But hey this is a learning process right ?

    Thank you for the help.
    Bobby

  5. #5
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default Still learning.

    I switched the wdt_ configuration back to on, and the toggle program still runs.
    The larger program even executes, more or less.
    The less part is that I'm required to press the reset button to get my program to run, where the original development board firmware executes on powerup.
    Any suggestions where to start looking ?

    Thanks,
    Bobby

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


    Did you find this post helpful? Yes | No

    Default

    ARGH, are you using some kind of bootloader??? if so add
    DEFINE LOADER_USED 1
    Steve

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

  7. #7
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default No autostart

    Thanks for responding.

    No, I'm not using a bootloader.

    I'm really surprised how poorly this has gone. There are a couple of guys at work who program PICs, they program strickly in assembly. I wondered why they went through all the trouble, at least when assembly wasn't actually required for speed or code size.

    The answer is, because the higher level tools aren't ready for prime time.
    I can't believe all the convoluted ways to do things I've looked up, which also happen to not work right or as often as not don't work at all.

    Sure this is frustration talking, but changing DEFINE OSC 12 to DEFINE OSC 11 (actual clock is 11.0592 MHz) results in 8 assembler errors, minor variations of:
    Error c:\pbp\pbppic14.lib 2827 : [225] Undefined Symbol 'PAUSEUS'

    and still no readable serial characters (at least with any communication protocol from this planet).

    And who's idea is that of a useful or appropriate error msg ?

    Bobby

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


    Did you find this post helpful? Yes | No

    Default one idea

    Quote Originally Posted by BobbyA View Post
    The less part is that I'm required to press the reset button to get my program to run, where the original development board firmware executes on powerup.
    Any suggestions where to start looking ?

    Thanks,
    Bobby
    Hi Bobby A,
    I agree with you about the books and manuals ability to convey everything a newbie needs to learn, they basicly blow! This forum is very helpful, very many smart people here!
    For the problem above try putting a capacitor of say 1uf from the reset pin to ground. the time it takes to charge through the resistor you have going to B+ will allow the PIC to stabalize on start up. It seems some individual pic chips need this, I do not know why . . . maybe est damaged? Just curious are the chips you are using samples?
    JS

  9. #9
    BobbyA's Avatar
    BobbyA Guest


    Did you find this post helpful? Yes | No

    Default

    Kind of late responding, but the forum just sent out (in Dec) an email notice there were 4 post to the thread (last in Aug ?). Procrastinator club anyone ?
    Anyway, it's not ic specific since the original demo program that came with the board can be reloaded (external device programmer) into the exact same ic and it will run from power up. But the PBP compiled program does not start to execute until the reset button is manually pressed.
    I don't know what the real cause was, eventually I chucked the board, PBP, and Hellebuyck's book in a drawer, and things got better.
    Cheers, Bobby
    PS. Royalty checks only prove people bought it, not that they found it useful.

Similar Threads

  1. Can't read sequential addresses in external EEPROM
    By tjkelly in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 18th February 2010, 14:46
  2. Cleaning up code
    By Tobias in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 2nd December 2009, 07:14
  3. SEROUT WORD variable problem
    By Tobias in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 19th April 2009, 11:20
  4. Q: using MCLR for Input on 12F683
    By picster in forum mel PIC BASIC Pro
    Replies: 46
    Last Post: - 31st January 2009, 15:25
  5. Changing declared variables names on the fly
    By jessey in forum mel PIC BASIC Pro
    Replies: 15
    Last Post: - 16th December 2006, 06:34

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