Search the Community
Showing results for tags 'OpenOCD'.
Found 4 results
I have the Stellaris LaunchPad and I can use it successfully with CCS and IAR. Now I am trying to setup the Eclipse CDT with the GNU ARM Eclipse plug-ins, GCC ARM toolchain, and OpenOCD on my Windows system. I have been following the instructions at the GNU ARM Eclipse plug-ins website. I have successfully created and built a project from the plug-in's generic ARM Cortex-M Project template. But now I am stuck trying to run the debugger with the OpenOCD GDB Server. I created a debugger configuration as described on the GNU ARM Eclipse Plug-ins instructions, here. Except on the Debugger tab in the OpenOCD Settings groupbox I set the Other Options field to "-f board/ek_lm4f120xl.cfg". When I attempt to debug with this configuration, I get the following output in the console window. (The launchpad is connected and powered on.) Open On-Chip Debugger 0.8.0 (2014-04-28-08:39) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : This adapter doesn't support configurable speed Info : ICDI Firmware version: 9270 Info : lm4f120h5qr.cpu: hardware has 6 breakpoints, 4 watchpoints Info : accepting 'gdb' connection from 3333 undefined debug reason 7 - target needs reset target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x00002000 msp: 0x20007904 semihosting is enabled Error: memory write failed: 0x7 Error: memory write failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x00002000 msp: 0x20007904, semihosting Error: Memory write failure! What do I need to do to get this working? This is on a Windows 7 system. I had previously installed the Stellaris ICDI driver from TI when I was using CCS. I'm assuming that same ICDI driver is what OpenOCD uses to interface with the board. Is there a different ICDI driver I need for OpenOCD? Thanks for your help. -- Kevin
So in this thread I'd like to share the tinkering and research around getting OpenOCD to flash the Hercules LaunchPads. After looking into the latest stable release (0.7.0) it looks like OpenOCD has good support for its JTAG emulator--the TI XDS100v2--but it's missing a Flash library to support TI's F021 Flash API. The closest thing it has is the "tms470" driver, but that's the F05 API and after perusing the code in src/flash/nor/tms470.c, there appear to be a lot of differences. I'd like to take a crack at this one, with a stretch goal of implementing on-the-fly ECC computation so users of open-source toolchains can fully utilize the SECDED flash error detection & correction modes of the chips. Luckily, Cortex-R4 support is there although I think it was for some Atmel chip. It's a slight variation of the Cortex-A8 support, funny enough.
Hello everyone, I'm facing a very weird problem.. the "JTAG-DP STICKY ERROR"! I'm running GDB 7.5 and OpenOCD 0.6.1 on a EK-LM3S9B90 board (ARM Cortex-M3). Introduction After analyzing the LM3S9B90's data sheet to find which are the addresses of some the processor registers addresses. -Watchdog Timer 1, Watchdog Load: 0x40000000, Read/Write -Watchdog Timer 1, Watchdog Value: 0x40000004, Read ... -GPIO Port A, GPIO Data: 0x40004000, Read/Write -GPIO Port A, GPIO Direction: 0x40004400, Read/Write ... -UART0, UART Data: 0x4000C000, Read/Write -UART0, UART Flag: 0x4000C018, Read Problem What i want to do is: Change/Get the actual value on some register, what i do is, example for "Watchdog Timer 1, Watchdog Load" register: monitor mdw 0x40000000 #Get value monitor mww 0x40000000 0x00000000 #Change value monitor mdw 0x40000000 #Get value And this commands will give a JTAG error like: (gdb) monitor mdw 0x40000000 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 Block read error address 0x40000000 in procedure 'mdw' (gdb) monitor mww 0x40000000 0x00000000 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 (gdb) monitor mdw 0x40000000 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 JTAG-DP STICKY ERROR MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40000004 Block read error address 0x40000000 in procedure 'mdw' In some forums i saw that this problem can be related to this: adapter_khz 500 but i already try to change the value to upper and lower values and nothing happen. "funny thing" Some of the registers work perfectly, like: GPIO Port A, GPIO Port B, GPIO Port D, UART0, USB, HIBERNATION Module, Flash memory control, System Control. Can see the full list on this url: https://dl.dropboxusercontent.com/u/13427263/registers.pdf FYI To connect to the LM3S9B90 i'm using the default configuration (ek-lm3s9b9x.cfg): C:/openocd-bin/openocd.exe" -f "C:/openocd-bin/board/ek-lm3s9b9x.cfg With the GDB 7.5: target remote | "C:/openocd-bin/openocd.exe" --pipe -f "C:/openocd-bin/board/ek-lm3s9b9x.cfg" Please Help me.. if you need more info.. just ask
Hello all, I noticed that there is a great tutorial for the STM32F0Discovery Board Development Environment Setup (Code Sourcery + Eclipse + OpenOCD) For the Linux OS on this forum. I have a similar tutorial (ARM-GCC + Eclipse + OpenOCD 0.6.0) for MS Windows 7 for those that do not have a Linux box. The tutorial can be found at www.hertaville.com. I also have some interesting information on the GCC build process and on using the GPIO for the STM32F0 Microcontroller. I hope that you find the tutorial to be helpful and appreciate your feedback. Regards, Hussam