Forum Replies Created
-
Posts
-
The RSP file looks OK. As a quick check, could you try creating a new “LEDBlink” project with the same toolchain? If it doesn’t work, please try reinstalling the toolchain.
If it does, please try comparing both RSP files.
Hi,
Thanks for the build log. Unfortunately it looks like an error that happens before the Linker manages to output enough information.
Please try locating the Release\Debug\<ProjectName>.link.rsp file and post its content here (please also attach your <mcu>.props file from the project directory). The file should contain the linker command line and should help us see what could be wrong.
If you see something suspicious in the file, please try running the following command from the project directory:
<full path to arm-eabi-gcc> @Release\Debug\<ProjectName>.link.rsp
If you can reproduce the same error, try removing the suspicious part and run GCC again. If you can successfully pinpoint a part that is causing an error, please edit your settings accordingly.
Hi,
No problem, we can walk you through diagnosing this. Please try setting a breakpoint in ReportFunctionRunTimeToRealtimeWatch() in the profiler framework.
Does the function get invoked? Does the rec.Address expression match the instrumented function address (the least significant bit will be 1 to signify the THUMB code)?
If yes, please try running a regular instrumenting profiler session and switch Live Profiling window to “Diagnostics”. It should show various statistical data (e.g. buffer utilization, samples/second, bytes received). Please attach a screenshot of the diagnostic data here (or simply list all the numbers) so that we can see what is going on.
Hi,
It looks like something in the linker command line is broken. Please try enabling verbose mode via VS Project Properties -> Linker -> Advanced (not the regular VisualGDB verbose mode) and post the entire verbose build output here so that we could help you understand what is going on.
Hi,
We actually have a HAL tutorial here: https://visualgdb.com/tutorials/arm/stm32/uart/hal/
Please try following it instead.
Hi,
Please attach the screenshot of your About window and your debug settings so that we could check the VisualGDB state.
Looks like the project is missing references to libraries or sources defining a few functions (like airkiss_printfImp). We would advise searching the SDK and your external libraries for definitions of those functions (not just declarations in .h files) and including the corresponding libraries.
Hi,
Yes [here], but it comes with absolutely no warranties or support of any kind.
Hi,
Unfortunately it’s hard to provide any help without seeing the full context: OpenOCD output, screenshots of your settings, screenshot of your About window to show the current VisualGDB state. Please attach those and we will try to help you.
The one from the LIBRARY_NAMES is the correct one (you would also need to remove it from the stm32.xml file as otherwise it will get regenerated).
std::array<> should not be related to compactcpp. Please feel free to post the errors you get and we will help you resolve them.
Hi,
The <offset> files are generated when you debug your program first. You can also use the ESPImageTool.exe from the <toolchain>\esp8266-bsp directory to generate the files or program them via the bootloader.
Hi,
OK, thanks for the log, that explains it. Looks like something is totally wrong with the temporary directory and this breaks the .Net framework. It is surprising it didn’t affect any other programs.
Please try deleting all files in the temporary directory and run chkdsk on the drive containing it.
OK, sorry about that. We have added another logging layer on top: http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1916.msi (the link will become available in ~10 minutes)
Please open the View->Other Windows->VisualGDB Diagnostics Console window and enable logging before opening VisualGDB Project Properties.
Hi,
Thanks for confirming this. Looks like some internal VisualGDB component is throwing an exception and VisualGDB is not handling it properly. Please try this build:
http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1915.msi
It should display a meaningful error message in this case.
