First post here, so ... hi there! Yesterday I managed to succesfully compile the latest OpenOCD release I took from SVN (revision 1302). I'm using Windows 2003 Server, and compiled that using MinGW/MSYS with hundreds of additional modules (;
I compiled the code just for the RLINK that sits on the STM32 Primer that I got today: > ./bootstrap > ./configure --enable-rlink CC="gcc -mno-cygwin" > make The compilation proces produced an executable that I can execute, but... I cannot connect to RLINK. When I start openocd with commands: > openocd -f interface/rlink.cfg -f target/stm32.cfg > openocd -f interface/rlink.cfg -f board/stm32f10x_128k_eval.cfg > openocd -f interface/rlink.cfg all the time I get the same message in return: > Open On-Chip Debugger 1.0 (2009-01-06-18:35) svn:unknown > > > BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS > > > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ > Error: No device found on bus. running in debug mode gives nothing more - only the init functions are executed, the error is produced by rlink_init() it actually doesn't matter if the Primer is connected or not, powered or not - the msg is always the same. The Primer and it's RLINK work under Ride7, so I guess my problem is situated in software... I've also compiled a version for FTDI based JTAG that I also have, and I think it works fine (I have no target now to check that, but OpenOCD connects to it and tries some various things (; [which fail of course] ) Any hints? Maybe the trunk version I compiled has the RLINK support with some bug? Thx in advance, Freddie Chopin _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
