Forum Replies Created
-
Posts
-
No problem. Unfortunately, there is no easy solution here, as it looks like different versions of the NXP framework (or the sample project itself) work differently.
The solution would be to extract the build command lines used by the NXP IDE, build the project manually using those command lines and then try combining them with the VisualGDB command lines (e.g. using VisualGDB’s linker command line to link the object files produced by the NXP IDE or vice versa). By checking the behavior of the build results, you should be able to pinpoint a specific source file (or a compiler/linker flag) that is causing the issue. Unfortunately, it would take several iterations to nail it down (you can check this tutorial for a similar process for the Keil compiler).
Another option would be to import the NXP project into VisualGDB as an externally built project (using NXP’s Makefile and NXP’s driver libraries). This will allow reusing the existing build system (that produces usable projects) with the rest of the VisualGDB’s features.
Hi,
The only change to R12 was the support of the Kendryte K210 AI chip. We have updated the history page accordingly.
Sorry, this is by design. The tab semantics for Unix terminals is fairly complex (e.g. it can be altered via the ANSI escape sequences and it’s also possible to start overwriting text in the middle of a tab break), so VisualGDB automatically translates all terminal input it receives into a simple 2-dimensional matrix of characters and attributes.
We might be able to add a special attribute tracking whether a group of spaces was created in response to a tab symbol, but realistically we won’t be able to do it until the next major redesign of the terminal logic (that is not on the radar yet), sorry.
Hi,
No problem. We will try to update the instructions for a newer OpenCV version soon, however due to the amount of other features scheduled before that, it will likely take 4-6 months or more.
Hi,
Sorry, it is still in the queue. ST recently released a few other device families (STM32MP1 and STM32WB) that got prioritized over STM8. We will likely get a better estimate for STM8 in the next 2-3 months.
If the project also doesn’t build directly, it might be missing some configuration entries, or it might be meant for a different version of ESP-IDF (unfortunately, different ESP-IDF versions are not always backward-compatible). Please consider posting on the ESP32 forum to get support for ESP-IDF-specific issues.
Hi,
Does the project also fail at the linking stage when building it directly via command line (outside VisualGDB)?
Hi,
It looks like your ESP-IDF installation is corrupt and is missing some files referenced by the CMake scripts. Please try building the project manually (using idf.py build) and ensure it builds without errors. If the build outside VisualGDB fails as well, please try reinstalling the toolchain/ESP-IDF and if it doesn’t help, try re-creating the project from scratch.
Normally, when VisualGDB rejects a license key that hasn’t been renewed, it will display an error message with a link to this page allowing you to download the latest version compatible with your key, or renewing your key. Please use that page to download the installer for the version compatible with your key.
Hi,
Good to know the installation succeeded. Most likely, the error was caused by some network issues.
You can reinstall CMake via Tools->VisualGDB->Manage VisualGDB Packages or by removing the %LOCALAPPDATA%\VisualGDB\CMake folder.
Thank you for renewing your license.
The error message you reported looks like the project references the system_nrf51.c file that is no longer present in the latest BSP.
Nordic has removed nRF51 support (only leaving out nRF52) in the latest SDK versions, so our BSPs had to follow.
As a workaround, we have released a separate BSP supporting the legacy nRF51 device using the latest BSP version that supports it.The recommended way to proceed with this would be to create a new project for the nRF51 device using MSBuild (GNU Make may not be compatible with the latest Nordic SDKs due to path length limitations) and moving the code to it. It would require additional setup, however omce the code is moved over, you will get much faster building experience than with GNU Make and also better integration with VS property windows.
We can also show you how to patch the existing project definition to have it retargeted to the special nRF51 BSP, however it may not work with GNU Make due to path length limitations.It is hard to say why the VisualGDB project would not call this function as our BSPs contain the code from the original SDKs and do not introduce any changes beyond trivial bugfixes.
That said, it should be relatively easy to narrow it down. Please try replacing the ELF file generated by VisualGDB (<Project directory>\VisualGDB\Debug\<Project Name without Extension>) with the ELF file generated by the NXP IDE. Then select Tools->Options->Projects and Solutions->Build and Run->When Project is out of date -> Ask. Finally, start a new debug session and don’t rebuild the project. This will launch the ELF file produced by the NXP IDE using the VisualGDB’s debugging logic. If this results in a usable USB device, the problem happens at the build stage.
In that case, please try setting a breakpoint on the code responsible for calling the Connect() method in both projects and try comparing the behavior. If debugging the original ELF file under VisualGDB doesn’t work, please check if using the “Program and start without debugging” works for the original executable and for VisualGDB-based executable.
As we have mentioned above, the errors are shown because the toolchain you installed got corrupt (some libraries got replaced with incompatible versions).
We can help you configure it correctly if you could let us know the exact steps you are performing (including the URLs of the toolchain, SD card image) and a description of the exact choices you pick in the wizard (if possible, with screenshots). Then we can check your configuration for common errors and suggest what could be causing it.
Please also try running “lsb_release -a” on the Beaglebone and share the output you receive.
Hi,
No problem, we can help you track this down, however we would need some clarification from you first.
Is the project that works built with the GCC compiler under a different IDE, or is it using a completely different compiler (e.g. IAR)?
If it using gcc, we would advise using Embedded Memory Explorer to compare the 2 ELF files (see this tutorial). Specifically, check if there are some symbols that are only present in one project, but not the other one, and also check the addresses of main() and some global variables (they will be different, but should be located in the same memory region for both ELF files). Also check if the project contains board-specific code for clock setup (e.g. PLL, clock divider, etc) and ensure both projects use the same settings.
