> Folks, this week we discussed a project with a
>lot of input-outputs.
>Possible ways were: PIC18F, AVR, MSP430. I battled
>for PICs, cause I'd like to have a reason to go on
>with PICList (the only reason).
>
> It was a tough task, guys, but I almost succeeded.
>(I used an old good soviet style propaganda trick:
>I asked which horse power he would prefer: 48 (max
>number of i/o lines in AVR and MSP430) or 68 (number
>of i/o lines in PIC18F8720). So Mchip has won:-)
>The problem remained to solve was TQFP package.
>
> We emailed local Mchip guys with question if they
>have some adapter (a little PCB we could solder
>PIC18F8720 to, for example, or something else).
>When developing project we'll change application PCB
>many times and also microcontroller will be replaced
>to get statistic. We wrote we bought and successfully
>used a number of DIP PICs earlier.
>
> Am I stupid as rock?
>
> In response we've got absolutely irrelevant nice
>little message with 700K 39583b.pdf attachment.
>They told us we needn't adapter, we must place five
>jumpers onto PCB (5v,13v,data,strobe,ground)to
>program the chip.
> Didn't I told them we bought their PICs ealier?
> And this 13v for HVP for 68 i/o 80 pins PIC18F8720?
>
> And this unnecessary 700K 39583b.pdf attachment,
>because we've downloaded it before? Unsolicited
>700K during day-time with our phone lines here in
>Ukraine was a pain.
>
> The question about AVR and MSP got up again.
>Should I fight for PICs now?
>
> Could anybody tell me what is the common approach
>to handle 80 pin TQFP package when developing
>project?
>
>Thanks in advance.
>
>Mike Singer.
>
>
>The guy who sent me the attachment:
>---------------------
>s UWAVENIEM, aNTON kUZNECOW
>tEHNI^ESKIJ CENTR MICROCHIP
>TEL. +38-044-295-55-19
>
anton
KILLspammicrochip.com.ua
>
http://www.microchip.com.ua
>----------------------
>
>
>
>
>
>--
>
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
>email
.....listservKILLspam
.....mitvma.mit.edu with SET PICList DIGEST in the body
>
>
>
>
>