Forum Replies Created
-
Posts
-
We have answered the question about the memalign() function in this thread.
Regarding the <vector> file, can you confirm that it is physically present somewhere under C:\Users\akhils\AppData\Local\VisualGDB\RemoteSourceCache\192.168.0.54? You can also try reloading the cached directories via VisualGDB Project Properties to ensure you get the latest versions of all files.
Hi,
Looks like your system headers may be too old and don’t support C++11 properly. Please examine the build output and try to understand why they have 2 different definitions of posix_memalign(). Once you locate both definitions, you can try modifying them to ensure they both match.
Hi,
Most likely there is a typo somewhere in the settings. Please try adding the -v option to CFLAGS/CXXFLAGS to force gcc to output the include search directories it uses. Then simply compare the listed directories with the command line shown in the build log. This should explain why the file is not found.
Please start with trying this Makefile literally:
test: <TAB>gcc -DTIMESTAMP=$(shell C:/mingw/msys/1.0/bin/date.exe +%s) -E test.c -o test.E
If it works, with your make.exe, please compare the syntax in it with your Makefile that is broken. If it does not, please download a clean MinGW toolchain from here and try using make.exe and mingw-make.exe from it.
Hi,
This is a known issue. Basically, OpenOCD does not know the current device ID and cannot detect the FLASH characteristics for it:
Warn : Cannot identify target as a STM32L4 family.
Normally the device IDs are added by the OpenOCD maintainers fairly quickly, so we would recommend simply waiting a month or two until an update is available. We could also provide brief instructions on building OpenOCD from scratch and patching it to support the new device if you don’t want to wait for the OpenOCD guys to do that for you.
Good to know it works. If you ever need our help to pinpoint the toolchain issue, feel free to share the error messages you get and we will give our best advice on figuring out what could be the cause.
Hi,
Yes, you can download them here: http://visualgdb.com/hwsupport/
Hi,
We have rechecked the OpenOCD support for FTDI and CC3200 and it looks like the current FTDI configuration files do not support the SWD signals yet.
There are third-party articles describing how to define them, but we have not retested those instructions. We would expect the OpenOCD maintainers to update the configuration files in the next few releases.
Also if you encounter errors like “The current target requires JTAG”, please try switching OpenOCD to manual configuration mode and replacing the cc3200.cfg script with the cc32xx.cfg.
If this does not help, please let us know.
Hi,
This is something that the Nordic guys should know much better than us. Their softdevice is closed-source, so it’s hard to say how compatible different versions are. Please consider contacting the Nordic support or asking on their forums.
OK, could you please share the error message you are currently getting? We should be able to suggest more once we see it.
Hi,
We would not recommend just including a 3rd-party Makefile directly into your main VisualGDB project, as it may cause some variable conflicts and other strange bugs.
We would instead recommend creating a new static library project for the GFX library, adding its sources to the project, specifying the include directories via the VisualGDB Project Properties, ensuring it builds and referencing it from the main project. If this does not work, please share the error messages you are getting and we will help you resolve them.
If you want to try including the Makefile nonetheless, you can edit the project’s Makefile as follows (after the normal SOURCEFILES := … line):
GFXLIB := <path to uGFX> include <uGFX makefile> SOURCEFILES += $(GFXSRC) INCLUDE_DIRS += $(GFXINC)
