From: Oleg Uzenkov <o.uzenkov@unicore.co.ua>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] eCos STM32 processor support
Date: Fri, 11 Jul 2014 08:15:00 -0000 [thread overview]
Message-ID: <53BF9D34.3050105@unicore.co.ua> (raw)
Dear All,
I have built a custom PCB board with STM32F407VET6 micro on it. Having
adapted the HAL for periphery, the eCos port for STM32F407VGT6
(STMicroelectronics STM32F4-Discovery) is perfectly working on a new board.
Now, I am thinking about making a new PCB iteration with a 64 pin STM32
controller.
Please, could you clarify whether STM32F407VGT6 eCos port can support
STM32F405RGT6 processor as well?
And that STM32F207IGH6 (STMicroelectronics STM3220G-EVAL) eCos port can
support STM32F205RGT6 processor chip?
I would be grateful for any information on this.
With best wishes,
Oleg
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2014-07-11 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53BF9D34.3050105@unicore.co.ua \
--to=o.uzenkov@unicore.co.ua \
--cc=ecos-discuss@ecos.sourceware.org \
/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).