This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: How to run ECO 3.0 on STM32
- From: kishore Srimat <kishorestp at gmail dot com>
- To: John Dallaway <john at dallaway dot org dot uk>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Fri, 31 Jul 2009 17:24:17 -0700
- Subject: [ECOS] Re: How to run ECO 3.0 on STM32
- References: <ab2643f10907271051r1b7d3be7x842a851c672a8456@mail.gmail.com> <ab2643f10907291037l522859cew679773694c705803@mail.gmail.com> <4A70A606.5060309@dallaway.org.uk> <ab2643f10907291433h8529d92qaf0e0b044367078@mail.gmail.com> <4A7156FF.9030206@dallaway.org.uk> <ab2643f10907301554r3d2b05e4h12e1a42d3ea8510a@mail.gmail.com> <4A72AAD3.70006@dallaway.org.uk>
Hi John,
I have done all the steps you have suggested except this:
"Linking your application object code with eCos in the way shown in
the examples makefile at:"
/opt/ecos/ecos-3.0/examples/makefile
I could run the Build--> Tests
And in Tools--> Runtests the last test is specific to STM32 which is "Timers"
I ran with this
$ arm-eabi-gdb -b 38400 my_application_ELF_file
(gdb) target remote /dev/ttyS0
(gdb) load
(gdb) continue
as you told. Even through I could run all the commands the example is
not doing any thing.
How should I add the hello.c and other examples in to the configtool
so that it builds for a user ?
If I cannot add the examples from the user how should I link them to the App.
I tried to do it by you suggestions still no luck.
Can you please be little more detailed about it.
Thanks
Kishore Srimat
On Fri, Jul 31, 2009 at 1:26 AM, John Dallaway<john@dallaway.org.uk> wrote:
> Hi Kishore
>
> Kishore Srimat wrote:
>
>> Thank you very much, Finally i could run Reboot.bin. I figured that I
>> need to change the ecos HAL->Cortex-M Architecture->Cortex-M3 STm32
>> Variant->STM32 Eval Development Board HAL->Startup type= "ROM"
>
> This change should occur when you import the redboot_ROM.ecm file.
>
>> Now I am trying to run Ecos, what is the easiest way to run Ecos ?
>
> For _application_ development, using the GDB stub in RedBoot is usually
> the best route because it provides thread-aware debugging. Configure and
> build another version of eCos for RAM startup. Use the "default"
> template rather than the "redboot" template. Link your application
> object code with eCos in the way shown in the examples makefile at:
>
> /opt/ecos/ecos-3.0/examples/makefile
>
> Then download and run your code as follows:
>
> $ arm-eabi-gdb -b 38400 my_application_ELF_file
> (gdb) target remote /dev/ttyS0
> (gdb) load
> (gdb) continue
>
>> For example, I have HTTP server running on STM32 with lwIP1.3.0. Now,
>> I know that Ecos does not provide lwIP 1.3.0. I have seen Simon
>> implemented lwIP 1.3.0 for Ecos, I could use that. before that I want
>> to first familiarize with Ecos environment by running different
>> examples.
>
> Once you have built eCos for RAM startup, you can build some examples:
>
> cd /opt/ecos/ecos-3.0/examples
> make INSTALL_DIR=/path/to/your/ecos-RAM-startup/install
>
> John Dallaway
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss