Post by thread:mplab

MPLAB will be available soon on Microchip's BBS. ______________________________ Reply Separator _________________________________ Subject: MPLAB Author: "Jose G. Pineda A. ELECTRONICO" <.....jpinedaKILLspam@spam@DINO.CONICIT.VE> at Internet_Exchange Date: 11/14/95 7:59 AM Does anyone know where to find MPLAB? ( ftp .. of course ). -- | ~~ ~~ /^\ | Jose Pineda | ~~ /^\ / \ ~~ | Fax : +58 2 2426039 | /_ \/ _ \ ~~ | E-mail : jpinedaKILLspamdino.conicit.ve | / # _ # _ # _ _ \ | Caracas, D.F. | / # # _ # # # # # _ \ | Venezuela |_/______#_#_#_#_#_#_#_#_#_____\_|

Joe McCauley wrote: >>Hi, >> >>Is MPLAB available from the Microchip ftp site? I could'nt find >>it yesterday (12/12/95) >> >>Joe >>________________________________________________________________ >> >>Joe McCauley >>Physics Department, Tel: 353-1-7022218 Trinity >>College, Fax: 353-1-6711759 >>Dublin 2, Email: .....pmcculeyKILLspam.....mail.tcd.ie" >>Ireland. MPLAB is not yet available from the ftp site. However, when we have a production release, it will be available. The production release is imminent. Check the ftp site in the next week or two and it should be there. Pete

I just downloaded mplab309.exe from mchipbbs.microchip.com from the int-rel directory. I tried to execute it under win95 by double-clicking on it in Explorer. It came up with: 'Run this file using File or Program Manager' Making sure that windows was detectable under a MSDOS prompt did not help and neither did using the Run.. command from the start menu. Anybody got any ideas? Cheers. J.W. ----------------------------------------------------------------- Johnnie Walker MSc Digital Systems Engineering Heriot-Watt University email: EraseMEceejbcwspam_OUTTakeThisOuTcee.hw.ac.uk ceejbwspam_OUTpp.hw.ac.uk www: http://www.cee.hw.ac.uk/~ceejbcw tel: (0131) 343 2864 -----------------------------------------------------------------

John B C Walker wrote: {Quote hidden}> > I just downloaded mplab309.exe from mchipbbs.microchip.com from the > int-rel directory. I tried to execute it under win95 by double-clicking > on it in Explorer. It came up with: > > 'Run this file using File or Program Manager' > > Making sure that windows was detectable under a MSDOS prompt did not help > and neither did using the Run.. command from the start menu. > > Anybody got any ideas? > > Cheers. > > J.W. > > ----------------------------------------------------------------- > Johnnie Walker > MSc Digital Systems Engineering > Heriot-Watt University > email: @spam@ceejbcwKILLspamcee.hw.ac.uk > KILLspamceejbwKILLspampp.hw.ac.uk > www: http://www.cee.hw.ac.uk/~ceejbcw > tel: (0131) 343 2864 > ----------------------------------------------------------------- Rather try the FTP site.

On Fri, 7 Jun 1996, Jattie van der Linde wrote: > > Rather try the FTP site. > I did use ftp: %ftp mchipbbs.microchip.com and ensured that download was type binary. The fault suggests that mplab does not like win95 although I'm sure this can't be true. ----------------------------------------------------------------- Johnnie Walker MSc Digital Systems Engineering Heriot-Watt University email: RemoveMEceejbcwTakeThisOuTcee.hw.ac.uk spamBeGoneceejbwspamBeGonepp.hw.ac.uk www: http://www.cee.hw.ac.uk/~ceejbcw tel: (0131) 343 2864 -----------------------------------------------------------------

John B C Walker wrote: > > On Fri, 7 Jun 1996, Jattie van der Linde wrote: > > > > > Rather try the FTP site. > > > > I did use ftp: > > %ftp mchipbbs.microchip.com > > and ensured that download was type binary. The fault suggests that mplab > does not like win95 although I'm sure this can't be true. I'm running MPLAB under Win95 and I did not experience any such problems. I got several files in a zipped package thou. If u like I can attach them as mail. Thanks Jattie.

