Get Started Faster! (A newer, simpler way to install the toolchain)

Getting Started
21

@Assaf Silly question: have you tried quitting and reopening terminal?
The path variable doesn’t update until you do so. That may be why oopsy can’t find the arm toolchain.

1 Like
22

What is strange is that brew is saying that gcc-arm-embedded is already installed, but then it can’t be found.

Can you try to run:
brew reinstall gcc-arm-embedded

and then afterwards try to invoke the command itself:
arm-none-eabi-gcc --version

This may at least confirm if the tool is installed or not.

There is also a related thread on github that some people have managed to resolve the progress on. Though as far as I know, others on the M1 mac (and BigSur) have been successful in getting it to work with the install.command.

Hope that’s helpful, let us know how it goes or if you need more assistance troubleshooting.

1 Like
23

Got it up and running thank you!
What fixed it for me was using git to clone - otherwise the install.sh of oopsy doesnt work - and the errors were not very obvious

24

Hey, took me time to answer but it did work! thanks for your help!

1 Like
26

Hey! Glad to hear it.

27

Hi All , cant get helper to run on windows in MINGW64. Any advice? i have installed it.

28

@Zifor depending on when/how you installed git-bash, python may have issues running within that terminal. Usually this results in a stalled terminal when you try to invoke python or a script that calls it.

There are a few things you can do:

  1. You could rerun the latest git-bash installer, during the optional settings there is a specific option for allowing virtual terminals (like python/node to run). Check that.
  2. More of a workaround, than anything else, but you can should be able to run helper.py from a different terminal like Powershell, or the command prompt.

Hope that helps :slight_smile:

1 Like
29

I solved the issue , I just diddnt follow the EXACT install method of python on windows. Word of warning for other newbies!

1 Like