Go to file
Russ Butler 1da259af3b Fix RTC test failures by removing critical sect
Remove the critical section in mbed_rtc_time.c and instead use a
mutex to protect this. This function does not need to be interrupt
safe, just thread safe.

This fixes crashes on the GCC_ARM toolchain on the RTC test due to
trying to lock the GCC environment mutex while in a critical section.
Prior to this patch, this failure was likely to occur on STM and LPC
processor families.
2016-07-28 14:35:51 -05:00
TESTS Merge pull request #2248 from pan-/define_stack_stize_for_RTOS_threads_test 2016-07-26 20:14:51 -05:00
docs Merge pull request #2279 from geky/docs-ca 2016-07-28 13:43:47 +03:00
features Fix for https://github.com/ARMmbed/mbed-os-example-client/issues/44 2016-07-27 22:03:53 +03:00
hal Fix RTC test failures by removing critical sect 2016-07-28 14:35:51 -05:00
libraries Create dedicated file for PlatformMutex 2016-07-28 14:21:04 -05:00
rtos Merge pull request #2211 from pan-/nrf52_nrf51_unified_integration 2016-07-27 02:35:43 -05:00
tools Merge pull request #2281 from geky/tools-ca-set-arith-fix 2016-07-28 16:23:17 +03:00
.gitattributes Added .gitattributes for automatic LF line ending conversion 2013-08-08 13:19:34 +03:00
.gitignore Move private_settings.py to root mbed_settings.py. Various updates to reflect the path changes 2016-06-09 22:24:05 +01:00
.travis.yml Add the toolchain api test to the travis CI 2016-07-15 10:12:31 -05:00
CONTRIBUTING.md Mentioned the Contributor Agreement in Contributing.md 2015-04-16 11:47:51 -04:00
LICENSE Add Apache v2 LICENSE file 2013-08-06 12:05:04 +01:00
MANIFEST.in Further changes to reflect workspace_tools to tools rename 2016-06-09 21:40:54 +01:00
README.md update Nucleo-F410RB 2016-06-14 22:09:21 +02:00
mbed_lib.json Added config option for stdio baud rate 2016-07-11 18:42:44 -05:00
requirements.txt IDE build tests with progen 2016-07-15 13:25:35 -05:00
setup.py adding project_generator_definitions to setup.py and requirements.txt 2016-07-11 10:55:02 +02:00

README.md

mbed SDK

Build Status

The mbed Software Development Kit (SDK) is a C/C++ microcontroller software platform relied upon by tens of thousands of developers to build projects fast.

The SDK is licensed under the permissive Apache 2.0 licence, so you can use it in both commercial and personal projects with confidence.

The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Documentation

Supported Microcontrollers and Boards

View all on the mbed Platforms page.

NXP:

Freescale:

STMicroelectronics:

Nordic:

Renesas:

Silicon Labs:

Atmel:

Supported Toolchains and IDEs

The current mbed exporters scripts (IDE support) will be replaced by Project generator (=progen). Any new IDEs support, should be implemented using progen API - add IDE to progen, use progen API to generate a mbed project.

API Documentation

Community

For discussing the development of the mbed SDK itself (Addition/support of microcontrollers/toolchains, build and test system, Hardware Abstraction Layer API, etc) please join our mbed-devel mailing list.

For every topic regarding the use of the mbed SDK, rather than its development, please post on the mbed.org forum, or the mbed.org Q&A.

For reporting issues in the mbed libraries please open a ticket on the issue tracker of the relevant mbed official library.

Setup

Skip any step where a compatible tool already exists

  1. Install Python 2.7.9 or above and make sure it's added to path
  2. Install Git and make sure it's added to path
  3. Install virtualenv in python
> git clone https://github.com/mbedmicro/mbed
> pip install virtualenv
> virtualenv venv
> 

Develop

  1. Update dependencies and start virtual environment. This should be done everytime you pull new changes
> "venv/Scripts/activate"
> pip install -r requirements.txt
> cd tools
> ... do things ...
> "venv/Scripts/deactivate"