Skip to content

Commit b11992b

Browse files
Usha GUsha G
authored andcommitted
MPAE-13691 Modified readme file
1 parent 2689991 commit b11992b

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

.main-meta/main.json

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
"content": {
55
"metaDataVersion": "1.3.0",
66
"name": "com.microchip.mcu8.mplabx.project.pic16f15244-uart-i2c-bridge-i2c-client2-mplab-mcc",
7-
"version": " ",
8-
"displayName": "",
7+
"version": "1.0.0",
8+
"displayName": "UART-I2C Bridge Implementation: I2C Client(Client-2) Implementation using PIC16F15244 Microcontroller",
99
"projectName": "pic16f15244-uart-i2c-bridge-i2c-client2-mplab-mcc",
1010
"shortDescription": "This example demonstrates UART I2C bridge implementation using PIC MCU The PIC16F15244 MCU processes periodically acquired sensor data and also acts as a I2C client Compatible PIC16F152xx family of MCUs are PIC16F15214 PIC16F15223 PIC16F15254 PIC16F15276",
1111
"ide": {
@@ -19,12 +19,12 @@
1919
}
2020
],
2121
"dfp": {
22-
"name": "",
23-
"semverRange": ""
22+
"name": "PIC16F1xxxx_DFP",
23+
"semverRange": "^1.9.163"
2424
},
2525
"configurator": {
26-
"name": "",
27-
"semverRange": ""
26+
"name": "MCC",
27+
"semverRange": ">=5.1.1"
2828
},
2929
"device": {
3030
"metaDataVersion": "1.0.0",
@@ -37,8 +37,8 @@
3737
}
3838
},
3939
"author": "Usha G",
40-
"peripherals": [],
41-
"keywords": [],
40+
"peripherals": ["ADC","MSSP","TMR0","UART"],
41+
"keywords": ["Melody","Curiosity Nano","Communication","Data Visualizer","I2C Protocol"],
4242
"additionalData": {
4343
"longDescription": {
4444
"metaDataVersion": "1.0.0",

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
# UART-I2C Bridge Implementation: I2C Client(Client-2) Implementation using PIC16F15244 Microcoontroller
66

7-
This code example is one of good use case to demonstrate uart-i2c bridge implementation using PIC16F15244 family microcontrollers. In this code example, PIC16F15244 MCU acts as I2C client 2s device. It periodically collects the data from the sensor, process the acquired data and keep the data ready to transmit to Host device over I2C interface. When the Host device requests to send the processed sensor data, then client device responds back to host request with the processed data through i2c interface. After receiving the data from the client device, host device displays the data on the terminal window.
7+
This code example is one of good use case to demonstrate uart-i2c bridge implementation using PIC16F15244 family microcontrollers. In this code example, PIC16F15244 MCU acts as I2C client 2 device. It periodically collects the data from the sensor, process the acquired data and keep the data ready to transmit to Host device over I2C interface. When the Host device requests to send the processed sensor data, then client device responds back to host request with the processed data through i2c interface. After receiving the data from the client device, host device displays the data on the terminal window.
88

99
Refer GitHub code example [UART-I2C Bridge and I2C Host Implementation using PIC16F15244 Microcontroller](https://github.com/microchip-pic-avr-examples/pic16f15244-uart-i2c-bridge-and-i2c-host-mplab-mcc) and [UART-I2C Bridge Implementation: I2C Client(Client-1) Implementation using PIC16F15244 Microcontroller](https://github.com/microchip-pic-avr-examples/pic16f15244-uart-i2c-bridge-i2c-client1-mplab-mcc) for more details about the implementation and application.
1010

@@ -41,7 +41,7 @@ The input commands and clients I2C address information has been displayed on the
4141
- Microchip PIC16F1xxxx Series Device Support [1.9.163 or newer](https://packs.download.microchip.com/)
4242
- MCC Melody Core 2.1.9
4343
- MSSP MCC Melody Core 6.1.1
44-
- ADC MCC Melody Core
44+
- ADC MCC Melody Core 3.0.6
4545
- TMR0 MCC Melody Core 4.0.8
4646
- UART MCC Melody Core 1.6.0
4747

0 commit comments

Comments
 (0)