[bflannery]

Is there any reason that the application bootloader would not be produced when built?

I have the GENERATE_BIN option on both BSP based executables. The bootloader target produces a .bin file but the application does not.

 

[bflannery]

Figured it out. I had a section in my bootloader linkerscript not marked (NOLOAD) that should have been.

[bflannery]

It just looks like you need to update your JRE to be compatible with that version of CubeMX.

[bflannery]

I am realizing that using something like msys might be too complicated for deployment.

[bflannery]

I am not one to resurrect old threads, but this felt like the most appropriate place.

This newer repo is where active development occurs for avarice. They even have support for JTAGICE3 which is much more easily acquired.

https://github.com/Florin-Popescu/avarice

They don’t release pre-built windows executables but they can be built with msys. It would be great if visualgdb packaged this version of avarice instead of the stagnant avrdude repo version.

 

[bflannery]

Oh I see now how this works.

[bflannery]

Okay neat. Is there any documentation for these vgdbxactions files?

[bflannery]

Figured this out:

bsp_include_directories(
${BSP_ROOT}/STM32H7xxxx/CMSIS_HAL/Core/Include/
${BSP_ROOT}/STM32H7xxxx/CMSIS_HAL/Device/ST/STM32H7xx/Include/
)

• This reply was modified 1 year, 6 months ago by bflannery.

[bflannery]

The microcontroller and OpenOCD have no idea how to communicate with external memory by default. I am not sure what the CubeIDE is doing in the background to initialize those peripherals (maybe semihosting or an externalLoader specifically for whatever is on the development kit).

Anyways, here is somewhere to start with VisualGDB

https://visualgdb.com/tutorials/arm/stm32/flash/

 

 

 

[bflannery]

I would second enabling Live Watch to infer the type from the source code as a feature.

[bflannery]

You may have already seen this, but this tutorial has some helpful info. https://visualgdb.com/tutorials/arduino/esp32/spiffs/

• This reply was modified 1 year, 8 months ago by bflannery.

[bflannery]

That was quick, and works great.

The one suggestion I would make is to duplicate that “(description)” in the dropdown so you can see at a glance which debugger is selected. Nice work!

[bflannery]

That did the trick. Now all my debuggers show up as USB Devices under the Debug Settings.

Thanks!

[Author]

Posts