Home
Welcome to Chopin's homepage!
OpenOCD 0.2.0 - service release 1
Written by Freddie Chopin   
Saturday, 29 August 2009 15:41

OpenOCD installer of version 0.2.0 which was available in the Download section was replaced with version 0.2.0-SR1, which stands for service release 1. The most important component of the installer - executable file openocd.exe was not modified, it is still basic 0.2.0 version. Changes were made only to the included libusb-win32 drivers for FT2232 based JTAGs. Currently the driver has entries for most of existing JTAGs based on that chip. Additionally a text file info.txt is included in the drivers archive - it describes the details of libusb-win32 driver usage with FT2232 based JTAGs. The change was motivated by problems that users were experiencing with these drivers.

Reinstallation is recommended to those who own a JTAG using FT2232 and were not able to get past the drivers installation process.

Last Updated on Saturday, 29 August 2009 16:14
 
JTAG-lock-pick manual
Written by Freddie Chopin   
Thursday, 20 August 2009 17:06

Finally I've found some time and finished the complete JTAG-lock-pick manual. Effects of my (long lasting) work can be downloaded in Download > Projects > JTAG-lock-pick (Polish only!). You all had to wait a while for that document, but... better now than never (; .

On the 29 pages you can find:

  • description of the project - it's functionality, motives for creation and guidelines of its design,
  • technical descripton of the circuit - its elements, PCB, case, various versions, connectors,
  • drivers installation and EEPROM programming description,
  • details about JTAG usage - LEDs and jumpers,
  • hints about using JTAG with OpenOCD or CrossWorks,
  • a few less important (but still useful) details,
  • circuit schematics,
  • bill of materials.

This file replaces the documents published earlier: the "ultra short manual", circuit schematics and bill of materials as separate files.

Post all opinions, comments, suggestions, info about mistakes and nonsenses as a comment here of via the contact form.

Last Updated on Thursday, 20 August 2009 17:59
 
OpenOCD 0.2.0 - Windows installer
Written by Freddie Chopin   
Saturday, 18 July 2009 12:52

In Download > Software > OpenOCD you can find OpenOCD 0.2.0 compiled for Windows in a convenient form of msi installer (Microsoft Installer). OpenOCD can communicate with ARM cores via many different ARM JTAGs and it can be used in any opensource toolchain which uses GDB for debugging.

Due to alleged GPLv2 license incompatibility of using ftd2xx.dll libraries, this version was compiled to use libftdi + libusb-win32 libraries. Details: #1, #2. That's why the previous version (0.1.0) was removed from this website.

It is recommended to uninstall the previous version before proceeding with 0.2.0.

Last Updated on Thursday, 20 August 2009 17:23
 
Example ARM projects
Written by Freddie Chopin   
Friday, 12 June 2009 12:17

In Download > ARM > Examples there are two example Eclipse projects - one for NXP LPC2103 and another for ST STM32F103RB. These examples (in my assumption) are an addition to ARM toolchain - tutorial article, so the schemes presented there are also present in the code and projects. All basic files - Makefile, linker script, startup, vector table - can be found inside the projects. Also predefined debugging shortcuts (External Tool and Debug Configuration) are available. In the code, beside blinking the LED, there are some basic system initialization routines - enabling all Flash accelerators and configuring the PLL to achieve max core speed. In the doc/ folder the projects include complete Doxygen generated documentation, which makes it easier to modify the code for different configurations.

Makefile attached to the examples requires a few GNU Coreutils files (beside make: echo, mkdir, rm, sh) for all features to work fully. Windows installer with those basic files can be found in Download > Programs > Coreutils. Those files are also available in WinAVR toolchain. Without those files it is necessary to create an output directory in the project tree (default name for that directory can be found in the Makefile in the line OUTPUT_DIR = ./out/ ) or to compile directly into the main project's directory (output directory should be configured as - OUTPUT_DIR = ).

