Unit 2

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 4

1) MICROPROCESSOR VS MICROCONTROLLER

Microprocessor Microcontroller

Microprocessor acts as a heart of computer system. Microcontroller acts as a heart of embedded system.

It is a processor in which memory and I/O output It is a controlling device in which memory
component is connected externally. and I/O output component is present internally.

Since memory and I/O output is to be connected Since on chip memory and I/O output component
externally. Therefore the circuit is more complex. is available. Therefore the circuit is less complex.

It cannot be used in compact system. Therefore It can be used in compact system.


microprocessor is inefficient. Therefore microcontroller is more efficient.

Microprocessor has less number of registers. Microcontroller has more number of registers.
Therefore most of the operations are memory based. Therefore a program is easier to write.

A microprocessor having a zero status flag. A microcontroller has no zero flag.

It is mainly used in personal computers. It is mainly used in washing machines,


air conditioners etc.

2) open source movement in hardware for the Internet of Things (IoT) refers to
the collaboration and sharing of hardware designs and technologies among
the developers and the community. The movement is based on the principles
of open source software, where the source code and design files are made
publicly available for others to use, modify, and distribute. The aim is to foster
innovation, reduce costs, and increase transparency and security for IoT
devices.

Advantages of open source hardware for IoT:

OPEN SOURCE HARDWARE MOVEMENT:

Collaboration and Sharing: Open source hardware allows developers to share their
designs and technologies with the community, which results in faster innovation and
the ability to leverage the collective expertise of the community.

Lower Development Costs: By using open source hardware, developers can avoid
the high costs of proprietary hardware, as well as the costs associated with
reinventing the wheel. Additionally, open source hardware reduces the barriers to
entry for smaller companies and hobbyists.
Customizability: Open source hardware allows developers to easily modify and
customize their devices to meet their specific needs. This is particularly important in
the rapidly evolving IoT landscape where new requirements and technologies are
emerging constantly.

Increased Transparency: Open source hardware promotes transparency in the


design and manufacture of IoT devices. This increased transparency can lead to
improved security, as it makes it easier to identify and fix security vulnerabilities.

Security: Open source hardware allows developers and security experts to examine
the source code and hardware design, which can help to identify and fix security
vulnerabilities. This is particularly important in the context of IoT devices, which often
collect and transmit sensitive data.

Long-Term Support: Open source hardware is often backed by large and active
communities, which can provide long-term support and maintenance, even after the
original manufacturer has stopped producing the hardware.

Examples of open source hardware for IoT include:

Raspberry Pi: A single-board computer that can be used as the basis for IoT
projects, including home automation, media centers, and gaming consoles.

Arduino: An open source electronics platform for building IoT devices, including
sensors, actuators, and wireless communication.

ESP8266 and ESP32: Low-cost microcontrollers with built-in WiFi capabilities, which
can be used for a wide range of IoT applications, including home automation and
industrial control.

OpenWRT: An open source Linux-based operating system for IoT devices, including
routers, access points, and network-attached storage devices.

In conclusion, the open source movement in hardware for IoT is an important trend
that promotes collaboration, innovation, and increased security for IoT devices. By
leveraging the collective expertise of the community, open source hardware is
helping to bring the benefits of IoT to a wider audience and to drive the
development of this exciting and rapidly evolving field.
3) Engineering and prototyping are two stages in the process of making
Internet of Things (IoT) devices.

Engineering is like planning and designing a house. It involves figuring out what the
device needs to do and how it will do it, just like an architect draws up plans for a
house. This stage involves choosing the right materials, making sure the device will
work properly, and testing it on computer simulations to catch any problems before
the actual device is built.

Prototyping is like building a small scale model of the house. It's about taking the
plans created during engineering and creating a physical model to test and make
sure everything works as it should. This stage involves putting together a working
version of the device, testing it, and making any necessary changes to improve its
functionality.

For example, let's say you want to build a smart home security system. During the
engineering stage, you would figure out what sensors you need, how they will
communicate with each other and with the central hub, and how you will power the
system. During the prototyping stage, you would put together a working model of
the system using the parts and components you chose during the engineering stage,
test it, and make any necessary adjustments before mass producing it.

In short, engineering is about planning and designing a device, while prototyping is


about testing and refining the design to make sure it works as intended. Both stages
are important to ensure that the final product is functional, reliable, and meets the
needs of the target market.

4) software development lifecycle for embedded system

The software development lifecycle (SDLC) for embedded systems involves the
following stages:

Requirements gathering and analysis: Identifying the needs and requirements of


the system, including functional and performance requirements.

Design: Creating a high-level design of the software and hardware architecture,


including selection of components and algorithms.

Implementation: Writing the code for the system and integrating it with the
hardware.

Testing: Verifying the functionality and performance of the system through unit
testing, integration testing, and system testing.
Debugging: Identifying and fixing any problems or bugs in the code.

Integration and Deployment: Integrating the software with other components and
deploying the system on target devices.

Maintenance: Providing ongoing support and updates for the system, including bug
fixes and security patches.

In the SDLC for embedded systems, testing is a critical stage, as it helps to ensure
that the system meets the requirements and functions as intended. It is also
important to consider the constraints of embedded systems, such as limited memory,
processing power, and power consumption, during the design and implementation
stages.

In conclusion, the SDLC for embedded systems involves a series of stages that help
to ensure the development of high-quality, reliable, and secure systems. By following
a structured approach, developers can minimize the risk of problems and ensure that
the final product meets the needs of the target market.

5) PROGRAMMING AND DEVELOPING SKTECHES:

Programming and developing sketches refer to the process of writing software code
for a microcontroller or microprocessor and uploading it to the device to perform
specific tasks.

Programming involves writing code in a specific language such as C, C++, or Python


that the microcontroller or microprocessor can understand and execute. This code
can be written using an Integrated Development Environment (IDE) or a simple text
editor, and it contains the instructions for the device to perform specific tasks, such
as reading inputs from sensors, controlling outputs to actuators, or communicating
with other devices.

Developing sketches is a term often used in the context of Arduino boards, where
the process of writing code for the microcontroller is simplified and made accessible
to non-programmers. Sketches are written in a simplified version of C++ and can be
uploaded to the device using the Arduino IDE.

In both cases, the code is compiled and uploaded to the microcontroller or


microprocessor, which then executes the instructions and performs the desired tasks.
The code can be modified and re-uploaded to the device to make changes or fix
bugs.

REFER SOMEWHERE FOR ARDUINO RES API, RASPBERRY PI, INTERFACES

You might also like