On 16/02/14 08:56, Pavol Rusnak wrote:
> On 01/15/2014 08:33 PM, Ken Sarkies wrote:
>> 2. Can anyone verify that the function flash_program_option_bytes() in
>> flash_common_f24.c is totally screwed and doesn't do anything like its
>> name promises? The equivalent func
I have to admit to searching out and doing cut and paste every time I
need to insert an action on a peripheral, so anything that is more
intuitive would be helpful. It needn't displace the API as it is now for
those who want to do kinky things like toggling multiple bits at once.
It's debatable
Hi All
I'm fiddling with the STM32 Flash modules to do some deduplication and
general documentation for the F0 and F1 series.
The STM32F1xx series has an XL series with Flash memory beyond 512KB and
organized in two banks. The second bank is programmed in the same way as
the first but using a
Hi
I've knocked up some boilerplate docs for the flash programming modules
in the STM32 families, without changing any code. Once that is merged
I'd like to fiddle the code a bit, mainly to de-duplicate the F0/F1/L1
modules which seem to have a fair bit in common.
Just a couple of points needi
On 14/01/14 14:59, Ken Sarkies wrote:
>
> The 205RE is 512K and you could well run into trouble with specifying a
> smaller memory. I have found that to be the case when I've played with
> 103's of different sizes.
>
Correction, I'm back to front. You should be OK b
On 14/01/14 14:42, skeezix wrote:
>
> /* Define memory regions. */
> MEMORY
> {
> rom (rx) : ORIGIN = 0x0800, LENGTH = 256K
> ram (rwx) : ORIGIN = 0x2000, LENGTH = 64K
> }
>
> /* Include the common ld script. */
> INCLUDE libopencm3_stm32f2.ld
>
> I'm obviously not using
On 13/10/13 16:36, Tommi Rouvali wrote:
> Maybe rcc_peripheral_enable_clock function could check incoming
> parameters and verify they are correct. This could be done only if DEBUG
> is defined, so there is no extra overhead. In case of error, function
> could call some user overridable function th
On 10/10/13 06:06, Michael Smith wrote:
> However, IMO the programming model for peripheral en/disable in general is
> completely broken. As it stands, it requires that the application programmer
> know which bus the peripheral is attached to, and thus which register must be
> touched in order t
On 22/09/13 15:06, Chuck McManis wrote:
So when ever I reset my board I get 'junk' that comes out of my serial
port. I've not quite gotten to the point where I can capture it on my
scope yet but its annoying.
I've been using the STM32F4-Discovery board, USART6 in this case, and
something duri
On 02/07/13 21:02, Philipp Kindt wrote:
> Hello,
>
> I compiled the latest libopencm3-examples and flashed the
> usb-cdcacm-example on my stm32f4 discovery board.
>
> The device does not enumerate and does not show up as a usb device on my
> PC (a dmesg on linux does not even mention a connection e
10 matches
Mail list logo
