Diff: main.cpp

Revision:

20:eb1a8042605e

Parent:

19:872e304d7e17

Child:

21:13ac27349025

--- a/main.cpp	Sat Aug 13 12:45:16 2016 +0000
+++ b/main.cpp	Tue Aug 16 21:13:47 2016 +0000
@@ -1,8 +1,8 @@
 /*
  * An example showing how to use the CANnucleo library:
  *
- * Two affordable (less than $4 on ebay) STM32F103C8T6 boards (20kB SRAM, 64kB Flash), 
- * compatible with the NUCLEO-F103RB platform (20kB SRAM, 128kB Flash), 
+ * Two affordable (less than $3 on ebay) STM32F103C8T6 boards (20kB SRAM, 64kB Flash), 
+ * (see [https://developer.mbed.org/users/hudakz/code/STM32F103C8T6_Hello/] for more details) 
  * are connected to the same CAN bus via transceivers (MCP2551 or TJA1040, or etc.). 
  * CAN transceivers are not part of NUCLEO boards, therefore must be added by you. 
  * Remember also that CAN bus (even a short one) must be terminated with 120 Ohm resitors at both ends.
@@ -46,7 +46,7 @@
 /* 
  * To avaoid name collision with the CAN and CANMessage classes built into the mbed library
  * the CANnucleo's CAN and CANMessage classes have been moved into the CANnucleo namespace.
- * So remember to qualify them with the CANnucleo namespace.
+ * Remember to qualify them with the CANnucleo namespace.
  */
 CANnucleo::CAN          can(PA_11, PA_12);  // CAN Rx pin name, CAN Tx pin name
 CANnucleo::CANMessage   rxMsg;