Designed for ARM Cortex-M processors, CooCox CoFlash is a free desktop application that facilitates methods to help you view, edit and program micro-controllers. It features a graphical. CooCox ColinkEx USB Driver is developed by coocox.org. The current user reach of this app is about 0.0002% of all PC users, however this reach has declined from a lifetime average of 0.0024%. The current version is 1.2.1 with 3 known versions. The most widely installed version is 1.2.1.

FEATURES

• First on market three-in-one USB JTAG debugger - offers JTAG + RS232 (full modem signals supported) port + power supply all in one compact device
• Adds virtual RS232 port to your computer with all modem signals like: DTR, DSR, DCD, RTS, CTS, Rx, Tx
• Debugs all ARM microcontrollers with JTAG interface supported by OpenOCD
• Can be used to power your target board with three jumper-selectable power supplies: 5V, 9V and 12VDC; USB source current is limited with resetable fuse at 300mA, at the different output voltages the maximum current is different: 5V/200mA, 9V/100mA, 12V/70mA, note that this also depends on your USB host current capabilities, if other USB devices are attached to your computer or if the laptop is running on batteries these figures may be different and would depend on your computer USB host. Cable for the external powering included - 2.1x5.5x14mm female connectors at both ends
• Uses ARM's standard JTAG connector (2 rows × 10 pins at 0.1' step)
• Supports ARM targets working in voltage range 2.0 – 5.0 V DC
• Supported by the open-source community and OpenOCD debugger software
• Downloadable Windows installer for full featured and open source tools as alternative to the commercial ARM development packages: GCC C compiler, OpenOCD debugger and Eclipse IDE.
• Works with IAR EW for ARM via GDB server
• Works with Rowley Crossworks IDE
• Works with CooCox IDE
• Supported in Windows, Linux and Mac
• Dimensions 50x40mm ~ (2x1.6)' + 20cm ~ 8' JTAG cable - ribbon cable included

SOFTWARE

• Additional resources: tutorials, instructions, demo software, customer projects, older drivers and more might be found at the wiki page: ARM-USB-OCD article

FAQ

• Can I use ARM-USB-OCD with EW-ARM?
• IAR EW has support for GDB and works with ARM-USB-OCD.

• I am currently using operating system X. It has FTDI drivers, how should I alter them to work with my installation?
• FTDI provide drivers and instructions at their web site, download them and use our ARM-USB-OCD PID: 0x0003, VID: 0x15BA to install the drivers.

• I have LPC1227 board and can't program it with your OpenOCD debugger. What do I do wrong?
• LPC1227 lacks JTAG according to the microcontroller's datasheet. The board can be programmed only via SWD (Serial Wire Debug) interface. Olimex OpenOCD debuggers have JTAG by default. You would need an addiitonal adapter – ARM-JTAG-SWD.

• How to install ARM-USB-OCD to work with CrossWorks

• Test with the FTDI drivers. The FTDI drivers can be downloaded from the following address:
  https://www.olimex.com/Products/ARM/JTAG/_resources/OLIMEX-FTDI-drivers-2-12-04.zip
  There is already profile for ARM-USB-OCD in CrossWorks but if you want to use it as 'Generic FTD2232' target interface you have to do as follows:

  1. Right click on a blank space in the targets window and select 'New Target Interface > Generic FT2232 Device'.
  2. Right click on the new target interface and select 'Properties' - set the following properties:
     Connected LED Inversion Mask 0x0000
     Connected LED Mask = 0x0800
     nSRST Inversion Mask = 0x0200
     nSRST Mask = 0x0200
     nTRST Inversion Mask = 0x0000
     nTRST Mask = 0x0100
     Output Pins = 0x0F1B
     Output Value = 0x0D08
     Running LED Inversion Mask = 0x0000
     Running LED Mask = 0x0800

  PID: 0x0003
  VID: 0x15BA

  In CrossWorks 1.7 there are Target interfaces for Olimex JTAGs, note that RTCK is not used with a FT2232 design so your JTAG clock should not exceed 1/6 of your target MCU clock or the JTAG will lock up. Start with JTAG divider 10 and decrease until you are able to debug to find your own value for your target.

