2009-12-09 08:52 AM
Free IDE for STM32 -- Coocox Builder new released
2011-05-17 04:29 AM
Hi all!
We have some really big news. CooCox Builder 0.15 has been released. It can give you a new development experience. See As I mentioned earlier in the topichttp://www.st.com/mcu/forums-cat-8999-23.html
, Only For ARM Cortex M3, STM32 Series for example, will look like this: * directly check to select the driver, RTOS, TCP/IP protocol stack through the mouse, without having to care about migration issues, and to easily view the help and examples * generates an driver example through a mouse click * simply generate a set of solutions by mouse, then compile, download and run in the target board But at present we have only partially implemented,We will implement examples automatically generated in the recent versions. CooCox Builder V0.15 is not perfect now, it is a prototype of Coocox Builder, so we need your help to improve the Builder. If you have some good ideas or requirements,please contact us. Thanks!! ---------------------------- , Cooperate on Cortex, Free and Open RTOS, Free embeded development tools For ARM Cortex M3.2011-05-17 04:29 AM
Looks very nice :)
Why Builder and Debugger are separete applications? [ This message was edited by: radzio on 16-11-2009 22:46 ]2011-05-17 04:29 AM
I am very interested by Coocox Builder
In 1 hour i have installed CoBuilder , build a project and flash the elf file to the µC on my Olimex module. For the flash , I used my Jtag probe Jtagkey-tiny with Eclipse and OpenOCD . I have to test a bit more the debugging and the ISR . CoBuilder generates the skeleton , the startup code , the equivalent of the makefile and link files , that are hard for me to put in place . My question : what is your economical model ? Are you pushed by ARM ? Or someone else ? Thank you for your job Daniel2011-05-17 04:29 AM
Hi radzio,
Thank you for your attention and question.Quote:
Why Builder and Debugger are separete applications?
The reason is like this: 1.builder is designed for building drivers, libraries, os without much thought to debug. 2.Parallel and phased development of product. Our builder will provide users with an integrated debugger version in the future.You can debug directly without any further configuration of the debugger after build. ---------------------------- Free and Open debug probe --Colink,http://www.coocox.org/Colink.htm
Free and Open RTOS--CoOS,http://www.coocox.org/CoOS.htm
Free and Pioneering IDE -- CoBuilder,http://www.coocox.org/CooCox_Builder.htm
Free Flash Programmer -- CoFlash, Free Debugging tool -- CoDebugger, CooCox wish your attention!2011-05-17 04:29 AM
Hi Coocox team,
Thanks indeed for this end of year gift;-) ;) ;) But I don't know how this can be useful if I don't have the Colink hardware. you have mentioned that you can do it by your self: but through the following link I can't find the component list (doc empty). I have also another qustion : is it feasible to use IAR or Keil hardware (Jlink and Ulink) with coocox software? Thanks in advance for your free support!!!! Cheers2011-05-17 04:29 AM
Hi armmcu.engineer,
Thank you for your reply.Quote:
but through the following link I can't find the component list (doc empty).
http://www.coocox.org/CoLinkGuide/how-to-do-CoLink.htm We will soon fix this problem.Quote:
I have also another qustion : is it feasible to use IAR or Keil hardware (Jlink and Ulink) with coocox software?
CooCox Colink is open, and it's production cost is very low. You can also buy it from a third party at a very low price.;-) CooCox wish your attention! [ This message was edited by: ahnniu on 30-11-2009 11:55 ]2011-05-17 04:29 AM
Thanks for your support. :D
2011-05-17 04:29 AM
Hi ahnniu, I'm downloading Coocox, and I'm willing to test it.
I had a look to the schematics of CoLink, I see it uses a FTDI2232. How should I program the eeprom, I mean, is there a hex file to program it? BTW who ever wants to build his/her own Colink can use a DLP mod available at FTDI web shop, I already have one I already used to prototype, I will recycle it. Thank in advance for your answer.2011-05-17 04:29 AM
Hi fabrizio,
Quote:
How should I program the eeprom, I mean, is there a hex file to program it?
We just program Manufacturer, ManufacturerId, Description and SerialNumber strings into the EEPROM. You can ignore this. If you want to program you FTDI's EEPROM,you can use tools below:http://http://www.ftdichip.com/Resources/Utilities/FT_PROG.zip
http://www.ftdichip.com/Resources/Utilities/MProg3.5.zip
You can find both them on this page:http://www.ftdichip.com/Resources/Utilities.htm
. Here is ahttp://www.coocox.com/downloadfile/Forum_attachment/Colink_FT_PROG_Template_File.zip
of CooCox Colink for reference. CooCox wish your attention!