Release candidate for mbed-os-5.10.0-rc2 #8083
Conversation
Users often use "show declaration" (or similar) in their IDE to see descriptions of callback methods so the function descriptions should be placed close to function declaration itself.
Copy edit for minor grammar nits and consistent tense across docs.
added missing current op
CRC used in LittleFS is Reversed ANSI, hence new polynomial added. Reversed polynomials perform shift in reverse direction of standard polynomial, and we do not have option to notify reverse shift to hardware. Hence this option is available in software only.
When length is zero, the buffer is not accessed. The CRC functions are used inside several other layers where a 0-length buffer may have meanings in different contexts and being able to pass 0-length NULL buffers to CRC as a noop simplifies the code.
Allow a FileBase (normally a FileSystemLike) to be set as the default, so it can be looked up as "/default" as well as its actual name.
"/fs" is a tautology - not a good name for the default filing system, as whereever we use it, we know we're specifying a filing system. Rename to "/default".
Make the built-in FileSystem::get_default_instance() implementation instantiate storage as "flash" or "sd", with "default" as an alias. This will aid interworking between simple and advanced filesystem code on various platforms. The expectation is that the names "sd" or "flash" will be always available if the device is available and configured, regardless of what "default" represents.
Quite a few of the scatter files are not (yet) aligned to 8-byte boundaries and therefore the removal of legacy alignment feature (which is under deprecation warning, but it actually not YET deprecated) broke quite a few builds to this error: Error: L6244E: Exec region RW_IRAM1 address (0x200001ac) not aligned on a 8 byte boundary. We must bring this option now back to fix the builds. This option to ld (--legacyalign) can only be removed once all of the scatter files have been fixed.
…erts those files excpet for K82F and K64F which are left as an example
- Bug fix: Remove timed out blockwise message from resend queue. If blockwise message was timed out message was still kept in the resend queue which causes unnecessary reconnections on client side. - Documentation: Document all the available macros.
Depending on initial size allocated on STM32L4 devices with TWO_RAM_REGIONS set a crash may occur. This is because there is a mismatch between the size newlib is expecting and the size actually returned by _sbrk. This is because the STM32L4 implementation of _sbrk is performing alignment internally. This patch fixes this problem by removing the code in __wrap__sbrk which performs the alignment.
Cast the pointer used in l4_retarget to uint32_t before comparing it to fix the warning: "comparison between pointer and integer"
I'm submitting a test plan for Mbed OS sockets, so that we have reference that describes wanted behaviour, required test environment, and priorities of test cases. This servers as a both documentation and specification. It needs to live with source code, as opposed to Handbook, because it will be extend, modified and fixed for faster cycle than what should be done for Handbook. Part of this document (How to run -section) will be submitted to Handbook with links to this.
Copy edit for active voice, inclusion of articles and U.S. spelling.
|
/morph build |
adbridge
force-pushed
the
release-candidate
branch
from
3a72d7b to
4599726
Compare
|
/morph mbed2-release |
Build : SUCCESSBuild number : 3047 Triggering tests/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
|
@studavekar We're going to need some more help:
|
Test : SUCCESSBuild number : 2821 |
Exporter Build : FAILUREBuild number : 2663 |
|
Relaunching the export job. It appears that the job used a node with a misconfigured network license config. /morph export-build |
|
Interesting. Looks like the morph2-build job was hit with the same build job oddity that the export job did. /morph mbed2-build |
Exporter Build : SUCCESSBuild number : 2664 |
|
/morph mbed2-build |
|
/morph mbed2-release |
Result: SUCESSYour command has finished executing! Here's what you wrote! Build artifacts : http://mbed-ci-master-2.austin.arm.com:8081/job/mbed_2_release/136/artifact/ |
No description provided.