Skip to content

Feature storage - update from master #3667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 241 commits into from
Jan 31, 2017

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Jan 31, 2017

Merge master branch to bring this branch up to date.

cc @geky @simonqhughes

ccli8 and others added 30 commits December 5, 2016 15:12
condition               posix error     mbed error
good host, closed port  ECONNREFUSED    NSAPI_ERROR_NO_CONNECTION
bad host                EHOSTUNREACH    NSAPI_ERROR_NO_CONNECTION
bad network             ENETUNREACH     NSAPI_ERROR_NO_CONNECTION
1. Add targets into build_travis.py and tests.py.
2. Add target SPI pins into SPI SD test samples.
3. Rename target TOOLCHAIN_GCC_ARM/retarget.c to avoid name collision of compiled retarget.o with platform/retargets.cpp.
Redress stm32f1xx_hal_can.h header file comment
- RCC init: one PLL parameter was missing
- GPIO: mode was not allowed by ST HAL API
Use MBED_CONF_RTOS_PRESENT to filter out mbedtls alternative for mbed OS 2.
A few new error codes are added to nsapi_error_t and
support for non-blocking socket connect is added.
Nanostack's connect call will be non-blocking.
Whereas LWIP connect call is currently blocking, and it could be changed now
to be non-blocking.
Attempt to maximize the devices bandwidth with an exponentially growing
transaction of random sequences. Also prints the time taken and bandwidth
reached during the tests.
- Unreliable service would occasionally lead to false-failures
- Redundant with hello world and echo tests
Added test for the pattern of packets used during the DTLS
handshake. This pattern (5x ~300 byte packets) has been very
problematic for new network interfaces.
Checks for connecting/disconnecting the network interface
A larger buffer gives the network stack the best options for maximizing
throughput. However, the initial buffer size did not fit on small
targets. Resized 8192 -> 1024.
…loods

Dynamic buffers gives the network stack the maximum throughput while
still supporting smaller devices. This should expose the largest number
of issues across differently sized platforms.

Additionally, restructured the UDP tests to avoid unintentionally flooding
the recieving side with bad data after failed packets.

Also, added a bit more documentation
Simply runs the echo tests with multiple sockets in parallel
Before the test would only succeed if all packets (16) succeed. Updated
to succeed if 75% succed.
Printing out dropped packets caused significantly more overhead in the
parallel tests due to increased noise on the network. This noise would
push the tests past their provided timeouts.
These tests could adopt the dynamically sized buffers used for the
packet-pressure tests, however throughput is not an important feature
of these tests.
Despite being able to buffer an arbitrary stream of data,
TCP send is still limited by the available buffer space in the
network stack. Errors from TCP send are perfectly reasonable
and should be handled by reducing the buffer that is attempted.
To allow a network stack to support both NSAPI and its own options, try to make
sure the NSAPI levels don't collide with level numbers likely to be used by
network stacks.

Distinguish between socket and stack options, and tighten up documentation. Add
IP MRU stack options as an example (implementation not immediately planned for
any stack, but could be useful).
This change was spurred by a confusing error. I attempted to compile for
the RZ_A1H (a Cortex-A device), and I had the standalone ARM compiler in
my system path, which supports Cortex-A. However, the default path for
the ARM compiler in settings.py uses a Keil installation, which only
supports Cortex-M. It found my Keil installation and used that instead.
This change proposes to remove this default behavior and instead
requires the user to explicitly set the intended compiler, either by a
settings file, mbed CLI, environment variables, or by placing the
compiler in your PATH.
Delete this page because an exact duplicate exists in the Handbook
Previously, the RTOS threads test was conditionally change the thread
stack size for all test cases based on the target. Now, it uses the
default stack size for all targets when threads are created serially,
and uses a 512 byte stack for the threads that are created in parallel.
It was possible to remove an entire project if clean was specified on
the command line. That's a Bad Thing(tm).
STM32 supported targets have 2 possible versions of I2C.
This patch makes the start / stop / read and write byte work ok for IP V2.
This was not working before and does not seem to be widely used.
0xc0170 and others added 26 commits January 26, 2017 10:24
Target system - Inherit names from target parents
…ain_check

Fixing toolchain executable not found error for build.py
Makefile: Allow user overrides of LINKER_SCRIPT Make variable
Signed-off-by: Mahadevan Mahesh <[email protected]>
Renaming test_env.cpp in greentea to avoid warning
Exporters: make jinja engine strict
tests: Fix error on MacOS for udp_dtls_handshake test
README: Build info; Docs version updated
STM32: make PortNames.h a common file
STM32: Move types definitions to a common file
STM32 I2C : Fix bug in i2c_byte_read function
Platform: Add sleep/deepsleep user facing functions
MAX32630FTHR: Adding new platform
Copy link
Contributor

@geky geky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wooh, assuming tests work 👍

@simonqhughes simonqhughes merged commit a010b57 into ARMmbed:feature-storage Jan 31, 2017
@0xc0170 0xc0170 deleted the my_test branch September 1, 2020 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.