This is the mail archive of the ecos-devel@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: STM32F107 on STM3210C-EVAL


Hello.

As it is in description the main diffrences in STM32F familly are on-board flash and ram. So if you are using STM32F107VC you can use F103VC variant.

Between STM32F107VC and STM32103VD the main diffrences are in their periphelias:
3xSPI;2xI2S;2xI2C;3xUSART;2xUART;SDIO;USB;CAN                                                          STM32103
3xSPI;2xI2S;2xI2C;3xUSART;2xUART;USB OTG FS;2xCAN;Ethernet MAC10/100;one add timer    STM32107

As you can see here the drivers only you will have to support are for periphelias which are missing in 103.

Best regards
Qber

P.S.
Sorry for the first mail - some stupid mail box error.

W dniu 2011-03-22 20:15:36 uÅytkownik Gian Maria <g_giacomello@yahoo.it> napisaÅ:
> 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?
> 
> 




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]