On Di, 2016-02-23 at 15:58 +0100, Bernd Mueller wrote:
> Marc Santhoff wrote:
>
> > Did you use the stmf103fw.pas translation from Jeppe or make you own
> > unit for supporting the 429?
>
> I needed only a few peripherals (GPIO, USART, RCC and embedded FLASH). I
> wrote this stuff by myself.
OK
Marc Santhoff wrote:
Did you use the stmf103fw.pas translation from Jeppe or make you own
unit for supporting the 429?
I needed only a few peripherals (GPIO, USART, RCC and embedded FLASH). I
wrote this stuff by myself.
My target would be f407, although the project in mind has to be done
u
On Di, 2016-02-23 at 12:25 +0100, Bernd Mueller wrote:
> Michael Ring wrote:
> >
> > (Glad to hear that basic functionality works...)
>
> I finished my first (small) project with the STM32F429ZI controller and
> everything went smooth :-) Even with optimization level -O2.
>
> Thanks everyone, w
Michael Ring wrote:
(Glad to hear that basic functionality works...)
I finished my first (small) project with the STM32F429ZI controller and
everything went smooth :-) Even with optimization level -O2.
Thanks everyone, who is involved in the ARM compiler/rtl development.
Regards, Bernd.
Good point, Jeppe, what do you think on compiling rtl on arm-embedded
with -O1 ?
Michael
(Glad to hear that basic functionality works...)
By the way, I have done a patch for Lazarus so that debugging with
ST-Link/JLink/Texane works, send me an e-mail when you want to test this.
Michael
Am
Michael Ring wrote:
By the way, with fpc trunc compiler you can target your board directly:
ppcrossarm -WpDISCOVERYF407VG (see ppcrossarm -i for other Discovery
boards)
You should also refrain from using optimizations > -O1 as there are some
issues with the compiler that make your compiled
Currently there is no support for embedded targets in the Lazarus
Debugger so you will need to load/debug your code with the help of other
tools.
For the Discovery board the easiest way to deploy binaries and to debug
is to install openocd:
openocd -f board/stm32f4discovery.cfg
should conne
On Sa, 2016-01-09 at 00:55 +0100, Jeppe Johansen wrote:
> Yes, you understand it correctly :)
> The FPC RTL only exposes the hardware, not the firmware stack on top.
>
> It might not be documented well anywhere but the weak linking with set
> defaults basically means you can declare interrupt han
Chiming in ;-)
There are two more options:
https://github.com/yunkot/pxl
There are units available for higher level access to STM32F4, Teensy and
some Freescale Devices. Very usable for devices that have >64k of Flash,
a number of displays and sensors are supported out of the box.
When your
Yes, you understand it correctly :)
The FPC RTL only exposes the hardware, not the firmware stack on top.
It might not be documented well anywhere but the weak linking with set
defaults basically means you can declare interrupt handlers like this:
procedure MySystickHandler; [public, alias: 'S
Answering myself here:
On Fr, 2016-01-08 at 23:43 +0100, Marc Santhoff wrote:
> On Fr, 2016-01-08 at 23:23 +0100, Jeppe Johansen wrote:
> > CMSIS is a lot of things. What exact part of it are you asking about here?
>
> In that file for example from line 887 on:
>
> http://svn.freepascal.org/cgi-
On Fr, 2016-01-08 at 23:23 +0100, Jeppe Johansen wrote:
> CMSIS is a lot of things. What exact part of it are you asking about here?
In that file for example from line 887 on:
http://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/rtl/embedded/arm/stm32f407xx.pp?revision=32386&view=markup
there are
CMSIS is a lot of things. What exact part of it are you asking about here?
FPC's embedded target has a bunch of controller units that are pulled in
depending on the -Wp argument. These define exactly what you see in the
units in the rtl/embedded/arm directory. In most cases just the physical
r
Hi,
looking at the embedded source code there has been done a lot of work.
I'm interested in trying fpc on Cortex-M3 and M4, mostly from ST.
While trying to get an overview of the sources I found the declarations
are pulled into a processor specific file by external declarations. But
where does i
14 matches
Mail list logo