Post all comments on these examples and the GNU Coreutils package as a comment to this article, throught the contact form of this page or in a topic on elektroda forum about these examples. If anyone is interested in helping me to create similar examples for other chips with ARM core (AT91SAM, ADuC, STR7, STR9, LM, ...) - contact me too, I will help as much as I can.

Last Updated on Friday, 12 June 2009 15:43
 
ARM toolchain - tutorial
Written by Freddie Chopin   
Sunday, 17 May 2009 16:36

Bez zb?dnego lania wody przejd?my do rzeczy... Do wygodnego tworzenia oprogramowania dla ARMów potrzeba nam:

  • edytora (IDE),
  • toolchaina (kompilator, assembler, linker, binutils, biblioteki, ...),
  • oprogramowania do debuggowania.

Edytor (IDE)

W roli edytora lub IDE dla ARMów spotykany jest zwykle jeden z dwóch programów - Programmers Notepad albo Eclipse. Poza tymi dwoma mo?liwe jest oczywi?cie zastosowanie wielu innych aplikacji, takich jak cho?by CodeBlocks lub DevC++. Poniewa? moim zdaniem ogromne mo?liwo?ci i du?a popularno?? Eclipse rekompensuj? jego niewielkie wady (jest napisany w Javie, wi?c czasem potrafi si? przyci??), tutorial ten bazowa? b?dzie w?a?nie na Eclipse. ?rodowisko Eclipse umo?liwia nam pisanie kodu, zarz?dzanie projektem, programowanie uk?adu oraz jego debuggowanie - czego chcie? wi?cej? (;

ARM toolchain

Na chwil? obecna dost?pnych jest wiele kompletnych i gotowych toolchainów dla ARMa - jedne s? na wiele platform, inne tylko na jedn?. Warto wymieni? takie pakiety jak WinARM, GNUARM i Yagarto. Tutorial ten jednak oparty b?dzie jednak o inne rozwi?zanie, a mianowicie o Sourcery G++ Lite pochodz?ce z CodeSourcery. Dlaczego? Przede wszystkim istotne jest to, ?e rozwój toolchaina firmy CodeSourcery jest sponsorowany przez ARM Ltd., dzi?ki czemu jest on zawsze najbardziej zgodny ze standardami ARM, a usprawnienia wprowadzane s? najszybciej - dopiero po pewnym czasie trafiaj? one do oficjalnej dystrybucji GCC, a stamt?d dopiero do innych toolchainów. Poza tym warto nadmieni?, ?e toolchain ten jest dost?pny zarówno dla platformy Windows jak i Linux, obs?uguje instrukcje typu ARM, Thumb i Thumb-2 oraz najnowsze architektury ARMów - takie jak cho?by Cortex. Nowe wersje toolchaina od CodeSourcery wydawane s? w pó?rocznych odst?pach.

Oprogramowanie do debuggowania

Debugger GDB (GNU Debugger) potrzebuje tak zwanego "klienta GDB", który przyjmowa?by i wykonywa? jego rozkazy. W ?wiecie ARMów rol? t? doskonale spe?nia OpenOCD, które równie? jest aplikacj? wieloplatformow?. Obecnie OpenOCD obs?uguje praktycznie wszystkie istniej?ce JTAGi do ARMa (m.in. klony Wigglera (LPT), uk?ady oparte o FT2232 (USB), JLink, RLink i wiele innych) oraz wi?kszo?? istniej?cych rodzajów ARMów (w tym ARM7, ARM9 i Cortex-M3).

Instalacja krok po kroku...

Poni?szy tutorial oparty jest o system Windows, niemniej jednak nie ma ?adnego problemu, aby porady tu przedstawione zastosowa? dla systemu Linux (oczywi?cie nie dos?ownie).

Last Updated on Friday, 12 June 2009 11:31
 
«StartPrev12345678910NextEnd»

Page 8 of 10