probe-run

[tcpipchip]

Hi @daschl (Michael)

Can you identify why i am getting this error ?

I tried on PC and MINGW, same problem!

Thank you! See if you can help me!

[daschl]

@tcpipchip The reason why you are seeing this is because we are running in a "no std" environment, so there is no std library available for that target.

• did you modify any of the code in this repository?
• Which command are you running?

[daschl]

@tcpipchip actually I think I know what might be wrong: try running the cargo install command outside of the directory.

Since in this directory the default target is set to arm: https://github.com/daschl/nrf52840dk-sample/blob/main/.cargo/config.toml#L9 but you need to build the probe-rs for your host machine

[tcpipchip]

Hi, i can compile succesfully your GIT example!

But, i can get success to install the probe-run to flash the NRF52840 (i am using u-blox NINA B302)

And thanks to help me!

Here the command cargo install probe-run --git https://github.com/knurling-rs/probe-run.git --branch main -f --features defmt

[tcpipchip]

look

[tcpipchip]

You said!

"Since in this directory the default target is set to arm: https://github.com/daschl/nrf52840dk-sample/blob/main/.cargo/config.toml#L9 but you need to build the probe-rs for your host machine"

Do you remember how to back from ARM to x86 ?

[tcpipchip]

look again Michael

[daschl]

@tcpipchip what does rustup target list say?

[tcpipchip]

tcpipchip@tcpipchip-PC MINGW32 ~ $ rustup target list aarch64-apple-darwin aarch64-apple-ios aarch64-fuchsia aarch64-linux-android aarch64-pc-windows-msvc aarch64-unknown-linux-gnu aarch64-unknown-linux-musl aarch64-unknown-none aarch64-unknown-none-softfloat arm-linux-androideabi arm-unknown-linux-gnueabi arm-unknown-linux-gnueabihf arm-unknown-linux-musleabi arm-unknown-linux-musleabihf armebv7r-none-eabi armebv7r-none-eabihf armv5te-unknown-linux-gnueabi armv5te-unknown-linux-musleabi armv7-linux-androideabi armv7-unknown-linux-gnueabi armv7-unknown-linux-gnueabihf armv7-unknown-linux-musleabi armv7-unknown-linux-musleabihf armv7a-none-eabi armv7r-none-eabi armv7r-none-eabihf asmjs-unknown-emscripten i586-pc-windows-msvc i586-unknown-linux-gnu i586-unknown-linux-musl i686-linux-android i686-pc-windows-gnu i686-pc-windows-msvc i686-unknown-freebsd i686-unknown-linux-gnu i686-unknown-linux-musl mips-unknown-linux-gnu mips-unknown-linux-musl mips64-unknown-linux-gnuabi64 mips64-unknown-linux-muslabi64 mips64el-unknown-linux-gnuabi64 mips64el-unknown-linux-muslabi64 mipsel-unknown-linux-gnu mipsel-unknown-linux-musl nvptx64-nvidia-cuda powerpc-unknown-linux-gnu powerpc64-unknown-linux-gnu powerpc64le-unknown-linux-gnu riscv32i-unknown-none-elf riscv32imac-unknown-none-elf riscv32imc-unknown-none-elf riscv64gc-unknown-linux-gnu riscv64gc-unknown-none-elf riscv64imac-unknown-none-elf s390x-unknown-linux-gnu sparc64-unknown-linux-gnu sparcv9-sun-solaris thumbv6m-none-eabi thumbv7em-none-eabi thumbv7em-none-eabihf (installed) thumbv7m-none-eabi (installed) thumbv7neon-linux-androideabi thumbv7neon-unknown-linux-gnueabihf thumbv8m.base-none-eabi thumbv8m.main-none-eabi thumbv8m.main-none-eabihf wasm32-unknown-emscripten wasm32-unknown-unknown wasm32-wasi x86_64-apple-darwin x86_64-apple-ios x86_64-fortanix-unknown-sgx x86_64-fuchsia x86_64-linux-android x86_64-pc-windows-gnu x86_64-pc-windows-msvc (installed) x86_64-rumprun-netbsd x86_64-sun-solaris x86_64-unknown-freebsd x86_64-unknown-illumos x86_64-unknown-linux-gnu x86_64-unknown-linux-gnux32 x86_64-unknown-linux-musl x86_64-unknown-netbsd x86_64-unknown-redox

tcpipchip@tcpipchip-PC MINGW32 ~ $

[daschl]

Make sure it is properly installed rustup target install thumbv7em-none-eabihf

[tcpipchip]

yes, installed tcpipchip@tcpipchip-PC MINGW32 ~ $ rustup target install thumbv7em-none-eabihf info: component 'rust-std' for target 'thumbv7em-none-eabihf' is up to date

[daschl]

@tcpipchip I'm afraid I'm not sure why this is happening, I also do not own a windows machine to test. Maybe you can open a ticket with https://github.com/knurling-rs/probe-run/issues maybe someone there has got it working with windows?

[tcpipchip]

Hi Michael

I am now installing the VM LINUX to see whats happens :)

[tcpipchip]

my opinion is that a W7 problem

[daschl]

@tcpipchip on linux you should have a much better experience. I only use linux and mac os, so I'm sorry that I'm not of much help on windows :)

[tcpipchip]

no problem! You opened my mind! Thanks so much!

[tcpipchip]

btw, can you send a good link to make step by step to NR52 rust on linux...

Only if near you :)

[daschl]

I think my blog post that you've used should work for linux - but I really recommend this: https://embedded-trainings.ferrous-systems.com/

[tcpipchip]

good choice!

[tcpipchip]

i guess that in w10 will work too!