Dennis Hromin wrote: > > That's really strange. The one I have ver 3.01 is 1.54 megs and even 3.09 > is also 1.54 megs. > Can you direct me to the url or ftp site where you downloaded this version? Unfortunately I cant seem to find the site where I got It from. I started off browsing David Taits Piclinks Page and from there to someone Else's site and eventually to Some FTP site. The File is in A zipped format and Include the Following. Directory of C:\TEMP . <DIR> 02-14-96 2:39p . .. <DIR> 02-14-96 2:39p .. LABHP301 EXE 457,927 05-17-96 7:51a labhp301.exe README LAB 16,963 05-17-96 7:23a readme.lab README EM 16,101 05-09-96 1:44p readme.em PPLUS101 EXE 93,993 05-17-96 7:52a pplus101.exe PMSTR300 EXE 433,335 05-10-96 10:22a pmstr300.exe MPLAB301 EXE 1,542,948 05-17-96 7:51a mplab301.exe README PLS 13,729 05-17-96 7:32a readme.pls DIR TXT 0 06-12-96 10:09a dir.txt 8 file(s) 2,574,996 bytes In the .ZIP file it totals to 2.4M You've got to Install MPLAB and all the adons to get all the Features > Or does this version also include the help file? I got my help file > seperately because it > did not come with the 3.01 zip file. I got it off the microchip bbs. > (telnet) What version This versiion is 3.01 > are you using? 3.01 or 3.09? does it make a difference? I suppose there will be Some Difference. Maybe someone else can shed some light on this. Jattie van der Linde.

Francesco Loconte wrote: > > Does anyone have any ideas about where i can find MBLAB on Internet and a > simulator of PIC16c84 for PC ? > Thank to every body. Try it at http://www.microchip2.com/softupdt.htm -- Friendly Regards Tjaart van der Walt ______________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | |WASP International GSM vehicle tracking and datacomm solutions| | +27-(0)11-622-8686 | http://wasp.co.za | |______________________________________________________________|

Francesco Loconte wrote: > > Does anyone have any ideas about where i can find MBLAB on Internet and a > simulator of PIC16c84 for PC ? > Thank to every body. > > Francesco Lo Conte > [s191448EraseME.....studenti.ing.unipi.it] Ciao Francesco, puoi trovare il software presso il sito della microchip http://www.microchip.com/ se hai difficoltˆ posso farti avere, visto che studio a Pisa, il simulatore, per l'mplab devo chiedere ad un mio amico che lo dovrebbe avere. Fammi sapere, Ciao Michele

Is it just my imagination (poor engineering skills?) or is mplab the worst piece of software available? Here's the situation: I'm writing drivers for four seven segment displays multiplexed on 12 i/o pins. Simple right? Of course it is. Unfortunatly, I find more often then not, when a computer is involved nothing is as simple as it should be. Single stepping through the program works. The tris registers say what they should, (all lows) port's a and b say what they should, things turn off. things turn on. things loop. it all works perfect. The problem: It doesn't work in my circuit. The program I wrote to test the display should count from 0 to 9999. However, it doesn't. It just stays on zero. Constnatly outputing 4 zeros. I modified the source, and did a "build all" in an attempt to start it at 7777 instead of 0, which should have had it outputing all 7's. But it doesn't. Still all zeros. All the time. Clues: When single steping in debug it all looks ok. The registers (4 binary values, which get compacted into BCD values, which then get converted to the proper led code, and the tris registers) all do what they should. The only thing that isn't "normal" is at certain points, when I right click on a section of code to be able to do a "run to here" sometimes the "run to here" option is faded. Which usually means you're NOT on a peice of code. But I clearly am. I've been pulling hair out in frustration all afternoon. Anyone have idea's where I should be looking for the problem? -Shane.

