Pr/cy mbed os 5.12.0 #9908

morser499 · 2019-03-01T23:14:48Z

Description

Added CM0+ targets for some Cypress boards
Initial support for Cypress PSA targets
Added flash iap component to Cypress psoc6 m4
Fixed type of STDIO UART initialization variable.
Updated Wiced connectivity libraries to support lower power modes

Pull request type

[ ] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

morser499 · 2019-03-01T23:17:53Z

We believe there is a problem with the following test suite:
Test Suite: features-storage-tests-kvstore-direct_access_devicekey_test
Test: test_direct_access_to_devicekey_tdb_last_two_sectors

Explaination of bug in TDBStore.cpp TDBStore::init():
_master_record_offset is at least 1 sector offset.
_master_record_size takes up at least 2 flash sectors.

When check_erase_before_write occurs, it erases 2 sectors offset by 1 sector.
Hence this code requires at least 3 sectors.
This code attempts to erase beyond the end of flash and causes a hard fault.

cmonr · 2019-03-01T23:25:51Z

@ARMmbed/mbed-os-storage Please review the above test comment (#9908 (comment))

cmonr · 2019-03-01T23:28:51Z

@morser499 Do y'all have local test runs for the new targets against the three compilers?

cmonr · 2019-03-01T23:29:30Z

TESTS/mbed_hal/spm/main.cpp

@@ -23,8 +23,8 @@
 #error [NOT_SUPPORTED] this test is supported on GCC only
 #endif

-#if defined(TARGET_FUTURE_SEQUANA_PSA)
-#error [NOT_SUPPORTED] Disable this Test until FUTURE_SEQUANA_PSA enables Memory protection
+#if defined(TARGET_FUTURE_SEQUANA_PSA) || defined(TARGET_CY8CKIT_062_WIFI_BT_PSA)


Not yet. Our tests are still running

Enable this test please
Your platform has memory separation enabled

0xc0170 · 2019-03-02T05:15:21Z

features/FEATURE_BLE/targets/TARGET_Cypress/TARGET_CYW43XXX/CyH4TransportDriver.cpp

@@ -0,0 +1,123 @@
+/* mbed Microcontroller Library
+ * Copyright (c) 2017-2017 ARM Limited
+ *


SPDX identifier for new files please

Done.
Fixes to PinNamesTypes.h and PortNames.h files from TARGET_Cypress\TARGET_PSOC6 will be merged to the PR on Monday.

SenRamakri · 2019-03-02T05:21:28Z

targets/targets.json

@@ -7965,12 +8019,21 @@
            "network-default-interface-type": "WIFI"
        }
    },
+    "CYW943012P6EVB_01_M0": {
+        "inherits": ["MCU_PSOC6_M0"],
+        "supported_toolchains": ["GCC_ARM", "ARM", "IAR"],


No need to specify supported_toolchains here as the parent MCU_PSOC6 already defines the same toolchain set as here.

Now that we have switched to ARMC6, these entries for supported_toolchains must change.
Cypress targets ares still using ARM compiler 5, and should change all "ARM" entries to "ARMC5" in supported_toolchains. Please make this change for all Cypress targets.

SenRamakri · 2019-03-02T05:21:40Z

targets/targets.json

+        "post_binary_hook": {
+            "function": "PSOC6Code.complete"
+        }
+    },
    "CYW943012P6EVB_01": {
        "inherits": ["MCU_PSOC6_M4"],
        "features": ["BLE"],
        "supported_toolchains": ["GCC_ARM", "ARM", "IAR"],


No need to specify supported_toolchains here as the parent MCU_PSOC6 already defines the same toolchain set as here.

davidsaada · 2019-03-02T06:46:02Z

We believe there is a problem with the following test suite:
Test Suite: features-storage-tests-kvstore-direct_access_devicekey_test
Test: test_direct_access_to_devicekey_tdb_last_two_sectors

Explaination of bug in TDBStore.cpp TDBStore::init():
_master_record_offset is at least 1 sector offset.
_master_record_size takes up at least 2 flash sectors.

When check_erase_before_write occurs, it erases 2 sectors offset by 1 sector.
Hence this code requires at least 3 sectors.
This code attempts to erase beyond the end of flash and causes a hard fault.

Can you tell the sector size, page size and the size of the internal flash?

orenc17 · 2019-03-02T12:42:18Z

targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CY8CKIT_062_WIFI_BT_PSA/prebuilt/README.md

@@ -0,0 +1,23 @@
+


Make this relevant to your target please

orenc17 · 2019-03-02T12:43:13Z

targets/TARGET_Cypress/TARGET_PSOC6/TARGET_CY8CKIT_062_WIFI_BT_PSA/prebuilt/export_binaries.py

@@ -0,0 +1,36 @@
+# Copyright (c) 2017-2018 ARM Limited


Not needed anymore, targets.json defines a delivery_dir

The file removed

0xc0170 · 2019-03-02T15:42:11Z

Please also attach test results for all 3 toolchains (as this is new target addition)

morser499 · 2019-03-02T16:35:01Z

We are observing a compilation failure with COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.c under IAR. Other toolchains work fine.

Compile: C:/Program Files (x86)/IAR Systems/Embedded Workbench 8.0/arm\bin\iccarm --no_wrap_diagnostics -e --diag_suppress=Pa050,Pa084,Pa093,Pa082 -Oh --enable_restrict -DMBED_TRAP_ERRORS_ENABLED=1 --cpu Cortex-M0+ --thumb --dlib_config DLib_Config_Full.h --vla --diag_suppress=Pe546 -DTARGET_CY8CKIT_062_WIFI_BT_M0 -DTARGET_PSA -DMBEDTLS_PSA_CRYPTO_SPM -DTARGET_PSA_Target -D__MBED__=1 -DTARGET_LIKE_MBED -DDEVICE_PORTINOUT=1 -D__MBED_CMSIS_RTOS_CM -DTARGET_NAME=CY8CKIT_062_WIFI_BT_M0_PSA -DCOMPONENT_FLASHIAP=1 -DDEVICE_RTC=1 -DDEVICE_SERIAL_ASYNCH=1 -D__CMSIS_RTOS -DMBED_MPU_CUSTOM -DCY8C6247BZI_D54 -DTARGET_SPE_Target -DDEVICE_USTICKER=1 -DDEVICE_I2C=1 -DDEVICE_CRC=1 -DTARGET_CORTEX_M -DTARGET_M0P -DDEVICE_ANALOGOUT=1 -DTARGET_PSOC6 -DMBEDTLS_ENTROPY_NV_SEED -DMBED_BUILD_TIMESTAMP=1551454731.09 -DMCU_PSOC6_M0 -DDEVICE_LPTICKER=1 -DTOOLCHAIN_IAR -DPSOC6_DYNSRM_DISABLE=1 -DCOMPONENT_SPE=1 -DMBED_TICKLESS -DDEVICE_INTERRUPTIN=1 -DTARGET_MCU_PSOC6_M0 -DCOMPONENT_PSA_SRV_IMPL=1 -DTARGET_CORTEX -DTARGET_CY8CKIT_062_WIFI_BT_M0_PSA -DDEVICE_PORTOUT=1 -D__CORTEX_M0PLUS -DDEVICE_STDIO_MESSAGES=1 -DDEVICE_PWMOUT=1 -DDEVICE_SPI_ASYNCH=1 -DTARGET_CY8C62XX -DTARGET_FF_ARDUINO -DTARGET_RELEASE -DCY_IPC_DEFAULT_CFG_DISABLE -DDEVICE_SERIAL_FC=1 -DTARGET_CY8CKIT_062_WIFI_BT -DMBEDTLS_PSA_CRYPTO_C -DDEVICE_TRNG=1 -DARM_MATH_CM0PLUS -DDEVICE_PORTIN=1 -DDEVICE_SLEEP=1 -DTARGET_MCU_PSOC6 -DCOMPONENT_PSA_SRV_IPC=1 -DDEVICE_SPI=1 -DTARGET_MBED_SPM -DTARGET_Cypress -DDEVICE_ANALOGIN=1 -DDEVICE_SERIAL=1 -DDEVICE_FLASH=1 -DDEVICE_I2C_ASYNCH=1 -DCOMPONENT_SPM_MAILBOX=1 -DTARGET_LIKE_CORTEX_M0 -f .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR.includes_70d6569d1107ac5e98f019d4cdd3dc01.txt --preinclude=.\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\mbed_config.h --dependencies BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.d -l BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.s.txt -o BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.o .\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.c
[DEBUG] Return: 0
[DEBUG] Output: Warning[Ms014]: some characters could not be correctly encoded in "C:\Users\ohks\Projects\mbed-os\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.s.txt", and have been replaced with '@'. The first such character has unicode code point 0x20ac ("€")
'ascii' codec can't decode byte 0xe2 in position 343: ordinal not in range(128)
Failed to build library
Memory map breakdown for built projects (values in Bytes):

name	target	toolchain	static_ram	total_flash
Traceback (most recent call last):
File "C:\Users\ohks\Projects\mbed-os\tools\test.py", line 296, in

status = print_report_exporter.report(build_report)

File "C:\Users\ohks\Projects\mbed-os\tools\test_exporters.py", line 92, in report
return self.exporter_print(test_summary_ext, print_log_for_failures=print_log_for_failures)
File "C:\Users\ohks\Projects\mbed-os\tools\test_exporters.py", line 345, in exporter_print
raise Exception("'test_run' did not have a 'result' value")
Exception: 'test_run' did not have a 'result' value
[ERROR] 'test_run' did not have a 'result' value
[mbed] Working path "C:\Users\ohks\Projects\mbed-os" (program)
[mbed] Exec "C:\Python27\python.exe -u C:\Users\ohks\Projects\mbed-os\tools\test.py -t IAR -m CY8CKIT_062_WIFI_BT_M0_PSA --source . --build .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR --test-spec .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\test_spec.json --build-data .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\build_data.json -n psa- -v --greentea" in "C:\Users\ohks\Projects\mbed-os"

morser499 · 2019-03-02T16:40:31Z

We believe there is a problem with the following test suite:
Test Suite: features-storage-tests-kvstore-direct_access_devicekey_test
Test: test_direct_access_to_devicekey_tdb_last_two_sectors
Explaination of bug in TDBStore.cpp TDBStore::init():
_master_record_offset is at least 1 sector offset.
_master_record_size takes up at least 2 flash sectors.
When check_erase_before_write occurs, it erases 2 sectors offset by 1 sector.
Hence this code requires at least 3 sectors.
This code attempts to erase beyond the end of flash and causes a hard fault.

Can you tell the sector size, page size and the size of the internal flash?

Flash Size = 1M
Sector Size = 512b
Page Size = 512b

0xc0170 · 2019-03-03T05:32:45Z

We are observing a compilation failure with COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.c under IAR. Other toolchains work fine.

@mikisch81 @orenc17 Please review

mikisch81 · 2019-03-03T08:55:40Z

We are observing a compilation failure with COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.c under IAR. Other toolchains work fine.

Compile: C:/Program Files (x86)/IAR Systems/Embedded Workbench 8.0/arm\bin\iccarm --no_wrap_diagnostics -e --diag_suppress=Pa050,Pa084,Pa093,Pa082 -Oh --enable_restrict -DMBED_TRAP_ERRORS_ENABLED=1 --cpu Cortex-M0+ --thumb --dlib_config DLib_Config_Full.h --vla --diag_suppress=Pe546 -DTARGET_CY8CKIT_062_WIFI_BT_M0 -DTARGET_PSA -DMBEDTLS_PSA_CRYPTO_SPM -DTARGET_PSA_Target -D__MBED__=1 -DTARGET_LIKE_MBED -DDEVICE_PORTINOUT=1 -D__MBED_CMSIS_RTOS_CM -DTARGET_NAME=CY8CKIT_062_WIFI_BT_M0_PSA -DCOMPONENT_FLASHIAP=1 -DDEVICE_RTC=1 -DDEVICE_SERIAL_ASYNCH=1 -D__CMSIS_RTOS -DMBED_MPU_CUSTOM -DCY8C6247BZI_D54 -DTARGET_SPE_Target -DDEVICE_USTICKER=1 -DDEVICE_I2C=1 -DDEVICE_CRC=1 -DTARGET_CORTEX_M -DTARGET_M0P -DDEVICE_ANALOGOUT=1 -DTARGET_PSOC6 -DMBEDTLS_ENTROPY_NV_SEED -DMBED_BUILD_TIMESTAMP=1551454731.09 -DMCU_PSOC6_M0 -DDEVICE_LPTICKER=1 -DTOOLCHAIN_IAR -DPSOC6_DYNSRM_DISABLE=1 -DCOMPONENT_SPE=1 -DMBED_TICKLESS -DDEVICE_INTERRUPTIN=1 -DTARGET_MCU_PSOC6_M0 -DCOMPONENT_PSA_SRV_IMPL=1 -DTARGET_CORTEX -DTARGET_CY8CKIT_062_WIFI_BT_M0_PSA -DDEVICE_PORTOUT=1 -D__CORTEX_M0PLUS -DDEVICE_STDIO_MESSAGES=1 -DDEVICE_PWMOUT=1 -DDEVICE_SPI_ASYNCH=1 -DTARGET_CY8C62XX -DTARGET_FF_ARDUINO -DTARGET_RELEASE -DCY_IPC_DEFAULT_CFG_DISABLE -DDEVICE_SERIAL_FC=1 -DTARGET_CY8CKIT_062_WIFI_BT -DMBEDTLS_PSA_CRYPTO_C -DDEVICE_TRNG=1 -DARM_MATH_CM0PLUS -DDEVICE_PORTIN=1 -DDEVICE_SLEEP=1 -DTARGET_MCU_PSOC6 -DCOMPONENT_PSA_SRV_IPC=1 -DDEVICE_SPI=1 -DTARGET_MBED_SPM -DTARGET_Cypress -DDEVICE_ANALOGIN=1 -DDEVICE_SERIAL=1 -DDEVICE_FLASH=1 -DDEVICE_I2C_ASYNCH=1 -DCOMPONENT_SPM_MAILBOX=1 -DTARGET_LIKE_CORTEX_M0 -f .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR.includes_70d6569d1107ac5e98f019d4cdd3dc01.txt --preinclude=.\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\mbed_config.h --dependencies BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.d -l BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.s.txt -o BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.o .\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.c
[DEBUG] Return: 0
[DEBUG] Output: Warning[Ms014]: some characters could not be correctly encoded in "C:\Users\ohks\Projects\mbed-os\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\components\TARGET_PSA\services\attestation\COMPONENT_PSA_SRV_IMPL\tfm_impl\attest_token.s.txt", and have been replaced with '@'. The first such character has unicode code point 0x20ac ("€")
'ascii' codec can't decode byte 0xe2 in position 343: ordinal not in range(128)
Failed to build library
Memory map breakdown for built projects (values in Bytes):

name target toolchain static_ram total_flash

Traceback (most recent call last):

File "C:\Users\ohks\Projects\mbed-os\tools\test.py", line 296, in

status = print_report_exporter.report(build_report)

File "C:\Users\ohks\Projects\mbed-os\tools\test_exporters.py", line 92, in report

return self.exporter_print(test_summary_ext, print_log_for_failures=print_log_for_failures)

File "C:\Users\ohks\Projects\mbed-os\tools\test_exporters.py", line 345, in exporter_print

raise Exception("'test_run' did not have a 'result' value")

Exception: 'test_run' did not have a 'result' value

[ERROR] 'test_run' did not have a 'result' value

[mbed] Working path "C:\Users\ohks\Projects\mbed-os" (program)

[mbed] Exec "C:\Python27\python.exe -u C:\Users\ohks\Projects\mbed-os\tools\test.py -t IAR -m CY8CKIT_062_WIFI_BT_M0_PSA --source . --build .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR --test-spec .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\test_spec.json --build-data .\BUILD\tests\CY8CKIT_062_WIFI_BT_M0_PSA\IAR\build_data.json -n psa- -v --greentea" in "C:\Users\ohks\Projects\mbed-os"

@moranpeker

davidsaada · 2019-03-03T09:42:42Z

We believe there is a problem with the following test suite:
Test Suite: features-storage-tests-kvstore-direct_access_devicekey_test
Test: test_direct_access_to_devicekey_tdb_last_two_sectors
Explaination of bug in TDBStore.cpp TDBStore::init():
_master_record_offset is at least 1 sector offset.
_master_record_size takes up at least 2 flash sectors.
When check_erase_before_write occurs, it erases 2 sectors offset by 1 sector.
Hence this code requires at least 3 sectors.
This code attempts to erase beyond the end of flash and causes a hard fault.

Can you tell the sector size, page size and the size of the internal flash?

Flash Size = 1M
Sector Size = 512b
Page Size = 512b

Thank you. In this case (page size equal to sector size), it's a known problem in that test, which we plan to have a PR fixing it today or tomorrow.

yossi2le · 2019-03-03T12:15:04Z

I am trying to compile the mbed-os bootloader for the CY8CKIT_062_WIFI_BT and CY8CKIT_062_BLE boards and currently I found out that the following code at gpio_init is calling RTOS:

`
/* Ignore pin reservation result because there is not possibility to release
* reserved HW resource. The MBED does not provide proper destructors for
* doing that.
*/

if (!(IsIrqMode() || IsIrqMasked())) {
    (void) cy_reserve_io_pin(pin);
}

`

Is there any possibility to overcome this issue? Cause compiling RTOS will have a significant impact on code size.

morser499 · 2019-03-07T18:14:22Z

just to make sure we are aligned please follow these steps:

1. rebase on latest master & cherry pick #9978

2. run `tools/psa/release.py -m <YOUR-M0-CORE-PSA-TARGET>`

3. commit the new secure binaires

4. supply test result for the following filter *psa*,*mbed-crypto*,*spm*

The changes have been made and added to the PR. We are in the process of running the updated tests and will post them as soon as they finish.

mikisch81 · 2019-03-07T22:51:28Z

@morser499 any updates wrt PSA test results?

mikisch81 · 2019-03-07T22:51:52Z

@cmonr can it go to CI?

morser499 · 2019-03-07T23:03:29Z

I have results for IAR; the other toolchains are still running

CY8CKIT_062_WIFI_BT__PSA__IAR.txt

volodymyrbotsian · 2019-03-07T23:04:02Z

Results for psa,mbed-crypto,spm on IAR
CY8CKIT_062_WIFI_BT_PSA__PSA__IAR.log

orenc17 · 2019-03-07T23:14:22Z

@volodymyrbotsian could you try running the failed test again? seems like a flashing issue
components-target_psa-tests-compliance_crypto-test_c035

volodymyrbotsian · 2019-03-07T23:15:53Z

@orenc17 sure, I'll rerun

volodymyrbotsian · 2019-03-07T23:23:36Z

Results for psa,mbed-crypto,spm on ARM
CY8CKIT_062_WIFI_BT_PSA__PSA__ARM.log

morser499 · 2019-03-08T00:50:46Z

Attached are the log files for all 3 runs. NOTE: This includes the re-run IAR test which is still showing the same timeout failure.

CY8CKIT_062_WIFI_BT_PSA__PSA__ARM.log
CY8CKIT_062_WIFI_BT_PSA__PSA__GCC_ARM.log
CY8CKIT_062_WIFI_BT_PSA__PSA__IAR.log

cmonr · 2019-03-08T05:42:10Z

@cmonr can it go to CI?

Will start CI to see where this is at whilst the last test is sorted out.

cmonr · 2019-03-08T06:48:31Z

CI started

mbed-ci · 2019-03-08T08:36:20Z

Test run: SUCCESS

Summary: 13 of 13 test jobs passed
Build number : 3
Build artifacts

0xc0170 · 2019-03-08T09:04:32Z

Waiting for approvals

0xc0170 · 2019-03-08T09:42:16Z

Attached are the log files for all 3 runs. NOTE: This includes the re-run IAR test which is still showing the same timeout failure.

@orenc17 @mikisch81 I marked this as ready for merge but would like to know what are these timeouts in the tests. Would these block this PRs - suggestions?

mikisch81 · 2019-03-08T09:49:20Z

Attached are the log files for all 3 runs. NOTE: This includes the re-run IAR test which is still showing the same timeout failure.

@orenc17 @mikisch81 I marked this as ready for merge but would like to know what are these timeouts in the tests. Would these block this PRs - suggestions?

@alzix
There is 1 test timeout only in IAR and may be related to small timeout value, as all the PSA teams not in office today we can't do manual checks.
I suggest not to block.

0xc0170 · 2019-03-08T10:00:18Z

It can be addressed on Sunday, would be good to create a tracking issue.

Ready for integration now

mikisch81 · 2019-03-08T10:02:48Z

It can be addressed on Sunday, would be good to create a tracking issue.

Ready for integration now

Thanks!

Can you open a jira ticket for us? (Not near PC right now)

0xc0170 · 2019-03-08T10:23:24Z

Done, #10007

cmonr requested review from a team March 1, 2019 23:26

cmonr added the needs: review label Mar 1, 2019

cmonr added the release-version: 5.12.0-rc1 label Mar 1, 2019

cmonr reviewed Mar 1, 2019

View reviewed changes

cmonr requested a review from a team March 1, 2019 23:31

SenRamakri mentioned this pull request Mar 2, 2019

ARM Toolchain update to ARM Compiler 6.11(ARMC6) #9888

Merged

0xc0170 requested changes Mar 2, 2019

View reviewed changes

SenRamakri reviewed Mar 2, 2019

View reviewed changes

orenc17 suggested changes Mar 2, 2019

View reviewed changes

0xc0170 added needs: work scope: new-target and removed needs: review labels Mar 2, 2019

morser499 force-pushed the pr/cy-mbed-os-5.12.0 branch from cde08a9 to 5741434 Compare March 2, 2019 15:51

morser499 force-pushed the pr/cy-mbed-os-5.12.0 branch from 5741434 to f8720a3 Compare March 3, 2019 06:29

This was referenced Mar 3, 2019

Fix bug in crypto_acl test #9913

Merged

Skip test on Cortex M33 devices #9916

Merged

mbed-SPM updates #9823

Merged

Rebuild PSoC6 secure binaries

4c1ff13

morser499 force-pushed the pr/cy-mbed-os-5.12.0 branch from 5c12c3c to 4c1ff13 Compare March 7, 2019 18:13

0xc0170 added needs: review and removed needs: work labels Mar 8, 2019

mikisch81 approved these changes Mar 8, 2019

View reviewed changes

0xc0170 approved these changes Mar 8, 2019

View reviewed changes

0xc0170 added ready for merge and removed needs: review labels Mar 8, 2019

0xc0170 merged commit 820a2e2 into ARMmbed:master Mar 8, 2019

0xc0170 removed the ready for merge label Mar 8, 2019

morser499 deleted the pr/cy-mbed-os-5.12.0 branch March 12, 2019 18:31

orenc17 mentioned this pull request Mar 14, 2019

osDelay gets stuck on FUTURE_SEQUANA_M0_PSA in spm tests #9726

Closed

Pr/cy mbed os 5.12.0 #9908

Pr/cy mbed os 5.12.0 #9908

Uh oh!

Conversation

morser499 commented Mar 1, 2019

Description

Pull request type

Uh oh!

morser499 commented Mar 1, 2019

Uh oh!

cmonr commented Mar 1, 2019

Uh oh!

cmonr commented Mar 1, 2019

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

davidsaada commented Mar 2, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xc0170 commented Mar 2, 2019

Uh oh!

morser499 commented Mar 2, 2019

Uh oh!

morser499 commented Mar 2, 2019

Uh oh!

0xc0170 commented Mar 3, 2019

Uh oh!

mikisch81 commented Mar 3, 2019

Uh oh!

davidsaada commented Mar 3, 2019

Uh oh!

yossi2le commented Mar 3, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

morser499 commented Mar 7, 2019

Uh oh!

mikisch81 commented Mar 7, 2019

Uh oh!

mikisch81 commented Mar 7, 2019

Uh oh!

morser499 commented Mar 7, 2019

Uh oh!

volodymyrbotsian commented Mar 7, 2019

Uh oh!

orenc17 commented Mar 7, 2019

Uh oh!

volodymyrbotsian commented Mar 7, 2019

Uh oh!

volodymyrbotsian commented Mar 7, 2019

Uh oh!

morser499 commented Mar 8, 2019

Uh oh!

davidsaada commented Mar 2, 2019 •

edited

Loading

yossi2le commented Mar 3, 2019 •

edited

Loading