Add simplified steps

Author: joseph-yiu

example1_cm4_mps2_an386/README.md

@@ -19,7 +19,7 @@ cpackget update-index
 Note: This is not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s blink.csolution.yml -m > required_packs.txt
+csolution list packs blink.csolution.yml -m > required_packs.txt
 ```
 ```
 /* Step 3: Install missing packs */
@@ -28,7 +28,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s blink.csolution.yml
+csolution convert blink.csolution.yml update-rte
 ```
 
 ```
@@ -37,3 +37,16 @@ cbuild blink+MPS2_CM4_FP.cprj
 ```
 
 Note: For IAR EWARM only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
+
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild blink.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild blink.csolution.yml --packs --update-rte --toolchain AC6
+```
+
+

example1_cm55_mps3_an552/README.md

@@ -19,7 +19,7 @@ cpackget update-index
 Note: This is not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s blink.csolution.yml -m > required_packs.txt
+csolution list packs blink.csolution.yml -m > required_packs.txt
 ```
 ```
 /* Step 3: Install missing packs */
@@ -28,7 +28,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s blink.csolution.yml
+csolution convert blink.csolution.yml update-rte
 ```
 
 ```
@@ -37,3 +37,14 @@ cbuild blink+MPS3-Corstone-300.cprj
 ```
 
 Note: For IAR EWARM only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
+
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild blink.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild blink.csolution.yml --packs --update-rte --toolchain AC6
+```

example2_cm4_mps2_an386/README.md

@@ -27,7 +27,7 @@ cpackget update-index
 Note: This is not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s hello.csolution.yml -m > required_packs.txt
+csolution list packs hello.csolution.yml -m > required_packs.txt
 ```
 ```
 /* Step 3: Install missing packs */
@@ -36,7 +36,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s hello.csolution.yml
+csolution convert hello.csolution.yml update-rte
 ```
 
 ```
@@ -45,3 +45,14 @@ cbuild hello+MPS2_CM4_FP.cprj
 ```
 
 Note: For IAR only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
+
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild hello.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild hello.csolution.yml --packs --update-rte --toolchain AC6
+```

example2_cm55_mps3_an552/README.md

@@ -27,7 +27,7 @@ cpackget update-index
 Note: Not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s hello.csolution.yml -m > required_packs.txt
+csolution list packs hello.csolution.yml -m > required_packs.txt
 ```
 ```
 /* Step 3: Install missing packs */
@@ -36,7 +36,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s hello.csolution.yml
+csolution convert hello.csolution.yml update-rte
 ```
 
 ```
@@ -46,3 +46,14 @@ cbuild hello+MPS3-Corstone-300.cprj
 Note: For AC6 only - Instead of using cbuild, you can use an IDE such as Keil MDK to compile the generated project.
 
 Note: For IAR only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
+
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild hello.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild hello.csolution.yml --packs --update-rte --toolchain AC6
+```

example3_cm4_mps2_an386/README.md

@@ -27,7 +27,7 @@ cpackget update-index
 Note: Not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s coremark.csolution.yml -m > required_packs.txt
+csolution list packs coremark.csolution.yml -m > required_packs.txt
 ```
 ```
 /* Step 3: Install missing packs */
@@ -36,7 +36,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s coremark.csolution.yml
+csolution convert coremark.csolution.yml update-rte
 ```
 
 ```
@@ -47,6 +47,17 @@ Note: For AC6 only - Instead of using cbuild, you can use an IDE such as Keil MD
 
 Note: For IAR only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
 
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild coremark.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild coremark.csolution.yml --packs --update-rte --toolchain AC6
+```
+
 ## Disclaimers
 
 * CoreMark is a benchmark from SPEC Embedded Group (formerly EEMBC) and is not a property of Arm.

example4_mps2_multi_devices/README.md

@@ -41,7 +41,7 @@ cpackget update-index
 Note: Not required for a new installation and usually this is not needed. But if the local CMSIS-Pack storage hasn't been used for a while, it worth running it to ensure the index is up-to-date.
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s coremark.csolution.yml -m > required_packs.txt
+csolution list packs coremark.csolution.yml -m > required_packs.txt
 ```
 
 ```
@@ -51,7 +51,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s coremark.csolution.yml
+csolution convert coremark.csolution.yml update-rte
 ```
 
 ```

example5_multi_projects/README.md

@@ -29,7 +29,7 @@ Note: Not required for a new installation and usually this is not needed. But if
 
 ```
 /* Step 2: Generate the list of missing packs */
-csolution list packs -s coremark-pro.csolution.yml -m > required_packs.txt
+csolution list packs coremark-pro.csolution.yml -m > required_packs.txt
 ```
 
 ```
@@ -39,7 +39,7 @@ cpackget add -f required_packs.txt
 
 ```
 /* Step 4: Generate build information */
-csolution convert -s coremark-pro.csolution.yml
+csolution convert coremark-pro.csolution.yml update-rte
 ```
 
 ```
@@ -49,6 +49,17 @@ cbuild proj_{project_name}/{project_name}+MPS2_CM7_DP.cprj
 
 Note: For IAR only - Instead of running step 4 and step 5, you can import csolution project in EWARM to compile the project.
 
+Alternatively, step 2 to step 5 can be shortened as one step:
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild coremark-pro.csolution.yml --packs --update-rte
+```
+You can also override the toolchain choice (the following example use AC6, but it can also be GCC, CLANG or IAR):
+```
+/* Step 2: Download packs and compile the project in one go */
+cbuild coremark-pro.csolution.yml --packs --update-rte --toolchain AC6
+```
+
 ## Disclaimers
 
 * CoreMark-Pro is a benchmark from SPEC Embedded Group (formerly EEMBC) and is not property of Arm.