support

Forum Replies Created

Viewing 15 posts - 6,721 through 6,735 (of 7,855 total)
  • Author
    Posts
  • in reply to: Suggestion required – Affordable JTAG for ESP8266 OCD #7200
    support
    Keymaster

    Hi,

    Almost all inexpensive JTAG adapters are based on the FT2232 chip, so they are pretty much all the same, just differently packaged. Any Olimex one or something like FlySwatter from TinCanTools will do.

    in reply to: User Variables in Pre-processor macros #7199
    support
    Keymaster

    Hi,

    The logic of automatically detecting that would be probably too complex and error-prone given a fairly simple workaround. We could add a button to trigger retesting manually if that helps.

    in reply to: Using the QuadSPI on STM32F7 Discovery #7198
    support
    Keymaster

    Hi,

    Sorry, we don’t support that yet. We would recommend using the ST-Link utility. We will also monitor the popularity of QSPI-related searches and add a tutorial on it if the topic becomes popular.

    in reply to: BeagleBone-Debian Qt5 Toolchain #7197
    support
    Keymaster

    Hi,

    The ui_MainWindow.h file is generated during build. So if you build the project and re-open it, IntelliSense should it pick it. If this does not happen, please check whether the file actually exists and whether its directory got added to the IntelliSense directories in VisualGDB Project Properties.

    in reply to: Openocd jtag driver problem #7196
    support
    Keymaster

    Hi,

    What exactly is happening to the device? Is the LED blinking? Did the FLASH programming progress window appear? What is the contents of the GDB Session window (if you enable “All commands” view)?

    Does changing reset mode in VisualGDB Project Properties help? Have you tried connecting the reset to pin 3 on your JTAG20 as described in the tutorial?

    in reply to: Openocd jtag driver problem #7192
    support
    Keymaster

    Hi,

    If this is a reprogrammed ARM-USB-OCD-H or another device, please use the ST-Util to restore the original VID/PID and specify the OpenOCD script accordingly. Please also ensure that you have a WinUSB-based driver installed. You can install it manually using USBDriverTool.

    in reply to: Wiping MCU memory #7191
    support
    Keymaster

    Hi,

    If you are using OpenOCD, you can try running the ‘mon flash erase_address’ command in the GDB Session window:

    mon flash erase_address pad <start address> <FLASH size>
    in reply to: Error 'Importing Specs' #7184
    support
    Keymaster

    Hi,

    This is strange. What happens if you open command-line prompt in your project directory and run the following commands?

    set PATH=C:\Pi\Toolchain\bin;%PATH%
    make

    Do you get the same error message? Is the .elf file created? What if you run “make all” or “make DEBUG/<ELF FILE NAME>.elf”?

    in reply to: #ifdef __cplusplus -> Where is this defined? #7183
    support
    Keymaster

    Hi,

    VisualGDB uses a different build mechanism, so forcing the C++ files to be treated as C would involve adding “-x c” to CXXFLAGS. However, we would recommend simply renaming your .cpp file to a .c file to avoid further problems.

    support
    Keymaster

    Hi,

    Please try updating to VisualGDB 5.0. Alternatively you can try downloading an older OpenOCD package and installing it via the Embedded Tools Manager, e.g.:
    http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd090.vgdbxedp
    http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd090r2.vgdbxedp

    in reply to: User Variables in Pre-processor macros #7181
    support
    Keymaster

    Hi,

    Do you get the ‘testing toolchain’ dialog? If no, try changing an arbitrary line on the Makefile Settings page (e.g. add a space to CFLAGS and remove it back) and clicking “Apply”.

    in reply to: ESP8266 and debugging with SEGGER j-link #7180
    support
    Keymaster

    Hi,

    OpenOCD needs a libusb-based driver for J-Link that is incompatible with the original J-Link driver. The easiest way to install it is using our USBDriverTool. You can also try configuring OpenOCD debugging with J-Link for an ARM project and click “Test settings” so that VisualGDB configures the driver automatically. We don’t have automatic driver setup for ESP8266 projects yet though.

    in reply to: Wrong include in file "cpu_utils.h" #7179
    support
    Keymaster

    Hi,

    Thanks for letting us know. We will consider fixing this in the next release of the STM32 package.

    in reply to: BeagleBone-Debian Qt5 Toolchain #7178
    support
    Keymaster

    Hi,

    Looks like we forgot to mention in the tutorial that you need to upload the Qt libraries from the toolchain to your device. We have updated the tutorial, please upload the files as shown below:

    in reply to: BeagleBone-Debian Qt5 Toolchain #7172
    support
    Keymaster

    Hi,

    Sorry for the confusion, looks like the Beaglebone page contained the wrong toolchain link. We have updated the page, please try downloading it again.

Viewing 15 posts - 6,721 through 6,735 (of 7,855 total)