Hi,

  yesterday I tried ( for first time ) to use the fpc for arm with the gcc-arm-none-eabi-8-2018-q4-major-win32 toolchain and I got this error :

"G:\Programming\dimitris\tools\gcc-arm-none-eabi\bin\arm-none-eabi-objcopy.exe: G:\Programming\dimitris\tools\mbf\Samples\Blinky\Blinky.hex 64-bit address 0x4b4fa300000000 out of range for Intel Hex file"

As I'm not familiar with ARM, does anyone have a clue or a hint on what I'm doing wrong ?

FYI,

FPC trunk builded with :

">make.exe clean crossall crossinstall OS_TARGET=embedded CPU_TARGET=arm SUBARCH=armv6m CROSSOPT="-O1"
INSTALL_PREFIX=G:\Programming\dimitris\tools\fpc-trunk CROSSBINDIR=G:\Programming\dimitris\tools\gcc-arm-none-eabi\bin BINUTILSPREFIX=arm-none-eabi-"

and the

project options are :

"G:\Programming\dimitris\tools\fpc-trunk\bin\x86_64-win64\fpc.exe -Tembedded
-Parm
-MObjFPC
-Scgi
-Ch8192
-Cs8192
-O1
-gw2
-l
-vewnhibq
-Fi..\..\Source
-Filib\arm-embedded
-Fu..\..\Source
-Fu.
-FUlib\arm-embedded
-FE.
-oBlinky
-Cparmv6m
-XParm-none-eabi-
-Wparduinozero"

PS: I used the "Microcontroller Board Framework" ( https://github.com/michael-ring/mbf ) from Michael Ring cause the official FPC doesn't have my MCU ( ATSAMD21G18A ).

regards,

On Sun, May 26, 2019 at 9:16 AM Dimitrios Chr. Ioannidis via fpc-devel <

I suspect the problem is with objcopy, not FPC. This bug report ( https://sourceware.org/bugzilla/show_bug.cgi?id=24065) mention a problem if the target is 64 bit and the host is 32 bit. Check if you can get a recent version of objcopy, or try the 64 bit version of the arm binutils (I assume you have a 64 bit Windows machine)

Hi Christo,

Στις 26/5/2019 11:10 π.μ., ο Christo Crause έγραψε:

Great find !

In this bug report there is a link for a patched toolchain . I'll try it later today to see how it goes.

PS: I don't see any commits reg. AVR's. Do you have any insight if some of the AVR bug reports ( stack error checking,  DIV, etc ) will be fixed / resolved ?

regards.

Hi,

Στις 26/5/2019 11:25 π.μ., ο Dimitrios Chr. Ioannidis via fpc-devel έγραψε:

< snip>

In this bug report there is a link for a patched toolchain . I'll try it later today to see how it goes.

Just FYI, the patched
toolchainhttps://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc/releases/tag/v8.2.1-1.2

works. Just tested.

regards,

Hi Dimitrios,

I have no indication or further communication from the compiler team regarding the open items in the bug tracker. If you are interested in testing FPC with all my AVR patches you can get the source here: https://github.com/ccrause/freepascal. Note that I don't continuously integrate that fork with upstream trunk, it is about 2 months behind at the moment.

Just one note of caution:

When you encounter strange behaviour of your Code on Cortex-M0 in respect to DIV commmand then check the mailinglist, Jeppe has provided a fix but I am not quite sure if the fix has made it into official trunk.

Michael

Hi Michael,

thx for the hint.

By the way, any chance for inclusion your MCU definitions if official FPC ?

regards,

Quite a number is already in on trunk, but as the support for devices is getting bigger and bigger (at least on my harddisc) there is a need for an inteligent mechanism to handle the huge amount of devices as the header files eat up a lot of space in svn and only a very few will actually get used.

Jeppe once had provided a nice mechanism to me but it never made it to trunk. From the last comment of Florian on the topic the door id open for implementing something that makes handling easier, but honestly I did not spend much time on this.

Do you use a board like the Arduino Zero or do you work with plain, not pre-programmed chips?

I am asking because in case you use Arduino Zero there will be some obstacles for you to get rid of the preinstalled bootloader that you will most likely have to face.

Contact me in that case, I have already been down that road and have a working solution. (see
https://learn.adafruit.com/proper-step-debugging-atsamd21-arduino-zero-m0/restoring-bootloader)

Michael

It's been snuck in now :)