Searching \ for '8bit Hexfile problems - HELP ME! - Urgent!!!!!!' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/index.htm?key=8bit+hexfile+problems
Search entire site for: '8bit Hexfile problems - HELP ME! - Urgent!!!!!!'.

Truncated match.
PICList Thread
'8bit Hexfile problems - HELP ME! - Urgent!!!!!!'
1997\04\24@130216 by Graversen, Soeren

flavicon
face
Hi,

I'm sure this subject has been discussed before, but of cause one can never
find what one is looking for.....

I am building a CLIP-interface with an PIC16C84, and I have some troubles
using my c-compiler together with my MPLAB (newest version).

If the C-compiler generates code above 0x1FF, the code above is discarded
by MPLAB when I try to import it. I have manually viewed the 8bit Hexfile,
and the code is present.

I am using a Picstart Plus programmer, so I need to import the hex-file to
mplab and programme it from there!!!????
----
From: Soeren Graversen
         Electronic Engineer, Denmark
Mail:   spam_OUTgraverTakeThisOuTspampost1.tele.dk

1997\04\24@132507 by myke predko

flavicon
face
Soeren,

This is a known problem with MPLAB 3.22.  Change the part definition to a
PIC16F84 and you should be fine.

myke
{Quote hidden}

"My ancestors didn't spend millions of years clawing their way to the top of
the food chain, just so I could become a vegetarian"

1997\04\24@133947 by Octavio Nogueira

flavicon
face
>If the C-compiler generates code above 0x1FF, the code above is discarded
>by MPLAB when I try to import it. I have manually viewed the 8bit
Hexfile,
>and the code is present.


Use 16F84 in MPLAB

Octavio
======================================================
Octavio Nogueira  - e-mail:   nogueiraspamKILLspammandic.com.br
http://www.geocities.com/~oct_nogueira
"ProPic" Production PIC Programmer Windows under US$20
======================================================->

1997\04\24@142502 by Kevin Coble

flavicon
face
part 0 974 bytes
It worked itself out after I saved and re-opened a project in MPLAB.
I think it keeps the 0x1FF limit from the PIC16C54 it defaults to on
startup.

Hope this helps.

Kevin Coble


---------------------------------------------------
This message was created and sent using the Cyberdog Mail System
---------------------------------------------------



<x-rich><SMALLER><X-FONTSIZE><PARAM>10</PARAM><FONTFAMILY><PARAM>Geneva</PARAM>I had the same problem with MPLAB, importing a MacPIC source file.


It worked itself out after I saved and re-opened a project in MPLAB.
I think it keeps the 0x1FF limit from the PIC16C54 it defaults to on
startup.


Hope this helps.


Kevin Coble



---------------------------------------------------

This message was created and sent using the Cyberdog Mail System

---------------------------------------------------

</FONTFAMILY></X-FONTSIZE></SMALLER>
</x-rich>

1997\04\24@143501 by Andrew Warren

face
flavicon
face
myke predko <.....PICLISTKILLspamspam.....MITVMA.MIT.EDU> wrote:

> [The "512-byte 16C84" issue] is a known problem with MPLAB 3.22.
> Change the part definition to a PIC16F84 and you should be fine.

   Keep in mind, however, that the polarity of the PWRTE
   configuration bit is different between the 'C84 and the 'F84...
   When you program a 16C84 with MPLAB configured for the 16F84,
   you'll need to set the PWRTE to the OPPOSITE value of the one
   you want.

   -Andy

=== Andrew Warren - EraseMEfastfwdspam_OUTspamTakeThisOuTix.netcom.com
=== Fast Forward Engineering, Vista, California
=== http://www.geocities.com/SiliconValley/2499

More... (looser matching)
- Last day of these posts
- In 1997 , 1998 only
- Today
- New search...