[sidprice]

I built the Led Blink project fine.

 

Trying to compare the two RSP files is very hard because my project is using libOpenCM3 so options are very different.

Sid

[sidprice]

.link.rsp file:

-o ../VisualGDB/Release/blackmagic.elf -L../VisualGDB/Release -Wl,-gc-sections -Wl,-verbose -Wl,–defsym,_stack=0x20006000, -Wl,-T,platforms/stm32/f4discovery.ld -nostartfiles -lc -lnosys -Wl,-Map=mapfile -mthumb -mcpu=cortex-m4 -Wl,-gc-sections, -mfloat-abi=hard -mfpu=fpv4-sp-d16  -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -mcpu=cortex-m4  -Wl,–start-group VisualGDB/Release/command.o VisualGDB/Release/crc32.o VisualGDB/Release/exception.o VisualGDB/Release/gdb_hostio.o VisualGDB/Release/gdb_main.o VisualGDB/Release/gdb_packet.o VisualGDB/Release/hex_utils.o VisualGDB/Release/main.o VisualGDB/Release/morse.o VisualGDB/Release/cdcacm.o VisualGDB/Release/swdptap.o VisualGDB/Release/timing.o VisualGDB/Release/gdb_if.o VisualGDB/Release/jtagtap.o VisualGDB/Release/serialno.o VisualGDB/Release/timing_stm32.o VisualGDB/Release/traceswo.o VisualGDB/Release/usbuart.o VisualGDB/Release/cc3100.o VisualGDB/Release/platform.o VisualGDB/Release/WiFi_Server.o VisualGDB/Release/device.o VisualGDB/Release/driver.o VisualGDB/Release/flowcont.o VisualGDB/Release/fs.o VisualGDB/Release/netapp.o VisualGDB/Release/netcfg.o VisualGDB/Release/nonos.o VisualGDB/Release/socket.o VisualGDB/Release/spawn.o VisualGDB/Release/wlan.o VisualGDB/Release/adiv5.o VisualGDB/Release/adiv5_jtagdp.o VisualGDB/Release/adiv5_swdp.o VisualGDB/Release/cortexa.o VisualGDB/Release/cortexm.o VisualGDB/Release/efm32.o VisualGDB/Release/jtagtap_generic.o VisualGDB/Release/jtag_scan.o VisualGDB/Release/kinetis.o VisualGDB/Release/lmi.o VisualGDB/Release/lpc11xx.o VisualGDB/Release/lpc15xx.o VisualGDB/Release/lpc43xx.o VisualGDB/Release/lpc_common.o VisualGDB/Release/nrf51.o VisualGDB/Release/sam3x.o VisualGDB/Release/sam4l.o VisualGDB/Release/samd.o VisualGDB/Release/stm32f1.o VisualGDB/Release/stm32f4.o VisualGDB/Release/stm32l0.o VisualGDB/Release/stm32l4.o VisualGDB/Release/swdptap_generic.o VisualGDB/Release/target.o -lopencm3_stm32f4 -Wl,–end-group

Sid

[sidprice]

