Merge pull request #2708 from sarahmarshy/uvision-and-iar

[Exporters] Refactor Uvision and IAR and initial support of CMSIS projects

Author: sg-

docs/mbed_targets.md

@@ -14,7 +14,7 @@ mbed uses JSON as a description language for its build targets. The JSON descrip
             "function": "TEENSY3_1Code.binary_hook",
             "toolchains": ["ARM_STD", "ARM_MICRO", "GCC_ARM"]
         },
-        "progen": {"target": "teensy-31"},
+        "device_name": "MK20DX256xxx7",
         "detect_code": ["0230"]
 ```
 
@@ -160,17 +160,10 @@ In this case, it converts the output file (`binf`) from binary format to Intel H
 
 The hook code can look quite different between different targets. Take a look at the other classes in *targets.py* for more examples of hook code.
 
-## progen
+## device_name
 
-This property is used to pass additional data to the project generator (used to export the mbed code to various 3rd party tools and IDEs). A definition for `progen` looks like this:
+This property is used to pass necessary data for exporting the mbed code to various 3rd party tools and IDEs.
 
-```
-"progen": {
-    "target": "lpc11u35_401",
-    "uvision": {
-        "template": ["uvision_microlib.uvproj.tmpl"]
-    }
-```
+This is possible because the device name corresponds to a field in publicly hosted CMSIS packs. These packs hold target properties. [This](http://www.keil.com/pack/Keil.Kinetis_K20_DFP.pdsc) is the pdsc that contains TEENSY_31 device (MK20DX256xxx7). The device information begins on line 156. The dname (device name) field on line 156 directly corresponds to that in the Uvision5 IDE target selection window. Beginning on line 15 of `tools/export/uvision/uvision.tmpl`, target information from these packs is used to generate valid Uvision5 projects. If the device name is not found, we use a generic ARM CPU target in Uvision5.
+`tools/export/iar/iar_definitions.json` utilizes this device name to store information necessary to set the target in an IAR project.
 
-The `target` property of `progen` specifies the target name that must be used for the exporter (if different than the mbed target name).
-For each exporter, a template for exporting can also be specified. In this example, the template used for generating a uVision project file is in a file called `uvision_microlib.uvproj.tmpl`. It is assumed that all the templates are located in `tools/export`.

requirements.txt

@@ -3,11 +3,13 @@ PySerial>=2.7
 PrettyTable>=0.7.2
 Jinja2>=2.7.3
 IntelHex>=1.3
-project-generator==0.9.10
-project_generator_definitions>=0.2.26,<0.3.0
 junit-xml
 pyYAML
 requests
 mbed-ls>=0.2.13
 mbed-host-tests>=1.1.2
 mbed-greentea>=0.2.24
+pyxdg>=0.25
+pycurl>=4
+beautifulsoup4>=4
+fuzzywuzzy>=0.11