Merge remote-tracking branch 'ARMmbed/master'

Author: komori-t

.github/issue_template.md

@@ -0,0 +1,48 @@
+Note: This is just a template, so feel free to use/remove the unnecessary things
+
+### Description
+- Type: Bug | Enhancement | Question
+- Related issue: `#abc`
+- Priority: Blocker | Major | Minor
+
+---------------------------------------------------------------
+## Bug
+
+**Target**
+K64F|??
+
+**Toolchain:**
+GCC_ARM|ARM|IAR
+
+**Toolchain version:**
+
+**mbed-cli version:** 
+(`mbed --version`)
+
+**meed-os sha:**
+(`git log -n1 --oneline`)
+
+**DAPLink version:**
+
+**Expected behavior**
+
+**Actual behavior**
+
+**Steps to reproduce**
+
+----------------------------------------------------------------
+## Enhancement
+
+**Reason to enhance or problem with existing solution**
+
+**Suggested enhancement**
+
+**Pros**
+
+**Cons**
+
+-----------------------------------------------------------------
+
+## Question
+
+**How to?**

.github/pull_request_template.md

@@ -0,0 +1,39 @@
+Notes:
+* Pull requests will not be accepted until the submitter has agreed to the [contributer agreement](https://github.com/ARMmbed/mbed-os/blob/master/CONTRIBUTING.md).
+* This is just a template, so feel free to use/remove the unnecessary things
+
+## Description
+A few sentences describing the overall goals of the pull request's commits.
+
+
+## Status
+**READY/IN DEVELOPMENT/HOLD**
+
+
+## Migrations
+If this PR changes any APIs or behaviors, give a short description of what *API users* should do when this PR is merged.
+
+YES | NO
+
+
+## Related PRs
+List related PRs against other branches:
+
+branch | PR
+------ | ------
+other_pr_production | [link]()
+other_pr_master | [link]()
+
+
+## Todos
+- [ ] Tests
+- [ ] Documentation
+
+
+## Deploy notes
+Notes regarding the deployment of this PR. These should note any
+required changes in the build environment, tools, compilers, etc.
+
+
+## Steps to test or reproduce
+Outline the steps to test or reproduce the PR here.

.gitignore

@@ -34,8 +34,6 @@ var
 sdist
 develop-eggs
 .installed.cfg
-lib
-lib64
 
 # Installer logs
 pip-log.txt

.pylintrc

@@ -0,0 +1,2 @@
+[Format]
+max-line-length=80

.travis.yml

@@ -3,6 +3,7 @@ python:
 
 script:
   - PYTHONPATH=. python tools/test/config_test/config_test.py
+  - python tools/test/pylint.py
   - py.test tools/test/toolchains/api.py
   - python tools/build_travis.py
 before_install:
@@ -17,3 +18,4 @@ install:
   - sudo pip install prettytable
   - sudo pip install jinja2
   - sudo pip install pytest
+  - sudo pip install pylint

CONTRIBUTING.md

@@ -1,18 +1,18 @@
 # Description
-This document is cheat sheet for everyone who wants to contribute to mbedmicro/mbed GitHub repository at GitHub. 
+This document is cheat sheet for everyone who wants to contribute to [ARMmbed/mbed-os](https://github.com/ARMmbed/mbed-os) GitHub repository at GitHub. 
 All changes in code base should originate from GitHub Issues and take advantage of existing GitHub flows. Goal is to attract contributors and allow them contribute to code and documentation at the same time.
 
 Guidelines from this document are created to help new and existing contributors understand process workflow and align to project rules before pull request is submitted. It explains how a participant should do things like format code, test fixes, and submit patches.
 
 ## Where to get more information?
-You can for example read more in our ```docs``` section in [mbedmicro/mbed/doc](https://github.com/PrzemekWirkus/mbed/tree/docs/docs) directory.
+You can for example read more in our ```docs``` section in [ARMmbed/mbed-os/doc](https://github.com/ARMmbed/mbed-os/tree/master/docs) directory.
 
 # How to contribute
 We really appreciate your contributions! We are Open Source project and we need your help. We want to keep it as easy as possible to contribute changes that get things working in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
 
 Before a pull request will be merged, the [mbed Contributor Agreement](http://developer.mbed.org/contributor_agreement/) must be signed.
 
-You can pick up existing [mbed GitHub Issue](https://github.com/mbedmicro/mbed/issues) and solve it or implement new feature you find important, attractive or just necessary. We will review your proposal via pull request mechanism, give you comments and merge your changes if we decide your contribution satisfy criteria such as quality.
+You can pick up existing [mbed-os GitHub Issue](https://github.com/ARMmbed/mbed-os/issues) and solve it or implement new feature you find important, attractive or just necessary. We will review your proposal via pull request mechanism, give you comments and merge your changes if we decide your contribution satisfy criteria such as quality.
 
 # Enhancements vs Bugs
 Enhancements are:
@@ -23,7 +23,7 @@ Enhancements are:
 * Documentation work.
 
 Bugs are:
-* Issues rose internally or externally by mbedmicro/mbed users.
+* Issues rose internally or externally by [ARMmbed/mbed-os](https://github.com/ARMmbed/mbed-os) users.
 * Internally (within mbed team) created issues from Continuous Integration pipeline and build servers.
 * Issues detected using automation tools such as compilers, sanitizers, static code analysis tools etc.
 
@@ -39,7 +39,7 @@ Please be patient, digest Gate Keeper's feedback and respond promptly :)
 * Before starting the mbed SDK porting, you might want to familiarize with the [mbed SDK library internals](http://developer.mbed.org/handbook/mbed-library-internals) first.
 
 # Glossary
-* Gate Keeper – persons responsible for overall code-base quality of mbedmicro/mbed project.
+* Gate Keeper – persons responsible for overall code-base quality of [ARMmbed/mbed-os](https://github.com/ARMmbed/mbed-os) project.
 * Enhancement – New feature deployment, code refactoring actions or existing code improvements.
 * Bugfix – Issues originated from GitHub Issues pool, raised internally within mbed classic team or issues from automated code validators like linters, static code analysis tools etc.
-* Mbed classic – mbed SDK 2.0 located in GitHub at mbedmicro/mbed.
+* Mbed classic – mbed SDK 2.0 located in GitHub at [ARMmbed/mbed-os](https://github.com/ARMmbed/mbed-os).

Jenkinsfile

@@ -0,0 +1,32 @@
+
+// List of targets to compile
+def targets = [
+  //"LPC1768",
+  //"NUCLEO_F401RE",
+  //"NRF51822",
+  "K64F"
+  ]
+
+// Map toolchains to compiler labels on Jenkins
+def toolchains = [
+  ARM: "armcc",
+  //IAR: "iar_arm",
+  GCC_ARM: "arm-none-eabi-gcc"
+  ]
+
+// mbed.getCurrentBranch returns either local branch name or reference to pull request
+def currentBranch = mbed.getCurrentBranch()
+
+// Create a map of predefined build steps 
+def parallelSteps = mbed.createParalleSteps("mbed-os", targets, toolchains)
+
+// Run build steps parallel, map as paramater
+mbed.compile(parallelSteps)
+
+def testApps = [
+  "mbed-os-cliapp",
+  "mbed-client-testapp"
+  ]
+
+// buildTestApps accepts array of test application names and a mbed-os branch or PR reference as parameters
+mbed.buildTestApps(testApps, "${currentBranch}")

README.md

@@ -8,7 +8,7 @@ mbed OS accelerates the process of creating a connected product by providing a p
 
 Our current release series is mbed OS 5.1:
 
-- [Release Note](https://docs.mbed.com/docs/mbed-os-release-notes/en/latest/5_1/release)
+- [Release Note](https://docs.mbed.com/docs/mbed-os-release-notes/en/latest/5_1/release/)
 
 ## Getting Started for Developers
 
@@ -20,4 +20,4 @@ We have a getting started guide for developers using mbed OS in applications:
 
 We have a getting started guide for contributors working on mbed OS:
 
-- Have a look in the docs directory
+- Have a look in the docs directory

TESTS/host_tests/timing_drift_auto.py

@@ -0,0 +1,106 @@
+"""
+mbed SDK
+Copyright (c) 2011-2013 ARM Limited
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+"""
+
+from mbed_host_tests import BaseHostTest
+
+
+class TimingDriftTest(BaseHostTest):
+    """ This test is reading single characters from stdio
+        and measures time between their occurrences.
+    """
+    __result = None
+    
+    # This is calculated later: average_drift_max * number of tick events
+    total_drift_max = None
+    
+    average_drift_max = 0.05
+    ticks = []
+    start_time = None
+    finish_time = None
+    dut_seconds_passed = None
+    total_time = None
+    total_drift = None
+    average_drift = None
+    
+    def _callback_result(self, key, value, timestamp):
+        # We should not see result data in this test
+        self.__result = False
+
+    def _callback_end(self, key, value, timestamp):
+        """ {{end;%s}}} """
+        self.log("Received end event, timestamp: %f" % timestamp)
+        self.notify_complete(result=self.result(print_stats=True))
+
+
+    def _callback_tick(self, key, value, timestamp):
+        """ {{tick;%d}}} """
+        self.log("tick! %f" % timestamp)
+        self.ticks.append((key, value, timestamp))
+
+
+    def setup(self):
+        self.register_callback("end", self._callback_end)
+        self.register_callback('tick', self._callback_tick)
+
+
+    def result(self, print_stats=True):        
+        self.dut_seconds_passed = len(self.ticks) - 1
+        
+        if self.dut_seconds_passed < 1:
+            if print_stats:
+                self.log("FAIL: failed to receive at least two tick events")
+            self.__result = False
+            return self.__result
+
+        self.total_drift_max = self.dut_seconds_passed * self.average_drift_max
+
+        self.start_time = self.ticks[0][2]
+        self.finish_time = self.ticks[-1][2]
+        self.total_time = self.finish_time - self.start_time
+        self.total_drift = self.total_time - self.dut_seconds_passed
+        self.average_drift = self.total_drift / self.dut_seconds_passed
+        
+        if print_stats:
+            self.log("Start: %f" % self.start_time)
+            self.log("Finish: %f" % self.finish_time)
+            self.log("Total time taken: %f" % self.total_time)
+        
+            total_drift_ratio_string = "Total drift/Max total drift: %f/%f"
+            self.log(total_drift_ratio_string % (self.total_drift,
+                                                 self.total_drift_max))
+                                                 
+            average_drift_ratio_string = "Average drift/Max average drift: %f/%f"
+            self.log(average_drift_ratio_string % (self.average_drift,
+                                                   self.average_drift_max))
+        
+
+        if abs(self.total_drift) > self.total_drift_max:
+            if print_stats:
+                self.log("FAIL: Total drift exceeded max total drift")
+            self.__result = False
+        elif self.average_drift > self.average_drift_max:
+            if print_stats:
+                self.log("FAIL: Average drift exceeded max average drift")
+            self.__result = False
+        else:
+            self.__result = True
+        
+        return self.__result
+
+
+    def teardown(self):
+        pass