I need help with my 6 DOF racesimulator

[Stijn_Carelsbergh]

hi

I’m stuck on installing openocd.

cheers

Carelsbergh Stijn

[jalbob]

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?

[Stijn_Carelsbergh]

Hi,

I’m sorry

I’m using a Windows 10 machine.

I have the odrivetool installed and working.

I have an st link and the correct driver installed.

I have ODrive serial test installed.

I have also installed the zadig tool.

I also have vscode installed with the extension but I can’t figure out the environement variable.

Configuring Visual Studio Code

I downloaded these things because they were in this post:

ASCII commands makes ODrive unreachable

Hi all, I try to connect the output of a simulator software to ODrive. My setting is a 3.5 board with the latest devel branch. Connected is a KEDA motor with mounted AMT102. The startup sequence is running fine and the motor resposes to the commands through a serial connection. Everything looks good till this point. This is the UI of the simulator software: [grafik] As you can see, the software sends a initial positioning command, waits for 1 second and starts to send positions every 50ms…

and also this one:

6DOF motion platform using ODrive

Hi Wickie, don’t be frustrated. Nobody says that Odrive is a ready build, end user friendly device. You have to read a lot and ask some people for help. For your first question look to the thread. For your second problem, I can not help you. I always use a ST programmer like this: At the beginning, my ODrive was also unaccessible after rebooting sometimes… But with the programmer you can always flash the firmware again. You do not need any knowledge about editing the firmware code. My su…

Now I’m stuck on trying to install openocd

Do you need to know anything else?

cheers

Carelsbergh Stijn

[jalbob]

Have you retrieved the OpenOCD zip file from the openocd github releases page and unzipped it to %userprofile%\AppData\Roaming\GNU MCU Eclipse yet?

The resulting path to the openocd executables should look something like this once unzipped:

"C:\Users\ilg\AppData\Roaming\GNU MCU Eclipse\OpenOCD\0.10.0-5-20171110-1117\bin\openocd"

[Stijn_Carelsbergh]

Hi

No I have not, I will try it after school.

Do you also know what the environment variabele is?

Thanks a lot

Cheers

Carelsbergh Stijn

[Stijn_Carelsbergh]

Hi

I tried the unzipping, but I’m not seeing the exacutables.

I’ve also succesfully installed openocd as an Xpack. I don’t know if this is also good and what I need to do with it now.

cheers

Thank you

Carelsbergh Stijn

[jalbob]

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”.

[Zennix]

Hi Stijn,

I installed OpenOCD like described here: https://gnu-mcu-eclipse.github.io/openocd/install/
Use the Windows part not XPack. Installing the drivers for ST-Link is also described there.

If you want to add Environment Variables to Windows 10, make right click to your PC-symbol, choose Properties. Then click on this:

Then choose this:

Add your variables here:

Depending on your location, this is only a example of my installation.

C:\Program Files\Git\cmd
C:\ProgramData\Anaconda3
C:\Program Files (x86)\GNU Tools ARM Embedded\7 2017-q4-major\bin
C:\Tools\tup
C:\Program Files (x86)\GnuWin32\bin
C:\Program Files\GNU MCU Eclipse\OpenOCD\0.10.0-7-20180123-1217\bin
C:\Program Files\Microsoft VS Code\bin
C:\Users\Entwicklung\AppData\Local\Programs\Microsoft VS Code\bin

Greetings / Zennix

[Stijn_Carelsbergh]

Hi

thanks for the reply.

I used the Xpack method and got here

If this is not good just tell me and I will do it the other way.
The problem is that when I run the exe file, it opens cmd and closes imediatly

I think I allready got the st-link drivers figured out.

The environment variabele is also added, what is the ODrive repository?

cheers

Carelsbergh Stijn

[jalbob]

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.

[jalbob]

what is the ODrive repository?

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.

[Stijn_Carelsbergh]

Hi,

Thanks, so I first have to try the original firmware before the firmware with end stops?

Cheers

Carelsbergh Stijn

[jalbob]

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.

[Stijn_Carelsbergh]

Hi

I’ve sceencaptured my screen on the startup of the exe and this is what I’m getting:

W
har should I do?

Cheers

Carelsbergh Stijn

[jalbob]

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.

[Stijn_Carelsbergh]

Hi

I think I have gotten my software under controll, doe this mean that the flash is succesfull?

Cheers

Carelsbergh Stijn

[jalbob]

Yep, that looks good.

[Stijn_Carelsbergh]

Hi

it says libusb failed, what does that mean?

cheers

Carelsbergh stijn

[jalbob]

Not sure. It looks like it goes on and completes the flashing process. Are you having problems?

[Stijn_Carelsbergh]

Hi

I can’t get it to show up on the odrivetool

Cheers

Carelsbergh Stijn