>Is it just my imagination (poor engineering skills?) or is >mplab the worst piece of software available? Boy, did you leave yourself open on this one. >Here's the situation:... <Nuked> ...Which usually means you're NOT on a peice of code. But I >clearly am. >I've been pulling hair out in frustration all afternoon. Anyone >have idea's where I should be looking for the problem? Last year, I spent about three months trying to find exactly the same kind of problem in the same kind of situation (only it was for 3 7-Segment LED displays). I had a very long initial delay (it could take up to three seconds), so my solution to this to debug my display code was to jump around the long setup. Big mistake; the problem was that I was improperly initializing three variables and enabling an interrupt handler and *then* doing the 3 second setup. If the 3 second set up wasn't there, everything would work fine. Run MPLAB all the way through to the display code. What this means is you'll have to start up the simulator, setup a break point and go watch the "X-Files", but wasting an hour this way will give you the actual conditions of the PIC, not what you think they should be. Or, drop $3K and buy a PICMaster (I wish I could). Good luck, myke "One must invoke enough raw truth to punch a hole in the world" - Darl Af

On Tue, 2 Sep 1997, myke predko wrote: > Boy, did you leave yourself open on this one. > > >Here's the situation:... > <Nuked> > ...Which usually means you're NOT on a peice of code. But I > >clearly am. *blink* Did I write that? Had to check my outbox and I guess I did. I meant: Which usually means it's not a peice of code. But it clearly is. (ie when you try to "run to here" where there isn't code, it won't let you.) Or something :) <snip> > Big mistake; the problem was that I was improperly initializing three > variables and enabling an interrupt handler and *then* doing the 3 second > setup. If the 3 second set up wasn't there, everything would work fine. Ok. 16c54. No interrupts that I know of. Just wdt which is turned off. Instead of stepping over the long parts of code, I modified the values so they wouldn't loop 1f times, but only once. > Run MPLAB all the way through to the display code. What this means is > you'll have to start up the simulator, setup a break point and go watch the > "X-Files", but wasting an hour this way will give you the actual conditions > of the PIC, not what you think they should be. I've tried this. Set it up, run/debug/animate, and watch all the numbers do what they should... But again, instead of leaving everything set for the full display time, I shortened it so it wouldn't loop as much. Everything appeared to be normal. The only thing that made it output anything other than 0000, was seting up the values to 7777,and removing the bcd packing routine. So it would appear my problem lies there... it appears to work when I single step. Can anyone see anything wrong with this bit: swapf digit2,w ;put tens place into high nibble iorwf digit1,w ;ior ones place into low nibble. movwf DSPbcdLow swapf digit4,w ;put thous into high nibble iorwf digit3,w ;ior hunds into low nibble. movwf DSPbcdHigh ? Or, drop $3K and buy a PICMaster (I wish I could). > > Good luck, > > myke > > "One must invoke enough raw truth to punch a hole in the world" - Darl Af > Punch? How about invoking enough precise knowledge to poke a hole in it?:) -Shane.

Shane Nelson wrote: > When single steping in debug it all looks ok. The registers (4 > binary values, which get compacted into BCD values, which then > get converted to the proper led code, and the tris registers) all > do what they should. The only thing that isn't "normal" is at > certain points, when I right click on a section of code to be > able to do a "run to here" sometimes the "run to here" option is > faded. Which usually means you're NOT on a peice of code. But I > clearly am. > When you changed your code, did it reassemble correctly? The reason I ask is because of a similar "problem" I once encountered using Microsoft's Codeview debugger. In that situation my C code was in 7 different modules - the Make utility was configured to compile only the modules that had changed since the last exe had been built. If I was looking away from the monitor (missing an error message and the indication that the module did NOT compile successfully) and pulled the program into the debugger, it would use the _text_ file from my latest editing session and the _symbol_ information from the last successful recompile. This resulted in breakpoints not being reached and "run to here" not working as expected because what the debugger was running and what I thought it was running could have been offset my one or more lines. --Matt --

That's exactly what I think is happening. Except, there are no apparent erros or warning messages. I commented out everything and made it display just fixed values which worked. And I'm slowly adding the rest of my code back in to try to find the problem. My guess is it'll be working without any changes, and I'll get to blame mplab :) -Shane. On Tue, 2 Sep 1997, Matt Bonner wrote: > When you changed your code, did it reassemble correctly? The reason I <snip> > it would use the _text_ file from my latest > editing session and the _symbol_ information from the last successful > recompile. This resulted in breakpoints not being reached and "run to > here" not working as expected because what the debugger was running and > what I thought it was running could have been offset my one or more > lines. > --Matt > -- >

