Updated review comments

Author: jasminefrancisca

dspic33e-adc-altsamp/README.md

@@ -25,11 +25,11 @@ Next, DMA uses DMA0STB base address to store the ADC samples and it generates in
 after transfer (TWO x 16 samples = 32 samples).
 Above process repeats continuously. 
 
-void \_\_attribute\_\_((\_\_interrupt\_\_)) _DMA0Interrupt(void);<br/>
+void \_\_attribute\_\_((\_\_interrupt\_\_)) _DMA0Interrupt(void);  
 DMA interrupt service routine, moves the data from DMA buffer to ADC signal buffer 
 
-Timer time outs at 60M/(4999+1) = 12000 Hz.<br/>
-DMA interrupt @ 12K/32=  375 Hz.<br/>
+Timer time outs at 60M/(4999+1) = 12000 Hz.  
+DMA interrupt @ 12K/32=  375 Hz.  
 I/O pin toggles at 375/2= 187 Hz.
 
 RA4 pin is toggled in ISR, hence it will be toggling at ~ 187Hz

dspic33e-adc-in-sleep/README.md

@@ -9,11 +9,11 @@ Start of conversion is issued in the background loop and device enters sleep mod
 
 When the ADC conversion is completed in sleep mode, it wakes up the device and enters ADC ISR.
 
-void initAdc1(void);<br/>
+void initAdc1(void);  
 ADC CH0 is set-up to covert AIN5 in 10-bit mode. ADC is configured to next sample data immediately after the conversion.
 But the start of conversion is issued manually in the background loop.
 
-void _ADC1Interrupt()<br/>
+void _ADC1Interrupt()  
 Device enters the ADC ISR after waking up from sleep mode. ADC result is read in the ISR and PORTA (RA4) pin is toggled.
 
 

dspic33e-ecan-crosswire/README.md

@@ -24,8 +24,8 @@ The configuration of the two ECAN modules is done in the ECAN1Config.c and ECAN2
 The number of message buffers to be allocated in DMA RAM are configured by using the following definitions
 in the ECAN1Config.h and ECAN2Config.h file.
 
-#define  ECAN1_MSG_BUF_LENGTH <br/>
-#define  ECAN2_MSG_BUF_LENGTH <br/>
+#define  ECAN1_MSG_BUF_LENGTH   
+#define  ECAN2_MSG_BUF_LENGTH   
 
 The aligment attribute is used to make sure that the DMA allocates the base address for the peripheral
 correctly and assigns an offset based on this base address. This is essential when using peripheral indirect
@@ -37,27 +37,27 @@ address generated by the peripheral. (in this case ECAN).
 The number of bytes may be decided based on the number of buffers being configured by the definition made earlier.
 This is calculated as follows -
 
-Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and <br/>
+Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and   
 Number of bytes = (ECAN2_MSG_BUF_LENGTH * Number of words in one buffer)*2.
 
 For eg : If 4 message buffers are defined as
 
-#define  ECAN1_MSG_BUF_LENGTH 4, then,<br/>
+#define  ECAN1_MSG_BUF_LENGTH 4, then,  
 Number of bytes = 4 * 8 * 2 = 64 (because Number of words in one buffer = 8 for ECAN).
 
 The information on transmit message identifiers and other bits are written as arguments into these functions
 
-ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
-ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
+ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
+ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
 
 The information on message acceptance filters and masks are written as arguments into these function
 
-ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan1Mask(int m, long identifierMask, unsigned int mide);<br/>
-ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan2Mask(int m, long identifierMask, unsigned int mide);<br/>
+ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan1Mask(int m, long identifierMask, unsigned int mide);  
+ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan2Mask(int m, long identifierMask, unsigned int mide);  
 
 Note :-
 a. The PPS configuration in the ecan1_config.c and ecan2_config.c source files change with the device being used. THe user is advised

dspic33e-ecan-fifo/README.md

@@ -4,7 +4,7 @@
 
 ## Description:
 
-Transmitting 6 messages from ECAN1 and receiving it in ECAN2 FIFO<br/>
+Transmitting 6 messages from ECAN1 and receiving it in ECAN2 FIFO  
 Transmitting 6 messages from ECAN2 and receiving it in ECAN1 FIFO
 
 32 Buffers are defined for ECAN1 and ECAN2
@@ -25,7 +25,7 @@ The configuration of the two ECAN modules is done in the ECAN1Config.c and ECAN2
 The number of message buffers to be allocated in DMA RAM are configured by using the following definitions
 in the ECAN1Config.h and ECAN2Config.h file.
 
-#define  ECAN1_MSG_BUF_LENGTH<br/>
+#define  ECAN1_MSG_BUF_LENGTH  
 #define  ECAN2_MSG_BUF_LENGTH
 
 The alignment attribute is used to make sure that the DMA allocates the base address for the peripheral
@@ -38,28 +38,28 @@ address generated by the peripheral. (in this case ECAN).
 The number of bytes may be decided based on the number of buffers being configured by the definition made earlier.
 This is calculated as follows -
 
-Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and <br/>
+Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and   
 Number of bytes = (ECAN2_MSG_BUF_LENGTH * Number of words in one buffer)*2.
 
 For eg : If 4 message buffers are defined as
 
