I really need your guys help. my project needs to be finished by the 12th of may. I need to connect 3 ODrives to my pc and drive 6 motors with them. I also need to use end stops
I have an ST-link V2 so tell me what to do. I have already installed a lot of software as mentioned in the other topics but probably not everything, so please sum up everything I need. I’m good with my PC and I am able to program.
I want to use SimTools. I’ve seen a post about it on the forum so somebody can prbably help me out.
I don’t even know where to begin to help you. We need a lot more details on what part you are stuck on.
What have you tried so far? Have you gone through the Firmware Developer Guide? If so, did you have any problems there that you need help with? If everything is honky dory with getting the development software installed then have you tried flashing some firmware onto your ODrive?
All of that basic information is covered under the docs. We can definitely help you further if you get hung up on a specific step, but your first place to look should be the link above.
I’ll repeat that you need to use a lot more detail when describing your problems. You aren’t going to get a lot of help with a one liner response that you are stuck.
What have you tried?
What worked? What isn’t working?
Are you getting any error messages that might be helpful to share?
What operating system are you using?
Have you done any googling to see if someone else has had similar problems installing openocd?
I’ve never used Xpack and haven’t used windows 10, but you’ll likey need to add the path to the openocd bin directory to your system path. Just do a google search for “windows 10 update system path”.
The behavior that you describe with the executable closing right away is typical for programs that are meant to be run on the command line. Open up a command prompt and try typing openocd (assuming that is the name of the executable). If it works then your system path is setup correctly. OpenOCD won’t do much without passing in some arguments though. During the build process it isn’t typically called directly. The make flash call from the odrive Firmware source directory is what makes the call to openocd. I think there is a way to get your IDE setup to also call openocd but I haven’t gone through the setup of that yet, so I won’t be much help there.
Have you pulled the odrive project down from github yet? I would start with the master branch of oskar’s repo first. Once you have confidence in the build workflow you can clone some of the other repos that are out there that have the functionality that you are looking for.
That’s just my suggestion. It’s much easier to problem solve when you take very incremental steps. It will be good to make sure your build environment is setup and working as expected before going too much further.
I’m not convinced that is a problem, it just looks like a config file is missing. Try doing a build in the Firmware directory of the odrive repo. If the build is successful then try make flash with the programmer hooked up to one of your odrive boards.
