On Mon, Jan 13, 2014 at 11:50:17PM -0500, skeezix wrote:
> setting up openocd as a gdb server (if it can do that)
Not only it can, it actually does so by default, just use
extended-remote protocol to connect to localhost:.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) sof
On Tue, 14 Jan 2014, 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.
I did fix this up, to no avail.
# Is your program crashing when using
On Mon, 13 Jan 2014, Chuck McManis wrote:
# Includes of the form #include
# are the correct form, the variant (F2) in this case is added by the
Quite, thanks.
# I would suggest you do initialization in the following order:
# 1) Clock
# 2) GPIOs
# 3) Alternate Function peripherals (usua
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 by specifying a smaller
memory.
Ok a couple of things.
Includes of the form #include
are the correct form, the variant (F2) in this case is added by the
-DSTM32F2 which shows up in Makefile.include, or you can put it
in your CFLAGS. The .elf target should pick up the correct library from
either the toolchain dir or your copy o
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
FWIW, I'm still bewildered with regards to the many configu
options during build and deployment, so I thought I'd "cheat" and perhaps
this is the issue (or leading to issues..)
- Given libopencm3-examples, I just navigated down to
stm32/f2/jobygps/miniblink and editted miniblin
Here is the code in question:
http://pastebin.com/xTxn5829
To summarize -- just polling the timer works fine; but my attempt
at enabling the ISR isn't working, so I'm probably missing a register
setting somewhere :)
If you fine people come up with anything, let me know
I've got 3 or 4 different attempts all fragmented together, but I can
appreciate not being given the whole picture :) Many ways to achieve similar
goals :)
I'll fiddle some more after kids go to bed and see if I can come up with
something; otherwise I'll split them apart and post the whole att
Hi Jeff,
I'm having a really hard time reading your source code as fragments.
For example in your timer2_setup there is a "#endif" in the middle of
it, where is the preceding #if? Did the timer code get compiled in?
It looks like you've got the basic concepts there but it is hard to tell.
I only
Does anyone have a libopencm3 based example, against the STM32 F2,
that illustrates ISR's invoking based on timers?
I did try using a couple of the examples (see timer.c) in the F1
directory to no avail; I've got a few attempts at it, and it looks like
(guessing, didn't hook up
11 matches
Mail list logo