Figured it out! First I got mplab to behave properly. The problem with the "run to here" thing appears to have been caused because I had two files with the same name. One was my projects .asm file, and one was a #include file. Different paths. Same name. After I changed the name of the #include file the mplab problems went away. But my circuit still didn't work. The software was perfect tho. After much experimenting, I noticed that it appeared to be reseting. Apparently because of a dirty power supply. Added a small cap between +5v and 0v, and the whole thing works now. I had no idea a pic and a few 7 segment displays could dirty a power supply so badly that it reset itself. -Shane.

On 3 Sep 97 at 10:53, Shane Nelson wrote: > Figured it out! First I got mplab to behave properly. The > problem with the "run to here" thing appears to have been caused > because I had two files with the same name. One was my projects .asm > file, and one was a #include file. Different paths. Same name. After > I changed the name of the #include file the mplab problems went > away. Had similar problem wiith Visual C (1.52) - had a .h file same name as a system one (io.h I think) Most of it worked - it'd compile etc, but the IDE stuffed up when debugging. I suspect it was something to do with not distinguishing between #include "io.h" and #include <io.h> ; and the set include = path environment thing. I chalked it to experience and renamed my h file. Nailing it down took a while. > > But my circuit still didn't work. The software was perfect tho. > After much experimenting, I noticed that it appeared to be reseting. > Apparently because of a dirty power supply. Added a small cap > between +5v and 0v, and the whole thing works now. > > I had no idea a pic and a few 7 segment displays could dirty a > power supply so badly that it reset itself. Just try running a PIC off a plugpak :( Between the hopeless regulation of the transformers in those things, and the very small cap (100u or so) they are fairly useless. (except the new switchmode ones) MikeS <EraseMEmikesmith_ozrelaymail.net>

>I had no idea a pic and a few 7 segment displays could dirty a >power supply so badly that it reset itself. It isn't the PIC's fault... Andy ================================================================== Andy Kunz - Montana Design - 409 S 6th St - Phillipsburg, NJ 08865 Hardware & Software for Industry & R/C Hobbies "Go fast, turn right, and keep the wet side down!" ==================================================================

Hi & seasons greetings ! Has anyone out there used the disassembler display in MPLAB ? I am trying to read the contents of a 'F84 hex file but the 'Program Memory' window only shows 'Hex' or 'Machine Code' views. When I do switch to the 'Disassembler' view, it looks the same as 'Machine Code' ! The About box shows 'Processor version 0.0000' and 'Disassembler version 2.0000'. What am I doing wrong ? Help files give no clues either. (already RTFM !) Regards... _______________________________________________________________ Dave Duffy Audio Visual Devices RemoveMEAVDEraseMEEraseMEmailbox.uq.edu.au Unit 8, 9-11 Trade Street, Cleveland, Queensland 4163 Australia Phone: +61 7 38210362 Facsimile: +61 7 38210281 _______________________________________________________________

David Duffy <RemoveMEPICLISTspam_OUTKILLspamMITVMA.MIT.EDU> wrote: > I am trying to read the contents of a 'F84 hex file but the 'Program > Memory' window only shows 'Hex' or 'Machine Code' views. When I do > switch to the 'Disassembler' view, it looks the same as 'Machine > Code' ! David: This is normal. The "disassenbler" view relies on information in the ".COD" file... If you don't have a COD file, it can't generate labels and symbols, so the result looks just like the "machine code" view. -Andy === Andrew Warren - RemoveMEfastfwdTakeThisOuTspamix.netcom.com === Fast Forward Engineering - Vista, California === http://www.geocities.com/SiliconValley/2499

Has anyone been using the latest MPLAB? i installed it, but not in the default C:\MPLAB directory. when i try to do the single source example in TUTOR.PDF, i get a 'can't find SAMPLE.HEX' type error after trying to build the project. if i open SAMPLE.ASM and attempt to assemble it, it says it can't find an open file of the proper name. i'm new to PICs, and while the IDE seems like a useful tool, it is quite a bit different from the 80xx tools i'm using, and i don't want to spend a lot of time playing with an apparent beta level tool when the DOS MPASM and MPSIM with PFE will get the job done. thanks for the input bowman

