ARMmbed / mbed-os-example-mbed-crypto

Mbed Crypto example for Mbed OS 5
Apache License 2.0
5 stars 19 forks source link

[Mbed-OS 5.11 OoB] can't deploy the example in windows #8

Open soleilplanet opened 5 years ago

soleilplanet commented 5 years ago

Description

Failed to deploy the example in Windows. Mbed-CLI version : 1.83

Steps:

  1. git clone -b mbed-os-5.11.0-oob git@github.com:ARMmbed/mbed-os-example-mbed-crypto.git
  2. cd mbed-os-example-mbed-crypto
  3. mbed deploy mbed-crypto-log.txt

Reproduced also with:

  1. mbed import git@github.com:ARMmbed/mbed-os-example-mbed-crypto.git -> this deployment succeeded
  2. cd mbed-os-example-mbed-crypto
  3. mbed update mbed-os-5.11.0-oob
  4. mbed deploy

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug
cmonr commented 5 years ago

@soleilplanet Could you rerun the commands, adding -vv to the deploy command?

I attempted to reproduce your commands, but no error was encountered.

It might also be worth posting your Python version (python --version) and list of modules in use (pip list)

toyowata commented 5 years ago

I also got same problem with latest code.

PS D:\work> mbed import https://github.com/ARMmbed/mbed-os-example-mbed-crypto
[mbed] Working path "D:\work" (directory)
[mbed] Importing program "mbed-os-example-mbed-crypto" from "https://github.com/ARMmbed/mbed-os-example-mbed-crypto" at latest revision in the current branch
[mbed] Adding library "mbed-crypto\mbed-os" from "https://github.com/ARMmbed/mbed-os" at latest revision in the current branch
[mbed] WARNING: Cannot find the mbed tools directory in "D:\work\mbed-os-example-mbed-crypto"
---
PS D:\work> cd .\mbed-os-example-mbed-crypto\
PS D:\work\mbed-os-example-mbed-crypto> mbed ls
[mbed] Working path "D:\work\mbed-os-example-mbed-crypto" (program)
mbed-os-example-mbed-crypto (#825b3dc3371d)
`- mbed-crypto\mbed-os (#2f136b977f49)
PS D:\work\mbed-os-example-mbed-crypto> mbed compile -m k64f -t gcc_arm
[mbed] Working path "D:\work\mbed-os-example-mbed-crypto" (program)
[mbed] ERROR: The mbed tools were not found in "D:\work\mbed-os-example-mbed-crypto".
       You can run "mbed deploy" to install dependencies and tools.
---

However, I can build the example by following steps:

PS D:\work> git clone https://github.com/ARMmbed/mbed-os-example-mbed-crypto
Cloning into 'mbed-os-example-mbed-crypto'...
remote: Enumerating objects: 44, done.
remote: Counting objects: 100% (44/44), done.
remote: Compressing objects: 100% (37/37), done.
Receiving objects:  99% (209/211)    25 (delta 7), pack-reused 167 eceiving objects:  96% (203/211)
Receiving objects: 100% (211/211), 59.79 KiB | 126.00 KiB/s, done.
Resolving deltas: 100% (68/68), done.
PS D:\work> cd .\mbed-os-example-mbed-crypto\mbed-crypto\
PS D:\work\mbed-os-example-mbed-crypto\mbed-crypto> mbed deploy
[mbed] Working path "D:\work\mbed-os-example-mbed-crypto\mbed-crypto" (program)
[mbed] Adding library "mbed-os" from "https://github.com/ARMmbed/mbed-os" at latest revision in the current branch
[mbed] WARNING: Cannot find the mbed tools directory in "D:\work\mbed-os-example-mbed-crypto"
---
PS D:\work\mbed-os-example-mbed-crypto\mbed-crypto> mbed compile -m k64f -t gcc_arm
[mbed] Working path "D:\work\mbed-os-example-mbed-crypto\mbed-crypto" (program)
[mbed] WARNING: Could not find mbed program in current path "D:\work\mbed-os-example-mbed-crypto\mbed-crypto".
       You can fix this by calling "mbed new ." in the root of your program.
---
Building project mbed-crypto (K64F, GCC_ARM)
Scan: mbed-crypto
Compile [  0.1%]: mbed_tz_context.c
Compile [  0.2%]: MCR20Drv.c
Compile [  0.3%]: rf_configuration.c
Compile [  0.5%]: psa_initial_attestation_api.c
Compile [  0.6%]: attest_boot_status_loader.c
Compile [  0.7%]: psa_attest_inject_key.c
Compile [  0.8%]: main.cpp
Compile [  0.9%]: attest_crypto.c
Compile [  1.0%]: attestation_bootloader_data.c
Compile [  1.2%]: psa_attestation_stubs.c
Compile [  1.3%]: attest_crypto_keys.c
Compile [  1.4%]: attest_iat_claims_loader.c

The Mbed-CLI version is 1.10.0.

ciarmcom commented 4 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2109