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 needing clarification: 1. The F0 module has functions flash_program_u32(), flash_program_u16() and flash_wait_busy() that are functionally (and code) identical to flash_program_word(), flash_program_half_word() and flash_wait_for_last_operation() in the F1/F2/F4 modules. I assume it's OK to change these to keep a consistent API across families? Actually flash_wait_for_last_operation() is probably mis-named for the F1/F2/F4 modules as bsy and eop flags signal different things. 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 function for F1 seems to be on the right track. cheers, Ken ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
