[Openocd-development] 'main.elf' vs 'main.out' for debug configuration
Hi, My example project does not have a rule to make main.out. I tried to add it but it did not work. Can I use .elf instead of .out in debug configuration for OpenOCD using olimex ARM-USB-TINY? What's the difference between two? Regards Rohit ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
I tried to use OpenOCD with the very basic test setup for my board (thanks to Michael Fischer). Inside the SAM7S256Test folder you will find a file openocd.cfg. This contains all the settings to connect to my target(i.e. Olimex AT91SAM7s256 Board with ARM-USB-TINY(olimex)). Yagarto toolchain is working fine and I was able to use make clean and make all commands to clean and build the project. But the problem comes when I give openocd at cmd line. Michael informed me that on this I should get connected to the Target through OpenOCD. But I get an error message in a new window saying openocd.exe has stopped working and the usual message whether to close, debug or look for a online solution. Am I missing something here. i have attached the zip provided by Michael with the mail. Also the inf files I had modified which were sent sometime back and were found to be Ok. Regards Rohit On Wed, Aug 26, 2009 at 2:36 AM, Freddie Chopin freddie_cho...@op.plwrote: Rohit Chandel pisze: Is there any quick test to find out that openocd is installed correctly? use it. 4\/3!! ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Fwd: OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
Sorry I forgot to attach the files in last mail. -- Forwarded message -- From: Rohit Chandel mygalaxy...@gmail.com Date: Wed, Aug 26, 2009 at 5:53 PM Subject: Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software To: openocd-development openocd-development@lists.berlios.de I tried to use OpenOCD with the very basic test setup for my board (thanks to Michael Fischer). Inside the SAM7S256Test folder you will find a file openocd.cfg. This contains all the settings to connect to my target(i.e. Olimex AT91SAM7s256 Board with ARM-USB-TINY(olimex)). Yagarto toolchain is working fine and I was able to use make clean and make all commands to clean and build the project. But the problem comes when I give openocd at cmd line. Michael informed me that on this I should get connected to the Target through OpenOCD. But I get an error message in a new window saying openocd.exe has stopped working and the usual message whether to close, debug or look for a online solution. Am I missing something here. i have attached the zip provided by Michael with the mail. Also the inf files I had modified which were sent sometime back and were found to be Ok. Regards Rohit On Wed, Aug 26, 2009 at 2:36 AM, Freddie Chopin freddie_cho...@op.plwrote: Rohit Chandel pisze: Is there any quick test to find out that openocd is installed correctly? use it. 4\/3!! ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development SAM7S256Test.7z Description: Binary data ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
On Wed, Aug 26, 2009 at 8:23 PM, Freddie Chopin freddie_cho...@op.plwrote: Rohit Chandel pisze: But the problem comes when I give openocd at cmd line. Michael informed me that on this I should get connected to the Target through OpenOCD. But I get an error message in a new window saying openocd.exe has stopped working and the usual message whether to close, debug or look for a online solution. Instead of the openocd.cfg file inside your project, just open the Command Prompt (anyway you like) and type: openocd -f interface/olimex-jtag-tiny.cfg -f board/olimex_sam7_s256.cfg Then post here the error message you get. On giving openocd -f interface/olimex-jtag-tiny.cfg -f board/olimex_sam7_s256.cfg on command prompt I got the same message: C:\Users\Rohit\SAM7S256Testopenocd -f interface/olimex-jtag-tiny.cfg -f board/olimex_sam7_s256.cfg Open On-Chip Debugger 0.2.0 (2009-07-18-09:50) Release $URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c$ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS A new window opens up after that saying openocd.exe has stopped working and the usual option to check online for solution, close the program or debug the program. Regards Rohit Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
On Thu, Aug 27, 2009 at 12:45 AM, Freddie Chopin freddie_cho...@op.plwrote: Rohit Chandel pisze: A new window opens up after that saying openocd.exe has stopped working and the usual option to check online for solution, close the program or debug the program. something must be seriously broken in that case... sorry, but I have no idea what that could be. what OS you use? I am using Vista(32). But what should I do next. Should I go back to 0.1.0 I am using OpenOCD just for personal use. So do this GPL license issue which has come up recently have any impact on me? As a simple user who just wants to experiment with ARM. I am fed up with this openOCD 0.2.0 not working. I do not bother whether drivers are from FTDI or from any other source. Its almost one month since I started this. I wanted to work on ARM not OpenOCD. I agree a lot of people have tried to help and community is really good but that does not help if at the end I am not able to use openOCD. Please suggest any straight forward tutorial on how to use OpenOCD with old FTDI drivers. Regards Rohit ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
On Mon, Aug 24, 2009 at 9:02 PM, Freddie Chopin freddie_cho...@op.plwrote: 1st of all - write to the list It does have a USB = RS-232 converter. FT2232 is like 2 devices in one chip - one is the JTAG (that's FT2232 channel A), and the other is RS-232 converter (that's FT2232 channel B). Those two devices can (and in this case - should) have different drivers, for example libusb-win32 for JTAG, original FTDI drivers for RS-232 channel. It might seem silly question for an experienced person but please excuse for this. Does that mean that I need to first install the the drivers which came along with the ARM-USB-TINY on a CD and then uninstall the driver for JTAG. And then install libusb-win32 for JTAG alone? Also I am unable to understand for what purpose I need the RS232 converted. My Jtag hardware's(olimex USB TINY) one end goes to USB drive and other goes to jtag socket on ARM board. It does not have an RS232port like the one mentioned here http://www.olimex.com/dev/index.html the inf file is fine, but you need the original drivers for the RS-232 channel. You may of course ignore that channel if you don't need it. Does ignoring means that I should just install the driver only once(for jtag) and on second time when prompted for drivers I should ignore it? Regards Rohit ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
Sorry the link given by me is not a direct one. I meant following device at Olimex website: *ARM-USB-OCD* 3-IN-1 FAST USB ARM JTAG, USB-TO-RS232 VIRTUAL PORT AND POWER SUPPLY 5-9-12VDC DEVICE (SUPPORTED BY OPENOCD OPEN SOURCE ARM DEBUGGER) On Tue, Aug 25, 2009 at 12:52 PM, Rohit Chandel mygalaxy...@gmail.comwrote: On Mon, Aug 24, 2009 at 9:02 PM, Freddie Chopin freddie_cho...@op.plwrote: 1st of all - write to the list It does have a USB = RS-232 converter. FT2232 is like 2 devices in one chip - one is the JTAG (that's FT2232 channel A), and the other is RS-232 converter (that's FT2232 channel B). Those two devices can (and in this case - should) have different drivers, for example libusb-win32 for JTAG, original FTDI drivers for RS-232 channel. It might seem silly question for an experienced person but please excuse for this. Does that mean that I need to first install the the drivers which came along with the ARM-USB-TINY on a CD and then uninstall the driver for JTAG. And then install libusb-win32 for JTAG alone? Also I am unable to understand for what purpose I need the RS232 converted. My Jtag hardware's(olimex USB TINY) one end goes to USB drive and other goes to jtag socket on ARM board. It does not have an RS232port like the one mentioned here http://www.olimex.com/dev/index.html the inf file is fine, but you need the original drivers for the RS-232 channel. You may of course ignore that channel if you don't need it. Does ignoring means that I should just install the driver only once(for jtag) and on second time when prompted for drivers I should ignore it? Regards Rohit ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
Ok, I did it... but how do i make sure that drivers have installed correctly? I used FTClean.exe to remove all FTDI drivers and then installed the new ones. In Device manager under LibUSB-Win32 Devices I have got an entry for Olimex OpenOCD JTAG TINY A. Also in driver Properties- Driver details it shows driver files: C:\Windows\system32\drivers\libusb0.sys C:\Windows\system32\drivers\libusb0.dll Is there any quick test to find out that openocd is installed correctly? regards rohit On Tue, Aug 25, 2009 at 9:41 PM, Freddie Chopin freddie_cho...@op.plwrote: Rohit Chandel pisze: It might seem silly question for an experienced person but please excuse for this. Does that mean that I need to first install the the drivers which came along with the ARM-USB-TINY on a CD and then uninstall the driver for JTAG. And then install libusb-win32 for JTAG alone? In your earlier post you provided a link to .pdf for the JTAG with RS-232. Now I know that you version (-TINY) doesn't have that interface. You should do exactly as it's said in the .inf file for OpenOCD: ; Devices which use only the first channel (JTAG only) should have TWO entries ; for BOTH channels. Amontec JTAGkey is an example. ... Amontec JTAGkey (Channel A)=LIBUSB_DEV, USB\VID_0403PID_cff8MI_00 Amontec JTAGkey (Channel B)=LIBUSB_DEV, USB\VID_0403PID_cff8MI_01 Do the same for your JTAG and the drivers part will be done. 4\/3!! ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY - unable to find driver software
Hi, I have installed OpenOCD 0.2.0 through the windows installer (found at http://www.freddiechopin.info/) in the default location C:\Program Files\OpenOCD\ Then I extracted the ft2232.zip inside C:\Program Files\OpenOCD\0.2.0\drivers\ft2232. I removed giveio.zip and rlink.zip. So now C:\Program Files\OpenOCD\0.2.0\drivers\ft2232 folder contains 1. libusb0.dll 2. libusb0.sys 3. libusb-win32_ft2232_driver.inf ( modified to specify Olimex ARM-USB-TINY. See attached zip file ) I replaced Board and Target folders with the folders (attached in the mail). That means now 'C:\Program Files\OpenOCD\0.2.0\board' folder contains only one file 'olimex_sam7_s256.cfg' ( contained in .zip file) and 'C:\Program Files\OpenOCD\0.2.0\target' folder contains only 'sam7s256.cfg' (contained in .zip file ) Then I connected the Olimex ARM-USB-TINY hardware to the PC. When it prompted to locate the driver I manually gave the path 'C:\Program Files\OpenOCD\0.2.0\drivers' First time it tells that drivers are loaded successfully and it prompts again for the location of the driver. I gave the same location again but it says 'could not find the driver software' for this device. Regards Rohit 0.2.0.rar Description: Binary data ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
