firmware upadte using PCAN dev pack for device pcan router pro fd

[manju]

Hello

I'm trying to upload the firmware to my PCAN router pro FD via PCAN DEV pack. I'm following these steps which is given in the manual,

1. Open a sample project for your PCAN hardware in Visual Studio Code.
2. Compile the code before execution with Make Debug ( |Ctrl| + |Shift| + |B| ).
3. Start the debugger with |F5|. In the process, the previously compiled firmware is
transferred to your PCAN hardware.

after completing the 1st 2 steps, I'm trying to start the debugger. But I'm getting the following error

openOCD: GDB server quit unexpectedly. see gdb-server output in TERMINAL tab for more details

image.png (30.67 KiB) Viewed 2664 times

image (1).png (25.34 KiB) Viewed 2664 times

[M.Heidemann]

Hello,

In order to use this, you have to prepare your examples by running both vbscript files as mentioned in the Readme,
have you done so already?

Also, you have to make sure not to open up a single file without context, this only works properly if you open the example folder
in VScode.

Can you confirm both is the case?

Also, please recheck your debug-connections to your PCAN-Router Pro FD again.

Best Regards

Marvin

[manju]

Hello,

Im using 01_routing examples folder and yes I have ran the vbscript file

I have also made the connections based on the manual

But this error "openOCD: GDB server quit unexpectedly. see gdb-server output in TERMINAL tab for more details" I just confused about this

[M.Heidemann]

Hello,

please check if you see the following:

1) Every example folder should contain a .vscode folder after running the SetPath_for_VSCode.vbs
2) in this vscode folder you should see a tasks, launch and c_cpp_properties json file
3) After running SetDebug_for_VSCode.vbs (from the debug folder), you should see that openocd is added
to the launch.json file and you should see configuration files for PCAN-Hardware in \PEAK-DevPack\Debug\Config_Files

4) Make sure you have sufficent rights when setting up the environment, if it is located on a network drive, move it locally.

Double check your connections and see if you missed anything in the readme file.

When in doubt, create a new local folder and start the setup from scratch again, make
sure to follow the steps closely.

Best Regards

Marvin