Comments for Open On-Chip Debugger http://openocd.sourceforge.net Free and Open On-Chip Debugging, In-System Programming and Boundary-Scan Testing Wed, 03 May 2006 13:12:43 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Back from Fosdem, OpenOCD updates, AT91SAM7 support, … by Pawel http://openocd.sourceforge.net/2006/03/back-from-fosdem-openocd-updates-at91sam7-support/#comment-110 Pawel Wed, 03 May 2006 13:12:43 +0000 http://openocd.berlios.de/web/?p=32#comment-110 Hi, OpenOCD connetcts to my AT91SAM7S256, "flash info 0" prints sane values, I played with mdw, mww commands. I used remap command by (mww 0xFFFFFF00 1). It works!. (I don't have time to flash now, but I'm sure it will work :P) Ah, I use cheap one wiggler-clone and It has to have a short cable (long doesn't work... ) Hi,

OpenOCD connetcts to my AT91SAM7S256, “flash info 0″ prints sane values, I played with mdw, mww commands. I used remap command by (mww 0xFFFFFF00 1). It works!. (I don’t have time to flash now, but I’m sure it will work :P )

Ah, I use cheap one wiggler-clone and It has to have a short cable (long doesn’t work… )

]]> Comment on CFI Flash support by Administrator http://openocd.sourceforge.net/2006/01/cfi-flash-support/#comment-20 Administrator Sun, 19 Feb 2006 21:49:04 +0000 http://openocd.berlios.de/web/?p=26#comment-20 Hi, if it's cfi compatible flash using the Intel commandset it should work. You don't have to install anything else. Just add a line to the configuration file specifying the external flash: flash bank cfi 0x80000000 0x400000 2 2 0 0x40000000 0x4000 The above line configures OpenOCD to use the external flash on my Olimex H2294 board, with a single 16-bit wide 4MB Intel flash located at chipselect 0. The flash writing algorithm uses 16kb of on-chip internal sram located at 0x40000000 to accelerate flash writing. Hi,

if it’s cfi compatible flash using the Intel commandset it should work. You don’t have to install anything else. Just add a line to the configuration file specifying the external flash:
flash bank cfi 0×80000000 0×400000 2 2 0 0×40000000 0×4000

The above line configures OpenOCD to use the external flash on my Olimex H2294 board, with a single 16-bit wide 4MB Intel flash located at chipselect 0. The flash writing algorithm uses 16kb of on-chip internal sram located at 0×40000000 to accelerate flash writing.

]]> Comment on CFI Flash support by branek http://openocd.sourceforge.net/2006/01/cfi-flash-support/#comment-19 branek Sun, 19 Feb 2006 21:36:38 +0000 http://openocd.berlios.de/web/?p=26#comment-19 Hello, I am newbee in JTAG debuging, so I want to ask one question... Is it possible to program External flash connected to LPC2292 with OpenOCD via wiggler interface. If it is possible what I should install among OpenOCD packet! thanx Hello,

I am newbee in JTAG debuging, so I want to ask one question…
Is it possible to program External flash connected to LPC2292 with OpenOCD via wiggler interface.

If it is possible what I should install among OpenOCD packet!

thanx

]]> Comment on OpenOCD and the Amontec JTAG Accelerator by Administrator http://openocd.sourceforge.net/2006/01/openocd-and-the-amontec-jtag-accelerator/#comment-18 Administrator Fri, 10 Feb 2006 16:10:36 +0000 http://openocd.berlios.de/web/?p=24#comment-18 Thanks for your comment, I'll look into this a bit closer. In my test I've never achieved more than about 160kByte/s. Thanks for your comment, I’ll look into this a bit closer. In my test I’ve never achieved more than about 160kByte/s.

]]> Comment on OpenOCD and the Amontec JTAG Accelerator by Radoslaw Szczygiel http://openocd.sourceforge.net/2006/01/openocd-and-the-amontec-jtag-accelerator/#comment-17 Radoslaw Szczygiel Fri, 10 Feb 2006 15:07:41 +0000 http://openocd.berlios.de/web/?p=24#comment-17 It is realy possible to download to RAM about 370Kbyte/s using DCC in EPP mode. I'm end writing Amontec JTAG Accelerator driver for http://sourceforge.net/projects/jtagarmgdbsrvr/ project and it work very well and speedy. It is realy possible to download to RAM about 370Kbyte/s using DCC in EPP mode. I’m end writing Amontec JTAG Accelerator driver for http://sourceforge.net/projects/jtagarmgdbsrvr/ project and it work very well and speedy.

]]> Comment on Documentation by Sergei Gavrikov http://openocd.sourceforge.net/documentation/#comment-16 Sergei Gavrikov Fri, 10 Feb 2006 12:07:14 +0000 http://openocd.berlios.de/web/?page_id=3#comment-16 It looks like that you'd maden the best open source branch of OCD. Thanks a lot for your job! Sergei Gavrikov It looks like that you’d maden the best open source branch of OCD. Thanks a lot for your job!

