Download False Flesh For PC Windows and Mac APK 1.0 - Free. All sources and details only here. A place for pictures and photographs. My download speed is phenomenal, but my upload speed is just mediocre, so for me it sometimes takes awhile when I'm uploading dozens of 24MP DSLR pics. EA Based on peak of last 'x candles. Ea finds the peak of previous 'x' candles in a particular Timeframe. The peaks should be tested at least twice. Valid examples are attached in the pic. Common reasons include incorrect or failed installation or uninstallation of software that may have. Megavideo, zshare videos, and pics on sites like.
Добавил:Chapter 1
main()
{
TRISA = 0; // all PORTA pins output
PORTA = 0xff;
}
Retesting PORTA
1.Rebuild the project now.
2.Set the cursor on the TRISA assignment.
3.Execute a 'Run to Cursor' command to skip all the compiler initialization just as we did before.
4.Execute a couple of single steps and...we have it!
Figure 1-6. MPLAB IDE Watch window detail; PORTA content has changed!
If all went well, you should see the content of PORTA change to 0x00FF, highlighted in the Watch window in red. Hello, World!
Our first choice of PORTA was dictated partially by the alphabetical order and partially by the fact that, on the popular Explorer16 demonstration boards, PORTA pins RA0 through RA7 are conveniently connected to 8 LEDs. So if you try to execute this example code on the actual demo board, you will have the satisfaction of seeing all the LEDs turn on, nice and bright.
Testing PORTB
To complete our lesson, we will now explore the use of one more I/O port, PORTB.
It is simple to edit the program and replace the two PORTA control register assignments with TRISB and PORTB. Rebuild the project and follow the same steps we did in the previous exercise and…you'll get a new surprise. The same code that worked for PORTA does not work for PORTB!
Don't panic! I did it on purpose. I wanted you to experience a little PIC24 migration pain. It will help you learn and grow stronger.
It is time to go back to the datasheet, and study in more detail the PIC24 pin-out diagrams. There are two fundamental differences between the 8-bit PIC microcontroller architecture and the new PIC24 architecture:
•Most of PORTB pins are multiplexed with the analog inputs of the analog-to-digital converter (ADC) peripheral. The 8-bit architecture reserved PORTA pins primarily for this purpose—the roles of the two ports have been swapped!
The first flight
•With the PIC24, if a peripheral module input/output signal is multiplexed on an I/O pin, as soon as the module is enabled, it takes complete control of the I/O pin—independently of the direction (TRISx) control register content. In the 8-bit architectures, it was up to the user to assign the correct direction to each pin, even when a peripheral module required its use.
By default, pins multiplexed with 'analog' inputs are disconnected from their 'digital'input ports. This is exactly what was happening in the last example. All PORTB pins in the PIC24FJ128GA010 are, by default at power-up, assigned an analog input function; therefore, reading PORTB returns all 0s. Notice, though, that the output latch of PORTB has been correctly set although we cannot see it through the PORTB register. To verify it, check the contents of the LATB register instead.
To reconnect PORTB inputs to the digital inputs, we have to act on the analog-to-digital conversion (ADC) module inputs. From the datasheet, we learn that the special-function register AD1PCFG controls the analog/digital assignment of each pin.
Upper Byte: | |||||||
R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 |
PCFG15 | PCFG14 | PCFG13 | PCFG12 | PCFG11 | PCFG10 | PCFG9 | PCFG8 |
bit 15 | bit 8 | ||||||
Lower Byte: | |||||||
R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 |
PCFG7 | PCFG6 | PCFG5 | PCFG4 | PCFG3 | PCFG2 | PCFG1 | PCFG0 |
bit 7 | bit 0 |
bit 15-0 PCFG15:PCFG0: Analog Input Pin Configuration Control bits
1 = Pin for corresponding analog channel is configured in Digital mode; I/O port read enabled 0 = Pin configured in Analog mode; I/O port read disabled, A/D samples pin voltage
Figure 1-7. AD1PCFG: ADC port conÞguration register.
Assigning a 1 to each bit in the AD1PCGF special-function register will accomplish the task. Our new and complete program example is now:
#include
main() | ||
{ | ||
TRISB = | 0; | // all PORTB pins output |
AD1PCFG = | 0xffff; | // all PORTB pins digital |
PORTB = | 0xff; | |
} |
This time, compiling and single-stepping through it will give us the desired results.
Chapter 1
Figure 1-8. Hello Embedded World Project.
Post-flight briefing
After each flight, there should be a brief review. Sitting on a comfortable chair in front of a cool glass of water, it's time to reflect with the instructor on what we have learned from this first experience.
Writing a C program for a PIC24 microcontroller can be very simple, or at least no more complicated than the assembly-language equivalent. Two or three instructions, depending on which port we plan to use, can give us direct control over the most basic tool available to the microcontroller for communication with the rest of the world: the I/O pins.
Also, there is nothing the C30 compiler can do to read our mind. Just like in assembly, we are responsible for setting the correct direction of the I/O pins. And we are still required to study the datasheet and learn about the small differences between the 8-bit PIC microcontrollers we might be familiar with and the new 16-bit breed.
As high-level as the C programming language is touted to be, writing code for an embedded-control device still requires us to be intimately familiar with the finest details of the hardware we use.
The first flight
Notes for assembly experts
If you have difficulties blindly accepting the validity of the code generated by the MPLAB C30 compiler, you might find comfort in knowing that, at any given point in time, you can decide to switch to the 'Disassembly Listing' view. You can quickly inspect the code generated by the compiler, as each C source line is shown in a comment that precedes the segment of code it generated.
Figure 1-9. Disassembly Listing Window.
You can even single-step through the code and do all the debugging from this view, although I strongly encourage you not to do so (or limit the exercise to a few exploratory sessions as we progress through the first chapters of this book). Satisfy your curiosity, but gradually learn to trust the compiler. Eventually, use of the C language will give a boost to your productivity and increase the readability and maintainability of your code.
As a final exercise, I encourage you to open the Memory Usage Gauge window—select 'View→ Memory Usage Gauge'.
Figure 1-10. MPLAB IDE Memory Usage Gauge window.
Chapter 1
Don't be alarmed! Even though we wrote only three lines of code in our first example and the amount of program memory used appears to already be up to 300+ bytes, this is not an indication of any inherent inefficiency of the C language. There is a minimum block of code that is always generated (for our convenience) by the C30 compiler. This is the initialization code (c0) that we mentioned briefly before. We will get to it, in more detail, in the following chapters as we discuss variables initialization, memory allocation and interrupts.
Notes for PIC MCU experts
Those of you who are familiar with the PIC16 and PIC18 architecture will find it interesting that most PIC24 control registers, including the I/O ports, are now 16 bits wide. Looking at the PIC24 datasheet, note also how most peripherals have names that look very similar, if not identical, to the 8-bit peripherals you are already familiar with. You will feel at home in no time!
Notes for C experts
Certainly we could have used the printf function from the standard C libraries. In fact the libraries are readily available with the MPLAB C30 compiler. But we are targeting embedded-control applications and we are not writing code for multigigabyte workstations. Get used to manipulating low-level hardware peripherals inside the PIC24 microcontrollers. A single call to a library function,
like printf, could have added several kilobytes of code to your executable. Don't assume a serial port and a terminal or a text display will always be available to you. Instead, develop a sensibility for the 'weight' of each function and library you use in light of the limited resources available in the embed- ded-design world.
Tips and tricks
The PIC24FJ family of microcontrollers is based on a 3V CMOS process with a 2.0V to 3.6V operating range. As a consequence, a 3V power supply (Vdd) must be used and this limits the output voltage of each I/O pin when producing a logic high output. However, interfacing to 5V legacy devices and applications is really simple:
•To drive a 5V output, use the ODCx control registers (ODCA for PORTA, ODCB for PORTB and so on…) to set individual output pins in open-drain mode and connect external pull-up resistors to a 5V power supply.
•Digital input pins instead are already capable of tolerating up to 5V. They can be connected directly to 5V input signals.
Be careful with I/O pins that are multiplexed with analog inputs though—they cannot tolerate voltages above Vdd.
The first flight
Exercises
If you have the Explorer16 board:
1.Use the ICD2 Debugging Checklist to help you prepare the project for debugging.
2.To test the PORTA example, connect the Explorer16 board and check the visual output on LED0–7.
3.To test the PORTB example, connect a voltmeter (or DMM) to pin RB0 and watch the needle move as you single-step through the code.
Books
•Kernighan, B. and Ritchie, D., 'The C Programming Language,' Prentice-Hall, Englewood Cliffs, NJ.
When you read or hear a programmer talk about the 'K&R,' they mean this book!
Also known as 'the white book,' the C language has evolved since the first edition of this book was published in 1978! The second edition (1988) includes the more recent ANSI C standard definitions of the language, which is closer to the standard the MPLAB C30 compiler adheres to (ANSI90).
•'Private Pilot Manual,' Jeppesen Sanderson, Inc., Englewood, CO.
This is 'the' reference book for every student pilot. Highly recommended, even if you are just curious about aviation.
Links
•http://en.wikibooks.org/wiki/C_Programming
This is a Wiki-book on C programming. It's convenient if you don't mind doing all your reading online. Hint: look for the chapter called 'A taste of C' to find the omnipresent 'Hello World!' exercise.
C H A P T E R 2
A loop in the pattern
In This Chapter
while loops
An animated simulation Using the Logic Analyzer
The 'pattern' is a standardized rectangular circuit, where each pilot flies in a loop. Every airport has a pattern of given (published) altitude and position for each runway. Its purpose is to organize traffic around the airport and its working is not too dissimilar to how a roundabout works. All airplanes are supposed to circle in a given direction consistent with the prevailing wind at the moment. They all fly at the same altitude, so it is easier to visually keep track of each other's position. They all talk on the radio on the same frequencies, communicating with a tower if there is one, or among one another
with the smaller airports. As a student pilot, you will spend quite some time, especially in the first few lessons, flying in the pattern with your instructor to practice continuous sequences of landings immediately followed by take-offs (touch-and-goes), refining your newly acquired skills. As a student of embedded programming, you will have a loop of your own to learn—the main loop.
Flight plan
Embedded-control programs need a framework, similar to the pilots' pattern, so that the flow of code can be managed. In this lesson, we will review the basics of the loops syntax in C and we'll also take the opportunity to introduce a new peripheral module: the 16-bit Timer1. Two new MPLAB® SIM features will be used for the first time: the 'Animate' mode and the 'Logic Analyzer.'
Preflight checklist
For this second lesson, we will need the same basic software components installed (from the attached CD-ROM and/or the latest versions, available for download from Microchip's website) and used before, including:
•MPLAB IDE, Integrated Development Environment
•MPLAB SIM, software simulator
•MPLAB C30 compiler (Student Version)
Chapter 2
We will also reuse the 'New Project Set-up' checklist to create a new project with the MPLAB IDE:
1.Select 'Project→Project Wizard', to start creating a new project.
2.Select the PIC24FJ128GA010 device, and click Next.
3.Select the MPLAB C30 compiler suite and click Next.
4.Create a new folder and name it 'Loop.' name the project 'A Loop in the Pattern,' and click Next.
5.There is no need to copy any source files from the previous lessons; click Next once more.
6.Click Finish to complete the Wizard set-up.
This will be followed by the 'Adding Linker Script file' checklist, to add the linker script 'p24fj128ga010.gld' to the project. It can typically be found in the MPLAB IDE installation directory 'C:/Program Files/Microchip/', within the subdirectory 'MPLAB C30/support/gld/'.
After completing the 'Create New File and Add to Project' checklist:
7.Open a new editor window.
To complete our lesson, we will now explore the use of one more I/O port, PORTB.
It is simple to edit the program and replace the two PORTA control register assignments with TRISB and PORTB. Rebuild the project and follow the same steps we did in the previous exercise and…you'll get a new surprise. The same code that worked for PORTA does not work for PORTB!
Don't panic! I did it on purpose. I wanted you to experience a little PIC24 migration pain. It will help you learn and grow stronger.
It is time to go back to the datasheet, and study in more detail the PIC24 pin-out diagrams. There are two fundamental differences between the 8-bit PIC microcontroller architecture and the new PIC24 architecture:
•Most of PORTB pins are multiplexed with the analog inputs of the analog-to-digital converter (ADC) peripheral. The 8-bit architecture reserved PORTA pins primarily for this purpose—the roles of the two ports have been swapped!
The first flight
•With the PIC24, if a peripheral module input/output signal is multiplexed on an I/O pin, as soon as the module is enabled, it takes complete control of the I/O pin—independently of the direction (TRISx) control register content. In the 8-bit architectures, it was up to the user to assign the correct direction to each pin, even when a peripheral module required its use.
By default, pins multiplexed with 'analog' inputs are disconnected from their 'digital'input ports. This is exactly what was happening in the last example. All PORTB pins in the PIC24FJ128GA010 are, by default at power-up, assigned an analog input function; therefore, reading PORTB returns all 0s. Notice, though, that the output latch of PORTB has been correctly set although we cannot see it through the PORTB register. To verify it, check the contents of the LATB register instead.
To reconnect PORTB inputs to the digital inputs, we have to act on the analog-to-digital conversion (ADC) module inputs. From the datasheet, we learn that the special-function register AD1PCFG controls the analog/digital assignment of each pin.
Upper Byte: | |||||||
R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 |
PCFG15 | PCFG14 | PCFG13 | PCFG12 | PCFG11 | PCFG10 | PCFG9 | PCFG8 |
bit 15 | bit 8 | ||||||
Lower Byte: | |||||||
R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 | R/W-0 |
PCFG7 | PCFG6 | PCFG5 | PCFG4 | PCFG3 | PCFG2 | PCFG1 | PCFG0 |
bit 7 | bit 0 |
bit 15-0 PCFG15:PCFG0: Analog Input Pin Configuration Control bits
1 = Pin for corresponding analog channel is configured in Digital mode; I/O port read enabled 0 = Pin configured in Analog mode; I/O port read disabled, A/D samples pin voltage
Figure 1-7. AD1PCFG: ADC port conÞguration register.
Assigning a 1 to each bit in the AD1PCGF special-function register will accomplish the task. Our new and complete program example is now:
#include
main() | ||
{ | ||
TRISB = | 0; | // all PORTB pins output |
AD1PCFG = | 0xffff; | // all PORTB pins digital |
PORTB = | 0xff; | |
} |
This time, compiling and single-stepping through it will give us the desired results.
Chapter 1
Figure 1-8. Hello Embedded World Project.
Post-flight briefing
After each flight, there should be a brief review. Sitting on a comfortable chair in front of a cool glass of water, it's time to reflect with the instructor on what we have learned from this first experience.
Writing a C program for a PIC24 microcontroller can be very simple, or at least no more complicated than the assembly-language equivalent. Two or three instructions, depending on which port we plan to use, can give us direct control over the most basic tool available to the microcontroller for communication with the rest of the world: the I/O pins.
Also, there is nothing the C30 compiler can do to read our mind. Just like in assembly, we are responsible for setting the correct direction of the I/O pins. And we are still required to study the datasheet and learn about the small differences between the 8-bit PIC microcontrollers we might be familiar with and the new 16-bit breed.
As high-level as the C programming language is touted to be, writing code for an embedded-control device still requires us to be intimately familiar with the finest details of the hardware we use.
The first flight
Notes for assembly experts
If you have difficulties blindly accepting the validity of the code generated by the MPLAB C30 compiler, you might find comfort in knowing that, at any given point in time, you can decide to switch to the 'Disassembly Listing' view. You can quickly inspect the code generated by the compiler, as each C source line is shown in a comment that precedes the segment of code it generated.
Figure 1-9. Disassembly Listing Window.
You can even single-step through the code and do all the debugging from this view, although I strongly encourage you not to do so (or limit the exercise to a few exploratory sessions as we progress through the first chapters of this book). Satisfy your curiosity, but gradually learn to trust the compiler. Eventually, use of the C language will give a boost to your productivity and increase the readability and maintainability of your code.
As a final exercise, I encourage you to open the Memory Usage Gauge window—select 'View→ Memory Usage Gauge'.
Figure 1-10. MPLAB IDE Memory Usage Gauge window.
Chapter 1
Don't be alarmed! Even though we wrote only three lines of code in our first example and the amount of program memory used appears to already be up to 300+ bytes, this is not an indication of any inherent inefficiency of the C language. There is a minimum block of code that is always generated (for our convenience) by the C30 compiler. This is the initialization code (c0) that we mentioned briefly before. We will get to it, in more detail, in the following chapters as we discuss variables initialization, memory allocation and interrupts.
Notes for PIC MCU experts
Those of you who are familiar with the PIC16 and PIC18 architecture will find it interesting that most PIC24 control registers, including the I/O ports, are now 16 bits wide. Looking at the PIC24 datasheet, note also how most peripherals have names that look very similar, if not identical, to the 8-bit peripherals you are already familiar with. You will feel at home in no time!
Notes for C experts
Certainly we could have used the printf function from the standard C libraries. In fact the libraries are readily available with the MPLAB C30 compiler. But we are targeting embedded-control applications and we are not writing code for multigigabyte workstations. Get used to manipulating low-level hardware peripherals inside the PIC24 microcontrollers. A single call to a library function,
like printf, could have added several kilobytes of code to your executable. Don't assume a serial port and a terminal or a text display will always be available to you. Instead, develop a sensibility for the 'weight' of each function and library you use in light of the limited resources available in the embed- ded-design world.
Tips and tricks
The PIC24FJ family of microcontrollers is based on a 3V CMOS process with a 2.0V to 3.6V operating range. As a consequence, a 3V power supply (Vdd) must be used and this limits the output voltage of each I/O pin when producing a logic high output. However, interfacing to 5V legacy devices and applications is really simple:
•To drive a 5V output, use the ODCx control registers (ODCA for PORTA, ODCB for PORTB and so on…) to set individual output pins in open-drain mode and connect external pull-up resistors to a 5V power supply.
•Digital input pins instead are already capable of tolerating up to 5V. They can be connected directly to 5V input signals.
Be careful with I/O pins that are multiplexed with analog inputs though—they cannot tolerate voltages above Vdd.
The first flight
Exercises
If you have the Explorer16 board:
1.Use the ICD2 Debugging Checklist to help you prepare the project for debugging.
2.To test the PORTA example, connect the Explorer16 board and check the visual output on LED0–7.
3.To test the PORTB example, connect a voltmeter (or DMM) to pin RB0 and watch the needle move as you single-step through the code.
Books
•Kernighan, B. and Ritchie, D., 'The C Programming Language,' Prentice-Hall, Englewood Cliffs, NJ.
When you read or hear a programmer talk about the 'K&R,' they mean this book!
Also known as 'the white book,' the C language has evolved since the first edition of this book was published in 1978! The second edition (1988) includes the more recent ANSI C standard definitions of the language, which is closer to the standard the MPLAB C30 compiler adheres to (ANSI90).
•'Private Pilot Manual,' Jeppesen Sanderson, Inc., Englewood, CO.
This is 'the' reference book for every student pilot. Highly recommended, even if you are just curious about aviation.
Links
•http://en.wikibooks.org/wiki/C_Programming
This is a Wiki-book on C programming. It's convenient if you don't mind doing all your reading online. Hint: look for the chapter called 'A taste of C' to find the omnipresent 'Hello World!' exercise.
C H A P T E R 2
A loop in the pattern
In This Chapter
while loops
An animated simulation Using the Logic Analyzer
The 'pattern' is a standardized rectangular circuit, where each pilot flies in a loop. Every airport has a pattern of given (published) altitude and position for each runway. Its purpose is to organize traffic around the airport and its working is not too dissimilar to how a roundabout works. All airplanes are supposed to circle in a given direction consistent with the prevailing wind at the moment. They all fly at the same altitude, so it is easier to visually keep track of each other's position. They all talk on the radio on the same frequencies, communicating with a tower if there is one, or among one another
with the smaller airports. As a student pilot, you will spend quite some time, especially in the first few lessons, flying in the pattern with your instructor to practice continuous sequences of landings immediately followed by take-offs (touch-and-goes), refining your newly acquired skills. As a student of embedded programming, you will have a loop of your own to learn—the main loop.
Flight plan
Embedded-control programs need a framework, similar to the pilots' pattern, so that the flow of code can be managed. In this lesson, we will review the basics of the loops syntax in C and we'll also take the opportunity to introduce a new peripheral module: the 16-bit Timer1. Two new MPLAB® SIM features will be used for the first time: the 'Animate' mode and the 'Logic Analyzer.'
Preflight checklist
For this second lesson, we will need the same basic software components installed (from the attached CD-ROM and/or the latest versions, available for download from Microchip's website) and used before, including:
•MPLAB IDE, Integrated Development Environment
•MPLAB SIM, software simulator
•MPLAB C30 compiler (Student Version)
Chapter 2
We will also reuse the 'New Project Set-up' checklist to create a new project with the MPLAB IDE:
1.Select 'Project→Project Wizard', to start creating a new project.
2.Select the PIC24FJ128GA010 device, and click Next.
3.Select the MPLAB C30 compiler suite and click Next.
4.Create a new folder and name it 'Loop.' name the project 'A Loop in the Pattern,' and click Next.
5.There is no need to copy any source files from the previous lessons; click Next once more.
6.Click Finish to complete the Wizard set-up.
This will be followed by the 'Adding Linker Script file' checklist, to add the linker script 'p24fj128ga010.gld' to the project. It can typically be found in the MPLAB IDE installation directory 'C:/Program Files/Microchip/', within the subdirectory 'MPLAB C30/support/gld/'.
After completing the 'Create New File and Add to Project' checklist:
7.Open a new editor window.
8.Type the main program header:
//
// A loop in the pattern
//
9.Select 'Project→AddNewFiletoProject', to save the file as: 'loop.c' and have it automatically added to the project source files list.
10.Save the project.
The flight
One of the key questions that might have come to mind after working through the previous lesson is 'What happens when all the code in the main() function has been executed?' Well, nothing really happens, or at least nothing that you would not expect. The device will reset, and the entire program will execute again…and again.
In fact, the compiler puts a special software reset instruction right after the end of the main() function code, just to make sure. In embedded control we want the application to run continuously, from the moment the power switch has been flipped on until the moment it is turned off. So, letting the program run through entirely, reset and execute again might seem like a convenient way to arrange the application so that it keeps repeating as long as there is 'juice.' This option might work in a few limited cases, but what you will soon discover is that, running in this 'loop.' you develop a 'limp.' Reaching the end of the program and executing a reset takes the microcontroller back to the very beginning to execute all the initialization code, including the c0 code segment briefly mentioned in the previous lesson. So, as short as the initialization part might be, it will make the loop very unbalanced. Going through all the special-function register and global-variables initializations each time is probably not necessary and it will certainly slow down the application. A better option is to design an application 'main loop.' Let's review the most basic loop-coding options in C first.
A Loop in the pattern
While loops
In C there are at least three ways to code a loop; here is the first—the while loop:
while ( x)
{
// your code here...
}
Anything you put between those two curly brackets ({}) will be repeated for as long as the logic expression in parenthesis ( x) returns a true value. But what is a logic expression in C?
First of all, in C there is no distinction between logic expressions and arithmetic expressions. In C, the Boolean logic TRUE and FALSE values are represented just as integer numbers with a simple rule:
•FALSE is represented by the integer 0.
•TRUE is represented by any integer except 0.
So 1 is true, but so are 13 and -278. In order to evaluate logic expressions, a number of logic operators are defined, such as:
|| the logic OR operator, && the logic AND operator,
Any Software Like False Flesh Pics Youtube
!the logic NOT operator.
These operators consider their operands as logical (Boolean) values using the rule mentioned above, and they return a logical value. Here are some trivial examples:
(when a = 17 and b = 1, or in other words they are both true)
( a || b) | is true, |
( a && b) | is true |
( !a) | is false |
There are, then, a number of operators that compare numbers (integers of any kind and floating-point values, too) and return logic values. They are:
the 'equal-to' operator; notice it is composed of two equal signs to distinguish it from the 'assignment' operator we used in the previous lesson,
!= the 'NOT-equal to' operator,
>the 'greater-than' operator,
>= the 'greater-or-equal to' operator,
Any Software Like False Flesh Pics Free
<the 'less-than' operator,
<= the 'less-than-or-equal to' operator. Here are some examples:
assuming a = 10
( a | > 1) | is true |
(-a | >= 0) | is false |
Тут вы можете оставить комментарий к выбранному абзацу или сообщить об ошибке.
Оставленные комментарии видны всем.
Соседние файлы в предмете Микроконтроллеры ЭВМ- #12.08.20132.34 Mб682PICmicro MCU C - An itroduction to programming The Microchip PIC in CCS C (N.Gardner, 2002).pdf
- #12.08.201319.87 Mб168Practical Embedded Controllers. Motorolla 68HC11 (J. Park, 2003).pdf
- #12.08.201320.93 Mб277Programmable Controllers, 3-rd edition (E.A. Parr, 2003).pdf
- #12.08.20135.55 Mб84Programmable controllers.Theory and implementation (L.A. Bryan, 1997).pdf
- #12.08.20136.34 Mб613Programmable logic controllers. Methods and Applications (Hackworth J., Prentice Hall).pdf
- #12.08.20136.77 Mб329Programming 16-Bit PIC Microcontrollers in C. Learning to Fly the PIC24 (Lucio Di Jasio, 2007).pdf
- #12.08.201331.16 Mб118Programming And Customizing The Avr Microcontroller (D.V. Gadre, 2001).pdf
- #12.08.201331.16 Mб108Programming And Customizing The Avr Microcontroller (Gadre D.V., 2001).pdf
- #12.08.20137.2 Mб232Programming Microcontrollers in C, 2-nd edit (Ted Van Sickle, 2001).pdf
- #12.08.201311.78 Mб151Programming PIC Microcontrollers with PicBasic (Chuck Hellebuyck, 2003).pdf
- #12.08.2013365.8 Кб63Real-time processing with the Philips LPC ARM mcu using GCC and uCOS II RTOS (D.W. Hawkins, 2006).pdf
