As of 722628be02, the "remainder" configuration
also uses the default location near the end of flash. Which makes the two tests
nearly identical with the exception that the "last two sectors" test correctly
handles parts with a low (possibly 1:1) erase size to program size ratio.
Therefore, change the "remainder" test to instead be a "default" test that uses
the tdb_internal_address/size values, so that it
a.) tests something meaningfully different and
b.) tests using the custom TDB address/size values if they are provided.
c.) functions correctly on devices where the default sector-based size computation
does not work (e.g. because of the low erase size to program size ratio)
and therefore a custom location and size has been specified.
The is_conf_tdb_internal variable is unused and therefore removed.
7e110b44c0 Added automatic version prefixing to releases
7f7b7332e3 Added scripts/prefix.py for automatically prefixing version numbers
d3a2cf48d4 Merge pull request #135 from johnlunney/patch-1
22b0456623 Add missing word (and reflow text)
ec4d8b68ad Changed release script to generate drafts
c7894a61e1 Added a handful of links to related projects
195075819e Added 2GiB file size limit and EFBIG reporting
97d8d5e96a Fixed issue where a rename causes a split and pushes dir out of sync
0bb1f7af17 Modified release script to create notes only on minor releases
447d89cbd8 Merge pull request #109 from OTAkeys/pr/fix-sign-compare
28d2d96a83 Fix -Wsign-compare error
cb62bf2188 Fixed release script issue with fetching recent tags
646b1b5a6c Added -Wjump-misses-init and fixed uninitialized warnings
1b7a15599e Merge pull request #106 from conkerkh/master
e5a6938faf Fixed possible infinite loop in deorphan step
6ad544f3f3 If stats file doesn't exist lfs_emubd_create will fail.
3419284689 Fixed issue with corruption due to different cache sizes
git-subtree-dir: features/storage/filesystem/littlefs/littlefs
git-subtree-split: 7e110b44c0e796dc56e2fe86587762d685653029
This is related to https://github.com/ARMmbed/mbed-os/issues/11256
When TARGET_PSA is enabled on Cortex-A boards, the SECURE
is redeclared. So to minimize the impact we can redeclare this in
val.h which is used only by Mbed. And `security_t` itself is used in
mbed-os\components\TARGET_PSA\TESTS, but the SECURE string is not used.
Renamed to `caller_security_t` which aligns with
https://github.com/ARM-software/psa-arch-tests
Earlier changes introduced a change to default Arm C6, which does not compile the micro library which is based on Mbed 2. This change fixes the compiler version for NRF51_MICROBIT devices.
This fixes the stack overflow error during the basic USB tests.
Update the ctrl_buf member of the USBTester and USBEndpointTester test
classes to be allocated on the heap. This saves 2 KB of a main stack.
The test floods the device with UDP requests (it skips the 100 ms delay to simulate instant timeout). ESP8266 starts responding with "busy p..." message. It needs more time to process the data and recover for subsequent tests.
Propagate separate alt cycle and dummy cycle counts from QSPIFBlockDevice
down to the qspi driver, so that drivers which handle the two separately have
enough information to do so.
The QSPI spec allows alt to be any size that is a multiple of the
number of data lines. For example, Micron's N25Q128A uses only a
single alt cycle for all read modes (1, 2, or 4 bits depending on
how many data lines are in use).
We get this compiler warning;
Compile [ 7.9%]: AT_CellularDevice.cpp
[Warning] AT_CellularDevice.cpp@206,18: variable 'err' set but not used [-Wunused-but-set-variable]
Due to the fact, that the code that would actually use this variable
is behind trace flags. Based on review feedback from Antti Kauppila and
Kimmo Väisänen, adding same flagging also for that.
- Reason being - the operation needs to be within the locks.
- Fixed miscalculation in SPI frequency setup (divider value).
- Added possibility to set up SCK line as NC (usable when SPI peripheral
is used to handle non-SPI protocols.
- Fixed handlingh of 16-bit (and other >8 bit) transfers.
(cherry picked from commit 7d391f257b4ff6cdd7b43eeaa4894f8ce6d2cf8e)
Return value was ignored, and TDBStore:init() ended up in a
MBED_ERROR() phase after that.
TDBStore API was limited to allow returning of only two separate
errors, which may end up hiding the actual return value. Change
the documentation slightly to allow returning of original error
code from the underlying block device.
Fixes#11591