Sergei Gavrikov

]]> Comment on LPC2000 flash writing improved by Administrator http://openocd.sourceforge.net/2006/01/lpc2000-flash-writing-improved/#comment-11 Administrator Thu, 02 Feb 2006 10:14:35 +0000 http://openocd.berlios.de/web/?p=23#comment-11 Adding support for different flash types is rather straight forward. The lpc2000 shows how flash programming using on-chip routines can be achieved, while the cfi flash uses either memory accesses (slow) or short hand-coded assembler routines that are copied to the target and executed there (fast). The code has been compiled and debugged using GNU/Linux, though GNU/Cygwin on Windows works as well. The GNU autotools are used to configure the source tree and generate make files, the GNU compiler collection (GCC) is used to compile the code, and the GNU Debugger (GDB) is used to debug problems. Adding support for different flash types is rather straight forward. The lpc2000 shows how flash programming using on-chip routines can be achieved, while the cfi flash uses either memory accesses (slow) or short hand-coded assembler routines that are copied to the target and executed there (fast).

The code has been compiled and debugged using GNU/Linux, though GNU/Cygwin on Windows works as well. The GNU autotools are used to configure the source tree and generate make files, the GNU compiler collection (GCC) is used to compile the code, and the GNU Debugger (GDB) is used to debug problems.

]]> Comment on LPC2000 flash writing improved by Thomas http://openocd.sourceforge.net/2006/01/lpc2000-flash-writing-improved/#comment-10 Thomas Thu, 02 Feb 2006 10:03:37 +0000 http://openocd.berlios.de/web/?p=23#comment-10 Hello, I just can accross this on Amontec web-side, as I just bought there JTAG interface. Now I wonder if it would be difficult to add FLASH programming support for other ARM7 devices (e.g. Atmel SAM7) to your software? Can you give some advice on that? What tools did you use to compile and debug your code? What would be the best way to start with that? Best regards, Thomas Hello,

I just can accross this on Amontec web-side, as I just bought there JTAG interface. Now I wonder if it would be difficult to add FLASH programming support for other ARM7 devices (e.g. Atmel SAM7) to your software? Can you give some advice on that? What tools did you use to compile and debug your code? What would be the best way to start with that?

Best regards,
Thomas

]]> Comment on Repository by Jochen Schröder http://openocd.sourceforge.net/repos/#comment-7 Jochen Schröder Wed, 01 Feb 2006 08:31:43 +0000 http://openocd.berlios.de/web/?page_id=15#comment-7 Welche Controller wird man noch programmieren können? Ist der STR7 von ST auf der Liste? Welche Controller wird man noch programmieren können?
Ist der STR7 von ST auf der Liste?

]]> Comment on OpenOCD and the Amontec JTAG Accelerator by Administrator http://openocd.sourceforge.net/2006/01/openocd-and-the-amontec-jtag-accelerator/#comment-6 Administrator Wed, 18 Jan 2006 18:17:34 +0000 http://openocd.berlios.de/web/?p=24#comment-6 I checked the quatech site, and they claim that their device should behave "exactly like a computer’s native parallel port". It also seems that you can configure these devices to use one of the standard parallel port I/O locations (like 0x378). So basically yes, it should work. Especially the Wigglers require a parallel port that behaves "normal" - you'll have to test this device to find out if it works. I checked the quatech site, and they claim that their device should behave “exactly like a computer’s native parallel port”. It also seems that you can configure these devices to use one of the standard parallel port I/O locations (like 0×378). So basically yes, it should work.
Especially the Wigglers require a parallel port that behaves “normal” – you’ll have to test this device to find out if it works.

]]>