public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "\"Ilija Kocho [Илија Кочо]\"" <ilijak@siva.com.mk>
To: BELPHEGOR <gather@belphegor.eu>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Specific needs on stm32
Date: Wed, 26 Feb 2014 16:01:00 -0000	[thread overview]
Message-ID: <530E0FC5.8040704@siva.com.mk> (raw)
In-Reply-To: <530DF5CB.9060909@belphegor.eu>

On 26.02.2014 15:10, BELPHEGOR wrote:
> Hello Ilija,
> (Excuse me to use your mail address directly),
> but I tried to write onto the ecos-discuss@ecos.sourceware.org mail
> address,
> and I didn't see a single mail pass.
> Do you think there is a problem on the whole mailing list ?
>

The cause is text formatting. Your email was formatted in HTML. eCos
mailing lists accept plain text only.
HTML format is usually triggered if there is some text formatting in
your text. It may also be default or set to default on your email client.
You have to set the format to plain text when sending to eCos mailing lists.

>
> By the way, thank you very much for your former help, I gave eCos a
> better try, and I'm working hard for a few days to port my application
> on stm32f4discovery.
>
> Below are the two mails I tried to send, they are obsolete by the way,
> because I succeed to compile the default template for stm32f4discovery
> (with the ROM build option (instead of JTAG), and to build little
> applications that use STM32F4 HAL to make some led blinking, and some
> thread mechanisms.
> That's coool ! :)
>
> I will focus now on having a functional file system in flash, a
> dynamic loading that works, and a printf that scroll over the LCD screen.
> If by chance you know some projects/people that could lead me on this
> way, I would be happier than I am.
>

This mailing list is the right place.
I would recommend you Masa's book. It's available in both paper and PDF.
Ref:
http://www.informit.com/store/embedded-software-development-with-ecos-9780130354730

Ilija


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

  parent reply	other threads:[~2014-02-26 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 16:13 Valentin BOUSSON
2014-01-20 20:04 ` "Ilija Kocho [Илија Кочо]"
     [not found]   ` <52E24132.2020505@belphegor.eu>
2014-01-26  2:51     ` "Ilija Kocho [Илија Кочо]"
     [not found]       ` <530C6522.7020704@belphegor.eu>
     [not found]         ` <530C9551.1060603@belphegor.eu>
     [not found]           ` <530DF5CB.9060909@belphegor.eu>
2014-02-26 16:01             ` "Ilija Kocho [Илија Кочо]" [this message]
2014-02-27 12:49               ` [ECOS] STM32F4 and Dynamic loading Valentin BOUSSON
2014-02-27 17:12                 ` [ECOS] " John Dallaway
2014-02-28 10:15                   ` Valentin BOUSSON
2014-02-28 17:47                     ` John Dallaway
2014-01-21  0:05 ` [ECOS] Specific needs on stm32 "Ilija Kocho [Илија Кочо]"

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530E0FC5.8040704@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gather@belphegor.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).