Post by thread:Availability of 16F877

At 11:35 1998-12-05 -0500, you wrote: > Does anyone know when the 16F877 will be available for production runs. > >Thanks Ray > And when and where can we get a few samples? Where can we learn more about it«s debugging feature. The datasheet just say it is available from Mchip and uses the serial programming pins, consumes one stack level and some program memory. BTW, I could not reach http://www.microchip.com for the moment. Thanks in advance /Morgan /Morgan Morgan Olsson ph +46(0)414 70741 MORGANS REGLERTEKNIK fax +46(0)414 70331 H€LLEKS (in A-Z letters: "HALLEKAS") SE-277 35 KIVIK, SWEDEN spam_OUTmrtTakeThisOuTiname.com ___________________________________________________________

> Where can we learn more about it«s debugging feature. The datasheet just > say it is available from Mchip and uses the serial programming pins, > consumes one stack level and some program memory. How compatible is it to the 16C77? I have a 16C77 HEX file that I don't have the source of. I can't do changes to it, except for hex editing single commands (to not move stuff around). Can I use the 16F877 with that software?

>How compatible is it to the 16C77? I have a 16C77 HEX file that I don't >have the source of. I can't do changes to it, except for hex editing >single commands (to not move stuff around). Can I use the 16F877 with >that software? Memory layout appears very similar. A few things are changed/added (2 bytes for ADRES, 2 for EEADR, 2 for EEDATA). Overall, it looks good. Only thing I picked up right away wrong is that you can't have a code-protected chip program itself. That, says I, is the stupidest thing around. The reason for self-programming is so that you can update it in the field w/o sharing the code with everybody who cares to read it from their chip burner. Andy ================================================================== Andy Kunz - Statistical Research, Inc. - Westfield, New Jersey USA ==================================================================

> Van: Marc <.....marcKILLspam@spam@AARGH.FRANKEN.DE> > Aan: PICLISTKILLspamMITVMA.MIT.EDU > Onderwerp: Re: Availability of 16F877 > Datum: zondag 6 december 1998 20:31 Hello Marc, <Snip> > How compatible is it to the 16C77? I have a 16C77 HEX file that I don't > have the source of. I can't do changes to it, except for hex editing > single commands (to not move stuff around). Can I use the 16F877 with > that software? Maybe you could disassemble the code ... I have heard that MPLAB can do it for you, but to write a dis-assembler yourself should be (and is, I've 'build' one in QBasic for the 16C84 and 17C44) quite easy. Greetz, Rudy Wieser

>> How compatible is it to the 16C77? I have a 16C77 HEX file that I don't >> have the source of. I can't do changes to it, except for hex editing >> single commands (to not move stuff around). Can I use the 16F877 with >> that software? > >Maybe you could disassemble the code ... I have heard that MPLAB can do it >for you, but to write a dis-assembler yourself should be (and is, I've >'build' one in QBasic for the 16C84 and 17C44) quite easy. Timo Rossi also did a disassembler which I've used and like. I don't have the URL (I found it with Alta Vista or Yahoo) but if you e-mail PRIVATE .....mtdesignKILLspam.....fast.net I'll send you the ZIP file. Andy ================================================================== Andy Kunz - Montana Design - http://www.users.fast.net/~montana ==================================================================

I'm not sure why you would use a brand new, possibly more expensive part in replacement for a 16c77. The flash parts are going to have a 10-bit A/D, with 2 registers for the result. That's the only difference I've been able to pic (no pun) out of the datasheet since yesterday. And of course, the new flash programming specifications. -Dave >Date: Tue, 8 Dec 1998 11:21:55 +0100 >Reply-To: pic microcontroller discussion list <EraseMEPICLISTspam_OUTTakeThisOuTMITVMA.MIT.EDU> {Quote hidden}>From: Caisson <caissonspam_OUTTELEBYTE.NL> >Subject: Re: Availability of 16F877 >To: @spam@PICLISTKILLspamMITVMA.MIT.EDU > >> Van: Marc <KILLspammarcKILLspamAARGH.FRANKEN.DE> >> Aan: RemoveMEPICLISTTakeThisOuTMITVMA.MIT.EDU >> Onderwerp: Re: Availability of 16F877 >> Datum: zondag 6 december 1998 20:31 > >Hello Marc, > ><Snip> > >> How compatible is it to the 16C77? I have a 16C77 HEX file that I don't >> have the source of. I can't do changes to it, except for hex editing >> single commands (to not move stuff around). Can I use the 16F877 with >> that software? > >Maybe you could disassemble the code ... I have heard that MPLAB can do it >for you, but to write a dis-assembler yourself should be (and is, I've >'build' one in QBasic for the 16C84 and 17C44) quite easy. > >Greetz, > Rudy Wieser ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

> I'm not sure why you would use a brand new, possibly more expensive part > in replacement for a 16c77. The flash parts are going to have a 10-bit > A/D, with 2 registers for the result. That's the only difference I've > been able to pic (no pun) out of the datasheet since yesterday. And of > course, the new flash programming specifications. > > -------------> what about the internal EEPROM similar to the F84 ? Are there other parts now besides this new one that contains this?

At 08:11 AM 12/8/98 PST, you wrote: >I'm not sure why you would use a brand new, possibly more expensive part >in replacement for a 16c77. The flash parts are going to have a 10-bit >A/D, with 2 registers for the result. That's the only difference I've >been able to pic (no pun) out of the datasheet since yesterday. And of >course, the new flash programming specifications. THey are also self-programmable and have more internal EEPROM. ================================================================== Andy Kunz - Montana Design - http://www.users.fast.net/~montana ==================================================================