Coocox Driver Ed

• Can I debug high voltage targets with ARM-USB-OCD?
• ARM-USB-OCD is not isolated, but you can use a USB-ISO isolator device to protect your PC while debugging high voltage targets.

• Howdy, guys. I can't program my MSP430 and PIC16 boards with your robust debugger. I need help ASAP.
• Technically, it is possible to program targets different than ARM using our OpenOCD debugger. Practically, almost all users use the debugger for ARM programming and only ARM targets are officially supported. There is a reason that the prefix in the name of the debugger is 'ARM-'.

• I am the maintainer of a commercial IDE with custom debugger code. I want to include support for your OpenOCD tools in my software, however I can't find specific information. It is obviously a win-win situation for both parties. Is it possible to provide me with more specific technical information for your debuggers?
• Olimex can provide the necessary information and cooperate with interested parties if they want to add low-cost USB debugger support to their C compilers and IDEs.

Related Products - People who bought this product also bought

ARM debugger with JTAG and SWD interfaces, based on CoLinkEX

High-speed 3-IN-1 fast USB ARM JTAG, USB-to-RS232 virtual port and power supply 5VDC device (supported by OpenOCD arm debugger)

Low-cost high-speed ARM USB JTAG (supported by the OpenOCD arm debugger)

This tutorial shows how to import an embedded project from Eclipse-based CooCox CoIDE to Visual Studio, build and debug it with VisualGDB. We will import a project created for the STM32F4Discovery board and show how to setup build and use the peripheral driver libraries provided by ST.

Coocox Colinkex Usb Driver

