So, hello to all viewers and welcome back to Gettobyte Platform. In This blog you are going to know about RFID Reader MFRC522, which is designed by NXP Semiconductors. Objective would be to interface this module with Host MCU’s like of NXP Semiconductors, STMicroelectronics or other vendors MCU’s. Will make the driver to interface the RFID Reader with any MCU, not unlike just with Arduino and Arduino IDE environment. To make the driver of RFID reader at first, we need to dig into its datasheet, to understand its various sub parts. And that’s all about this blog is gotten going to be, to make the datasheet understand in easy way-out.
Table of Contents
Next & Previous Blog
RFID Technology
RFID modules is a wireless sensing technology which is used to track/identify/monitor the objects.
MFRC522 RFID Reader/PCD
MFRC522 is a highly integrated reader/writer IC for contactless communication at 13.56 MHz. These reader supports the ISO 14443 A protocol for communicating with RFID Tags. They are used to detect the MIFRAME RFID tags.
MFRC522 has internal RF transceiver, which provides a robust and efficient implementation for demodulating and decoding signals from MIFRAME compatible cards using ISO 14443 A protocol. The digital module of MFRC522 manages the complete ISO/IEC 14443 A framing and error detection (parity and CRC) functionality.
MFRC522 supports 3 tags of MIFRAME family, that are MF1xxS20, MF1xxS70 and MF1S50 products.
MFRC522 features
MFRC522 though quite old RFID reader and in today’s time many new advance RFID readers have come up. But so as to get started with this technology as a hobbyist/student/DIY project, it is perfect module to lay your hands on this Technology.
- MFRC522 has highly integrated analog circuitry to demodulate and decode responses when RFID tags are brought in close proximity of these devices.
- RFID readers are connected with some host MCU, where the processing of data which is received via RFID tags happens according to the application. MFRC522 can connect with host MCU, using SPI, Serial UART and I2C -bus interface.
- It supports ISO 14443 A protocol and can be used with MIFRAME family of RFID tags. And in MIFRAME family it supports only MF1xxS20, MF1xxS70 and MF1xxS50 products.
- It has internal CRC-coprocessor.
- Internal FIFO buffer which can handle 64 bytes of sending and receiving.
- It uses the Crypto-1 cipher for authenticating.
- It supports Internal oscillator for connection to 27.12 MHz quartz crytsal.
- It is low power device, need 2.5 V to 3.3 V power supply.
- It also has flexible interrupt modes when some RFID tags are detected and trigering events too. In addition to flexible interrupt, it has programmabe I/O pins and timer.
- It can perform Internal self-test too.
MFRC522 Functional description
MFRC522 Host Interfaces
MFRC522 can be connected to Host MCU using 3 serial protocols: UART, I2C or SPI.
MFRC522 checks the current host interface type.
automatically after performing a power-on or hard reset. The MFRC522 IC identifies the host
interface by sensing the logic levels on the below pins after the reset phase. 
The MFRC522 is equipped with a series of registers that allow the Host MCU to access its functional description blocks. To ensure the proper functioning of the MFRC522, the Host MCU must initialize and configure these functional blocks by sending the corresponding register addresses.
Each register is essentially an address byte that is transmitted from the Host MCU. Depending on the function described in the register section, read/write operations are performed on the corresponding address byte.
It is crucial to properly initialize and configure these functional blocks to ensure the optimal performance of the MFRC522. By understanding the purpose of each register and its corresponding function, the Host MCU can effectively communicate with the MFRC522 and achieve the desired results.
–> MFRC522_write_register()
–> MFRC522_Read_register()
MFRC522 Interrupts
MFRC522 can trigger the interrupts, when certain events occur. There are 8 events as shown in below table when interrupt can be triggered.
When above event occurs, IRQ pin is used to interrupt the host. IRQ pin signal is asserted and host MCU can use its interrupt handling capabilities (basically NVIC if we are talking about ARM based MCU) on what to do when corresponding interrupt has occurred.
- Status1Reg Register IRq bit is used to indicate if any interrupt source has been triggerered.
- Which interrupt has been triggered is indicated by ComIrqReg and DivIrqReg Register. 
- Which interrupts to be configured and behavior of IRQ pin is configured by ComIEReg and DivIEReg Register.
MFRC522 Time Unit
There is a Timer unit in MFRC522, that is used for multiple purposes. Timer unit is essential for maintaing the configuring the clock and analog interfaces. Also timer unit can be used for following features:
- Timeout counter
- Watchdog counter
- Stopwatch
- Programmable one shot
- Periodical trigger
Timer has an input clock of 13.56 MHz derived from the 27.12 MHz quartz crystal oscillator. The timer consists of 2 stages: prescaler and counter.
- The prescaler(TPrescaler) is a 12-bit counter. That can be configured using TModeReg register’s TPrescaler_Hi[3:0] and TPrescalerReg register’s TPrescaler[7:0] bits.
- The Reload value for the counter is defined by 16 bits between 0 & 65535 in the TReloadReg register.
- The current value of the timer is indicated in the TCounterVAlReg Register.
MFRC522 FIFO
FIFO overview
The MFRC522 contains an internal FIFO buffer of 64 bytes, which is equivalent to 8 x 64 bits. This buffer is utilized for both input and output data streams. The host MCU has the capability to perform both Read and Write operations on this FIFO. The host MCU sends commands to PCD for communication with PICC. these commands are specified in ISO14443 A standard, which is then inputted into the FIFO. When the PICC responds to these commands, the response is also stored in the FIFO. The host MCU can then read the FIFO to obtain the response from the PICC.
The FIFO buffer is a crucial component in the communication process between the host MCU and the PICC. It allows for efficient data transfer and ensures that all responses are stored in a centralized location. The ability to perform both Read and Write operations on the FIFO provides flexibility and control to the host MCU. By utilizing the FIFO buffer, the communication process is streamlined and optimized for maximum efficiency.
About FIFO registers
FIFO buffer input and output data bus is connected to the FIFODataReg register. Writing to this register stores one byte in the FIFO buffer and increments the internal FIFO buffer write pointer. Reading from this register shows the FIFO buffer contents stored in FIFO read pointer and decrements the FIFO buffer read pointer.
Only one FIFO buffer has been implemented which can be used for input and output. The microcontroller must
ensure that there is not any unintentional FIFO buffer accesses.
The FIFOLevelReg is utilized to determine the number of bytes stored in the FIFO. This register is particularly useful in checking the number of bytes received in the FIFO buffer when the PICC sends a response to the PCD command. By using the FIFOLevelReg, you can easily keep track of the amount of data stored in the FIFO, which is essential in ensuring the smooth operation of your system.
One can also get the status of FIFO buffer using status and error registers.
- FIFO buffer almost full warning can be got to know from Status1Reg register’s HiAlert bit.
- FIFO buffer almost empty warning can be got to know from Status1Reg register’s LoAlert bit.
- FIFO buffer overflow warning, using ErrorReg register’s BufferOvfl bit.
MFRC522 CRC
MFRC522 has a Cyclic Rebudency Check (CRC) coprocessor to check the integrity of the data when data from PICC is received or when data is wriiten to PICC.
- CRC has preset value 0000h, 6363h, A671h or FFFFh. We can configure the preset values using ModeReg CRCPreset[1:0].
- CRC polynomial for the 16-bit CRC is fixed to x^16 + x^12 + x^5 + 1.
- CRCResultReg register indicates the result of the CRC calculation.
- CRC algorithm which is used is according to ISO/IEC 14443 A and ITU-T.
To perform the CRC calculation refer its state machine in below section.
MFRC522 Command Set
MFRC522 operation is determined by certain commands. According to these commands, correspondingly MFRC522 would be performing some action.
So, it’s like at first, we will configure the FIFO, CRC, Interrupts and timer unit. After that Host MCU will instruct the commands to MFRC522 in order to tell what it has to do. Host MCU will write the command code to the CommandReg Register.
Main commands that would be used are Idle, Transceive, CalcCRC and Transmit commands. Transceive command is the one which has to be sent from Host MCU to MFRC522 to send the FIFO buffer data to the antenna, which is further propagated to the RFID readers. And according to the data which we have written in FIFO RFID readers would act and give response.
Each command that needs a data bit stream (or data byte stream) as an input immediately processes any data in the FIFO buffer. An exception to this rule is the
Transceive command. Using this command, transmission is started with the BitFramingReg register’s StartSend bit.
MFRC522 Block Diagram
Above is the simplified block diagram of MFRC522 module. MFRC522 has an internal memory, power supply, interrupt pins, FIFO buffer, Antenna and analog interface, digital module for communicating with Host MCU.
Analog Interface handles the modulation and demodulation of the analog signals. FIFO Buffer ensures fast and convenient data transfer.
Register bank are the set of registers through which MFRC522 would be configured and initialized to use. Parameters like Clock, Interrupts, status of errors while communicating with RFID readers, CRC calculation, FIFO configuration and etc need to be configured before using the MFRC522.
How the MFRC522 Internal system works?
Host MCU will send PCD Commands to MFRC522, according to which it will perform some operations. MCU will send these commands by writing into one of the registers of PCD.( For MFRC522 CommandReg is register)
Operations like:
- Activation of CRC Coprocessor
- Transmission of data from FIFO buffer of MFRC522 and activation of receiver circuits to get the response from PICC
- transfer of data from FIFO to an internal buffer
- soft reset and authentication-based operations
Further MFRC522 will emit the commands for communicating with PICC, here referred to as PICC Commands, according to which operation with PICC takes place, like scanning of PICC, selecting the PICC, reading and writing the data on PICC. MFRC522 emits these commands via electromagnetic induction and electric coupling. ( That is the main working principle behind the RFID technology)
Host MCU to PCD
Host MCU will send the commands to PCD, according to which PCD will perform the operations like activation of FIFO buffer or CRC coprocessor, and transmission of data from FIFO. We will name these commands as MFRC522 Commands sets. Host MCU will send those commands to PCD (here MFRC522) by writing into the CommandReg Register using low level Host Interface write API.
- Idle Command: Places the MFRC522 in Idle mode.
- Mem Command: Transfers the 25 bytes from the FIFO Buffer to the internal buffer. This command is used when, we want to read the data from PICC( As described in ISO-14443-4 doc), as PICC response is always recorded in PCD FIFO.
- Generate RandomID: generates a 10-byte random ID number.
- CalcCRC: Activates the CRC coprocessor or performs a self test.
- Transmit: transmit data from the FIFO buffer
- NoCmdChange: no command change, can be used to modify the CommandRef register bits without affecting the command
- Receive: activates the receiver circuits
- Transceive: Transmit data from the FIFO buffer to antenna and automatically activates the receiver after transmission.
- MFAuthent: performs the MIFARE standard authentication as a reader
- SoftReset: This command performs a reset of the device. The configuration data of the internal buffer remains unchanged. All registers are set to the reset values. This command automatically terminates when finished.
PCD to PICC
Further there are also command set which PCD have to emit to communicate with PICC and enter the PICC into some state machine.
PICC States:
- Power-off State: In the POWER-OFF state, the PICC is not powered by a PCD operating field
- Idle State: In the IDLE state, the PICC is powered. It listens for commands and shall recognize REQA and WUPA commands.
- Ready State: Cascade levels are handled inside this state to get the complete UID. PICC enters the ACTIVE state when it is selected with its complete UID.
- Active State: PICC complies with ISO-14443-4 to accept protocol activation commands (RATS)
- HALT State: In this state PICC only responds to WUPA command.
- Protocol State: PICC behaves according to 1s014443-4 specifications.
We will name these commands as PICC commands. Host MCU will write these PICC command into the PCD FIFO (refer the MFRC522 FIFO section on how to write the data on FIFO). PCD would transmit the FIFO data when it enters the Transceiver state machine (refer above topic).
PCD would transmit these commands via the electromagnetic induction and communicates with PICC via electronic coupling. PCD’s have RF transceivers through which it emits the electromagnetic waves with commands sets encoded in them. PICC have antenna and small circuitry, which gets energized via electromagnetic waves emitted by PCD and then further both PCD and PICC get coupled together to have 2 way wireless communication. How PCD would send commands to PICC and in return how PICC would respond, that is done according to IS014443 protocol. ISO14443 specifies all the frame formats,PICC command and their format , modulation schemes for RFID technology. 
PICC Frame formats:
- Short Frame:
- Standard Frames
PICC Command Set:
- REQA/WUPA Command: This command is send by PCD to scan the valid and IS014443 compatible PICC’s. This command is in short frame format. Host MCU will write this command into the PCD FIFO, from where this command is transmitted and emitted wirelessly. Response to this command is with ATQA. PICC are in Idle state when listening to this command and after successfully transmitting the ATQA response they enter into Ready State. These commands consist of 7 bits, as specified below:
- ANTICOLLISION/SELECT Command: PICC are in ready state when listening to this command and after this command they enter into ACTIVE STATE. This Command is used to get the UID of the scanned PICC and further select the corresponding PICC for Reading and writing data from it. For the MF1S503 PICC’s UID is of 4 bytes, for that only 1 cascade level is needed.
These commands need to be configured and then these bytes are written into The PCD FIFO for transmission and emission of signal to PICC wirelessly. This Command consists of:
- Select code SEL(1byte): Specify the cascade level.
- No of valid bits NVB (1 byte): specify number of bytes that would be transmitted by PCD to PICC (including SEL, NVB and below point)
- 0 to 40 data bits of UID according to value of NVB.
ANTICOLLISION Command consist of:
- Select Code: Cascade level 1= 0x93
- No of valid bits NVB = 0x20
Response to ANTICOLLISION Command is with the UID of the Scanned PICC(0xEA, 0x24, 0x77, 0x15) and its CRC(0xAC).
- SELECT Command consists of:
- Select code: Cascade level 1 = 0x93
- No of valid bits NVB – 0x70
- 0 to 40 data bits of UID that has been received in ANTICOLLISION Command( 0xEA, 0x24, 0x77, 0x15)
- CRCA(1 byte) : CRC of SELECT Command would be calculated by PCD and then it would be sent to PICC. And When PICC receives the SELECT Command it will check this CRCA and then will send the ACK.(0xAC)
Response to SELECT Command is with the Select Acknowledge:
MFRC522 Hardware and Pinout
MFRC522 IC has 32 pins in total and it comes in SOT617-1 package.
Pin description can be found from the datasheet of MFRC522. To use the MFRC522 IC its module is widely available and quite inexpensive. Can be brought from Robu at cost of 150 rupees. With the module an RFID tag and a key fob tag of MIFRAME Classic 1KB comes in.
In MFRC522 module, IC has 8 pins exposed out for connection and connecting to host MCU.
- The module has 4 pins exposed out for connecting it to host MCU using either SPI, I2C or UART. By default, reader can communicate with a microcontroller over a 4-pin SPI with a maximum data rate of 10 Mbps. It also supports I2C and UART protocols. As told in MFRC522 functional description part, MFRC522 checks the host interface type automatically depending on the signals on it’s control pins.
- MFRC522 module has 1 interrupt pin also exposed out, which can be used to trigger interrupts to alert the microcontroller when a RFID tag is in the vicinity.
- And remaining 3 pins are power supply pins and a reset pin. Reset pin is used for power down mode and reset signal. Module requires the power supply of 3.3 V, that is provided via VCC and GND pins.
Other vendor RFID readers
STMicroelectronics
Texas Instruments
Infenion technologies
Sensor & Modules to explore
Technologies to Explore
Other Blog to Explore
Silicon Labs Thunderbolt EFM32BG22
IDE To be used: Simplicity Studio – Silicon Labs (silabs.com) SDK to be used: Gecko Platform Silicon Labs (silabs.com) SDK documentation: EFR32BG22 Gecko MCU and Peripheral Software Documentation – v5.9 – MCU EFR32BG22 API Documentation Silicon Labs (silabs.com) HDK to be used:SLTB010A EFR32BG22 Thunderboard Kit – Silicon Labs (silabs.com) HDK manual: UG415: Thunderboard EFR32BG22 User’s Guide (silabs.com) Microcontroller datasheet: EFR32BG22C112 Wireless Gecko SoC Data Sheet (silabs.com) Microcontroller Reference manual: EFR32xG22 Wireless Gecko Reference Manual (silabs.com) Author: Kunal Gupta
RECTIFIER CIRCUIT
Why do we need a rectifier Circuit? Whenever DC power is needed that time, we need to convert an AC Power to DC Power and that process is known as Rectification. A simple PN junction diode acts as a rectifier. The forward biassing and reverse biassing conditions of the diode makes the rectification. Types of Rectifier circuits There are two main types of rectifier circuits, depending upon their output. They are Half-wave Rectifier Full-wave Rectifier A Half-wave rectifier circuit rectifies only positive half cycles of the input supply whereas a Full-wave rectifier circuit rectifies both positive and negative half cycles of the input supply. Half-wave Rectifier Disadvantages of a half-wave rectifier Power is delivered only during the one-half cycle of the input alternating voltage. Ripple factor is high, therefore required to give steady dc output. They only allow a half cycle through per sine wave, and the other half cycle is wasted. This leads to power loss. Full-wave rectifier FWR has two types as follows: Centre tapped full wave rectifier Bridge full-wave Rectifier 1) Centre tapped full wave rectifier Advantages of a center-tapped full-wave rectifier: The ripple factor is much less than that of a half-wave rectifier. DC load current values are twice those of a half-wave rectifier. The rectification efficiency of the full-wave rectifier is double that of a half-wave rectifier. Disadvantages of center-tapped full-wave rectifier Location of center-tapping is difficult. The dc output voltage is small. The PIV of the diodes should be high. 2) Full-wave bridge rectifier Advantages of bridge rectifier: The need for the center-tapped transformer is eliminated. It can be used in application floating output terminals; no output terminal is grounded. The transformer utilization factor, in the case of the bridge rectifier, is higher than that of a center tap rectifier. Disadvantages of Bridge Rectifiers over center tap rectifiers. It requires four diodes for operation, thus, circuit components requirements in the case of the bridge rectifier are more than that of center tap rectifiers. The voltage drop across diodes increases four times that of a center tap full-wave rectifier. Types of Components and Its Symbol used in circuit Schematic of bridge rectifier PCB Layout of bridge rectifier Track Width – 1.00 mm Bill of material During the PCB assembly process, a BOM provides information about the components under a single roof such as their quantity, reference designators, footprints, etc. Designers will save lots of time and effort during PCB design by preparing a bill of materials with all the updated parts list. Every line of the bill of materials (BOM) includes the product code, part name, part number, part revision, description, quantity, unit of measure, size, length, weight, and specifications or features of the product. Go to fabrication bar in Easyeda online tool Download BOM Gerber File Each artwork layer, copper circuitry, power, or ground must have a corresponding Gerber file to create the required pattern. The outermost layers, referenced as “top” and “bottom,” component and solder or by layer count will also have a conforming layer for solder mask and silkscreen to be applied. Summary In this second blog, we have created a schematic of bridge rectifier and pcb layout also and learnt about bill of material and Gerber file. Apart from that we have seen that type of rectifier and understood which one is suitable for industry. Reference https://www.powerelectronicsnews.com/power-supply-design-notes-rectifier-circuits/ https://www.tutorialspoint.com/electronic_circuits/electronic_circuits_full_wave_rectifier.htm https://www.allaboutcircuits.com/textbook/semiconductors/chpt-3/rectifier-circuits/ Author: Kunal Gupta
Hardware Development Kit In Mcrocontrollers
So hello guys, welcome to series of Microcontroller tutorials. As Microcontrollers are big thing happening across the globe, but to learn about microcontrollers becomes quite challenging as most of the content on web is theoretical based and quite unorganized. Or the content is only roaming around 2-3 microcontrollers (Arduino, ESP or PIC), even though there are number of Microcontrollers of different vendors. Also, framework of Arduino and Arduino IDE hides most of the things that are going inside the microcontrollers. If you guys want to start with microcontroller coding and looking for chronological order then you have come to right place. How to start with Microcontrollers? – gettobyte Hardware Development Kit In Mcrocontrollers – gettobyte Software Development Kit In Microcontrollers – gettobyte Would recommend viewers to read these 3 blogs in order, so as to get understanding on how to get started with any Microcontroller and in what order. In the last blog we get to know a lot about microcontrollers and how to start with them. One of the essential and important things to know before starting with microcontrollers is Hardware Development Kit. So let’s start with it. Objective of this blog Objective of this blog, will be to understand: What is Hardware Development Kit in Embedded (SDK). Different components in Hardware Development Kit in Embedded. Why there is need of Hardware Development Kit in Embedded. What is Hardware Development Kit Hardware Development Kit in embedded is collection of hardware tools to assist developers to design and prototype the products/projects easily on microcontroller and semiconductor chips. These hardware tools majorly include: Microcontroller/SoC Development Boards/Evalution Boards Debuggers/Programmers Breakout Boards Hardware Debugging Tools. Microcontroller/SoC In the last blog, all we talk about is microcontrollers, so refer to this blog to know what microcontrollers are. Microcontroller and SoC word would be used quite inerchangibly throughout this blog and in subsequent blogs too. Difference between SoC and MCU is that. (SoC): SoC is a less well-defined term. A SoC is typically an encapsulation of one or more of CPUs, memory, micro-controllers, DSPs, accelerators, and supporting hardware; however, it does not adhere to any standards regarding its containing circuitry. An SoC is intended for applications with requirements that are too complex for a single MCU to handle. To explore about different microcontrollers best place is semiconductor company websites like and many others: NXP® Semiconductors Official Site | NXP Semiconductors Analog | Embedded processing | Semiconductor company | TI.com Silicon Labs (silabs.com) Nordic Semiconductor | Empowering Wireless Innovation – nordicsemi.com STMicroelectronics: Our technology starts with you and etc Go to products page of these websites and then navigate to microcontroller-microprocessor section. You will find there are so many microcontrollers which have been categorized in terms of Either processor they have (ARM Cortex CPU based, 8 bit CPU based, or some proprietary CPU core) Or Microcontroller family name’s (Like LPC series, S32 Series, MSP430 series, Kinetic series, STM32 series) Application based( Digital signal processing, IoT protocol’s, peripheral and etc) and etc. Microcontrollers/SoC can’t be used directly, for making projects or learning out the things. Microcontrollers comes in different packaging like BGA, DIP, QFN, QFP, SOP, SQP. Every package takes up different amount of space. In these packages MCU pins are very small to use and in some packages of MCU, we cant even properly touch individual pins of the MCU (BGA and QFN). Now to connect some sensors/modules to the MCU, we need to connect them to the pins of the MCU. So, there is need of some hardware circuit by which we can expose all these pins of MCU in a way that they can be used for prototyping and developing the embedded application by connecting different sensor/modules. And thus, here comes the story of development boards. Development /Evalution Boards Development boards in the field of embedded systems refer to pre-built circuit boards designed to use the microcontrollers/SoC’s. These boards typically include a microcontroller/SoC or microprocessor, along with essential components required to use the microcontroller like: Input/Output interfaces (Header pins, LEDs, Push buttons and etc.), Power regulators (For powering the MCU/SoC), and Miscellaneous circuit required for microcontroller functioning (oscillator circuit, pull-up/down resistors, decoupling capacitors and etc.) Debugging and programming feature. They provide a convenient platform for developers to test their code, interface with external devices, and evaluate the performance of their embedded system designs. These development boards are extensively used among the college students, hobbyists for making DIY projects or learn the microcontroller coding by having hands-on over the microcontrollers using these kind of development boards. These development boards are connected to Host Desktop/Laptop through USB cable via Debugger/Programmer to program/debug the microcontrollers. Thus, these development board provide easy way to use microcontrollers/microprocessor/SoC. Now for every microcontroller there is a development board for using it. Development boards are designed either by the semiconductor companies itself for their corresponding MCU’s or by the Third-party vendors, like: Arduino is a development board which has Atmega 328 MCU. Atmega 328 MCU is designed by Microchip Semiconductor company, but Arduino is designed and developed by Third party organization Arduino. BluePill is a development board which has STM32F103 MCU. STM32F103 MCU is designed by STMicroelectronics, but Bluepill is designed and developed by third party vendors. ElecronicsV1 is development board which has S32K144 Automotive MCU. S32K144 is designed by NXP Semiconductors, but ElecronicsV1 is designed and developed by Gettobyte community. S32K312 MCU which is Automotive General Purpose MCU designed by NXP Semiconductors, there is development board designed by NXP Semiconductors itself S32K312EVB-Q172. Another example is NRF52840 SoC for General Purpose IoT applications designed by Nordic Semiconductor, there is development board designed by Nordic Semiconductors itself nRF52840 DK. Another example is of STM32WB55 SoC for Low-Power IoT applications designed by STMicroelectronics, there is development board designed by STMicroelectronics itself that is P-NUCLEO-WB55. Another example is of MSP430 MCU for General pupose embedded applications designed by Texas Instruments, there is development board designed by Texas Instruments itself that is MSP-EXP430G2ET Their is one more SoC of NXP Semiconductors JN5189 IoT SoC. NXP semiconductors design and develop the development board
Cryptography Basics/Terminologies
Learn about basics of cryptography technology for embedded world
CSEc security sub-system(Cryptography) in S32K1 MCU
How to use Cryptography in S32K Microcontrollers? What is CSEc Peripheral? how does CSEc peripheral in S32K Microcontrollers work.
ADC Driver of Autosar MCAL Layer
ADC Driver of Autosar MCAL layer Explanation, Understanding and tutorial using ElecronicsV3 Development board
Author: Kunal Gupta
