Pull request #18: updating main.json to 1.1.0 for release

Merge in MCU16CE/pic24-dspic-can-canfd-bootloader from ~C14050/pic24-dspic-can-canfd-bootloader:release/CC16BOOT-1251-deploy-to-github-can-example-repo to develop

* commit '8939a2043af04dee4939ef0b26d6576b7296f74a':
  cleanup markdown formatting so it renders readable.
  removing 1.0.1 and adding it to 1.1.0
  adding change log back from previous commit
  updating main.json to 1.1.0 for release

Author: davidflowers

.main-meta/main.json

@@ -1,8 +1,8 @@
 {
-   "metaDataVersion":"1.0.1",
+   "metaDataVersion":"1.1.0",
    "category":"com.microchip.ide.project",
    "content":{
-      "metaDataVersion":"1.0.1",
+      "metaDataVersion":"1.1.0",
       "name":"com.microchip.mplabx.project.pic24-dspic-can-canfd-bootloader",
       "version":"1.0.1",
       "displayName":"PIC24/dsPIC CAN/CAN-FD Bootloader",
@@ -25,10 +25,10 @@
          "semverRange": ">=4.0.1"
       },
       "device":{
-         "metaDataVersion":"1.0.1",
+         "metaDataVersion":"1.1.0",
          "category":"com.microchip.portal.contentRef",
          "content":{
-            "metaDataVersion":"1.0.1",
+            "metaDataVersion":"1.1.0",
             "category":"com.microchip.device",
             "name":"dsPIC33CK256MP508",
             "versionRange":"*"

README.md

@@ -12,10 +12,11 @@ https://www.microchip.com/16-bit-bootloader
 
 ## Setup And Operation
 
-There are 3 configurations provided in this demo:
+There are 4 configurations provided in this demo:
 1) Using CAN classic on a device with the CAN-FD module
 2) Using CAN-FD on a device with the CAN-FD module
 3) Using CAN classic on a device with the enhanced CAN controller
+4) Using CAN-FD on a device with the CAN-FD module and using TA100 for external ECDSA verify
 
 The hardware and software setup is different for each of these use cases.  There are readme*.html files associated with each folder that describe the required hardware and software as well as how to setup and run each of the corresponding demos.
 
@@ -25,4 +26,5 @@ The hardware and software setup is different for each of these use cases.  There
 
 [dspic33ep-can2.0b](/dspic33ep-can2.0b "dsPIC33EP512MU810 CAN based bootloader example project")
 
+[dspic33ck-canfd-ta100](/dspic33ck-fd-ta100 "dsPIC33CK256MP508 CAN-FD based bootloader example project w TA100 Verify")
 

changelog.md

@@ -1,18 +1,20 @@
-# PIC24/dsPIC CAN / CAN-FD Bootloader Firmware v1.0.1
+# PIC24/dsPIC CAN / CAN-FD Bootloader Firmware v1.1.0
 ### Release Highlights
 
-Fixes project loading issues.
+- Fixes project loading issues.
+- ADD Demo using TA100 Trust Anchor external HSM for ECDSA verify of CAN bootloader
 
 ### Features Added\Updated
 
-Bug fixes to use externally released MCC modules rather than internal builds.  The previous version would give import warnings to user due to it being unable to find the specified version.
+- Support for TA100 ECDSA verify
+- Bug fixes to use externally released MCC modules rather than internal builds.  The previous version would give import warnings to user due to it being unable to find the specified version.
 
 # PIC24/dsPIC CAN / CAN-FD Bootloader Firmware v1.0.0
 ### Release Highlights
 
-CAN and CAN-FD bootloader firmware 
-Requires Unified Bootloader Host Application 1.17.0
+- CAN and CAN-FD bootloader firmware
+- Requires Unified Bootloader Host Application 1.17.0
 
 ### Features Added\Updated
 
-Initial Release
+- Initial Release

index.html

@@ -40,6 +40,7 @@ <h2>Setup And Operation</h2>
   <a href="./dspic33ck-can/">./dspic33ck-can/</a><br>
   <a href="./dspic33ck-canfd/">./dspic33ck-canfd/</a><br>
   <a href="./dspic33ep-can2.0b/">./dspic33ep-can2.0b/</a><br>
+  <a href="./dspic33ck-canfd-ta100/">./dspic33ck-canfd-ta100/</a><br>
 
 </body>