part 0 1099 bytes <META content=text/html;charset=iso-8859-1 http-equiv=Content-Type> <META content='"MSHTML 4.72.2106.6"' name=GENERATOR> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT color=#000000 size=2>Hi,</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>I'm trying to use MPLAB 3.40, but I'm new to PICs. I have read the MPLAB Help file, but I can not manage to copy a file into the project. Not as described in the help file. I have already tried some hints on some similar problems, but it doesn't seem to help. </FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT size=2>Can someone give a hint ?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Best regards</FONT></DIV> <DIV><FONT color=#000000 size=2>Øystein.</FONT></DIV></BODY></HTML> </x-html>

v3.31 is like this: open new project, select *.asm file, OK project. save project [alt], [w]indow, Pr[o]ject here it is ! note: include files only show as added after successful assembly. version 3.4 was until recently a "beta" I tried it then and decided to continue with 3.31 for now. recent 3.4 may be better and is required if using relocatable "modules" regards Graham Daniel. ¯ystein Straume wrote: {Quote hidden}> > Hi, > > I'm trying to use MPLAB 3.40, but I'm new to PICs. I have read the > MPLAB Help file, but I can not manage to copy a file into the project. > Not as described in the help file. I have already tried some hints on > some similar problems, but it doesn't seem to help. > > Can someone give a hint ? > > Best regards > ¯ystein.

Xystein Straume wrote: > Hi, > > I'm trying to use MPLAB 3.40, but I'm new to PICs. I have read the > MPLAB Help file, but I can not manage to copy a file into the project. > Not as described in the help file. I have already tried some hints on > some similar problems, but it doesn't seem to help. > > Can someone give a hint ? > > Best regards > Xystein. Encoding: quoted-printable I have 3.31 at work, but I discovered this at home saturday, where I have 3.40, so I have to do this from memory. When you create the project, you name it, and then the name appears in a big empty box at the bottom of the dialog with something like ".[hex]" after it. Click on that name, then "properties" should become active. If you then click "properties", you can get to the box to select which source files to include in the project. Bruce Sherry Strobe Data, Inc sherrySTOPspamspam_OUTstrobedata.com

Peter Schultz wrote: > > Hi All, > I just wondering how Microchip figure out the new version number. > I was thinking a lot, but still do not see any explainable connection > between 3.40.09 and 3.99.06. > Peter > KILLspamschupetspamBeGonedvp.com v3.40.09 was the 9th build after the released version of v3.40. v3.99.06 is the sixth build of an advance release in preparation for v4.00. -- ___________________________ | Darrel Johansen | | tempe, arizona | | EraseMEdarreljEraseMEprimenet.com | |_________________________|

> Van: Stig Brautaset <spamBeGonesbrautasKILLspamC2I.NET> > Aan: .....PICLISTspam_OUTMITVMA.MIT.EDU > Onderwerp: MPLAB > Datum: vrijdag 27 november 1998 21:08 > > I use MPLAG 3.40.00, and whenI try to type teh 'letter' $, it refuses to do > so. Is there a bug, or is there some tric I don't know of? That's probably not MPLAB's fault. It has most likely to do with country-dependend setings. I think that the '$' is replaced with a special character more common to your country. But... to type any kind of char you could use the numeric key-pad. To get a "$" sign just press-and-hold the ALT-key, type 36 (NUMERICAL-keys "3" and "6" ), and release the ALT-key. A "$" sign should apear. Greetz, Rudy Wieser

Dear PICsters, I try to debug some PIC12C508 code in MPlab IDE simulator. Half a year ago I could watch the w and GPIO registers in a watch window. After installing MPlab 4 this watch works neither in MPlab 3.4 nor in MPlab 4.0. GPIO watch only shows asynchronous stimulus. What am I doing wrong? Leo van Loon SBB simpeltronics Netherlands tel +31 (0481) 450034 fax+31 (0481) 450051 mail TakeThisOuTsbb.simpeltron.....TakeThisOuTtip.nl url http://www.sbb-simpeltronics.nl SBB simpeltronics ontwikkelt technische projecten voor basisschool en basisvorming. SBB simpeltronics develops technical projects for children in primary and secondary education.

part 0 3099 bytes <P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">It's not an error, it's a warning.  The assembler is not particularly clever and dosen't recognise that you have explicity changed banks in the previous instruction.  It can be annoying, but your code should still assemble OK.</FONT></P> <P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Mike Rigby-Jones</FONT> </P> <UL> <P><FONT SIZE=1 FACE="Arial">{Original Message removed}