-#define  ECAN1_MSG_BUF_LENGTH 4, then,<br/>
+#define  ECAN1_MSG_BUF_LENGTH 4, then,  
 Number of bytes = 4 * 8 * 2 = 64 (because Number of words in one buffer = 8 for ECAN).
 
 The information on transmit message identifiers and other bits are written as arguments into these functions
 
 
-ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
-ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
+ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
+ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
 
 The information on message acceptance filters and masks are written as arguments into these function
 
-ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan1Mask(int m, long identifierMask, unsigned int mide);<br/>
-ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan2Mask(int m, long identifierMask, unsigned int mide);<br/>
+ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan1Mask(int m, long identifierMask, unsigned int mide);  
+ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan2Mask(int m, long identifierMask, unsigned int mide);  
 
 Note :- The PPS configuration in the ecan1_config.c and ecan2_config.c source files change with the device being used. THe user is advised
 to refer the datasheet and use the appropriate values for RPINR/RPOR registers for proper operation.

dspic33e-ecan-rtr/README.md

@@ -8,13 +8,11 @@ Transmitting a Remote message from ECAN1 and requesting transmission from ECAN2
 
 4 Message Buffers are defined for ECAN1 and ECAN2
 
-
 Two message buffers are configured for ECAN1. One is configured as a Transmit Buffer to generate a Remote Frame.
 The other is configured as a Receive Buffer to receive message sent by ECAN2.
 
 One message buffer in ECAN2 is configured as a Transmit buffer for transmitting the requested data frame.
 
-
 Filters and Masks are enabled for both ECAN1 and ECAN2 for Message Reception.
 
 ECAN2 Transmit Buffer will be pointing to a filter in the case of Remote Transmission.
@@ -28,7 +26,7 @@ The configuration of the two ECAN modules is done in the ECAN1Config.c and ECAN2
 The number of message buffers to be allocated in DMA RAM are configured by using the following definitions
 in the ECAN1Config.h and ECAN2Config.h file.
 
-#define  ECAN1_MSG_BUF_LENGTH<br/>
+#define  ECAN1_MSG_BUF_LENGTH  
 #define  ECAN2_MSG_BUF_LENGTH
 
 The aligment attribute is used to make sure that the DMA allocates the base address for the peripheral
@@ -41,27 +39,27 @@ address generated by the peripheral. (in this case ECAN).
 The number of bytes may be decided based on the number of buffers being configured by the definition made earlier.
 This is calculated as follows -
 
-Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and<br/>
+Number of bytes = (ECAN1_MSG_BUF_LENGTH * Number of words in one buffer)*2 and  
 Number of bytes = (ECAN2_MSG_BUF_LENGTH * Number of words in one buffer)*2.
 
 For eg : If 4 message buffers are defined as
 
-#define  ECAN1_MSG_BUF_LENGTH 4, then,<br/>
+#define  ECAN1_MSG_BUF_LENGTH 4, then,  
 Number of bytes = 4 * 8 * 2 = 64 (because Number of words in one buffer = 8 for ECAN).
 
 The information on transmit message identifiers and other bits are written as arguments into these functions
 
-ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
-ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );<br/>
-ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);<br/>
+ecan1TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan1TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
+ecan2TransmitMsg(unsigned int buf, long txIdentifier, unsigned int ide, unsigned int remoteTransmit, unsigned int srr, unsigned int dataLength );  
+ecan2TxData(unsigned int buf, unsigned int data1, unsigned int data2, unsigned int data3, unsigned int data4);  
 
 The information on message acceptance filters and masks are written as arguments into these function
 
-ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan1Mask(int m, long identifierMask, unsigned int mide);<br/>
-ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);<br/>
-ecan2Mask(int m, long identifierMask, unsigned int mide);<br/>
+ecan1Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan1Mask(int m, long identifierMask, unsigned int mide);  
+ecan2Filter(int n, long identifier, unsigned int exide,unsigned int bufPnt,unsigned int maskSel);  
+ecan2Mask(int m, long identifierMask, unsigned int mide);  
 
 Note :- The PPS configuration in the ecan1_config.c and ecan2_config.c source files change with the device being used. THe user is advised
 to refer the datasheet and use the appropriate values for RPINR/RPOR registers for proper operation.

dspic33e-ext-intr/README.md

@@ -13,10 +13,10 @@ Both, initialization and interrupt service routines have been provided.
 The code example in the file  traps.c  contains trap service routines (handlers) for hardware exceptions
 generated by the dsPIC33E device
 
-For Testing:<br/>
-dspic33ep512gm710 : connect the pins RB3 and RF8<br/>
-dspic33ep512mu810 : connect the pins RA0 and RA4<br/>
-dspic33ep256gp506 : connect the pins RB5 and RF8<br/>
+For Testing:  
+dspic33ep512gm710 : connect the pins RB3 and RF8  
+dspic33ep512mu810 : connect the pins RA0 and RA4  
+dspic33ep256gp506 : connect the pins RB5 and RF8  
 
 Note :- The PPS configuration in the external_interrupts.c source file changes with the device being used. The user is advised
 to refer the datasheet and use the appropriate values for RPINR/RPOR registers for proper operation.