I'm using OpenOCD and GDB to load executables through JTAG to an ARM chip.
Up until now, the ARM chip (an STM32) was in an evaluation board, and I got
things working. Now, a custom built board containing the *exact same* ARM
chip has arrived, and I cannot load executables to it.
Comparing the OpenOCD output from both boards, it seems that the first
problem that occurs with the new board is that the ARM cannot "reset"
properly:
Halt timed out, wake up GDB.
timed out while waiting for target halted
TARGET: stm32f2xxx.cpu - Not halted
This error crops up in the `monitor reset init` command (and can be
reproduced with `monitor reset halt`).
Why do two exact same ARM chips with the exact same software behave
differently? What could explain that I cannot halt the ARM chip on my new
board?
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
