Dear OpenOCD developer, I would like to do something uncommon with OpenOCD. Instead of connecting to the chip, I'd like to merely detect the chip. The procedure I have in mind would look like this:
1. Start OpenOCD with the probe config file (eg. stlink.cfg ) given as -f parameter. So OpenOCD knows what probe to use, but doesn't know what chip it will find. 2. OpenOCD detects a chip and reports this somehow (eg. write something to stdout). If possible, this action should not be intrusive to the chip (like resetting it). 3. OpenOCD shuts down. Here are some more notes about the procedure: Note 1: It would be nice if OpenOCD doesn't reach the "server" state where I need to setup a Telnet or GDB client to interact with it. I'd be happy to get the chip detection reported in a more convenient way, like getting the chip info on the stdout channel. Note 2: The detection should be non-intrusive to the chip. However, if OpenOCD doesn't find anything, I'd like to have a backup method where OpenOCD tries to find a chip more aggressively (like holding down the nRST pin). I can invoke this other approach myself if needed (so there's no need for OpenOCD to do that automatically). Note 3: At first, I'll just apply this "chip detection" only on STM32 chips with an STLinkV2 or STLinkV3 probe, later on other probes and chips as well. Note 4: Some boards only have an SWD connection (no JTAG). Thank you very much :-) Kind greetings, Kristof Mulier PS: I only have basic user-knowledge about OpenOCD.
_______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
