CooCox ARM Cortex M3 and Cortex M0 Development Tools

• Free and open
• Supports ARM Cortex-M3 devices
• Download speed up to 250 KB/sec *
• From 5-pin to 20-pin connector support
• Wide target voltage range: 1.2V - 3.3V, up to 5V with optional probe
• No power supply required, powered through USB
• Plug-and-Play installation using standard Windows USB drivers
• Integrates seamlessly into IAR Embedded Workbench and Keil RealView MDK

• CooCox CoIDE
• CooCox CoFlash
• Keil RealView MDK 4.03 or higher
• IAR Workbench 5.xx

bigdogguru said:

Interesting, I'll have to give it a try.

Click to expand...

• Atmel: AT91SAM3Ux

• Energy Micro: EFM32G2xx, EFM32G8xx

• NXP: LPC11c1x, LPC11xx, LPC13xx, LPC17xx

• Nuvoton: NUC100, NUC120, NUC130, NUC140, NuMicroM051 series

• ST: STM32F100x, STM32F101x, STM32F102x, STM32F103x, STM32F105x, STM32F107x

• TI: LM3S19xx, LM3S2xxx, LM3S3xxx, LM3S5xxx, LM3S6xxx, LM3S8xx, LM3S8xxx, LM3S9xxx

• After selecting a component, the top left window in CoIDE will show component name(with * examples). Click it and you’ll see the Example window, where there are 327 examples in total.

• Click some component, and the Help window will show the component’s information, some of which include a Hello world item, i.e. a simple example of the component.

• Free and open real-time Operating System
  Free is on behalf of “the poor”, and Open aims at speeding up the burst of new ideas.

• Specially designed for Cortex-M series
  CoOS supports ALL Cortex-M0&Cortex-M3 chips.

• Scalable, minimum system kernel is as small as 974Bytes
  The file OsConfig.h includes all configurable and able-to-be-cut items in CoOS. Users can modify items according to needed configuration simply and conveniently.

• Adaptive Task Scheduling Algorithm

• Supports preemptive priority and round-robin
  CoOS supports two kinds of scheduling mode, preemptive priority and round-robin. The former is used among tasks of different priority, while the latter among tasks of the same priority. You can set CFG_PRIORITY_SET_EN as 1 in OsConfig.h to enable the preemptive priority scheduling mode.

• Interrupt latency is next to 0

• Stack overflow detection option

• Semaphore, Mutex, Flag, Mailbox and Queue for communication & synchronization
  In mutex section, CoOS has considered the issue of priority inversion, and solved it by the method of priority inheritance.

• Supports the platforms of ICCARM, ARMCC, GCC
  This means CoOS can not only be used in CoIDE (by selecting CoOS component), but also used independently in MDK and IAR.

• Added: supports new adapters---ST-Link, Nu-Link-pro, OpenJTAG.
• Corrected: Modified the flash algorithm for STM32F1xx series to support different version of chips.

• Free
• Most common Cortex-M3 MCUs supported
• Nuvoton Cortex-M0 MCUs supported
• User-defined flash program algorithm supported
• Intuitive user interface with GUI and Command line mode
• Image file (currently .bin or .elf ) supported
• Keep user's last configuration

• Added: Supported: NXP's LPC1200 series, some chips of TI and NUC130 and NUC140 series
• Corrected: Modify names for Nuvoton chips
• Added: Component library and examples for LPC1200 series
• Updated: The components and examples for STM32
• Added: Support for new debugging adapters: Nu-Link-pro, ST- Link, OpenJTAG
• Added: Support for opening an MDK project
• Added: Login and logout functions
• Added: Function to display the current selected chip
• Added: Beforebuild and postbuild functions
• Added: The options for Debug in Flash or Debug in RAM
• Corrected: The bug of pop-up "program is not being run" when entering debugging
• Corrected: Fix the bug of J-link debugging
• Corrected: the bug that the memory.ld of SAM3U series chips generate a wrong file
• Corrected: The bug that some M051 chips cannot download and debug.

Embedded_Geek said:

I downloaded CooCox IDE it seems to be good. Anyways I am more interested to know about the CooCox RTOS.

Can you provide some more details about it other than the details mentioned in the site.

Click to expand...

• STM32F10X series
  In function SystemInit(), file system_stm32f10x.c, folder cmsis_boot, there are sentences as follows:
  #ifdef VECT_TAB_SRAM
  SCB->VTOR = SRAM_BASE | VECT_TAB_OFFSET; /* Vector Table Relocation in Internal SRAM. */
  #else
  SCB->VTOR = FLASH_BASE | VECT_TAB_OFFSET; /* Vector Table Relocation in Internal FLASH. */
  #endif
  
  So you just need to select “Debug in RAM” in file build.xml, and add VECT_TAB_SRAM to Defined symbols.

• LPC17xx series
  In function SystemInit(), file system_LPC17xx.c, folder cmsis_boot, there are sentences as follows:
  #if (__RAM_MODE__==1)
  SCB->VTOR = 0x10000000 & 0x3FFFFF80;
  #else
  SCB->VTOR = 0x00000000 & 0x3FFFFF80;
  #endif
  
  So you just need to select “Debug in RAM”, and add one sentence to file system_LPC17xx.c -
  #define __RAM_MODE__ 1

• Chips which have no sentences above, e.g. LM3S series
  After selecting “Debug in RAM”, add one sentence to function SystemInit() in file system_lm3s.c, folder cmsis_boot -
  SCB->VTOR = 0x20000000 | 0x0; /* Vector Table Relocation in Internal SRAM. */
  
  Since VTOR is defined in file core_cm3.h, you need to add one sentence as well -
  #include "core_cm3.h"

• How to update components?
  
  Click “Refresh” button in the top right corner of Repository View, CoIDE will link to components server and refresh the Repository View. After refreshing, you can see links of update / download behind components available for updating / downloading. Click the links to download the components for use.

• How to update examples?
  
  After selecting components, click the name of a component in the top left Component View, CoIDE will refresh and download examples in background. When finished, double-click the name of the component, you can see refreshed examples.