Hi, thanks for your reply.
The following is the approach I currently working on. I use MATLAB and Simulink for algorithm development. Using Simulink and Real-Time Workshop Embedded Coder (tool to automate C-Code generation from Simulink models) I generate code and compile and link it within MATLAB to get the *.elf product. However I always need to launch the external IDE from Hitex to download the product on the target. The reason I want to use OpenOCD is to automate the entire workflow. However before I start working on OpenOCD I need to get an idea about the complexity and if it really will result in an easy to use download command line interface. This is what I need to investigate first. Every comments welcome. Best, -David -----Original Message----- From: Uwe Hermann [mailto:[email protected]] Sent: Thursday, March 19, 2009 3:00 AM To: David Lange Cc: Subject: Re: [Openocd-development] OpenOCD flash programming STR9-comStick Hi, On Mon, Mar 16, 2009 at 12:01:44PM +0000, David Lange wrote: > I found OpenOCD to be a free and command based flash programming tool. I > currently have a project running using the Hitex USB stick STR9-comStick. > However so far I only was able to download the application using the IDE > HiTop. What I am looking for is a tool to automate this via the command line. > In the OpenOCD pdf-documentation I found that on page 9 the link to the > comstick is exactly the device that I use. > > Does anyone have experiences using OpenOCD in combination with the > STR9-comStick? I have such a device here, but didn't test much so far. What you generally want is to start OpenOCD like this (for example): $ openocd -f /usr/lib/openocd/interface/str9-comstick.cfg -f /usr/lib/openocd/target/str9comstick.cfg Open On-Chip Debugger 1.0 (2009-03-12-01:10) svn:r1409 BUGS? Read /usr/share/doc/openocd/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ 3000 kHz Runtime error, file "/usr/lib/openocd/target/str9comstick.cfg", line 19: can't read "_CHIPNAME": no such variable However, as you can see this currently results in an error (as of r1409), I guess this needs to be fixed in svn. I didn't have the time to investigate the issue further, yet. Assuming the OpenOCD connection works, you use 'telnet localhost 4444' to connect to OpenOCD via telnet, where you can the use all commands available. HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