1. Create a project with CooCox CoIDE, add references to the GPIO module and put the following code into the main source file:
   
   </div><div><table><tbody><tr><td><div><div>2</div><div>4</div><div>6</div><div>8</div><div>10</div><div>12</div><div>14</div><div>16</div><div>18</div><div>20</div><div>22</div><div>24</div><div>26</div><div>28</div><div>30</div></div></td><td><div><div><span>#include <stm32f4xx_rcc.h></span></div><div><span>void</span><span>Delay</span><span>(</span><span>)</span></div><div><span>int</span><span>i</span><span>;</span></div><div><span>asm</span><span>(</span><span>'nop'</span><span>)</span><span>;</span></div><div><span>{</span></div><div><span>RCC_AHB1PeriphClockCmd</span><span>(</span><span>RCC_AHB1Periph_GPIOD</span><span>,</span><span>ENABLE</span><span>)</span><span>;</span></div><div><span>GPIO_InitStructure</span><span>.</span><span>GPIO_Pin</span>=<span>GPIO_Pin_12</span><span>;</span></div><div><span>GPIO_InitStructure</span><span>.</span><span>GPIO_Mode</span>=<span>GPIO_Mode_OUT</span><span>;</span></div><div><span>GPIO_Init</span><span>(</span><span>GPIOD</span><span>,</span><span>&GPIO_InitStructure);</span></div><div><span>for</span><span>(</span><span>;</span><span>;</span><span>)</span></div><div><span>GPIO_WriteBit</span><span>(</span><span>GPIOD</span><span>,</span><span>GPIO_Pin_12</span><span>,</span><span>Bit_SET</span><span>)</span><span>;</span></div><div><span>GPIO_WriteBit</span><span>(</span><span>GPIOD</span><span>,</span><span>GPIO_Pin_12</span><span>,</span><span>Bit_RESET</span><span>)</span><span>;</span></div><div><span>}</span></div></div></td></tr></tbody></table></div></div><br /></li><li>Run the “tree /f” command from the project directory to get an overview of the source files included in the project:The most important about the file layout is that the header files are located in cmsis, cmsis_boot and cmsis_lib/include subdirectories. We will need to specify this later when we get the project to build under Visual Studio.</li><li>Launch Visual Studio and start the VisualGDB Embedded Project Wizard:</li><li>Select “Import a project built with command-line tools -> Generate a Makefile”:</li><li>Select your ARM toolchain and pick the device from the list:</li><li>Specify the directory with your CoIDE project so that VisualGDB can import files from it:</li><li>Select OpenOCD as the debug method. If your Discovery board is plugged in, VisualGDB will detect it automatically. Otherwise, select the programming interface from the list or press “Detect” to try detecting it again:</li><li>Press Finish to create the project. By default it will use the new STM32 HAL library. As the CoIDE projects include the files from the ST libraries, this would cause a conflict. To avoid it, open VisualGDB Project Properties, go to the Embedded Frameworks page and remove references to all frameworks:</li><li>Go to the Makefile settings page and specify the relative paths to the directories containing .h files in the Include Directories field:</li><li>Remove the startup file used by VisualGDB as the CoIDE includes its own startup file:</li><li>Try building your project. If VisualGDB shows errors related to the assert function, edit the stm32f4xx.h to include the stm32f4xx_conf.h file:</li><li>Press F10 to step into the main() function:Once the debugging starts, you can step through the function or press F5 to resume debugging.</li><li>Once you verify that the program works as expected, stop debugging by pressing Shift-F5. Now we will remove the files that CoIDE copied from the STM32 libraries and replace them with references to the VisualGDB STM32 library. This will ensure that the files will be stored in one central location shared between the projects and that updating them to newer versions automatically affects all related projects. First, remove the files from the cmsis, cmsis_boot and cmsis_lib subdirectories:</li><li>Then add a reference to the Legacy Peripheral Library framework via VisualGDB Project Properties:</li><li>Finally, clear the Include Directories field on the Makefile Settings page:</li><li>Now you can build your project again. Instead of the files copied by CoIDE, it will use the shared files provided by VisualGDB:</li><li>Press F10 to step into it and then hit F5 to continue debugging and validate that it is working as before:</li><li>You can also delete the files in cmsis, cmsis_boot and cmsis_lib directories from the disk, as they do not participate in build anymore:</li></ol><br><br><a href='https://netlify.mix-goapp.com/heroes-of-might-and-magic-6-for-mac-os-torrent.html#McPTXhsN=BlJPQ1EAUABVFgFTU1UNVFhZBVxJcAtcUQ5MTnMTXxcHERUAA1cVVRsHRw8VAEpAHwAeSFEdVgMAUBhQG1MaBAxObGIeUAtQGQ1QEg8MXkoaUEIUSR8QVkoVR0AEABNSAzA=' target='_blank'><img src='https://cdn-ak.f.st-hatena.com/images/fotolife/r/ruriatunifoefec/20200910/20200910011337.png' style='cursor:pointer;display:block;margin-left:auto;margin-right:auto;'></a><br><br></p> <div class="tags"></div> </div> </div> </div> </article> <aside class="sidebar c-4-12"> <div id="sidebars" class="sidebar"> <div class="sidebar_list"> <div id="sidebar-search" class="widget"> <h3>Search</h3> <div class="widget-wrap"> <form method="get" id="searchform" class="search-form" action="#" _lpchecked="1"> <fieldset> <input type="text" name="s" id="s" value="Search this site..." onblur="if (this.value == '') {this.value = 'Search this site...';}" onfocus="if (this.value == 'Search this site...') {this.value = '';}" > <input type="submit" value="Search" /> </fieldset> </form> </div> </div> <div id="sidebar-archives" class="widget"> <h3>MOST POPULAR ARTICLES</h3> <div class="widget-wrap"> <ul> <li><a href='/barco-driver-download'>: Barco Driver Download</a></li> <li><a href='/drivers-anmo'>: Drivers Anmo</a></li> <li><a href='/download-agamatrix-driver'>: Download Agamatrix Driver</a></li> <li><a href='/aimsrl-input-devices-driver-download-for-windows-10'>: Aim_srl Input Devices Driver Download For Windows 10</a></li> <li><a href='/cartimex-laptops-desktops-driver'>: Cartimex Laptops & Desktops Driver</a></li> </ul> </div> </div> </div> </div> </aside> </div> </div> <footer id="site-footer" role="contentinfo"> <div class="copyrights"> <div class="container"> <div class="row" id="copyright-note"> <span> © 2021 ® Blogintel332 <div class="top"> <a href="#top" class="toplink">Back to Top ↑</a> </div> </div> </div> </div> </footer> </body> </html>