Aaron wrote: {Quote hidden}> I am getting errors when compiling the following > > PAGE0 > CLRF PORTA > CLRF PORTB > PAGE1 > CLRF TRISA > MOVLW b'00001010' > MOVWF TRISA > CLRF TRISB > > I am programming a 16f873 and have got the pages defined as: > #DEFINE PAGE0 BCF STATUS,RP0 > #DEFINE PAGE1 BSF STATUS,RP0 > > when compiling i get the message > Message[302] A:\ECU.ASM 108 : Register in operand not in bank 0. Ensure > that bank bits are correct. > > what am i doing wrong > > aaron Nothing! IT is a warning not an error. -- Thomas C. Sefranek WA1RHP ARRL Instructor, Technical Specialist, VE Contact. http://www.harvardrepeater.org http://hamradio.cmcorp.com/inventory/Inventory.html

I agree with Thomas there is no any error just as a warning! I'm working with PIC17C75X and the same warning occurs and the programs work as well. So I guess the same happen with u. Regards, Ismael M. Khangane, Instituto de Automatica Industrial IAI-CSIC. Spain. Thomas C. Sefranek escribis: {Quote hidden}> Aaron wrote: > > > I am getting errors when compiling the following > > > > PAGE0 > > CLRF PORTA > > CLRF PORTB > > PAGE1 > > CLRF TRISA > > MOVLW b'00001010' > > MOVWF TRISA > > CLRF TRISB > > > > I am programming a 16f873 and have got the pages defined as: > > #DEFINE PAGE0 BCF STATUS,RP0 > > #DEFINE PAGE1 BSF STATUS,RP0 > > > > when compiling i get the message > > Message[302] A:\ECU.ASM 108 : Register in operand not in bank 0. Ensure > > that bank bits are correct. > > > > what am i doing wrong > > > > aaron > > Nothing! IT is a warning not an error. > > -- > Thomas C. Sefranek WA1RHP > ARRL Instructor, Technical Specialist, VE Contact. > http://www.harvardrepeater.org > http://hamradio.cmcorp.com/inventory/Inventory.html

I've just finally started to use MPLAB. (I couldn't peel myself from DOS MPSIM) It's pretty good I suppose, but frustrating at times as well. It caught me a real beaut. It doesn't display a RED error bar after compiling if your code runs of the end of the ROM space available for the chip selected. It just gives a warning which may be written past the end of the page size on the compile results screen. I couldn't work out why the code kept failing, until I finally simulated it and found the problem. I didn't expect any errors because of the GREEN error bar, but it pays to check every one of those result lines I suppose. -- Best regards Tony http://www.picnpoke.com .....salesRemoveMEpicnpoke.com

I really like MPLAB and Microchip, I wanted to get started playing around w/ microcontrollers and they were kind enough to give me a decent IDE w/ assembler/simulator, some free sample chips to play with, and the code for a bootloader so I could get code on my chips at home (there's a burner at school I used to get the bootloader on the chip). Guess who I'll go to when I'm working in industry and need a microcontroller for a project which will ship thousands of units? ~Jake B On 5/2/05, ThePicMan <RemoveMEthepicmanspamBeGoneinfinito.it> wrote: {Quote hidden}> At 10.16 2005.05.02 -0500, you wrote: > > >>>7. Brand Loyalty ... This last one may not mean much, but Microchip has > >>> been good to me by supplying samples and excellent > >>> support (both H/W and S/W), and for that, they have > >>> earned my loyalty. > >> > >>Indeed, but that 4MHz bug of the 18F8720 and 18F1x20 really made me mad.. > >>I bought more than 100 of each.. now what do I do with them??? > >> > >>"Workaround: run them at 4MHz".. INGENIOUS! > > > > > >Have you contacted Microchip or a distributor (ie Arrow) to see about > exchanging A3 parts for A4 or higher revision parts? > > I originally bought them off an eBay auction. > Moreover, to save space they are packed in a quite artigianal way (some, > truly few, may have bent pins). > > Q: Should I still contact Microchip? :P > > > > --