Re: [Sdcc-user] STM8 bootloader flash software (Georg Icking-Konert)

[Georg Icking-K. <ic...@on...>]

hello all,

sorry for the (very) late response. I have just uploaded my STM8 flash tool using COM or USB to Github (https://github.com/gicking/STM8_serial_flasher.git <https://github.com/gicking/STM8_serial_flasher.git>). I have selected the Apache License for it, because that seems to account for 3rd party rights of contained code - which is the case for the flash routines by STM. Please feel free to improve my code and/or report bugs. Have fun!

Notes:
  - the tool works under Windows, MacOSX and Linux operating systems
  - for the STM8 Discovery Board, you have to connect the STM8 to the PC via a UART->USB adapter. The board itself connects to the PC via SWIM (=debug interface) only
  - the STM8 bootloader has to be enabled via option bytes. This can be done using the "ST Visual Programmer“ (Windows only)


Georg

> ------------------------------
> 
> Message: 2
> Date: Sun, 6 Apr 2014 15:17:58 +0300
> From: Kustaa Nyholm <Kus...@pl...>
> Subject: Re: [Sdcc-user] STM8 bootloader flash software
> To: "sdc...@li..."
> 	<sdc...@li...>
> Message-ID: <CF671F10.8EEF7%kus...@pl...>
> Content-Type: text/plain; charset="us-ascii"
> 
> On 06/04/2014 14:45, "Georg Icking-Konert" <ic...@on...> wrote:
> 
>> hello Georg O.,
>> 
>> sure, no problem. Actually I never bothered about license, yet. So how do
>> I release something under a GPL?
> 
> Before you do you might want to consider what license(s) you want to
> release
> your code under.
> 
> Think what you want, think what it means to your users, what you want to
> given them
> and what you want them to be able to do, think what it means to your code
> in terms
> of breath of usage and popularity and getting contributions (if that is
> what you want).
> 
> I realize the code in question is not a large body of code so may not
> matter that
> much but still worth to think about these things for a minute or two.
> 
> I sometimes release GPL, sometimes LGPL and sometimes BSD and other times
> I just keep it proprietary,
> sometimes even a combination, it all depends.
> 
> To release code under some license all you have to do is to put the notice
> about the license in your source code and include the source code with it.
> 
> br Kusti
> 
> 
> This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
>