Forum Replies Created
-
Posts
-
Hi,
You can do that via custom pre-debug actions. Simply open VisualGDB Project Properties, go to the Debug Customization page and add steps to upload your DLLs. Note that this feature is available in the Custom and Ultimate editions.
Most likely while deleting and reinstalling everything you installed the new version of the debug package that includes the fix as we suggested above.
Now that you have the latest version installed, the problem should not occur anymore.
OK, then please post the contents of the OpenOCD window in Visual Studio here so that we could help you figure out what is causing the problems.
Yes, the problem happens because arm_abs_f32.c does not include stm32f407xx.h.
You could edit the arm_abs_f32.c file (or one of the central headers it includes), forcibly include stm32f407xx.h into all source files via CFLAGS or explicitly add _FPU_PRESENT to preprocessor defines like you did. Either one of those workarounds is fine.
Hi,
Most likely one of your files ends up including the core_cmX.h file that checks for the _FPU_PRESENT macro before including stm32f407xx.h file that defines it.
First of all, please identify the source file that is showing the error (you can remove the -j<number of CPUs> flag from Makefile arguments and check the last built file in the output log). Then try including the stm32f407xx.h file before any other files.
If this does not help, please try reducing the source file to just one include statement that still causes the error and then post the source file a build log showing the include directories here.
Hi,
Please check the OpenOCD window for errors. There was a bug in our recent OpenOCD release that could have caused it and it was fixed in VisualGDB 5.1r6.
Please upgrade to that version or alternatively re-download the latest OpenOCD debug package via Embedded Tools Manager. Then open the Debug Settings page, change any setting there and press “OK”. This should fix the problem.
Not sure what you meant. Adding a non-existent path to IntelliSense should have no effect and be the same as not adding any path there.
Hi,
Good to know it works. Let us know if you encounter further problems.
Note that we do recommend using Debian-based Linux distros like Ubuntu as they have convenient package managers that can install most of the commonly used software.
Hi,
Thanks for letting us know. Yes, the after-initialization commands are indeed executed after ALL of the commands from the debug method.
As a better workaround, you can define a variable like “com.yourname.init_mcu” in your custom device definition and then add $$com.yourname.init_mcu$$ to the startup commands in the EDP. Then you won’t have to hardcode the device-specific commands in the EDP file.
We currently don’t have any plans for changing the current behavior as it looks like a fairly rare scenario and the workaround is also very simple, however if you believe it’s a big annoyance (or anyone else encounters a similar issue), please let us know so that we could reconsider this.
Hi,
It looks like Nordic has discontinued the S110 softdevice in the latest SDK. Please use S130 instead or install the previous version of the SDK.
Hi,
Most likely the new image does not have the OpenSSH server installed. You can install it by logging on via a COM port and running “sudo apt-get install openssh-server”.
OK, this confirms that you can connect from your Windows machine. Could you run “telnet 192.168.0.100 2000” on the Linux machine and see if gdbserver reports an incoming connection like it does when connecting from Windows?
Please check the actual output of OpenOCD. It should contain information about the specific error. If you are not sure, please post the output here so that we could help you.
