PIC files download List
You are free to download the following files. If you wish to list your files here, read the instructions at the bottom of this page. |
FILENAME |
Size |
Date |
Description / Author |
** ASSEMBLERS/DISASSEMBLERS ** |
|||
|
|||
** MONITORS / DEBUGGERS ** |
|||
|
|||
** DATA LOGGER / CAPTURE ** |
|||
|
|||
** COMMUNICATION ** |
|||
53515 |
03/23/98 |
RS232<>I2C,
RS232<>SIRCS protocol convertor- Glenn
Goovaerts |
|
|
|||
** MATH ROUTINES ** |
|||
|
|||
** MISC. INFORMATION AND UTILITY ** |
|||
|
|||
** HARDWARE IMAGE FILES ** |
|||
|
|||
** DATA SHEETS ** |
|||
|
|||
** TEXT FILES ABOUT MAGAZINES, TIPS, FAQ'S... ** |
|||
±359k |
JUL/2000 |
Páginas 678, 698, 699, 700 e 701 da EPE |
|
±150k |
NOV/2000 |
Páginas
858 e 859 da EPE |
|
ELEKSET28.JPG |
±150k |
SET/2000 |
Páginas
28-34 da revista ELEKTOR |
EPE752.JPG |
±150k |
OCT/2000 |
Páginas
752, 753, 754, 755, 756, 757, 758 e 759 da EPE |
** NEW (UNSORTED) FILES ** |
|||
28417 |
04/24/99 |
Assembler file extracted from the Microchip's 00689A.PDF file. |
|
Note: The above files were supplied by the author or from some internet sites.
Send the files to wagnerl@earthlink.net as
attached files to an email subject "DOWNLOAD LIST", and you need to
include an additional text file, or include in the source text a line explaining
that this file is free for download, including (if you want) your email address and name.
If you do not want your name to appear in the list as the author, you need to
tell me that, as a default I will always include your email/name as the author
in the list. If in any part of your source code file exist the word "Copyright"
and even so you want to turn it public and free for download, it is a requirement
that you write in the first lines of the source code that it is free for download,
it would avoid any future problems. It is a good rule of thumb to comment
all source code lines, or at the begining of the code routines, explaining what
it does, for the reader better understanding of the code. Remember that most
people learn by example, so if they can read what those code lines represent
they will learn faster and your code will be more valuable. Avoid to use common
names for the filename. If I receive two files with the same name, I will need
to change one, and then it would be different from your original name.
An easy way to generate filenames for public domain is using your name initials
at the begining of the filename, example; John Smith sending an UART code, just
name it as JS_UART.ASM or similar. As the author, You know much better
the funtion of your software, so you are the best person to describe your software,
so please, describe it in few words so I can use that text in the list, example:
"16F84 PORT SETTINGS". You are free to send the source code,
a text file about it and even a binary code or the Intel hex code, in this case
I will group all files together in a zip file with the same filename from the
.asm file. I thank you in name of the readers who will enjoy the benefits
of your files listed here.