Release candidate for mbed-os-5.8.3 #6697
Conversation
There are cases where HW registers are found in unpexcepted state when exiting Deep Sleep only few micro-seconds after it was entered. By using an internal clock that does not depend on anythin and clocking the system without using PLL, this allows SetSysClock default configuration to run fine whatever possible configuration we find the HW in when exiting Deep Sleep. Also we shall restore interrupts only after all cloks are back to expected running state.
Tests have shown that there is hich-up on MSI clock during the setup phase. If this stabilization phase happens when application has restarted again this can have side effects, like grambled UART characters typically. So we're adding a delay before hading-over back to application. With this modification, on NCULEO_L476RG, the wake-up time is increased from 2ms to 2,5ms. If possible this should be improved in the future to save 500 microseconds of wak-up time. See TODO
… to be accessible in the template directory
…gnore so mbed compile doesn't pick them up
…m getting confused
remove this target from json file as this is not a real target but a parent target fix error removing the target
There's not a port
Using credentials avoids rate-limiting based on Travis's IP address
This patchs adds TRNG support using the upstreamed, open-source, TZ-TRNG driver. It also implements the HAL for TRNG and add it in features. The mbed-os.py script deletes files that are unused by mbed-os. Change-Id: Idf8eefd809f00d40e0ad3cf7657f2a8c2eca3505 Signed-off-by: Hugues de Valon <[email protected]>
Use X to fill PR template and be more specific about only one PR type per pull request.
Bug was reported by @tpet93 and it was correctly diagnosed that channels were not being set in the phy_params structure. This commit fixes the bug and sets up channels correctly.
Contains one error fix: IOTCLT-2469 CoAP UDP retransmission does not work for blocks after first one for requests (Eg. registration POST) NOTE! These are internal changes required for cloud client. This has no direct relevance to any mbed-os functionality.
Copy edit for grammar.
Copy edit file for grammar.
Copy edit file for grammar.
Copy edit file for grammar.
One of the big simplifications in littlefs's implementation is the complete lack of tracking free blocks, allowing operations to simply drop blocks that are no longer in use. However, this means the lookahead buffer can easily contain outdated blocks that were previously deleted. This is usually fine, as littlefs will rescan the storage if it can't find a free block in the lookahead buffer, but after changes that caused littlefs to more conservatively respect the alloc acks (e611cf5), any scanned blocks after an ack would be incorrectly trusted. The fix is to eagerly scan ahead in the lookahead when we allocate so that alloc acks are better able to discredit old lookahead blocks. Since usually alloc acks are tightly coupled to allocations of one or two blocks, this allows littlefs to properly rescan every set of allocations. This may still be a concern if there is a long series of worn out blocks, but in the worst case littlefs will conservatively avoid using blocks it's not sure about. Found by davidefer
…inters As pointed out by davidefer, the lookahead pointer modular arithmetic does not work around integer overflow when the pointer size is not a multiple of the block count. To avoid overflow problems, the easy solution is to stop trying to work around integer overflows and keep the lookahead offset inside the block device. To make this work, the ack was modified into a resetable counter that is decremented every block allocation. As a plus, quite a bit of the allocation logic ended up simplified.
|
/morph build |
|
/morph mbed2-release |
Build : SUCCESSBuild number : 1819 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1464 |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputBuild failed! |
Test : SUCCESSBuild number : 1626 |
|
Looks like the mbed2 build failed for KL27Z with : |
|
Looking at the failure - I could reproduce locally as well. |
|
This broke it #6468. It run mbed 2 build, but not for KL27Z device. This is the define that is missing https://github.com/ARMmbed/mbed-os/pull/6468/files#diff-587fe16f0abeb13087f7aa9a27cc7ef7R470 ( this was defined for the wrong cpu type, our kl27z uses different CPU so its missing). I'll send a patch soon the release job has that device in. @studavekar @kegilbert Please can you review, I'll create a separate jira ticket for this. |
KL27Z: Flash protection macro addition
|
/morph build |
Build : SUCCESSBuild number : 1824 Triggering tests/morph test |
Test : SUCCESSBuild number : 1630 |
Exporter Build : FAILUREBuild number : 1468 |
|
Appears that a Jenkins machine left the party too soon. /morph export-build |
Exporter Build : SUCCESSBuild number : 1474 |
No description provided.