Is the L0 series directly compatible with F0? I've had no problems using
rcc_clock_setup_in_hsi_out_48mhz() on a F0, the STM32F030F4. (little TSSOP
guy). I also just adjusted the F0-discovery .ld file.
usart, systick, spi, all seemed to work fine, as well, didn't test much
else.
I don't generally use the drag-n-drop flash, but I've just tested it and it
does seem to work (on a nucleo F401RE, anyway). You can also use 'st-flash'
with the st-link onboard.
I seem to think some nucleos shipped with buggy debugger firmware, so try
updating (suppose this requires windows).
I'm thinking ST may have changed some things on the L0 vs the F0 though.
On 16 November 2014 23:38, Chuck McManis <[email protected]> wrote:
> I'm trying to run LOC3 on the Nucleo board. (STM32L053 with an M0 on it).
> I thought I would just re-use code in the stm32f0-discovery examples to see
> if I could just compile and go but they don't work. the LED on the Nucleo
> board is on PA5, which I changed in miniblink and nothing.
>
> That makes me suspect there is something going on with the clock chain
> that I don't have an answer for. There is still some random breakage in the
> f0 build tree the libopencm3 sub repo in examples complained about
>
>
> make[2]: *** No rule to make target
> `../../../include/libopencm3/stm32/common/exti_common_l1f24.h', needed by
> `exti_common_all.o'. Stop.
> make[1]: *** [lib/stm32/f2] Error 2
> make: *** [lib] Error 2
>
> Which I'm not sure what its all about, but the f0 library built. Looking
> at the schematic of the Nucleo board it seems like its pretty standard,
> 8Mhz HSI clock input, and I call rcc_clock_setup_in_hsi_out_48mhz (actually
> I've tried multiple versions of that). I took the linker file for the
> discovery board and re-purposed it for the nucleo board but its basically
> identical (64K of flash at 0x80000000 and 8K ram at 0x20000000).
>
> One thing I can't veriify easily is that the .bin file is compatible with
> the mBed loader (it shows up as a disk drive, you copy the .bin file into
> it and it writes it into the flash). Now I'm looking at pulling the bmp
> probe over here to see what is going on, but thought I would check in here
> as well.
>
> --Chuck
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> libopencm3-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
>
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
libopencm3-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
