- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi:
We know that when I compiled a common "c/c++ Application",there are RTOS combo in the system library ,which includes: none(single-thread) and MicrC/OS-II . now ,I had set up the ecos , and buildt a "Advance c/c++" , meanwhile , the "Build Command" on the "Make Builder" tab is fix : make INSTALL_DIR=<PATH> , but ecos did not appear on the RTOS combo, Can anyone can tell me how the ecos can be added to the RTOS comboLink Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is no RTOS combo box for an "Advanced C/C++ project", so please check that's what you really selected and not a "C/C++ Application".
All eCos realated build features are defined by the Makefile you provide for your project, so there is no need to select the RTOS in Eclipse.- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi monkeyboy :
From your replying it means that if I want to builde a new standard "c/c++" project on the ecos ,I should build the standard "c/c++" on the Advance "c/c++" project , yes or not? Thanks- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not certain what your question is here, but if I understand you correctly, you should only use an "Advance c/c++" project for eCos, not the standard "c/c++ Application".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi monkeyboy:
my promble is that when I had successed built a application following the document meanwhile successed build a "advance c/c++ project " and run the "hello.c" following the document , now I want to set a common "c/c++ application" in the evirment of ecos . I found that the Microu/os is listed in the combo of the RTOS on a "c/c++ application " project 's " system peoperties " and the "c/c++ application ' can choose the os evirment by choosing the "none or Micro/os ". So i think the ecos should be listed in the combo but it is ont found .So I think if i want to set a "c/c++ application " in the evirment of ecos , I should built a "Advance c/c++ application" project----named aihuazou, which is based on ecos , then I set a "c/c++ application " below the project "aihuazou" ,only that ,I can success a c/c++ application on ecos, is it right or not. thanks- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's right up until the point you try to use a standard "c/c++ application". These don't work for eCos. You can only use an "advanced c/c++ project ". The easiest ways to do this is to start with the examples provided, and then modify the makefile to build whatever source files you want to build.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi monkeyboy:
Thanks for your help, and I had soluted all the problem refered before. Now I designed a new kit ,whose components is different from the components of the altera's kit which refered in the configuration template of the ecos . How can I added myself kit or the kit's components to the template ? Additional ,how can I transplant my design to our hard target ? Thanks!- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you want to create a new target, you can do so by editing the ecos.db file that comes with the released version of eCos. Look at what's been done for the nios2_dev_board target as an example.
To download an executable to the board, you can use: nios2-elf-download -g <elf file> from the command line. Alternatively you can use the run or debug features of the IDE. If you want to program the flash on your board, you can use the IDE flash programmer, or the auto-generated program-flash script as descrived in the getting started guide.- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mokeyboy:
Thanks for your help. Now I want to ask you that there include the "nios2 's hal" in the condition of the ecos , if i want to transplant the ecos system to my target , I need not to modify the content of the nios2 , what i should modify is to modify the content of I/O components and dev componts , yes or not? .- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Nios II HAL should have been automatically configured to match your hardware design (PTF file) by the nios2configtool. If you follow the steps outlined in the getting started documentation, you will be able to succesfully run the examples on your board.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page