Hi,
Yes, some peripherals have completely different internals (see the
difference between ADC on
F30x and F37x as one example - it is different peripheral with different
register sets). Moreover
F37x have Sigma-delta ADC as another peripheral added (do not be confused by
this peripheral
in the comparsion)
I see that Esden run many commits today, and master has been updated.
Thanks, esden ! If you
like to fork my branch, please wait some days, to give me some time to
synchronize and update
all my branches to have clean start for next work to be enabled it for
merging to master.
Regards,
Frantisek
---------- Původní zpráva ----------
Od: Ormund Williams <ormu...@panix.com>
Datum: 23. 8. 2013
Předmět: Re: [libopencm3-devel] Support for STM32F372
"On Thu, 2013-08-22 at 22:25 +0200, František Burian wrote:
> Hi, Ormund,
>
> Beware that the F30x has peripherals like as F0, and F37x has
> peripheral set near the F4 set.
> Currently implemented is F30x, that is contained in STM32F3Discovery
> board.
>
> I´m doing the unification of the peripheral set through entire stm32
> family, and still waiting for
> a lot of my work to be pushed to the master, having clean starting
> point for deeper unification.
> During unification I didn't forgotten for F37x, but in the current
> implementation i have no idea
> how to differentiate between F30x and F37x by using same library for
> both families.
>
I noticed the difference in the peripheral set between the F30x and the
F37x but are you saying that its more than which peripheral but how they
are implemented?
> It has been discussed heavily on the IRC channel, and multiple
> solution exists. The implementation
> of new processor has lower priority than finish of the organization of
> common peripherals in the
> existing ones.
>
> Feel free to create "F37" family directory, making the basic support
> for irq.yaml and memorymap
> for it, create the doxygen dirs and edit makefiles to make it
> correctly as the starting point.
> If i can remember it correctly, all peripherals there is implemented
> now, therefore it's selection of
> implementation for F37 will be fast after the reorganization of common
> peripherals will be finished.
>
OK, I'll git clone master and start on this. Is your branch accessible?
> Your impression is correct with limits. Some peripherals have some
> different functions on different
> platforms, and must be programmed as platform-dependent. The
> unification that I am currently doing
> is to grab all platform dependent code for given peripheral (seems
> that this is a lot of code), and strip
> out common functions that exists in all platforms that support the
> peripheral.
>
> Do You have board with F37x processor ?
>
Yes, its a board I designed and I used a STM32F372CC, I also have a
STM32F3Discovery board which has the STM32F303VC, it seems not as useful
for development as I had hoped.
> All informations containing in this email is provided as-is, as my
> opinion, not opinion of the library
> makers. I am only one from the set of currently active authors and
> someone will direct you better
> which work will help us best.
Thanks Frantisek and best regards.
--
Ormund
----------------------------------------------------------------------------
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
libopencm3-devel mailing list
libopencm3-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libopencm3-devel"
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
libopencm3-devel mailing list
libopencm3-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libopencm3-devel