New more compact design of ARM-USB-OCD-H(L) is released with USB-C connector

ARM-USB-OCD-H is very popular OpenOCD debugger supported by almost all IDEs and platforms. It’s in the Application notes of Intel and ARM processor vendors.

The ARM-USB-OCD-H initial design was made many years ago and some parts are obsolete like the USB-B to USB-A cable, big plastic shell from centronic 36/36 connectors etc.

As the centronic plastic became unavailable this year we decided that it’s good time to re-design ARM-USB-OCD-H completely.

Smaller and more compact plastic box is used. The USB connector now is USB-C, so popular USB phone cables can be used.

Our recommendation is customer to move to ARM-USB-OCD-HL it’s completely same as ARM-USB-OCD-H but supports targets with voltage levels from 0.65-5.5V

The popular Olimex ARM OpenOCD JTAG programmer debugger ARM-USB-OCD-H gets better, now has a modification which works with targets from 0.65 up to 5.5V

ARM-USB-OCD-H is a low-cost ARM OpenOCD debugger. It supports targets from 1.65V up to 5.0V. Many SOC manufacturers like Intel, Intel/Movidius, nVidia and others use it in their development work. Intel quotes ARM-USB-OCD-H and ARM-JTAG-20-10 in their appnote “Source Level Debug using OpenOCD/GDB/Eclipse on Intel® Quark™ SoC X1000”.

A few month ago we got an interesting question. A new SOC manufacturer was trying to debug their SOC with ARM-USB-OCD-H, but the problem was that their target was working on 1.2V. They asked us if we could modify our JTAG to be able to work at lower than 1.65V targets.

Our engineers identified a couple of components which we could upgrade to support lower voltages. The final result was that the ARM-USB-OCD-HL new modification of the JTAG can now work with targets from 0.65V up to 5.5V.

This pretty much covers all existing SOCs on the market.

Tutorial: Running micro-ROS on STM32-E407 with JTAG

via Twitter we noticed this tutorial with step by step instructions how to build configure and program STM32-E407

Appnotes and Tutorials about Debugging UEFI and Linux Kernel on Intel SoCs with OpenOCD and ARM-USB-OCD-H or ARM-USB-TINY-H

Intel made nice video tutorial how to use OpenOCD and our JTAGs with their SoCs! This explains the frequent purchases they do from many Intel locations all around the world of ARM-USB-TINY-H , ARM-USB-OCD-H and ARM-JTAG-20-10.

Searching bit more there is application note How to setup ARM-USB-OCD-H with Intel Quark SoC X1000 and tutorials about Low-cost UEFI debugging options for Intel and How to debug Linux Kernel on Intel Quark

ESP8266-EVB support for JTAG development with flash load, breakpoints, disassembly, step debugging in Visual Studio C/C++

Ivan Shcherbakov @SysProgs shared interesting article. He wrote support for ESP8266-EVB to VisualGDB Visual Studio plugin for embedded software development in C/C++.

With this plugin you can use JTAG to debug code in ESP8266, also to set breakpoints, view the disassembled code etc. This adds new level for professional developing using ESP8266.

FRIDAY FREE BOARD QUIZ ISSUE #14 PRIZE IS ARM-JTAG-COOCOX

If you still didn’t heard CooCox IDE is complete FREE ARM Cortex development environment with editor, compiler, debugger. It’s made by few open source fans who work in Wuhan University in China in their spare time.

CooCox IDE does absolutely the same what other expensive commercial IDEs offer, so not wonder that it’s platform of choice for many big names in the semiconductor industry.

ARM-JTAG-COOCOX is an ARM debugger based on CoLinkEX design. It is meant to work out-of-the-box with the free CooCox IDE.

It can also be used with Keil MDK and IAR EW IDEs via external plugins, but the driver for IAR is still not perfect knowing from our own experience with ARM-JTAG-EW how cooperative IAR is for their drivers we suspect the CooCox team made the same we did – their driver is based on reverse engineering.

ARM-JTAG-COOCOX is fast and affordable and the ability to debug via both SWD (Serial Wire Debug) and JTAG interfaces are the key points.

Today at 17.00 o’clock our local Bulgarian time (GMT+3) we will post on Twitter our question.

You have one hour to reply to our tweet with the correct answer.

At 18.00 o’clock we will count the correct answers and ask random.org to generate random number in range then anнounce the winner and ship the board by airmail next Monday.

Good luck!

New Product: ARM-JTAG-COOCOX

CooCox is highly integrated and free ARM Cortex-M0-3-4 development IDE with compiler, debugger and lot of code examples.

