[fpc-devel] Teensy (no OS) programmed with Free Pascal Embedded ARM
Michael Ring
mail at michael-ring.org
Mon Oct 12 00:11:32 CEST 2015
I've already addressed some of the issues, instead of using records I am
using objects now (classes unfortunately do not work) and there's a base
class for gpio, spi, i2c, uart.
The idea of having comments was that they show up as context sensitive
help in Lazarus, they can easily be left out, same with bitbanded
records, they are configurable.
I can see that I can address the issue with the repeated sub-records,
they were bugging me too, but never bugging me enough to do something
about it.
I will try to fix the headers for Frdm-k64f during the week, perhaps you
can have a look if they are OK for inclusion.
Michael
Am 11.10.15 um 23:25 schrieb Jeppe Johansen:
> Well I think it might be too much for now. Haven't really maintained
> it since then
>
> Anyway, from what I found last I tried with your headers I think there
> could be some improvement that might instead warrant their inclusion
> into SVN.
> The main point back then was that the size was pretty tremendous.
>
> To reduce size:
> - Similar types be in common records. What I found was that using your
> generated headers for the STM32F7xx HAL required a lot of casting
> because all the GPIO records, for example, for all the different ports
> were different types. This cause duplication of all the helpers too.
> - Could the helpers be in external units?
> - Have an option to remove comments? Not sure how much this would give
>
> Another thing was things like repeated sub records. CAN mailboxes or
> DMA channel streams all had the repeated registers, while the existing
> firmware codebase used arrays of records.
> This probably changes from manufacturer to manufacturer but it might
> be nice to reduce size, and probably wouldn't require a lot of change
> when porting code.
>
> Actually, maybe also not emit the bitband records? So far I've never
> once seen it used in normal code, and the places where it could be
> useful you might just as well calculate the offset yourself, or refer
> to it in an external unit(maybe one with the helpers? :)
>
> Best Regards,
> Jeppe
>
> On 10/11/2015 11:02 PM, Michael Ring wrote:
>> The code that makes the compiler work with conf files:
>>
>> fpc -Fb*.conf
>>
>> [ring at macbookpro-wlan stm32f407vg]$ cat stm32f4xx.conf
>> STM32F401CB,stm32f401x,stm32f4xx.lkr,%FLASHBASE:0x08000000,%FLASHSIZE:0x00020000,%SRAMBASE:0x20000000,%SRAMSIZE:0x00010000
>>
>> STM32F401RB,stm32f401x,stm32f4xx.lkr,%FLASHBASE:0x08000000,%FLASHSIZE:0x00020000,%SRAMBASE:0x20000000,%SRAMSIZE:0x00010000
>>
>> STM32F401VB,stm32f401x,stm32f4xx.lkr,%FLASHBASE:0x08000000,%FLASHSIZE:0x00020000,%SRAMBASE:0x20000000,%SRAMSIZE:0x00010000
>>
>>
>>
>> Am 11.10.15 um 22:58 schrieb Jeppe Johansen:
>>> Not sure what you are referring to here?
>>>
>>> On 10/11/2015 10:47 PM, Michael Ring wrote:
>>>> I want to interface my Freedom-K64F code with this lib, on first
>>>> view this looks pretty straightforward. Any chance to get your
>>>> great patch for the use on arbitrary system units into trunk ? (the
>>>> one you wrote for me to make cmsis work)
>>>>
>>>> Am 11.10.15 um 22:33 schrieb Jeppe Johansen:
>>>>> On 10/11/2015 10:10 PM, Michael Ring wrote:
>>>>>> Wow Jeppe, I am impressed, you used your time much better than I
>>>>>> did, your port looks pretty complete!
>>>>>>
>>>>>> Please have a look at
>>>>>>
>>>>>> https://github.com/yunkot/pxl
>>>>>>
>>>>>> this lib was mentioned yesterday on lazarus list, this looks like
>>>>>> a good layer above the lowlevel code, there are already
>>>>>> implementations for several sensors and displays and it already
>>>>>> supports Raspberry Pi.
>>>>>>
>>>>>> The Author is also thinking about extending the lib in the
>>>>>> direction of microcontrollers, so those two efforts combined
>>>>>> could some day get a very user friendly solution that is a lot
>>>>>> closer to what mbed is for the C guy today to what we have right
>>>>>> now.
>>>>>>
>>>>>> Michael
>>>>> Thanks :)
>>>>>
>>>>> Yeah, that PXL library looks like it has a lot of code already.
>>>>> Could be a great project to combine it with for sure!
>>>>> _______________________________________________
>>>>> fpc-devel maillist - fpc-devel at lists.freepascal.org
>>>>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>>>>
>>>> _______________________________________________
>>>> fpc-devel maillist - fpc-devel at lists.freepascal.org
>>>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>>>>
>>>
>>> _______________________________________________
>>> fpc-devel maillist - fpc-devel at lists.freepascal.org
>>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>>
>> _______________________________________________
>> fpc-devel maillist - fpc-devel at lists.freepascal.org
>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>>
>
> _______________________________________________
> fpc-devel maillist - fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
More information about the fpc-devel
mailing list