Am 18.02.2018 um 20:41 schrieb Philipp Klaus Krause:
>
> This is a known limitation. Currently, SDCC only supports 16-bit
> adresses for STM8, both for data and code. In particular, support for a
> larger memory model that uses 24-bit addresses for code or data is not
> yet implemented.
In SDCC
Am 27.03.2018 um 09:30 schrieb Eric Rullens:
>
> It looks like the basiscs are almost working (but as they say: the devil is
> in the details). I would like to work on a few patches, but currently time
> is limited. I would be able to have some experiments done on a larger
> project once the
, but it works for this little test. Do you think it
can also work with the code generator?
Eric
> -Oorspronkelijk bericht-
> Van: Eric Rullens
> Verzonden: dinsdag 27 maart 2018 09:31
> Aan: 'sdcc-user@lists.sourceforge.net'
> Onderwerp: Re: [Sdcc-user] STM8 &
> -Oorspronkelijk bericht-
> Van: Philipp Klaus Krause [mailto:p...@spth.de]
> Verzonden: zondag 25 maart 2018 20:06
> Aan: sdcc-user@lists.sourceforge.net
> Onderwerp: Re: [Sdcc-user] STM8 >32kB code fails...?
>
> Work on the feature request
> (https://sou
Am 21.02.2018 um 22:34 schrieb Eric Rullens:
>
> All STM8 parts with more than 32 kB flash currently cannot be used to their
> full potential with SDCC.
>
> Looking at the ST website, at the moment this means 58 of the 138 variants.
> Including the interesting ones of course. ;-)
>
> A while
Am 21.02.2018 um 22:34 schrieb Eric Rullens:
>
> All STM8 parts with more than 32 kB flash currently cannot be used to their
> full potential with SDCC.
>
> Looking at the ST website, at the moment this means 58 of the 138 variants.
> Including the interesting ones of course. ;-)
I would have
> Am 19.02.2018 um 10:50 schrieb Maarten Brock:
> >
> > Do I understand correctly that your STM8 has code memory
> above 0x?
> > So the problem is that SDCC only generates 16 bit jump/call
> > instructions and thus cannot reach 0x1 and above, but
> it can 'overflow' into that area.
>
Am 19.02.2018 um 10:50 schrieb Maarten Brock:
>
> Do I understand correctly that your STM8 has code memory above 0x? So
> the problem is that SDCC only generates 16 bit jump/call instructions and
> thus cannot reach 0x1 and above, but it can 'overflow' into that area.
>
> Does the STM8
> Am 18.02.2018 um 07:50 schrieb Georg Icking-Konert:
>> hello all,
>>
>> following a discussion on the updated STM8 SPL license (see
>> https://github.com/gicking/STM8-SPL_SDCC_patch/issues/1 ) I happened to
>> notice something strange:
>>
>> 1) build example including all SPL modules, where a
Am 18.02.2018 um 07:50 schrieb Georg Icking-Konert:
> hello all,
>
> following a discussion on the updated STM8 SPL license (see
> https://github.com/gicking/STM8-SPL_SDCC_patch/issues/1 ) I happened to
> notice something strange:
>
> 1) build example including all SPL modules, where a pin
for an example please contact me via "icking at onlinehome.de", or apply
SPL patch
https://github.com/gicking/STM8-SPL_SDCC_patch/blob/master/STM8S_StdPeriph_Lib_sdcc.patch
and compile "Projects/STM8S_StdPeriph_test_ok" (case 1) and
"Projects/STM8S_StdPeriph_test_fail_32k" (case 3)
hello all,
following a discussion on the updated STM8 SPL license (see
https://github.com/gicking/STM8-SPL_SDCC_patch/issues/1 ) I happened to
notice something strange:
1) build example including all SPL modules, where a pin toggles every 500ms
- code adress range is 0x8000 to 0x1000c,
12 matches
Mail list logo
