Advice please - Warning message


Closed Thread
Results 1 to 40 of 51

Hybrid View

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


    Did you find this post helpful? Yes | No

    Default

    O.K, you have two choices.

    1. You rem all _CONFIG lines and set them in your code using the old way... well as i posted before

    2. you rem all _CONFIG lines and you past those i posted.. so it should looks like

    Code:
    ;****************************************************************
    ;*  18F2550.INC                                                 *
    ;*                                                              *
    ;*  By        : Leonard Zerman, Jeff Schmoyer                   *
    ;*  Notice    : Copyright (c) 2004 microEngineering Labs, Inc.  *
    ;*              All Rights Reserved                             *
    ;*  Date      : 12/31/04                                        *
    ;*  Version   : 2.46                                            *
    ;*  Notes     :                                                 *
    ;****************************************************************
            NOLIST
        ifdef PM_USED
            LIST
            "Error: PM does not support this device.  Use MPASM."
            NOLIST
        else
            LIST
            LIST p = 18F2550, r = dec, w = -230, f = inhx32
            INCLUDE "P18F2550.INC"	; MPASM  Header
            ;__CONFIG    _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L
            ;__CONFIG    _CONFIG1H, _FOSC_HS_1H
            ;__CONFIG    _CONFIG2H, _WDT_ON_2H & _WDTPS_128_2H
            ;__CONFIG    _CONFIG3H, _PBADEN_OFF_3H
            ;__CONFIG    _CONFIG4L, _LVP_OFF_4L & _XINST_OFF_4L
            __CONFIG  _CONFIG1L, _CPUDIV_OSC1_PLL2_1L  
            __CONFIG  _CONFIG1H, _FOSC_XT_XT_1H
            __CONFIG  _CONFIG3H, _PBADEN_OFF_3H
            __CONFIG  _CONFIG4L, _LVP_OFF_4L & _XINST_OFF_4L        
            NOLIST
        endif
            LIST
    EEPROM_START	EQU	0F00000h
    BLOCK_SIZE	EQU	32
    About now?

    For sure there's no Device line for any 18F device. DEVICE is when you compile with PM, __CONFIG is when you compile with MPASM.
    Last edited by mister_e; - 10th December 2006 at 20:56.
    Steve

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

  2. #2
    malc-c's Avatar
    malc-c Guest


    Did you find this post helpful? Yes | No

    Default

    Ok - I've copied and pasted the code over the original INC file (I did back up the old one first) - and removed the ASM part from the PBP code and it compiled fine.

    On the breadboard RB0 is faintly lit and appears to be flickering slightly as I'm only getting +0.85v on RB0 - all other pins are low - also removing the Xtal seems to have no affect on the LED output, which to me would suggest that the timing is still not working ??

    Taking pin5 (RA3/AN3/Vref+) takes RB0 low (with or without Xtal present) if that has any bearing on what is happening.

    If I get chance I'll try and post a schematic of the basic hardware set up

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


    Did you find this post helpful? Yes | No

    Default

    Kind of strange behaviour... it's working as suppose here. I suspect a faulty contact or a bad PIC first... well i think ...
    Steve

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

  4. #4
    malc-c's Avatar
    malc-c Guest


    Did you find this post helpful? Yes | No

    Default

    Well I've tried a new Xtal and PIC and I still get the same result, only the LED appears to be more stable (+0.58v)

    I'll think I'll give up on this one...

  5. #5
    malc-c's Avatar
    malc-c Guest


    Did you find this post helpful? Yes | No

    Default

    Just in case it was the application that I was using to program the chip that was the cause, I loaded up the code in Winpic and then varified and read-back the code programmed using PICpgm - It varified and readback without errors. In fact I was able to program your code to a PIC using PICpgm, then read back from that PIC using WinPIC, change to a new PIC and program that from WinPIC, so it would seem that there are no issue with programming the PIC. So the problem is leaning to either coading or hardware, and given your experience and the fact you have it working fine your side of the pond, its a case of "that when you have eliminated the impossible, whatever remains, however improbable, must be the truth?" as Sherlock would of put it.

    I'll post up the schematic - just in case there is something I've overlooked.

    EDIT:

    Schematic uploaded - and tried 0.1uf decoupling capacitor (missed it of the drawing)
    Attached Images Attached Images  
    Last edited by malc-c; - 10th December 2006 at 22:24.

  6. #6
    malc-c's Avatar
    malc-c Guest


    Did you find this post helpful? Yes | No

    Default

    Well I've tried re-breadboarding it on a different breadboard and still the same.

    Any suggestions for a different PIC - preferably with 28 pins - internal oscillator and min of one A to D converter for the music input - supported by 2.46 ???

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


    Did you find this post helpful? Yes | No

    Default

    It's kinda strange but anyways..

    PIC18F2525, PIC18F2431, 2320,2220,2620,2680 are some i keep in stock here.

    i tried... even removing a Vss pin didn't provide any bad results... ARGH i hate that when it happen

    You also added the ADCON1=$0F line too?

    When you look at the config fuse in your DeviceProgrammer software... is LVP & DEBUG are set to off as well?

    The worst.. there's no revealant stuff multiplexed with PORTB.0 pin if ADCON1=$0F line is there OR if the PBADEN_OFF fuse is correctly programmed.. DAMN!
    Last edited by mister_e; - 10th December 2006 at 23:06.
    Steve

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

Similar Threads

  1. PIC16F690 PBP boundary crossing warning message
    By xnihilo in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 9th May 2008, 12:17
  2. Micro Code Studio - Warning message
    By flotulopex in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 17th November 2006, 22:17
  3. MicroCode Studio Boundary Warning Message
    By coyotegd in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 16th March 2006, 10:13
  4. Message String Table using Readcode
    By mytekcontrols in forum Code Examples
    Replies: 2
    Last Post: - 11th July 2005, 00:17
  5. warning message
    By pic beginner in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 23rd July 2004, 03:53

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