Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it work on MacOS - Apple Silicon #15

Open
mc-cat-tty opened this issue Apr 12, 2024 · 4 comments
Open

Make it work on MacOS - Apple Silicon #15

mc-cat-tty opened this issue Apr 12, 2024 · 4 comments

Comments

@mc-cat-tty
Copy link

No description provided.

mc-cat-tty added a commit to mc-cat-tty/tricore-probe that referenced this issue Apr 12, 2024
mc-cat-tty added a commit to mc-cat-tty/tricore-probe that referenced this issue Apr 14, 2024
mc-cat-tty added a commit to mc-cat-tty/tricore-probe that referenced this issue Apr 14, 2024
mc-cat-tty added a commit to mc-cat-tty/tricore-probe that referenced this issue Apr 15, 2024
@arctic-alpaca
Copy link
Member

Hi @mc-cat-tty,

I cannot reproduce the issue. Could you provide some more information like your system configuration, error messages you are seeing, etc?

mc-cat-tty added a commit to mc-cat-tty/tricore-probe that referenced this issue Apr 17, 2024
@mc-cat-tty
Copy link
Author

mc-cat-tty commented Apr 17, 2024

Sure! I should also edit the title, since it is no longer self-explanatory.

The issue arose while building the Xwin container on M1 OS X. However, I later realized that the issue concerned the arm64 platform and didn't impact builds on Linux/x86_64 platforms - as you said, on the right platform, everything works fine.

I am now wondering if tricore-probe might work on MacOS/arm64. As of now, I have been able to build artifacts on Xwin and run flash-tricore container, building them with ... buildx --platform linux/amd64 ....

I am now tinkering with the build of tricore-probe.
RUSTFLAGS="-C link-args=-L/opt/homebrew/Cellar/libusb-compat/0.1.8/lib -lusb" cargo build --no-default-features --features "docker" makes compilation exit successfully, but trying to run it leads to a crash:

./target/debug/tricore-probe ~/.../Blinky_LED_1_KIT_TC397_TFT/build/Blinky --no-flash --list-devices
[...]
thread '<unnamed>' panicked at tricore-docker/win-ftd2xx-dll/src/exports.rs:16:1:
Patched DLL function "_FT_CreateDeviceInfoList" aborted: Error processing response to command

Caused by:
    Io(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
wine: Unhandled page fault on read access to FFFFFFFFFFFFFFFF at address 0000000140030F85 (thread 00e8), starting debugger...

If you have any suggestion, let me know.

@daniel-veecle
Copy link
Member

daniel-veecle commented Apr 18, 2024

As a fellow Mac user I feel your pain :)

I will investigate and let you know. What I fear is that certain dependencies (MEMTOOL, DAS or the compiler) will simply refuse to run on a Mac, docker or not (at least this is what I experienced ~1 year ago)...

I will let you know!

EDIT: By Mac I mean aarch64

@mc-cat-tty mc-cat-tty changed the title Xwin container doesn't build Make it work on MacOS - Apple Silicon Apr 18, 2024
@mc-cat-tty
Copy link
Author

Thanks @daniel-veecle!

I will also keep you up to date with my work, if I make any progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants