Using a RPi4 as the host

[TimHutchinson]

Hi,
Have you ever used a RPi4 as a host for a RiP3 as the target. In this case for me the makefile does not build the kernel. It just seems to silently fail.

Everything works fine for me if I use an X64 machine as the host.

Thanks

Regards
Tim.

[andre-richter]

Ha! That's an interesting use-case I never would have thought of 😎

Absolutely no output at all when doing make?

[TimHutchinson]

Hi, Thanks for the quick reply. Below is the output from running make on one of your tutorials. The copy towards the end fails because there is no kernel built for the make file to copy. The kernel.d file however is written out. I started out thinking the kernel was being built but put in some other place, but I now don't think that is so. As I said previously if I try this on my x64 Linux machine it all works fine. Regards Tim

…

------------------------------------------------------------------------ pi@raspberrypi:~/sources/rust-raspi3-OS-tutorials-master/02_runtime_init $ make rm -rf target RUSTFLAGS="-C link-arg=-Tsrc/bsp/rpi/link.ld -C target-cpu=cortex-a53 -D warnings -D missing_docs" cargo xrustc --target=aarch64-unknown-none-softfloat --features bsp_rpi3 --release Updating crates.io index Compiling core v0.0.0 (/home/pi/.rustup/toolchains/nightly-2019-12-20-armv7-unknown-linux-gnueabihf/lib/rustlib/src/rust/src/libcore) Compiling compiler_builtins v0.1.24 Compiling rustc-std-workspace-core v1.99.0 (/home/pi/.rustup/toolchains/nightly-2019-12-20-armv7-unknown-linux-gnueabihf/lib/rustlib/src/rust/src/tools/rustc-std-workspace-core) Compiling alloc v0.0.0 (/tmp/xargo.npQWs8qhTaHC) Finished release [optimized] target(s) in 1m 21s Compiling kernel v0.1.0 (/home/pi/sources/rust-raspi3-OS-tutorials-master/02_runtime_init) Finished release [optimized] target(s) in 0.73s cp target/aarch64-unknown-none-softfloat/release/kernel . cp: cannot stat 'target/aarch64-unknown-none-softfloat/release/kernel': No such file or directory make: *** [Makefile:60: kernel8.img] Error 1

On Thu, 16 Jan 2020 at 21:14, Andre Richter ***@***.***> wrote: Ha! That's an interesting use-case I never would have thought of 😎 Absolutely no output at all when doing make? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKGJUBHI34VZU4GYWLTQQ3Q6DE3BANCNFSM4KH2SUNA> .

[andre-richter]

Okay, so something is getting successfully compiled it seems. Maybe the name or path that the Makefile assumes differs.

Can you take a look into the target folder?

[TimHutchinson]

As requested here are the contents of the target directory pi@raspberrypi:~/sources/rust-raspi3-OS-tutorials-master/02_runtime_init/target $ ls -R .: aarch64-unknown-none-softfloat release ./aarch64-unknown-none-softfloat: release ./aarch64-unknown-none-softfloat/release: build deps examples incremental kernel.d ./aarch64-unknown-none-softfloat/release/build: ./aarch64-unknown-none-softfloat/release/deps: kernel-dee76b2943f6c6b2.d ./aarch64-unknown-none-softfloat/release/examples: ./aarch64-unknown-none-softfloat/release/incremental: ./release: build deps examples incremental ./release/build: ./release/deps: ./release/examples: ./release/incremental:

…

On Thu, 16 Jan 2020 at 23:24, Andre Richter ***@***.***> wrote: Okay, so something is getting successfully compiled it seems. Maybe the name or path that the Makefile assumes differs. Can you take a look into the target folder? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKGJUGFN4IZXF35DDSXHKTQ6DUCBANCNFSM4KH2SUNA> .

[andre-richter]

Hmm, strange... I don't have an explanation for that right now from the top of my head.

[TimHutchinson]

Me neither, but thanks for looking. I added the verbose flag to the xrustc command in the makefile but it didn't help. There is one thing I did different from your tutorial. I already had a Rust setup on my RPi4 so I just installed the nightly build and required components by hand and switched the cargo default toolchain. Maybe I missed something. I'll keep poking around. I have a spare SD card so I might go back and start again exactly following your curl script. (I did this on the x64 machine). I'll let you know if I find anything. BTW thank you for doing this project. Tim.

…

On Fri, 17 Jan 2020 at 08:36, Andre Richter ***@***.***> wrote: Hmm, strange... I don't have an explanation for that right now from the top of my head. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKGJUEHWXHDLXDRQCUJMJ3Q6FUYBANCNFSM4KH2SUNA> .

[andre-richter]

Hi Tim,

any updates on this? I think I would close this issue soon otherwise until further questions pop up.

Thanks,
Andre

[TimHutchinson]

Hi Andre, No joy I'm afraid. I tried various things including running everything as root in case it was some weird permissions problem. I even did a fresh install and exactly followed your instructions but still it would not build the kernel. Recently I installed a 64 bit version of Ubuntu on my Pi4 and tried to build your code there, but still the same problem it just silently fails. I think it might be an error in the linker as then maybe any error message is just getting thrown away by cargo. But that is just a guess I don't think I'm going to make any further progress.So will switch to using an x86 machine where it all seems to work ok. You can close the log. Thanks for your time. Regards Tim.

…

On Tue, 11 Feb 2020 at 08:09, Andre Richter ***@***.***> wrote: Hi Tim, any updates on this? I think I would close this issue soon otherwise until further questions pop up. Thanks, Andre — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKGJUF22FMXEKFEW2MRECTRCJMMTANCNFSM4KH2SUNA> .

[andre-richter]

Alright, thanks for the update and sorry that I currently lack bandwidth to dig into that myself.

Best,
Andre