[PeterU]

Hi,

The old behavior is not required

Thanks

 

[PeterU]

Thanks, will keep using GNU Make for now, and ignore the warning.

[PeterU]

Hi,

Thanks for the feed back. The clang version is not a blocking issue, I have been trying out the .clang_format for code formatting and there are options that are available in later versions that would be useful.

I had noticed that VisualGDB has been at v5.x for a number of years and had assumed the next major version in your answer meant v6.o. From your answer it seems that v5.6 is a major version and the next would major version will be v5.7

[PeterU]

Hi,

Does Sysprogs have a planed release date for the next major version of VisualGDB, as I have notice the next major version mentioned in a few posts.

Thanks

[PeterU]

Thanks, current using it on a project and will inform you if I encounter any issues.

[PeterU]

Hi,

Thanks for your help downloaded the update, it now has the new .dll but uses has the old msp430-gdbproxy.exe. I had to copy the new msp430-gdbproxy.exe in to get “start without debugging”(Ctrl F5) to work.

I would have thought you would have the new msp430-gdbproxy.exe in the new package?

Thanks again

[PeterU]

Thanks, for updating the tool chain and fixing the errors; the hardware register view seems to operate properly.

On this new release the previous patch https://sysprogs.com/w/forums/topic/msp430-debug-probe-fails-to-reset-after-programming/  was not included, so I had to replace msp430-gdbproxy.exe again.

Note: I only replace msp430-gdbproxy.exe the  MSP430.dll in the zip does not seem to work.

Regards,

Daniel

[PeterU]

Screen shot of issue

Attachments:

You must be logged in to view attached files.

[PeterU]

Thanks,

This release seems to work as expected- the firmware runs after programming (ctrl+F5).

[PeterU]

Same project as above while changing the .vgbsettings> Makefie settings > CFLAGS: (added switch -mfloat-abi=softfp) then saved this cause Visual Studio to stop responding and after closing VS. Could not reopen project. Found that two files had been added to the project:

<None Include="../sdk/platform/Device/SiliconLabs/EFR32MG1P/Source/GCC/efr32mg1p.ld">
<Filter>Source files</Filter>
</None>
<ClCompile Include="$(BSP_ROOT)\EFR32MG1P\StartupFiles\startup_efr32mg1p.c">
<Filter>Source files\Device-specific files</Filter>
</ClCompile>

Deleting the references to both files in Visual Studio .vcxproj and .vcxproj.filter files made it possible for visual studio to reopen the project.

The efr32mg1p.ld file was already included in the project with its include path with the the \ as directory delimiter as shown below:

<None Include="..\sdk\platform\Device\SiliconLabs\EFR32MG1P\Source\GCC\efr32mg1p.ld">
<Filter>Source files</Filter>
</None>

 

 

 

[PeterU]

Thanks for solving this issue downloaded and tried the new version of VisualGDB and can now generate the project; was also able to build the project as the missing header file is not reference in any of the source code files.

Have now reported the issue to ST

 

[PeterU]

Configuration log:

Running CMake: C:\Users\Daniel\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G "Ninja" -DCMAKE_BUILD_TYPE=DEBUG -DTOOLCHAIN_ROOT=c:/sysgcc/arm-eabi -DCMAKE_MAKE_PROGRAM="C:/Program Files (x86)/Sysprogs/VisualGDB/ninja.exe" -DCMAKE_TOOLCHAIN_FILE=C:\Working\stmTest\EmbeddedProject1/build/VisualGDB/Debug/toolchain.cmake -DPLATFORM=VisualGDB -DLOCALAPPDATA=C:/Users/Daniel/AppData/Local
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe
-- Check for working C compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-gcc.exe
-- Check for working C compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-gcc.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe
-- Check for working CXX compiler: c:/sysgcc/arm-eabi/bin/arm-none-eabi-g++.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Generated C:/Working/stmTest/EmbeddedProject1/build/VisualGDB/Debug/BSP.cmake.
-- Configuring done
CMake Error at C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:43 (add_library):
Cannot find source file:

C:/Working/stmTest/EmbeddedProject1/Drivers/STM32L0xx_HAL_Driver/Inc/stm32l0xx_hal_dma_ex.h

Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
.hpp .hxx .in .txx
Call Stack (most recent call first):
C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:306 (create_bsp_library)
CMakeLists.txt:5 (find_bsp)

CMake Error at C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:43 (add_library):
No SOURCES given to target: BSP
Call Stack (most recent call first):
C:/Program Files (x86)/Sysprogs/VisualGDB/CMake/embedded/bsp.cmake:306 (create_bsp_library)
CMakeLists.txt:5 (find_bsp)

CMake Generate step failed. Build files cannot be regenerated correctly.
System.Exception: CMake exited with code 1
at za.a(l a)

========== Project Configuration Summary ==========
EmbeddedProject1 configured in 00:05
========== Configuration: 1 Succeeded, 0 Failed, 0 Skipped ==========

• This reply was modified 3 years, 9 months ago by support. Reason: formatting

[Author]

Posts