[ECOS] STM dev board

[ECOS] STM dev board

[grahamlab]

Hello
I am a complete newcomer to ecos!
I have a STM32 dev board and am trying to configure ecos to run on it
So far I have successfully used the config tool to build the libraries and
test code
But the output file seem quite large and have the .exe extension - I was
expecting a .bin
Any pointers would be gratefully accepted
Thanks
Graham
-- 
View this message in context: http://www.nabble.com/STM-dev-board-tp22725493p22725493.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: STM dev board

[John Dallaway]

Hi Graham

grahamlab wrote:

> I am a complete newcomer to ecos!

No problem. Welcome to the eCos community.

> I have a STM32 dev board and am trying to configure ecos to run on it
> So far I have successfully used the config tool to build the libraries and
> test code
> But the output file seem quite large

The test executables generated by the eCos arm-eabi toolchain are ELF
images which include many non-loadable sections including debug records
for use by GDB. To determine memory usage on your STM32 target, use the
"arm-eabi-size" tool.

> and have the .exe extension - I was expecting a .bin

Are you sure that you are using the eCos arm-eabi toolchain? This
toolchain should produce test executables (ELF images) with no file
suffix at all.

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

Re: [ECOS] STM dev board

[Chris Holgate]

Hi Graham,

I'm not sure about the .exe extension - by default, on Linux all the
test executables in the xxx_install/tests subtree don't have an
extension, so I'm guessing it may be a CygWin thing.

If you've built the 'all you can eat' version for the STM3210E eval
board, most of the resulting test binaries are too big to fit into the
supplied RAM, so you'd be better doing a 'default' or even a 'kernel'
build to start off with.

Also, if you've not already done so you should build and flash a RedBoot
image first then use a RAM based eCos build for development.  Once
you've started debugging using RedBoot/GDB you'll never want to go back
to JTAG again!

Finally, if it is of interest, I'm about to wrap up my eCos USB driver
for the STM32 so am looking for beta testers...

Chris.

grahamlab wrote:
> Hello
> I am a complete newcomer to ecos!
> I have a STM32 dev board and am trying to configure ecos to run on it
> So far I have successfully used the config tool to build the libraries and
> test code
> But the output file seem quite large and have the .exe extension - I was
> expecting a .bin
> Any pointers would be gratefully accepted
> Thanks
> Graham


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] STM dev board

[Simon Kallweit]

Chris Holgate wrote:
> Finally, if it is of interest, I'm about to wrap up my eCos USB driver
> for the STM32 so am looking for beta testers...
>   

Count me in. Unfortunately our current hardware design does not come 
with an USB port, but I still have the STM3210e eval board around for 
testing.

Simon

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss