Search found 17 matches

As a question, are you changing the BBSIZE setting in the fuses?.
The reason I ask, is the default boot block size should give this issue
at 0x7FF, not at 0xFFF. This was why I didn't consider this ...

Explicitly set the protection fuses off:

#FUSES NOWDT
#FUSES NOPROTECT
#fuses 6=0xE00F

The #fuses 6=0xE00F was the information I needed. I didn't know how to set the registers m ...

It needs a really short track as well.

The key is that this is what actually runs the CPU core. It runs at a much
lower voltage than the I/O (typically 1.8v), and if this is wrong individual
inst ...

I used a 45K80 to be sure.

I see you have a Vddcore problem. Presumably your board was actually
built for one of the chips that doesn't have this pin.
I have to mirrtor Newguy's comment about the ...

I learned a couple of years ago that "any old" 10uF cap might not necessarily do. Laid out a PCB with a pad for a 0603 package capacitor but the ESR in that tiny package was too high. Ha ...

Are you sure your chip is working correctly?.

Try a similar test program, but compile it to load at address 0, and write it
with the programmer.
Ensure it does serial I/O, and tests both receive ...

What is your compiler version number?

Sorry, you're right, I completely forgot to post that. I believe it is the most recent since I recently updated it a few weeks ago, 5.091.

Post what you have changed in loader.c.

The bootloader does work, so it is something you have done that is
causing the problem. You need to give us a chance to see 'what'.

That's the thing, I'm ...

OK.

Your new line is wrong.
I was talking about what is being 'loaded', rather than what is doing the
loading.

The correct lines are:

#if defined(__PCM__)
#org LOADER_END+1,LOADER ...

Er. That load line is completely wrong, and is not the load line it should
be reaching or using. The correct one for _PCH_, is:

#build(reset=LOADER_END+1, interrupt=LOADER_END+9)

The line yo ...

OK.
The point is that the packet you posted is not where the address is 0x0FF.
The packet you post is for address 0x0FF0.

Now address 0xFF, should never be written, since it is inside the bootl ...

Seriously to be writing to address 0FF0, there would need to be quite a
lot of code, not just an extra line like If (x==1) x=0; bootload.c, uses
up just a couple of hundred bytes of code. The bootl ...

I don't think that's FF. The first two digits after the colon are the record
length. The next four are the address.

Hex file format:
http://www.keil.com/support/docs/1584/

I've debugged ...

I've been using the CCS bootloader example, and I have something strange occurring, and for the life of me, I can't figure out what the difference is or what the error is.

I'm using a PIC18F45K80. ...

According to the 18F4580 data sheet, your PIC part number will only run
properly at 4.2v or higher. Look at this graph on page 422:

Look at Param. 1A, in the lower section for "Oscillator Fr ...