-
Notifications
You must be signed in to change notification settings - Fork 84
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
osx-arm64 support #915
Comments
Hi @spalani7, we're in the process of releasing ARM64 OpenOCD binaries for MacOS. Previously, we've relied on Rosetta (see setup instructions here) to run our OpenOCD binaries, but we received some reports last week that the procedure has changed on the latest MacOS. Now we have the hardware and signing process setup for ARM64. Here are the binaries that we'll be releasing in the next week or so. If you wouldn't mind testing them for us and reporting any issues here we'd greatly appreciate it. (removed - available from the installer now) |
Thanks @Jake-Carter - I totally missed those instructions on the userguide. Glad that I created this ticket anyways. Happy to test the above openocd and report if there are issues! |
I can report that the above OpenOCD is working for me - feel free to close this once you have pushed a fix for this. |
@Jake-Carter Thank you for working on this. I tried installing the binaries above using the README instructions in the zip I'm receiving the same error as before installing the binaries: `Creating /Users/tot/MaximSDK/Examples/MAX32690/Hello_World/build/max32690.hex Warn : Flash driver of max32xxx.flash does not support free_driver_priv() |
@EricB-ADI can you test a macOS OpenOCD flash for the MAX32690 against the error above? |
@Jake-Carter yes, I will. @EdwinFairchild were you having a similar error on your laptop? |
for me it was on ME17 I could never get it to succeed flashing |
@EricB-ADI & @Jake-Carter But when the EVKit is connected and powered on, I receive the error posted above after ~10 seconds of terminal trying. |
@tyVandeZande Can you attach your current "DETAILS.TXT" (should be in the DAPLINK drive)? Potentially related to #883 Try updating your PICO firmware if you haven't already (see here) |
@Jake-Carter Pre-update TETAILS.txt: DAPLink Firmware - see https://mbed.com/daplinkUnique ID: 04091702d5aa035200000000000000000000000097969906 |
I just updated the PICO. Same error. I'm not missing something simple, like putting the EVKit into a programming mode, correct? Updated Details.txt: DAPLink Firmware - see https://daplink.ioBuild ID: v0257-52-gb85b53df (armcc, local mods) |
@tyVandeZande Setting TARGET and BOARD correctly (see here) should be it with the default jumper settings. Can you run the following commands for me? This will print the version number. openocd --version This one will log extra debug info about the problem to an openocd -d -s $MAXIM_PATH/Tools/OpenOCD/scripts -f interface/cmsis-dap.cfg -f target/max32690.cfg -c "init; reset halt" > openocd_debug_log.log 2>&1 |
@Jake-Carter openOCD version 0.12.0 TARGET & BOARD are set correctly. Here is the log:
|
@tyVandeZande looks like your
The .zip file I provided earlier puts the binary at ln -s $MAXIM_PATH/Tools/OpenOCD/bin/openocd $MAXIM_PATH/Tools/OpenOCD/openocd Then the command-line setup instructions should work for configuring the PATH correctly to load our openocd first. Afterwards, your |
I tried this initially, and when I added this link, it returned the result Is there a step-by-step video somewhere to follow? I tried removing and re-installing the MaximSDK (and all links/ profile entries) from the very beginning, using the automatic installer. Now, when I try to run Thanks! |
I will respond more fully soon, but I cannot see any substantial differences between your screenshots and my file structure. There may be permission issues adding to the complications— When I used the .dmg automatic installer, I was required to "Open Anyway" from system preferences, twice. When I ran I'm working through the command line. I will try a full reinstall on a fresh user profile and follow up. Thanks for all your help. |
Hi @Jake-Carter I ran into problems with the fresh install when I checked the validity of the tools. Here is the full terminal window:
Same error that started this thread. |
@Jake-Carter I just tried adding the binaries from above and adding the symlink and received the same @spalani7 Will you please let us know two pieces of info: Thank you! |
@Jake-Carter I upgraded my machine to Sonoma 14.3.1 with no success. Which macOS are you using?
|
At this point the only error you have is a missing search path for the libraries. (Duplicate of analogdevicesinc/VSCode-Maxim#21) It seems that Homebrew will install A reported workaround is to manually symlink Your latest errors could also be similar dependency issues (see https://stackoverflow.com/questions/1562071/how-can-i-find-which-elf-dependency-is-not-fulfilled) Sorry for all the trouble... This has the symptoms of the usual dependency hell that can sometimes happen on Linux/MacOS. What I usually do to troubleshoot this is use i.e. on Linux: ~/MaximSDK/Tools/OpenOCD/bin » ldd openocd
linux-vdso.so.1 (0x00007ffc1a9cb000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fb793586000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb793581000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb79357c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb792c00000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb7935da000) I'm mostly a linux user... We are limited in our MacOS hardware at the moment, so we're reliant on the community. When we find a resolution to your issue we will integrate it into our installer/documentation for MacOS users. |
my macos version is 13.4.1 and yes my file vault is ON. |
@Jake-Carter I do not see these issues on my system flashing MAX32690. That is all I have at home. |
@Jake-Carter !success! ....it just require the time to be 1:30 am for it to work. I will follow up soon. Of course it was a small misunderstanding on my part. thx |
Thanks @tyVandeZande, let me know what the issue was when you can |
Closing out - the updated MacOS binaries have been released as of https://github.com/analogdevicesinc/msdk/releases/tag/v2024_02 |
Thanks |
Currently I'm facing some issues trying to run a hello-world example for MAXIM 32672 EV Kit.
I initially faced issue #913 - solved it by fixing the board make file. Now that the build is passing - I tried to flash the output which resulted in OpenOCD complaining about not finding the right libraries.
Seems like that problem is OpenOCD is looking for libraries for x86_64 rather that native architecture (arm64).
The text was updated successfully, but these errors were encountered: