OpenOCD common error .cfg path not found

[Max VIZZINI]

Hi,

If you are getting this kind of error when you try to run your OpenOCD in AutoDevKit Studio 2.2.1:

Then most probably you have not updated the search path of the config files.

From main AutoDevKit menu, select Run > Debug Configurations

In the new window, select “GDB OpenOCD Debugging” drop down and the “SPC582Bxx_RLA AutoDevKit Studio generic” entry.

On the right hand-side, please choose the tab “Debugger”

The issue is in the “Config options” field. The path present should be identical to your installation path.

If you did not change anything from the installation default, the correct path should be:

C:\AutoDevKitStudio-2.2.1\openocd\scripts

If you installed under other path, please put the correct installation path.

Repeat the same procedure for all the generic AutoDevKit Studio per type of microcontroller.

To double check, you can look at the installation file and check for the missing .cfg file:

In standard case, the installation path is:

The file presents are:

Best Regards,

AutoDevKit Team

[Bwang.3]

Hello! I bought 2 AEK-MCU-SPC5LNK debuggers to download the program for the AEK-MOT-MR200G1 development board! But during use, a prompt as shown in the following picture will appear! I don't know if it's a device issue or something! The AEK-MOT-MR200G1 development board uses the controller chip SPC582BE1! And I observed that AEK-MCU-SPC5LNK only has 3 LED lights lit up after plugging in the USB harness! They are POWER, The three LED indicator lights LED1 and LED2 are on! But the eLNK LED never lit up! What's going on? Can you tell me? Thank you!

[ATROI]

Hi Bwang,

To solve the problem, please follow the steps below:

Step1: Go to folder C:\{installation folder}\openocd\drivers

Step2: Right-click on UNISTALL_UDESTK.bat and select "Run as Administrator"

Step3: INSTALL_UDESTK.bat  (with Administrator rights) from the following folder:

           C:\{installation folder}\openocd\drivers

A CMD window and a security message appear three times, as shown below

Step4: Uncheck “Always trust from “StellarLINK.com(Test)”. Then, click on the “Install” button.

Thanks,

AutoDevKit Team

[Bwang.3]

Hello! I reinstalled the driver according to your steps, but the result is still the same! And my device manager has recognized my device! But there is a problem as shown in the following figure when debugging with software! Can't this be solved?

[Max VIZZINI]

Hi,

If you are not supply the AEK-MOT-MR200G1A the MCU will not turn on.

Best Regards,

AutoDevKit Team

[ATROI · Accepted solution]

Hi Bwang, 

The following changes are required for programming and debugging the AEK-MOT-MR200G1 board with OpenOCD:

step 1: Under C:\AutoDevKitStudio-2.2.1\openocd\scripts\board open the file spc582b_dis.cfg

step2: at line 12 insert: reset_config srst_push_pull as showed in the image below.

step3: save the file.

step4: program and debug your code using OpenOCD in AutoDevKIt Studio

Thanks,

AutoDevKit Team