Confirmed that it works, the build errors were coming from some old
dependency files (I just replaced GCC Arm Embedded q1 with q3) once I did a
make clean; make it worked fine. I pulled over your repo and checked out
the l0 draft branch, then verified miniblink worked on both the Nucleo and
STM32L0-Discovery board. The OpenOCD stuff still doesn't work but I suspect
it is also an f0/l0 issue. Its possible ST is using the CMSIS-DAP profile
for these things, I just know they aren't recognized.
LOC3 on the Nucleo boards is pretty sweet though.
Now to figure out if I can build a Black Magic Debug probe build that I can
just flash into the debug processors on the Nucleo, that would totally rock
the house!
--Chuck
On Mon, Nov 17, 2014 at 2:55 PM, Karl P <[email protected]> wrote:
>
> Have a look at
>
> https://github.com/libopencm3/libopencm3/pull/362
> and the example referenced there, I got a basic miniblink up and running
> tonight, and finished off all the RCC register defiitions at least.
>
> Cheers,
> Karl P
>
>
> On 11/17/2014 05:03 PM, Chuck McManis wrote:
>
>> On Mon, Nov 17, 2014 at 8:45 AM, Karl Palsson <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> I doubt you'll have any real happiness tryign to fun f0 code as is on
>> the l0.
>> Maybe more than running f1 code, but still...
>>
>> I've got a L0 disco (the epaper board) but I haven't sat down to get
>> it up
>> and running with locm3
>> yet. Been busier than I expected :)
>>
>>
>> I've got the L0 disco epaper board as well, so we'll have independent
>> verification :-)
>>
>> I should be able to get the basic miniblink stuff up pretty easily
>> though,
>> but yeah, I do expect
>> to need different memory maps.
>>
>>
>> That was my thought, to be honest sitting through the seminar they
>> rattled on
>> and on about how it was just a low power version of the f0 and I figured
>> what
>> the heck. Clearly not as simple a change as I would have thought. I'll
>> dig out
>> the programming reference for this version of the chip and get a bit
>> deeper look
>> at where the changes are. If I get miniblink running I'll send you a pull
>> with
>> my changes on an L0 branch.
>>
>> >
>> >
>> > 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
>>
>> wat? that shouldn't be happening?!
>>
>>
>> I'll track this down. Between trying to update my environment (which
>> still has
>> uncommitted '429 stuff in it so I stashed and changed back to master and
>> fetched
>> upstream to rebuild it) the problem is in my tree. Just for sanity checks
>> I
>> cloned a new copy of the repo and built it and it built fine. So I just
>> need to
>> figure out if I've got a merge or something that hasn't happened causing
>> issues.
>>
>> --Chuck
>>
>>
>> Cheers,
>> Karl P
>>
>>
>>
------------------------------------------------------------------------------
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
