Software reset - What am I doing wrong?

[mackrackit]

I have never had this problem before either and the 4550 or 2550 is what I use the most.

I normally have the MCLRE off and alway have the ICPRT off. The ICPRT is only available on the 44 pin packages and yes I use those too.

I have been reading section 25.9 of the data sheet trying to understand this.

[mackrackit]

Never mind.
I looked at the schematic for the demo board and ICPRT has to be ON.

[Christopher4187]

This is what Microchip uses for the config files. When their program is loaded, the power up sequence works fine so I don't think my issue is in the config file. If I can get the software reset to work correctly I would be golden.

#pragma config PLLDIV   = 5         // (20 MHz crystal on PICDEM FS USB board)
        #pragma config CPUDIV   = OSC1_PLL2   
        #pragma config USBDIV   = 2         // Clock source from 96MHz PLL/2
        #pragma config FOSC     = HSPLL_HS
        #pragma config FCMEN    = OFF
        #pragma config IESO     = OFF 
        #pragma config PWRT     = OFF 
        #pragma config BOR      = OFF
        #pragma config BORV     = 3
        #pragma config VREGEN   = ON      //USB Voltage Regulator
        #pragma config WDT      = OFF
        #pragma config WDTPS    = 32768
        #pragma config MCLRE    = ON
        #pragma config LPT1OSC  = OFF
        #pragma config PBADEN   = OFF
      #pragma config CCP2MX   = ON
        #pragma config STVREN   = ON
        #pragma config LVP      = OFF
        #pragma config ICPRT    = ON       // Dedicated In-Circuit Debug/Programming
        #pragma config XINST    = OFF       // Extended Instruction Set
        #pragma config CP0      = OFF
        #pragma config CP1      = OFF
      #pragma config CP2      = OFF
      #pragma config CP3      = OFF
        #pragma config CPB      = OFF
      #pragma config CPD      = OFF
        #pragma config WRT0     = OFF
        #pragma config WRT1     = OFF
      #pragma config WRT2     = OFF
      #pragma config WRT3     = OFF
        #pragma config WRTB     = OFF       // Boot Block Write Protection
        #pragma config WRTC     = OFF
      #pragma config WRTD     = OFF
        #pragma config EBTR0    = OFF
        #pragma config EBTR1    = OFF
      #pragma config EBTR2    = OFF
      #pragma config EBTR3    = OFF
        #pragma config EBTRB    = OFF

EDIT: My configs do match Microchips, I just changed them today to try and rectify this issue.

[Christopher4187]

I need to clear my head and rethink this. I just turned off the power up timer and it's a little better. Removing the power-up timer no longer shuts down the CAN network but my program still doesn't work. This was a significant issue because if the 18F wasn't reset before the CAN network came on line, my car would be disabled (i.e. no throttle and all warning lights illuminated.)

I must have changed the settings along the way and forgot I did so. Let me do some more investigating as this issue is most likely caused by me. Thanks for turning on that proverbial light bulb in my head.

[Christopher4187]

And the second problem is solved! But, it creates another issue. I use a serial LCD and when I used the HSPLL, I couldn't get the LCD to work correctly. Perhaps someone reading this thread has encountered this before.

I'm using a 20mhz crystal. I use $4054 for the LCD speed. I defined my OSC as 20. If I use the HSPLL setting, what speed do I have to set the LCD at?

[mackrackit]

I did not notice that...
With the configs posted use
DEFINE OSC 48

[Christopher4187]

No dice. I tried using all of the prescalers from 4 to 48 but none work. By using the Define OSC 48, my program will not work. Any other adjustments you can think of?

[Christopher4187]

I just ran a loop increasing the communication speed of the LCD by 1 and then displaying the speed. When I was able to read the information on the LCD, that is the speed to use. It looks like something from $40E2 to $40F6 works. I need to do a little more testing to find out if there any differences in that range. I'm not sure if this the right way to go about solving this problem but it works......for now.