Kyle Kearney 65def89e94 Make devicekey remainder test more meaningful ... 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.		2019-10-16 11:58:32 +01:00
..
direct_access_devicekey_test	Make devicekey remainder test more meaningful	2019-10-16 11:58:32 +01:00
filesystemstore_tests	Newline at the end of files	2019-08-01 08:44:58 +02:00
general_tests_phase_1	Newline at the end of files	2019-08-01 08:44:58 +02:00
general_tests_phase_2	Newline at the end of files	2019-08-01 08:44:58 +02:00
securestore_whitebox	Newline at the end of files	2019-08-01 08:44:58 +02:00
static_tests	Fix kvstore-static_tests failing with OOM	2019-08-15 17:53:31 +08:00
tdbstore_whitebox	Remove kvstore's mbed_lib.json file (not relevant any more)	2019-01-09 16:25:13 +02:00