1>—— Build started: Project: bmp_windows_build, Configuration: Release VisualGDB ——
1> command.c
1> crc32.c
1> exception.c
1> gdb_hostio.c
1> gdb_main.c
1> gdb_packet.c
1> hex_utils.c
1> main.c
1> morse.c
1> cdcacm.c
1> swdptap.c
1> timing.c
1> gdb_if.c
1> jtagtap.c
1> serialno.c
1> timing_stm32.c
1> traceswo.c
1> usbuart.c
1> cc3100.c
1> platform.c
1> WiFi_Server.c
1> device.c
1> driver.c
1> flowcont.c
1> fs.c
1> netapp.c
1> netcfg.c
1> nonos.c
1> socket.c
1> spawn.c
1> wlan.c
1> adiv5.c
1> adiv5_jtagdp.c
1> adiv5_swdp.c
1> cortexa.c
1> cortexm.c
1> efm32.c
1> jtagtap_generic.c
1> jtag_scan.c
1> kinetis.c
1> lmi.c
1> lpc11xx.c
1> lpc15xx.c
1> lpc43xx.c
1> lpc_common.c
1> nrf51.c
1> sam3x.c
1> sam4l.c
1> samd.c
1> stm32f1.c
1> stm32f4.c
1> stm32l0.c
1> stm32l4.c
1> swdptap_generic.c
1> target.c
1> Linking ../VisualGDB/Release/blackmagic.elf…
1> GNU ld (GNU Binutils) 2.29
1> Supported emulations:
1> armelf
1> opened script file platforms/stm32/f4discovery.ld
1> opened script file libopencm3_stm32f4.ld
1> using external linker script:
1> ==================================================
1> /*
1> * This file is part of the libopencm3 project.
1> *
1> * Copyright (C) 2009 Uwe Hermann <uwe@hermann-uwe.de>
1> *
1> c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/bin/ld.exe: cannot find : Invalid argument
1>collect2.exe : error : ld returned 1 exit status
1> * This library is free software: you can redistribute it and/or modify
1> * it under the terms of the GNU Lesser General Public License as published by
1> * the Free Software Foundation, either version 3 of the License, or
1> * (at your option) any later version.
1> *
1> * This library is distributed in the hope that it will be useful,
1> * but WITHOUT ANY WARRANTY; without even the implied warranty of
1> * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
1> * GNU Lesser General Public License for more details.
1> *
1> * You should have received a copy of the GNU Lesser General Public License
1> * along with this library. If not, see <http://www.gnu.org/licenses/&gt;.
1> */
1>
1> /* Generic linker script for STM32 targets using libopencm3. */
1>
1> /* Memory regions must be defined in the ld script which includes this one. */
1>
1> /* Enforce emmition of the vector table. */
1> EXTERN (vector_table)
1>
1> /* Define the entry point of the output file. */
1> ENTRY(reset_handler)
1>
1> /* Define sections. */
1> SECTIONS
1> {
1> .text : {
1> *(.vectors) /* Vector table */
1> *(.text*) /* Program code */
1> . = ALIGN(4);
1> *(.rodata*) /* Read-only data */
1> . = ALIGN(4);
1> } >rom
1>
1> /* C++ Static constructors/destructors, also used for __attribute__
1> * ((constructor)) and the likes */
1> .preinit_array : {
1> . = ALIGN(4);
1> __preinit_array_start = .;
1> KEEP (*(.preinit_array))
1> __preinit_array_end = .;
1> } >rom
1> .init_array : {
1> . = ALIGN(4);
1> __init_array_start = .;
1> KEEP (*(SORT(.init_array.*)))
1> KEEP (*(.init_array))
1> __init_array_end = .;
1> } >rom
1> .fini_array : {
1> . = ALIGN(4);
1> __fini_array_start = .;
1> KEEP (*(.fini_array))
1> KEEP (*(SORT(.fini_array.*)))
1> __fini_array_end = .;
1> } >rom
1>
1> /*
1> * Another section used by C++ stuff, appears when using newlib with
1> * 64bit (long long) printf support
1> */
1> .ARM.extab : {
1> *(.ARM.extab*)
1> } >rom
1> .ARM.exidx : {
1> __exidx_start = .;
1> *(.ARM.exidx*)
1> __exidx_end = .;
1> } >rom
1>
1> . = ALIGN(4);
1> _etext = .;
1>
1> .data : {
1> _data = .;
1> *(.data*) /* Read-write initialized data */
1> . = ALIGN(4);
1> _edata = .;
1> } >ram AT >rom
1> _data_loadaddr = LOADADDR(.data);
1>
1> .bss : {
1> *(.bss*) /* Read-write zero initialized data */
1> *(COMMON)
1> . = ALIGN(4);
1> _ebss = .;
1> } >ram
1>
1> /*
1> * The .eh_frame section appears to be used for C++ exception handling.
1> * You may need to fix this if you’re using C++.
1> */
1> /DISCARD/ : { *(.eh_frame) }
1>
1> . = ALIGN(4);
1> end = .;
1> }
1>
1> PROVIDE(_stack = ORIGIN(ram) + LENGTH(ram));
1>
1>
1> ==================================================
1> attempt to open failed
========== Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped ==========

[sidprice]

Excuse the long delay responding I had to wait for a suitable time on my projects to try the update.

 

I can confirm that Preview 8 allowed me to update the ESP32 toolchain, thank you, Sid

[sidprice]

Anti-virus is off on this VM. Plus, if I delete the previous installation it will install, see above in this thread,

Sid

[sidprice]

Same result if I “run as Administrator” or not. Screen shot shows the error and the exception details are:

 