CooCox supports our OpenOCD ARM-JTAG-TINY-H, ARM-USB-OCD-H and ARM-JTAG-SWD ARM-JTAG-2010 adapters, so our customers could work with CooCox IDE with our current JTAGs.

What we missed in our product range though was the designed by CooCox team own JTAG adapter with build in support for SWD and fast programming.

This is why we built ARM-JTAG-COOCOX it’s open source hardware and software JTAG which is supported out of the box by CooCox IDE, so you can fast program and debug your code with CooCox IDE.

At EUR 24.95 ARM-JTAG-COOCOX is fast, reliable and completely open source product.

CooCox IDE generally gives you the same what commercial IDE vendors provide and sell for thousands of euro, but it’s completely free, so you should definitely give it a try when you make your next ARM project.

MSPDEBUG – Power profiling with the MSP430-JTAG-ISO-MK2

MSP430-JTAG-ISO-MK2 has power profiling functionality which can be used from MSPDebug. When a chip is running, the debugger continuously captures current consumption and MAB (program counter) samples, which can be read and analysed.

As of 4 Oct 2012, MSPDebug contains support for the following power profiling functionality:

• Basic statistics (average current, run time, charge consumption).
• Time-domain analysis, including exporting of raw samples to CSV format.
• Disassembly annotations, which show power consumption on a per-instruction basis.
• Hotspot/profile analysis to discover which functions are consuming the most power.

The driver for this device supports both raw USB and tty access, and can be used to perform firmware updates.

MSPDEBUG is open source tool, for debugging MSP430 microcontrollers. The project is hosted on Sourceforge 

The next logical step is to create IDE with MSPGCC+Eclipse+MSPDEBUG plugin for one completely free development environment for MSP430 supporting all MSP430 devices and JTAGs on the market +  Power Profiling feature if you use MSP430-JTAG-ISO-MK2. The IDE will support Linux and Windows and we hope to be able to demonstrate it at Electronica 2012 in November.

Friday’s Free Board Quiz ISSUE #4 Prize is ARM-USB-TINY-H

Time is fly so fast when you are on vacation 😉 It’s Friday again and time for our next Quiz ISSUE#4

Today the quiz prize is ARM-USB-TINY-H (USB HIGH Speed) OpenOCD JTAG debugger. With it you can program and debug almost any ARM device and with the recent development made by Sergey Vakulenko EJTAGPROXY http://code.google.com/p/ejtagproxy/ you can also program and debug MIPS cores like PIC32 but you have to make special cross-cable.

You can win this board if you answer correctly to our question today.

The conditions are still same: At 17.00 o’clock our local Bulgarian time (UTC/GMT+3) we will post question on Twitter, you have to reply to our Tweet with the correct answer.
At 18.00 o’clock we will count the correct answers and ask at random.org for random number in this range, then anounce the winner.

Good Luck to everyone!

A13-OLinXino JTAG works

A13 documentation is very brief and so far we found inside ton of errors, to me it looks like somebody wrote this document in hurry with copy and paste from A10 (also brief) documentation.

This may be shock for somebody of Western world but seems pretty normal for Chinese SoC vendor as their model is to sell not chips but solutions i.e. their customers (the consumer electronics manufacturing companies) do not do any design work on their sites, Allwinner sell them processors, pre-routed PCBs, pre-build Android and Linux images with all features enabled, so they just manufacture and spend no resources to develop.

What I found very useful with the Android A13-SDK image which we got from Allwinner is that there you have kernel configuration text script where you can define every processor feature as port functions, CPU voltages, times, DDR3 organization, timing, etc etc you name it and when the board reboots the bootloader read this script and pre-configure your kernel on the fly, no need to re-compile kernels and you ork with the newest Kernel 3.x available. So in this situation Allwinner customers never need decent datasheet at all because all development is already done for them by Allwinner. This explains why they do not bother to spend time to release proper dcumentation too.

We actually did the very first A13 design which is made outside Allwinner, but this leave us to explore A13 features by ourself, which is not so bad by the way, we feel like the pioneers of the wild west.

Today Henrik Nordstrom (who got one of the very first prototypes) send me message that he successfully run OpenOCD with A13 and can debug with ARM-USB-TINY-H adapter I sent him with the A13-OLinuXino, so in the next revision of the board we will break out the JTAG signals on separate connector.

Here is the A13 GPIO description we have so far http://linux-sunxi.org/A13/PIO

Note that SD card share UART0 and JTAG signals this means if you have no internal NAND will be hard to debug Linux as SD card will be used to boot the Linux image.

UART0 can be enabled to be used for the console.