GSoC'18-Introduction

[Chris Johns]

On 01/03/2018 18:08, Christian Mauderer wrote:
> Am 28.02.2018 um 05:52 schrieb Chris Johns:
>> On 28/02/2018 15:37, Christian Mauderer wrote:
>>> Yes, seems that I misunderstood it. So OpenOCD will remain on top of the recommendation list.
>>
>> For open solutions currently it seems so.
>>
>>>  
>>>>> As a positive report: I have a quite stable setup with the Segger J-Link
>>>>> EDU. 
>>>>
>>>> I do not run Linux and do not put Macs close to hardware so I cannot run their
>>>> closed source GDB server. I will stick with a fully open solution I can control
>>>> and fix.
>>>
>>> Most of the time I prefere open solutions too. I had some problems with OpenOCD on another target and bought the J-Link for that one. I only re-used it for the Beagle and it run quite well. 
>>
>> Nice. Please add it to the Wiki and some instructions if you feel it is needed.
>> It should be up to users to decide based on their needs and budget.
> 
> I'll add a section with the scripts that I used for debugging.
> 

Thanks.

>>
>>>>
>>>>> The EDU is a affordable variant with the disadvantage that it must
>>>>> only be used for non-commericial purpose.
>>>>
>>>> Ouch, messy. If I am paid to work on open source is that a non-commmercial
>>>> purpose or commercial purpose? What if I am paid more for coding and I debug for
>>>> free? ;)
>>>
>>> Same problem as allways with licensing. I would expect that GSoC is more educationall than commercial. But it's an edge case.
>>
>> Agreed.
> 
> I have been on the embedded world trade show yesterday and talked to one
> of the people on the Segger booth. He has seen no problem if GSoC
> students use the EDU version of the debugger.

Excellent news.

> 
>>
>>> For my applications I dont have a problem to distinguish because we have another debugger at work. So I can separate these quite well.
>>
>> For a BBB? I think we should list solutions, commercial or open, cheap or expensive.
> 
> Currently I don't have a BBB project at work. So I currently don't have
> ready made debugger scripts for the debugger we use there most of the time.
> 

Sure.

Chris