Last Updated: June 9, 2017
+Last Updated: June 11, 2017
@@ -2150,12 +2150,24 @@ x++; +
+ Forbidden Multicharacter Forms.
+ Many operators are expressed as a character in combination with = such as +=, >=, >>=, etc.
+ Some compilers will accept the = at the beginning or the end of the sequence.
+ This standard, however, requires that the = always appear last in order to avoid amiguities that may arise if the = were to appear first. For example, a =++ b; could also be interpreted as a =+ +b; or a = ++b all of which are very different.
+
if then else StatementCoding Standard:
if separated from <condition>.
+ The if keyword and the <condition> must appear on the same line.
+ The if keyword and the <condition> must be separated by a single space.
+ if <condition> and else must lie on separate lines with nothing else present on the line.
@@ -2185,7 +2197,7 @@ x++;
Use of braces must follow all other standard rules for braces and spacing.
if <condition>-else statement is nested within another compound statement; there should be no blank lines between consecutive right braces as discussed in the standard rules for use of braces.
Coding Standard:
switch separated from <value>.
+ The switch keyword and the switch <value> must appear on the same line.
+ The if keyword and the <value> must be separated by a single space.
+ break statements are normally indented by two spaces.
When used conditionally with case logic, the placement of the break statement follows normal indentation rules.
switch <value> statement must be followed by a single blank line.
+ switch <value> statement is nested within another compound statement; there should be no blank lines between consecutive right braces as discussed in the standard rules for use of braces.
+ Other Applicable Coding Standards. @@ -2333,6 +2358,11 @@ x++;
while StatementCoding Standard:
while separated from <condition>.
+ The while keyword and the <condition> must appear on the same line.
+ The while keyword and the <condition> must be separated by a single space.
+ while <condition> must lie on a separate line with nothing else present on the line.
@@ -2356,7 +2386,11 @@ x++;
while <condition> statment must be followed by a single blank line.
+ while <condition> statement is nested within another compound statement; there should be no blank lines between consecutive right braces as discussed in the standard rules for use of braces.
@@ -2404,15 +2438,20 @@ x++;
do must always be enclosed in braces, even if only a single statement follows.
+ Statement(s) following the do must always be enclosed in braces, even if only a single statement (or no statement) follows.
while separated from <condition>.
+ The while keyword and the <condition> must appear on the same line.
+ The while keyword and the <condition> must be separated by a single space.
+ while <condition> must be followed by a single blank line.
@@ -2447,6 +2486,7 @@ x++;
ptr++;
}
while (*ptr != '\0');
+
diff --git a/configs/b-l475e-iot01a/README.txt b/configs/b-l475e-iot01a/README.txt
index fe2cc91d973..e99c3a9503a 100644
--- a/configs/b-l475e-iot01a/README.txt
+++ b/configs/b-l475e-iot01a/README.txt
@@ -65,6 +65,7 @@ Board Features
(AWS) IoT platform.
NOTES:
+
1. The board usese Wi-Fi® module Inventek ISM43362-M3G-L44 (802.11 b/g/n
compliant), which consists of BCM43362 and STM32F205 host processor
that has a standard SPI or UART interface capability. It means you
@@ -194,8 +195,12 @@ Configurations
1. The PATH environment variable include the correct path to the
directory than holds your toolchain binaries.
- 2. Make sure that the configuration is set for your build platform
- and that the toolchain is set for the toolchain type you are using.
+ 2. Check the .config file. Make sure that the configuration is set for
+ your build platform (e.g., Linux vs. Windows) and that the toolchain
+ is set for the toolchain type you are using.
+
+ The