The atmel-rf-driver-mirror repo is pointing to a SHA in the
atmel-rf-driver repo. This prevents mbed-os from building.
This patch updates atmel-rf-driver.lib to point to the correct
SHA.
Update the Callback class to handle a NULL thunk by returning 0
rather than trying to call the thunk. This fixes a crash that occurs
on some targets when the TX uart handler is not attached.
Background:
The K64F HAL uart implementation calls the TX interrupt handler
every time a uart interrupt occurs while the TX register is empty.
It does not check to see if the TX interrupt has been enabled.
This means that the TX interrupt can and typically does get
run on RX events. This causes a crash with the newer callback
code which did not (prior to this patch) support a NULL thunk.
Make the following changes for IAR support:
-define __deprecated_message for IAR
-fix python error in iar.py
-move variable length array in buffered serial from cpp file to c file.
IAR only supports variable length arrays in c.
Added a parameter '-l' to control how many project runs are uploaded at a
time. The default is 1000. The prevents HTTP errors when the POST request
is too large.
It is now possible to remove a macro using "_remove" for both macros
without vale (MACRO) and macros with value (MACRO=VALUE) simply by
specifying the macro name.
Updated include files within tests to use subdirectory/header.h
Updated global variables within tests to be static
Fixed indentation issue.
Renamed Timeout class variables to be more meaningful
Moved definition of utest_trace into stack_trace.cpp
Removed unecessary call to .clear() method in utest_add_to_trace()
Changed UTEST_LOG_FUNCTION macro to UTEST_LOG_FUNCTION();
Turn on support for variable length arrays for the IAR C compiler.
This provides greater compatibility with GCC and ARMCC.
Note: The current version of iccarm at the time of this patch
(V7.40.3.8902) does not support variable length arrays in C++.
I ran into this earlier today and yesterday:
If you spelled something wrong/forgot to tab complete and had build succesfully before it woild silently and incorrectly build successfully
Check the content of `.mbedignore` files and try to match the file
patterns against the directories and source files found while travelling
the directory structure.
Every line in `.mbedignore` file is treated as a unix style glob pattern.
Before matching, the pattern is appended with its directory location, so
it will match only folder on same level, or deeper in the directory structure.
For example:
Directory ./source/test contains .mbedignore with content:
`unittest/*`
Then everything under ./source/test/unittest/ is ignored, including the
unittest folder itself.
Another example:
When .mbedignore file contains just `*`, then everything under the folder
it is located, is ignored. It won't even be added to include paths.
Brian Daniels
Anna Bridge
Martin Kojtal
Devaraj Ranganna
Christopher Haster
Russ Butler
Bogdan Marinescu
Stephen Kyle
Sam Grove
Bogdan Marinescu
Simon Hughes
Marcus Shawcroft
Jimmy Brisson
Seppo Takalo