From: "Gian Maria" <g_giacomello@yahoo.it>
To: <ecos-devel@ecos.sourceware.org>
Subject: STM32F107 on STM3210C-EVAL
Date: Tue, 22 Mar 2011 19:15:00 -0000 [thread overview]
Message-ID: <DE0674571A15429DB6B96106B02BBE8D@Mr32bitPC> (raw)
I'm porting eCos to STM3210C and I find a logical error on the
implementation of CYGPKG_HAL_CORTEXM_STM32.
CYGPKG_HAL_CORTEXM_STM32 must be the base of all STM32 uP and so is not
correct for me to use
cdl_option CYGHWR_HAL_CORTEXM_STM32 {
display "STM32 variant in use"
flavor data
default_value {"F103ZE"}
legal_values {"F103RC" "F103VC" "F103ZC"
"F103RD" "F103VD" "F103ZD"
"F103RE" "F103VE" "F103ZE" }
description "The STM32 has several variants, the main
differences
being in the size of on-chip FLASH and SRAM
and numbers of some peripherals. This option
allows the platform HAL to select the specific
microcontroller fitted."
}
That is inside "ecoscvs\ecos\packages\hal\cortexm\stm32\var\current\cdl",
because with my EVB for example
the uP is a STM32F107VC. With this I can't set the right uP as default for
the template.
I'm right? I think the correct is to put the code inside
"ecoscvs\ecos\packages\hal\cortexm\stm32\stm3210e_eval\current\cdl"
Can someone modify this so I can update my CVS and work with the right code?
Best regards Gisn.
PS:
1 - When I finish my piece of port, that is at the beginning and I'm
learning eCos who can upload?
2 - For every suggest Is this the right place?
3 - I have to post the full port or can post pieces of code as they are
ready?
next reply other threads:[~2011-03-22 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 19:15 Gian Maria [this message]
2011-03-23 10:51 ` John Dallaway
2011-03-26 11:07 ` Ilija Kocho
2011-03-28 9:55 ` qber_
2011-03-28 10:47 ` jerzy dyrda
2011-03-28 19:13 ` R: " Gian Maria
2011-03-28 11:34 ` Ilija Kocho
2011-04-14 10:59 ` mlazcoz
2011-03-23 10:30 qber_
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=DE0674571A15429DB6B96106B02BBE8D@Mr32bitPC \
--to=g_giacomello@yahoo.it \
--cc=ecos-devel@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).