This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
STM32F107 on STM3210C-EVAL
- From: "Gian Maria" <g_giacomello at yahoo dot it>
- To: <ecos-devel at ecos dot sourceware dot org>
- Date: Tue, 22 Mar 2011 20:16:06 +0100
- Subject: STM32F107 on STM3210C-EVAL
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?