Lazarus cross-compiler for embedded arm

[krolikbest]

Hi,
 despite having a separate copy of Lazarus for compiling for arm I wanted the same option for compiling for arm in my normal (normal=windows os) installation. I used fpcupdeluxe as ususall for that purpouse; have selected embedded(os) and arm(cpu) from cross tab of fpcupdeluxe application. Installation went ok. So started Lazarus, selected new program and in Project->Project options->Config and target: Target os: Embedded, Target cpu: Arm. Then hit OK button. But then I get popup window with
info (see attachment below). I already have compilers installed for other platforms (Linux, ARM, WinCE) and I don't really have any problems compiling for them. Does embedded require some different way than other os-targets? or is this because of this a little outdated version of Lazarus, or am I something missed..
Regards,
Martin
Lazarus 2.2.6, FPC 3.2.2, win64

[ccrause]

I also get that warning when using Lazarus (even recent main branch) for some embedded & freertos targets. Perhaps it is due to these targets saving the rtl units in subarch specific structures?  But not IIRC for avr-embedded, so not sure exactly what is causing this.

What happens if you click OK and compile your example?  In my case (if the cross compiler, rtl units and cross binutils are installed correctly) the project should compile successfully despite this warning.

[krolikbest]

I did a test on my other computer with win10 64bit and the same Lazarus ver as in my first post and this time I could choose Target: Embedded and CPU: arm but no luck with compiling (please see photo below). No matter Target processor (tested: default, arm7, armv7em, ..). Not yet investigated what the error does mean.

[ccrause]

Disable line info option.  There is no lnfodwrf unit provided for embedded targets.

[krolikbest]

Aha!  Very helpful hint. Thank you. However.. one must remember to avoid spaces in saving path of project. After saving project files and attempting to compile I got a message (in attachment). Then I recollected a similar problem related to spaces in directories. No spaces no problem

[krolikbest]

Hi,
 if a program for pico looks like

Code: Pascal  [Select][+][-]

1. program prg1;
2. {$MODE OBJFPC}
3. {$H+}
4. {$MEMORY 10000,10000}
5.  
6. begin
7. end.

then there is not a problem to compile but if it looks like

Code: Pascal  [Select][+][-]

1. program prg1;
2. {$MODE OBJFPC}
3. {$H+}
4. {$MEMORY 10000,10000}
5.  
6. uses
7.  pico_gpio_c,
8.  pico_timer_c;
9.  
10. begin
11. end.
12.  

I get error during compiling. The error says

pico_c.pas(195,15) Error: Identifier not found "resets"

Use Win10/64bit, FPC 3.2.2. The file pico_c.pas obtained from picoexamples4fpc.

[avra]

Maybe identifier was not defined in FPC 3.2.2 and you need more fresh version?

Have you tried FPC trunk? That would probably need newer Lazarus as well...

[ccrause]

Maybe identifier was not defined in FPC 3.2.2 and you need more fresh version?

Correct, the RP2040 unit was added after FPC 3.2.2 was released.  Thus one needs to build a new compiler based on the FPC main source branch.  As per the wiki, one only needs FPC 3.2.2 to bootstrap the new compiler version.

[krolikbest]

That's how I felt it should be, but I didn't want to change my Laz/fpc instalations. Anyway thanks a lot guys for explanations.

[krolikbest]

Hi, it's me again.. sorry to bother anybody but I installed fpc+Laz using button PICO from  fpcupdeluxe. Now if I choose new simply project (like begin end.) and set in config OS-embedded, Family-arm, Processor=armv6m, deselect in Debugging option Display Line Number I get this(see please image1). How to fix it? It looks that I'm back at beginning of this topic

[avra]

Did you build a cross compiler for your target in fpcupdeluxe?
Did you use the new desktop shortcut made for PICO Laz/FPC combo?

[ccrause]

Hi, it's me again.. sorry to bother anybody but I installed fpc+Laz using button PICO from  fpcupdeluxe. Now if I choose new simply project (like begin end.) and set in config OS-embedded, Family-arm, Processor=armv6m, deselect in Debugging option Display Line Number I get this(see please image1). How to fix it? It looks that I'm back at beginning of this topic

As already mentioned, Lazarus performs some checks, but it is not perfect so ignore the error.  What happens when you click OK, then build an empty project?

[krolikbest]

Compilation attempt of blinking example ended up successfully. I have one more small question about the configuration in Lazarus:
if I start new project (for Pico) it would be nice to check someting in the project that this is for Pico, so then all necesarry options like

-Wpraspi_pico
-godwarfsets
-godwarfcpp
-Xu

I wouldn't have to add them manually; they would be added automatically after selecting a project for Pico. I'm not sure if am I making myself clear? Maybe I've even seen it somewhere before, but I forgot how to do it...

[DonAlfredo]

In case of the Lazarus error you encountered, you might try to rescan the FPC sources.
See: https://github.com/LongDirtyAnimAlf/fpcupdeluxe/issues/779#issuecomment-3275789669

[krolikbest]

In my case it doesn't help, but I can live with such harmless (presumably) error.