VisualGDB version: 5.3.6.1730
—————— System.Exception ——————
System.Exception: Some tools could not be updated. Check error log for more details.
at db.c1.d(ka1 a)
at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass1_0`1.<RunAction>b__0()

Sid

Attachments:

You must be logged in to view attached files.

[sidprice]

Once again the ESP32 update failed to install. This is a pain to have to manually download and install. How can we debug this issue and fix it rather than working around it.

Sid

[sidprice]

Thanks for the help, I deleted the toolchain was able to install the latest version.

Sid

[sidprice]

When I try to install the toolchain manually I get a popup that says “Access Denied.”

 

I also tried running the downloaded toolchain as administrator, with the same “Access denied” error.

Sid

[sidprice]

This is an MSBuild project.

 

I switched to MS Intellisense and my problem went away,

Sid

[sidprice]

Thank you, that almost got me there.

The remaining issue is that Intellisense is still looking in the BSP for header files. The compiler does not and it follows the include file directories I have entered, however Intellisense does not. If I right click on an include file line to open that file the IDE opens the file in the BSP.

How can I force Intellisense to reparse my project?

Sid

[sidprice]

There are quite a few entries in STM32.XML that appear to be referring to the wrong MCU, I am nervous about changing all of them, should I correct all the MCU references:

<?xml version=”1.0″?>
<EmbeddedProfile xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; xmlns:xsd=”http://www.w3.org/2001/XMLSchema”&gt;
<ToolchainID>com.visualgdb.arm-eabi</ToolchainID>
<BspID>com.visualgdb.bsp.in-place</BspID>
<BspVersion>1.0</BspVersion>
<McuID>STM32F103CB</McuID>
<MCUDefinitionFile>$(ProjectDir)\STM32F411xx.mcudef</MCUDefinitionFile>
<MCUProperties>
<Entries />
</MCUProperties>
<BSPSourceFolderName>Device-specific files</BSPSourceFolderName>
<InPlaceMCU>
<ID>STM32F103CB</ID>
<UserFriendlyName>STM32F103CB</UserFriendlyName>
<CompilationFlags>
<PreprocessorMacros>
<string>STM32F4</string>
<string>BLACKMAGIC</string>
<string>WIFIF4</string>
</PreprocessorMacros>
<IncludeDirectories>
<string>.</string>
<string>C:/DataRoot/Projects/bmp_windows_build/bmp_windows_build/bmp_windows_build/platforms/stm32</string>
</IncludeDirectories>
<CFLAGS>-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ggdb -fno-inline-small-functions -O0</CFLAGS>
<CXXFLAGS>-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ggdb -fno-inline-small-functions -O0</CXXFLAGS>
<LDFLAGS>-Wl,–defsym,_stack=0x20006000, -Wl,-T,platforms/stm32/f4discovery.ld -nostartfiles -lc -lnosys -Wl,-Map=mapfile -mthumb -mcpu=cortex-m4 -Wl,-gc-sections, -mfloat-abi=hard -mfpu=fpv4-sp-d16 </LDFLAGS>
<ASFLAGS>-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ggdb -fno-inline-small-functions -O0</ASFLAGS>
<LinkerScript />
<COMMONFLAGS>-mcpu=cortex-m4 -mthumb</COMMONFLAGS>
<EnableLinkerGroups>true</EnableLinkerGroups>
</CompilationFlags>
<AdditionalSourceFiles />
<AdditionalHeaderFiles />
<AdditionalSystemVars>
<SysVarEntry>
<Key>com.sysprogs.bspoptions.arm.core</Key>
<Value>M3</Value>
</SysVarEntry>
<SysVarEntry>
<Key>com.sysprogs.stm32.hal_header_prefix</Key>
<Value>stm32f1xx</Value>
</SysVarEntry>
<SysVarEntry>
<Key>com.sysprogs.bspoptions.stm32.hal_system_file</Key>
<Value>STM32F1xxxx/CMSIS_HAL/Device/ST/STM32F1xx/Source/Templates/system_stm32f1xx.c</Value>
</SysVarEntry>
<SysVarEntry>
<Key>com.sysprogs.bspoptions.stm32.hal_config_template_file</Key>
<Value>STM32F1xxxx/STM32F1xx_HAL_Driver/Inc/stm32f1xx_hal_conf_template.h</Value>
</SysVarEntry>
<SysVarEntry>
<Key>com.sysprogs.stm32.hal_device_family</Key>
<Value>STM32F103xB</Value>
</SysVarEntry>
<SysVarEntry>
<Key>com.sysprogs.stm32.legacy_device_family</Key>
<Value>STM32F10X_MD</Value>
</SysVarEntry>
</AdditionalSystemVars>
<ConfigurableProperties>
<PropertyGroups>
<PropertyGroup>
<Properties>
<PropertyEntry xsi:type=”Enumerated”>
<Name>Execute from</Name>
<UniqueID>com.sysprogs.bspoptions.primary_memory</UniqueID>
<OmitPrefixIfEmpty>false</OmitPrefixIfEmpty>
<SuggestionList>
<Suggestion>
<UserFriendlyName>FLASH</UserFriendlyName>
<InternalValue>flash</InternalValue>
</Suggestion>
<Suggestion>
<UserFriendlyName>SRAM</UserFriendlyName>
<InternalValue>sram</InternalValue>
</Suggestion>
</SuggestionList>
<DefaultEntryIndex>0</DefaultEntryIndex>
<AllowFreeEntry>false</AllowFreeEntry>
</PropertyEntry>
<PropertyEntry xsi:type=”Enumerated”>
<Name>C Library Type</Name>
<UniqueID>com.sysprogs.toolchainoptions.arm.libctype</UniqueID>
<OmitPrefixIfEmpty>false</OmitPrefixIfEmpty>
<SuggestionList>
<Suggestion>
<UserFriendlyName>Default</UserFriendlyName>
<InternalValue />
</Suggestion>
<Suggestion>
<UserFriendlyName>Newlib-nano</UserFriendlyName>
<InternalValue>–specs=nano.specs</InternalValue>
</Suggestion>
<Suggestion>
<UserFriendlyName>Newlib-nano with floating point support in printf()</UserFriendlyName>
<InternalValue>–specs=nano.specs -u _printf_float</InternalValue>
</Suggestion>
<Suggestion>
<UserFriendlyName>Newlib-nano with floating point support in printf() and scanf()</UserFriendlyName>
<InternalValue>–specs=nano.specs -u _printf_float -u _scanf_float</InternalValue>
</Suggestion>
</SuggestionList>
<DefaultEntryIndex>1</DefaultEntryIndex>
<AllowFreeEntry>false</AllowFreeEntry>
</PropertyEntry>
<PropertyEntry xsi:type=”Boolean”>
<Name>Provide default stubs for system calls</Name>
<UniqueID>com.sysprogs.toolchainoptions.arm.libnosys</UniqueID>
<OmitPrefixIfEmpty>false</OmitPrefixIfEmpty>
<DefaultValue>false</DefaultValue>
<ValueForTrue>–specs=nosys.specs</ValueForTrue>
</PropertyEntry>
</Properties>
<CollapsedByDefault>false</CollapsedByDefault>
</PropertyGroup>
</PropertyGroups>
</ConfigurableProperties>
<HierarchicalPath>STM32\STM32F1</HierarchicalPath>
<FamilyID>STM32F1</FamilyID>
<FLASHSize>131072</FLASHSize>
<RAMSize>20480</RAMSize>
<FLASHBase>134217728</FLASHBase>
<RAMBase>536870912</RAMBase>
<MCUDefinitionFile>..\..\iccv8cortex\bin\idb\SVD\STM32F411xx.svd</MCUDefinitionFile>
<AdditionalSourcesRequiredForTesting>false</AdditionalSourcesRequiredForTesting>
</InPlaceMCU>
<MCUMakFile>stm32.mak</MCUMakFile>
<TestFrameworkProperties>
<Entries />
</TestFrameworkProperties>
</EmbeddedProfile>

Sid

[sidprice]

That works well, thanks,

Sid

[sidprice]

Thanks, I look forward to getting an update that fixes this annoying problem,

Sid

[sidprice]

I am using STM32F411RE MCU, however I see the following in STM32.XML:

<McuID>STM32F103CB</McuID>
<MCUDefinitionFile>$(ProjectDir)\STM32F411xx.mcudef</MCUDefinitionFile>
<MCUProperties>
<Entries />
</MCUProperties>
<BSPSourceFolderName>Device-specific files</BSPSourceFolderName>
<InPlaceMCU>
<ID>STM32F103CB</ID>
<UserFriendlyName>STM32F103CB</UserFriendlyName>

This may be the source of the Flash/RAM issue. How can I correct this? I don’t see a way to change the MCU in the project settings.

Sid

[Author]

Posts