[support]

OK, could you please share the error message you are currently getting? We should be able to suggest more once we see it.

[support]

Good to know it works. If you encounter further problems, feel free to contact us again.

[support]

Hi,

We would not recommend just including a 3rd-party Makefile directly into your main VisualGDB project, as it may cause some variable conflicts and other strange bugs.

We would instead recommend creating a new static library project for the GFX library, adding its sources to the project, specifying the include directories via the VisualGDB Project Properties, ensuring it builds and referencing it from the main project. If this does not work, please share the error messages you are getting and we will help you resolve them.

If you want to try including the Makefile nonetheless, you can edit the project’s Makefile as follows (after the normal SOURCEFILES := … line):

GFXLIB := <path to uGFX>
include <uGFX makefile>
SOURCEFILES += $(GFXSRC)
INCLUDE_DIRS += $(GFXINC)

 

[support]

Hi,

Looks like the timer module is disabled in your project configuration. Please check the HAL_TIM_MODULE_ENABLED macro in the stm32f4xx_hal_conf.h file and define it if it’s missing.

[support]

Hi,

In order to use a custom softdevice in your VisualGDB project, you will need to do 2 steps:

1. Convert the softdevice from the .hex format to a .o file (see nRF51\SoftdeviceLibraries\ConvertSoftdevice.bat)
2. Modify your linker script to have correct addresses/sizes for the softdevice FLASH/RAM and program FLASH/RAM (you can take those from the linker scripts in the IoT SDK).
3. Change the name of the .o file with the softdevice mentioned in the linker script (inside the GROUP() statement).

 

[support]

Hi,

Yes, we are definitely planning to support ESP32 as well as soon as we could some boards. We have ordered a few boards from seeedstudio and will post updates on our Twitter once we have a preliminary version of the BSP.

[support]

Hi,

We don’t have a specific ADC example for STM32F7, however if you get errors like ‘undefined ADC_xxx’, please try searching the solution for the definitions of those functions and check if they are grayed out by IntelliSense.

If they are, most likely you are missing some configuration definition like HAL_ENABLE_ADC. Checking the code around the grayed out definitions should explain why they are not being compiled.

If this does note help, please share the error messages you are getting and let us know if the function definitions are grayed out.

[support]

Hi,

Have you tried explicitly selecting the SWD transport in the VisualGDB Project Properties window?

[support]

Hi,

Sure, sorry, looks like the link did not get inserted properly first: https://sysprogs.com/w/forums/topic/nrf5x-iot-sdk-setup-in-visualgdb/

 

[support]

Hi,

You can do this with environment variables as shown below:

[support]

Hi,

Unfortunately that won’t work reliably. GDB has support for multiple inferiors (i.e. debugging multiple process at the same time), but it’s very unreliable when it comes to handling events from the processes and stopping them. The solution with the custom script should be the easiest.

To make it more clear please refer to the screenshot below for details:

[support]

Hi,

We have investigated this and pinpointed it to an issue in libssh2.

To work around this, we have added support for RSA keys to the upcoming VisualGDB 5.2 Preview 3. It will not work with the regular PuTTY key files, but will work when used in the automatic setup mode using Windows key containers.

[support]

Hi,

We are actually working on supporting the new IoT SDK out-of-the-box and expect to release a BSP for it in the next couple of months.

If you want to set it up manually, please refer to the following thread for a discussion about the SDK. https://sysprogs.com/w/forums/topic/nrf5x-iot-sdk-setup-in-visualgdb/

• This reply was modified 9 years, 1 month ago by support.

[support]

Hi,

Yes, you can achieve this by making a small script that waits for the process to start and then gets its PID and outputs it, then add this script as a custom pre-debug action that will set the AttachPID variable.

Then you can select “Attach to existing instance -> specify PID -> 0” on the Debug Settings page (VisualGDB will show a hint that $(AttachPID) will be used to specify the PID).

So each time you start debugging, VisualGDB will launch your script that will locate the process, store the PID output by it in $(AttachPID) and immediately attach to it as if you had selected the process manually.

[support]

We would still recommend comparing the .map files of the working and broken projects side-by-side. Significantly different addresses of sections or missing groups of functions could provide good clues on what is going on.

[Author]

Posts