> -----Original Message-----
> From: David Gomez Otero [SMTP:david.gomezspam_OUTUPCNET.ES]
> Sent: Friday, December 08, 2000 12:19 PM
> To:   @spam@PICLISTKILLspamMITVMA.MIT.EDU
> Subject:      Re: [PIC]: Hardware for using MPLAB-ICD
>
> Thanks for the information.
>
> I have read all the docu that you all have told me, and i finally have one
> more question :
>
> I am building a startkit (for my personal usage) for the PIC  18pin ,  28
> pin  and 40pin,  and I  there I include the programmer, and
> some periphericals as LCD, leds,  a serial port ,....   and I also wanted
> to
> add a debugger facilitie for the 28-40 16F87X family.
>
> All the documentations talk about a special board that includes a 16F876
> MCU, and can be connected into the socket of the board where there is the
> PIC that I want to debug. So you connect the PC to a board that has a
> 16F876
> with a firmware written and from this board you use a 6-pin-connection to
> a
> header that can be connected into the socket where the PIC is, as a
> simulator ...
> but that implies that in my startkit I will have to add a part from the
> sockets for the normal MCU to use, an other one for the 16F876 because the
> ICD needs it????
>
> i think I am a bit confused ??
> is it possible to debug the 87x family directly connecting the 2 pins of
> the
> 87x MCU that i want to debug with the serial MAX232 to the PC without
> using
> this extra 16F876?  .  The idea is that I will build all my programs in
> this
> startkit board so I don't need the header to be connected to the target
> board  .
>
> thanks for the help
>
> david
>

>Yes you can build your own.  The debugger does have a PIC, but Microchip
>kindly (unintentionaly?) provided a way to program your own by supplying the
>hex code with MPLAB.  If you read through the links James provided at
>
>See the FREE IDC documentation on the piclist.com site
>www.piclist.com/techref/piclist/freeicd/
>and also
>http://www.piclist.com/techref/microchip/icd.htm
>
>then this explains pretty much all you need to know.  Unless you have all
>the bits lying around and/or are very keen to build your own for the fun of
>it, then buying the genuine article is a better bet.
>

>
> Dear all,
>
> Talking of hardware for the MPLAB, I wonder if there is such a thing as
> a Visual Basic DLL so that we can write software which automatically
> reprograms the PIC (rather than having to do this in the MPLAB
> software)?
>
> Chris
> --
> Dr. Chris Kirtley MD PhD
> Associate Professor
> HomeCare Technologies for the 21st Century (Whitaker Foundation)
> NIDRR Rehabilitation Engineering Research Center on TeleRehabilitation
> Dept. of Biomedical Engineering, Pangborn 105B
> Catholic University of America
> 620 Michigan Ave NE
> Washington, DC 20064
> Tel. 202-319-6247,  fax 202-319-4287
> Email: EraseMEkirtleyspamspamBeGonecua.edu
> http://engineering.cua.edu/biomedical
>
> Clinical Gait Analysis: http://guardian.curtin.edu.au/cga
> Send subscribe/unsubscribe to RemoveMElistprocKILLspaminfo.curtin.edu.au
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

>> -----Original Message-----
>> From: David Gomez Otero [SMTP:spamBeGonedavid.gomezSTOPspamEraseMEUPCNET.ES]
>> Sent: Friday, December 08, 2000 1:04 PM
>> To:   KILLspamPICLISTspamBeGoneMITVMA.MIT.EDU
>> Subject:      Re: [PIC]: Hardware for using MPLAB-ICD
>>
>> Ok.  it is clear now.
>>
>> Anyway, I took a look to the mpl876.hex file and it uses 14Kb, it is too
>> long for the 8K of the 16F876,  isn't it ?
>>
>> and, is it possible to use a 28pin 87X MCU  instead of the 40pin one ??
>> it
>> would be cheaper ...
>>
>>
>The size of the hex file isn't the same as the final program size, it is
>much larger because it is an ASCII representation of the code, using 4
>characters to represent one word of memory.  Plus there is an overhead
>ascociated with the addressing scheme and the checksums.
>
>The 16F876 is a 28 pin part.