Home > Jtag Dp Sticky > Jtag-dp Sticky Error

Jtag-dp Sticky Error

instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse OpenOCD - Open On-Chip Debugger Mailing Lists OpenOCD - Open On-Chip Debugger The Open On-Chip Debugger Brought to you by: dail, gowinex, ntfreak Summary Files Reviews Support News Donate Mailing Lists Tickets Code Gerrit Review openocd-commit openocd-devel openocd-user [OpenOCD-user] "JTAG-DP STICKY ERROR" message with STM32F429 [OpenOCD-user] "JTAG-DP STICKY ERROR" message with STM32F429 From: R. Diez - 2015-01-19 12:55:03 Hi all: I have wasted several days dealing with message "JTAG-DP STICKY ERROR" while programming new STM32F429 chips, and thought I should share my story here. Now that I know what to look for, I have realised that other people have already reported the same issue, but I still think that this e-mail could be of help for many, especially as there are a couple of shortcomings/bugs in OpenOCD that could be worth fixing. My company is manufacturing boards with a JTAG chain made of 3 x STM32F429 CPUs. We are using the 2 MiB flash part (STM32F429IIT6). The chips come with their internal flash completely erased. The default "all ones" (0xFF) memory contents in the small "option bytes" flash area means that the whole flash memory is read-protected when accessed through the debug interface. That is, you cannot read any flash memory values, including the "option bytes" themselves, with OpenOCD (which means GDB cannot either). The reference manual

don't worry. OpenOCD will still be able to talk to the board. The errors look like this. There is a bug in OpenoCD 0.4.0 causing the first debug session, after OpenOCD has been started, to fail if the target is running when OpenoCD tries to https://sourceforge.net/p/openocd/mailman/message/33250161/ connect. This bug has been fixed in recent git and can be worked around in OpenOCD 0.4.0 by adding -c init -c 'reset init' to the command line when starting OpenOCD. If you see this error, then the next time https://www.tincantools.com/wiki/OpenOCD_Troubleshooting:_JTAG_Sticky_Error you try to start OpenOCD it will give an error the next time it tries to communicate with the Beagleboard. When you exit OpenOCD you will need to disconnect and reconnect the power cable to the Beagleboard before OpenOCD will be able to communicate with the Beagleboard again. Retrieved from "https://www.tincantools.com/w/index.php?title=OpenOCD_Troubleshooting:_JTAG_Sticky_Error&oldid=1035" Navigation menu Personal tools Log in Namespaces Page Discussion Variants Views Read View source View history More Search Navigation Main Page Flyswatter Flyswatter2 Silverjaw SPI Hook OpenOCD Compile OpenOCD OpenOCD Troubleshooting Recent changes Random page Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 18 July 2011, at 12:05. Privacy policy About TinCanTools Disclaimers

6 Building openocd for Fedora 20 for the BeagleBoard-xM 7 Running as non-root user 8 Invoking OpenOCD (Flyswatter2 and BeagleBoard-xM) 9 Procedures 10 GDB 11 Commands (related to BB-xM http://www.crashcourse.ca/wiki/index.php/Openocd and FTDI) 11.1 Questions 11.2 General 11.3 Ports 11.4 Targets 11.5 Interfaces and transports and adapters 11.6 Clocking stuff (not sure) 11.7 JTAG and scan chain 11.8 Logging and debugging [edit] Overview Specifically, OpenOCD running on Fedora 20 for the BeagleBoard-xM, and its associated current issue(s), but there should be a little something here for everyone. [edit] Notes ftdi_sio loadable module [edit] User's Guide changes "sprung4b" should jtag-dp sticky be "sprugn4b", and check validity of link openocd.berlios.de -> openocd.sourceforge.net Section 8.1, "interface transports" should be a config command gdb_port, telnet_port can be used in R/O mode, but not tcl_port "help exit" doesn't seem to show subcommands [edit] Links [edit] General OpenOCD links Sourceforge OpenOCD home page "Unknown target type cortex_a" pastebin page (current Fedora 20 error, easily fixable) [edit] Tin Can Tools links Main page JTAG jtag-dp sticky error debuggers page OpenOCD Running OpenOCD on Linux with the Beagleboard Compiling OpenOCD Compiling OpenOCD v07 Linux Compiling OpenOCD Linux for Flyswatter2 OpenOCD Troubleshooting [edit] elinux.org links Quite a number of OpenOCD-related pages at http://elinux.org/Main_Page, some of which look old, redundant or dead. Openocd-Redux (now marked as "dead") Main OpenOCD page BeagleBoardOpenOCD Running OpenOCD on Linux with the Beagleboard xM OpenOCD config files Debugging the linux kernel using gdb ... lots more coming ... [edit] Installing and running openocd under Fedora 20 Simple. First: # yum install openocd Then, sadly, you need to hack a file: # vi /usr/share/openocd/scripts/target/amdm37x.cfg and edit line 144 to change cortex_a to cortex_a8: target create $_TARGETNAME cortex_a8 -chain-position $_CHIPNAME.dap It's not clear why this is necessary, it just is. I've already asked about this on the openocd-devel mailing list. Finally, the command: $ sudo openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c "reset init" [edit] Building openocd for Fedora 20 for the BeagleBoard-xM Check out the Git repo: $ git clone git://git.code.sf.net/p/openocd/code git Next, rather than build everything else from source, just go with the Fedora packages, which seem sufficient: # yum install libftdi libftdi-devel libusbx-devel Then in the openocd source directory: $ ./bootstrap $ ./

 
No related pages.