Home
Welcome to Chopin's homepage!
JTAG-lock-pick Tiny 2 - done!
Written by Freddie Chopin   
Monday, 29 October 2012 12:32
Whole thing took a little more time than expected (as usually [; ), but finally everything is ready! I introduce you the final version of the new project - JTAG-lock-pick Tiny 2!

JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
JTAG-lock-pick Tiny 2
 

JTAG-lock-pick Tiny 2 in brief:

  • USB 2.0,
  • max TCK 30MHz,
  • support for RTCK,
  • support for SWD,
  • target voltage 1.4 - 3.6V,
  • two separate reset lines, each independently configured as PP or OD,
  • small size (whole device about 53 x 33mm),
  • "case" made of transparent heat-shrink tube.

Key assumption was to desing the device to be small, cheap but at the same time functional. Compared to JTAG-lock-pick 1.x.x new version does not have some bonus features - UART, RS-232 and powering of target via JTAG, so it's reasonable to say that it's "just a JTAG". More details coming soon! If someone is really impatient I encourage him/her to contact me now (;

Next project - JTAG-lock-pick 2 (without "Tiny") (;

Last Updated on Monday, 29 October 2012 13:54
 
New OpenOCD version 0.6.1
Written by Freddie Chopin   
Saturday, 13 October 2012 16:02

Because of huge amount of obligations (and a little bit of rest in a form of climbing trip [; ) I did not publish any info about release of OpenOCD version 0.6.0, which took place at the beginning of September. As it turned out later (after getting back from the trip) it wasn't so bad, as this version contained a serious regression, which was introduced somewhere between 0.6.0-rc1 and 0.6.0-rc2. To cut things short, the problem manifested itself in the fact that some operations worked correctly only on the first try, all subsequent tries failed - this is what happened when trying to flash something to LPC17xx/LPC2xxx chip. Those interested may find some more info on OpenOCD's mailing list and in the news about fixed version on project's website.

So, soon after the regression was discovered, a new bugfix version 0.6.1 was published, which brought back correct behavior of these functionalities that were affected by the bug. As usually I have provided a binary version for Windows (both 32- and 64-bit version) in Download > Software > OpenOCD section. By the way - because of recurring questions - these packages since 0.5.0 (inclusive) are not available in the form of installer, only as a compressed archive with everything that is needed. So it's not possible to install them (as written in my article about toolchain), it's enough to extract them anywhere and execute the binary using full path. Creating an installer was too much hassle for completely no benefit it gave (;

What interesting changes does new version of OpenOCD bring? A lot! I don't know where to start, so I'm going through some more significant things from the list which you may find in the news about new version on project's website.

  • OpenOCD supports ST-LINK interface (probably best known from Discovery series of development boards) - both older (V1) and newer variant (V2). By the way it's worth noting that with these interfaces it's possible to debug targets via SWD.
  • New, currently a bit experimental, driver was introduced for interfaces based on FTDI chips from FTx232 series, so probably the most popular interfaces used with OpenOCD (like well-known JTAG-lock-pick 1 and coming-very-soon JTAG-lock-pick Tiny 2). This driver uses libusb-1.0 library in asynchronous mode in place of libftdi + libusb-0.1, which results in it's great performance - detailed comparison can be found here, in brief the speed gain may reach as high as 500%! Configuration files using this new driver can be found in interfaces/ftdi folder - they're worth trying, but before tests you need to change the driver for your JTAG to the one using libusb-1.0 (a short description of the process for Windows can be found in the package with binary version, in the drivers\libusb-1.0 drivers.txt file).
  • Support for debugging RTOSes - currently working with Linux, FreeRTOS, ThreadX and eCos.
  • Asynchronous flashing algorithm for selected targets (STM32, Stellaris and PIC32), which - of course - results in speed gain.
  • ...
I highly encourage to download and use the most recent version, especially people who downloaded version 0.6.0 (now removed from website) should upgrade.

Last Updated on Saturday, 13 October 2012 17:32
 
Another "next level"
Written by Freddie Chopin   
Tuesday, 03 July 2012 21:38

It's been a while since anything happended on the site, so it's high time to share some secrets (; What do you say?

JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
  

EDIT (2012.07.08):

A few more photos that add some "scale" to the case (;

JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
JTAG-lock-pick 2 Tiny
 

Last Updated on Sunday, 08 July 2012 09:16
 
Two new examples - STM32F4 and LPC1769
Written by Freddie Chopin   
Saturday, 07 April 2012 15:21

Source code examples for LPC1114LPC2103STM32 and STM32CL available in Download > ARM > Examples were joined by two new projects, written for "super-fast high-end" MCUs - one for STM32F4 (new chips from ST, Cortex-M4F core with integrated floating point unit, 168MHz) and second one for LPC1769 (Cortex-M3, 120MHz).

These examples are both configured for linaro toolchain. In case of STM32F4 example it is not possible to use CodeSourcery toolchain, because it lacks libraries supporting floating point coprocessor. LPC1769 example - due to lack of high-end fancy stuff in Cortex-M3 core - can be used on any toolchain available.

STM32F4 example is configured for STM32F4DISCOVERY board, which has an embedded ST-LINK/V2 interface, so for debugging it requires development version of OpenOCD, from these available on this website in Download > Software > OpenOCD dev - at least from February 2012 (OpenOCD 0.6.0-dev-120229143915 / 0.6.0-dev-00448-gc59a441 or 64-bit version) - previous versions, including "stable" 0.5.0, don't support this interface.

It's also a good idea to remind that for proper operation of the examples GNU Coreutils have to be installed in the system (Windows installer is available in Download > Software > Coreutils). This information is provided above the examples, but some people miss it anyway... (; This time it is even more important, as Windows package of linaro toolchain does not contain make executable. It is also worth noting that Coreutils and toolchain must not be installed in a path that contains brackets (so "Program Files (x86)" in 64-bit systems is out of the question).

Taking the occasion, I'll also write that STM32F4DISCOVERY modules (and other...) can be bought from DISTORTEC for a very good price, better (that means "lower") than on allegro! If someone would be interested in buying one of these (of course with a receipt / invoice) - contact me here or there (; .

Last Updated on Monday, 09 April 2012 11:24
 
DISTORTEC launches!
Written by Freddie Chopin   
Thursday, 02 February 2012 19:27

Yesterday, on the first day of February, on a very frosty Wednesday (-20deg in the morning!), my firm named DISTORTEC started. The profile of business activity is obviously obvious - electronics (; . There is already a domain and temporary website - www.distortec.com (or .pl). People / companies interested in cooperation are invited to contact me, but if you're interested in buying an ARM JTAG described on this page (currently available "in stock", only Polish description at the moment) feel free to contact me too. The purchase of JTAGs (or any future products [there are many ideas]) or services will be documented by VAT invoice, so (in case of companies) the expense reduces income and VAT tax can be deducted. For now - since there is no web shop available at this moment - you can reach me via e-mail address This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Keep your fingers crossed and - as usual - stay tuned! (;

Last Updated on Thursday, 02 February 2012 19:49
 
«StartPrev12345678910NextEnd»

Page 4 of 10