Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2018-09

Does mipsel-embedded build?

7 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

christo

I'm trying to understand how the RTL build process fits together. Looking at the makefile for embedded it seems that there may be a couple of files missing for mipsel-embedded.  Firstly make complains about "no rule to make target mipsel/startup.s" probably because that file is missing from trunk (at least I cannot find it either). Secondly the cpu units such as pic32mx1xxfxxxb etc. are also missing.

There is a comment for svn rev. 27188: "partially merged the mips-embedded branch from Michael Ring".  I couldn't see any subsequent commits related to mipsel-embedded.

Can anyone else build mipsel-embedded RTL with trunk?  I've built ppcrossmipsel compiler so far.

Reply by email

Michael Ring
to christo

Unfortunately a few files are missing in trunk, however I can provide patches to you to make things work, if you are in hurry then please send me an e-mail.

I am currently working together with Alfred Glänzer (who does fpcupdeluxe) to integrate his port for Microchip SAMC/D controllers in my small framework for embedded controllers, next step after this is done will be to also better support PIC32 chips, so if you have a little time you will be able to use working support for PIC32 via fpcup deluxe.

I can also provide the missing parts to the core defs to include those parts in trunk fpc if they are willing to do so.

Michael

christo wrote 16 lines
I'm trying to understand how the RTL build process fits together. Looking at the makefile for embedded it seems that there may be a couple of files missing for mipsel-embedded.  Firstly make complains about "no rule to make target mipsel/startup.s" probably because that file is missing from trunk (at least I cannot find it either). Secondly the cpu units such as pic32mx1xxfxxxb etc. are also missing. There is a comment for svn rev. 27188: "partially merged the mips-embedded branch from Michael Ring".  I couldn't see any subsequent commits related to mipsel-embedded. Can anyone else build mipsel-embedded RTL with trunk?  I've built ppcrossmipsel compiler so far. _______________________________________________ fpc-devel maillist  -  http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply by email

Florian Klämpfl
to Michael Ring
Michael Ring wrote 8 lines
Unfortunately a few files are missing in trunk, however I can provide patches to you to make things work, if you are in hurry then please send me an e-mail. I am currently working together with Alfred Glänzer (who does fpcupdeluxe) to integrate his port for Microchip SAMC/D controllers in my small framework for embedded controllers, next step after this is done will be to also better support PIC32 chips, so if you have a little time you will be able to use working support for PIC32 via fpcup deluxe. I can also provide the missing parts to the core defs to include those parts in trunk fpc if they are willing to do so.

Of course, the only problem we need to handle are the huge controller specific files. But maybe those can be keep separate.

Reply by email

Michael Ring
to Florian Klämpfl

Hi Florian!

I have already reduced size to the same size to the size as on other platforms, so a lot less space will be used. Please give me a little time to cleanup my patches...

On providing headers seperate, a loooonnnnnngggggg time ago Jeppe created a (close to genious) patch that allowed to use a configuration file to inject embedded controllers at runtime, but this never was implemented in trunk.

I have tons of .pas files for embedded controllers (complete STM Line, now also complete SAMC/SAMD line of controllers and PIC32) that I can all provide as a patch but this increases the emedded directory a lot and 95% of all headers will most likely never get used. Having the mechanism that Jeppe once developed would allow people to install just the files they need, keeping the embedded directory clean & lean.

Perhaps this is something to implement in the future, what do you think?

FYI, here are the current patches for SAMCD+STM32 family:

https://github.com/michael-ring/mbf/tree/master/Patches

Michael

Florian Klämpfl wrote 13 lines
Am 30.09.2018 um 19:33 schrieb Michael Ring: > Unfortunately a few files are missing in trunk, however I can provide patches to you to make things work, if you are in > hurry then please send me an e-mail. > > I am currently working together with Alfred Glänzer (who does fpcupdeluxe) to integrate his port for Microchip SAMC/D > controllers in my small framework for embedded controllers, next step after this is done will be to also better support > PIC32 chips, so if you have a little time you will be able to use working support for PIC32 via fpcup deluxe. > > I can also provide the missing parts to the core defs to include those parts in trunk fpc if they are willing to do so. Of course, the only problem we need to handle are the huge controller specific files. But maybe those can be keep separate. _______________________________________________ fpc-devel maillist - http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply by email

Florian Klämpfl
to Michael Ring
Michael Ring wrote 7 lines
Hi Florian! I have already reduced size to the same size to the size as on other platforms, so a lot less space will be used. Please give me a little time to cleanup my patches... On providing headers seperate, a loooonnnnnngggggg time ago Jeppe created a (close to genious) patch that allowed to use a configuration file to inject embedded controllers at runtime, but this never was implemented in trunk.

True, I don't remember though were the patch was available.

Show quoted text 7 lines
I have tons of .pas files for embedded controllers (complete STM Line, now also complete SAMC/SAMD line of controllers and PIC32) that I can all provide as a patch but this increases the emedded directory a lot and 95% of all headers will most likely never get used. Having the mechanism that Jeppe once developed would allow people to install just the files they need, keeping the embedded directory clean & lean. Perhaps this is something to implement in the future, what do you think?

Yes, this could be done for sure.

Show quoted text 6 lines
FYI, here are the current patches for SAMCD+STM32 family: https://github.com/michael-ring/mbf/tree/master/Patches

Ah, now I remember the other problem with the controller units: they are BSD style licensed because of the license of the original headers, so we cannot include them into FPC.

Reply by email

Michael Ring

Most likely Jeppe sent the patch only to me, I have forwarded the patch to so that you can get an idea on what he did.

Forgive me, I am a license dummy, can the licensing be handled properly with something like Jeppe's approach? If yes then I would love to maintain a repro of controller units, I can automagically generate Headers for most relevant microcontrollers currently available.

Michael

Florian Klämpfl wrote 35 lines
Am 30.09.2018 um 19:48 schrieb Michael Ring: > Hi Florian! > > I have already reduced size to the same size to the size as on other > platforms, so a lot less space will be used. Please > give me a little time to cleanup my patches... > > On providing headers seperate, a loooonnnnnngggggg time ago Jeppe > created a (close to genious) patch that allowed to use > a configuration file to inject embedded controllers at runtime, but > this never was implemented in trunk. True, I don't remember though were the patch was available. > I have tons of .pas files for embedded controllers (complete STM > Line, now also complete SAMC/SAMD line of controllers > and PIC32) that I can all provide as a patch but this increases the > emedded directory a lot and 95% of all headers will > most likely never get used. Having the mechanism that Jeppe once > developed would allow people to install just the files > they need, keeping the embedded directory clean & lean. > > Perhaps this is something to implement in the future, what do you think? Yes, this could be done for sure. > > FYI, here are the current patches for SAMCD+STM32 family: > > > https://github.com/michael-ring/mbf/tree/master/Patches Ah, now I remember the other problem with the controller units: they are BSD style licensed because of the license of the original headers, so we cannot include them into FPC. _______________________________________________ fpc-devel maillist - http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply by email