Forum Replies Created
-
Posts
-
Hi,
This looks like something specific to the OpenOCD FLASH erasing logic. Although this is normally not covered by our support (please consider using Segger J-Link if you are looking for a debug probe that just works out-of-the-box and comes with its own support), we have published a detailed tutorial showing how to build our OpenOCD fork from scratch and debug it with VisualGDB: https://visualgdb.com/tutorials/arm/openocd/build/
Please ensure you use the following VisualGDB build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2094.msi
This should help understand why OpenOCD decides to merge the 2 erase regions and tweak it if necessary.
Hi,
Looks like your project is built without debugging symbols. Please ensure you specify the “-ggdb” flag in the CFLAGS/CXXFLAGS.
Hi,
This looks like some sort of a wiring problem. Please double-check the power and reset connections and try using a different example (e.g. LEDBlink) to see the exact moment where the board starts/stops working.
Hi,
Actually Segger provides their firmware for some of the LPC boards that turns the on-board LPC-Link into a limited version of a J-Link that works with their software. We would advise trying that first before doing any changes to the board.
Hi,
Please ensure you are using the latest VisualGDB 5.3R8 and are creating an MSBuild-based project.
Hi,
Thanks, this looks like an OpenOCD bug. Unfortunately OpenOCD’s support for NXP LPC FLASH programming is a bit flaky. As a workaround please try using Segger J-Link with the Segger GDB stub – it’s much more reliable and faster.
Hi,
Eclipse likely does is via the semihosting mechanism that allows reading files on the Windows machine via special syscalls that are handled by the debugger. VisualGDB doesn’t support it as this has a very limited use (it won’t work in production code that doesn’t run with the debugger attached) and introduces security risk (attaching to a board running malicious firmware could potentially let it compromise files on your computer).
If you would like to embed binary resources (such as graphics or sound files) into your program, please consider following our Embedded Resource Tutorial.
Hi,
Yes, there are several libraries that can help you do that. Where do you envision storing the files on the device? FLASH memory, SD card, or some other location?
Hi,
Looks like you are using both our startup file and the original assembly startup file (.S). Please try excluding the original one from the project.
If the resulting project doesn’t work, please try setting a breakpoint on the Reset_Handler() function and step through it. It should help understand what is going on.
Hi,
The original problem is most likely caused by the unexpected error settings (normally conversion from a function pointer to a function should not cause any errors). The easiest workaround would be to simply patch the file manually by replacing “&” with “(void *)&” in that block of text.
By removing the startup file from the project you have likely removed the entry point, so the program indeed won’t start. Please try restoring the startup file.
Hi,
Unfortunately we still got the “undeliverable message” error. Please try using a different email provider (e.g. gmail).
Hi,
No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2093.msi
It uses separate variables for gcc/g++ executables used for linking (see link.targets, e.g. GCCBinaryNameForLinking). You can now override them in your custom rule file to use xild instead.
Please note that updating VisualGDB will overwrite any changes you made to the MSBuild files; please ensure you make backups of them.
Hi,
No problem. Based on our communication with ST, they consider GPDSC to be the format used for exporting projects to 3rd-party tools and we fully support it (see our STM32CubeMX importer tutorial). Either way, we will continue monitoring the formats used by the ST project samples and will consider supporting more of them in case they change.
Hi,
If you upgrade within 1 month from your original purchase, you will pay just the price difference. If you upgrade later, the upgrade price will also include the price of extending support period (it will be set to 12 months after the upgrade).
Hi,
AVaRICE does a pretty good job for an open-source tool, so we do recommend using it. If the license of the Atmel GDB server allows using it with non-Atmel products like VisualGDB, it could be a good alternative to AVaRICE, however it might be tough troubleshooting it as it’s likely not designed to be used outside Atmel Studio.
