<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 26, 2018, 1:10 PM Christian Mauderer <<a href="mailto:list@c-mauderer.de">list@c-mauderer.de</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Peter,<br>
<br>
yes, that sounds about right. I'm not entirely sure about the name of<br>
the file we used as a base back then. I would have to take a look at the<br>
exact version at work.<br>
<br>
I think the new software should be based on the "legacy" one so I would<br>
expect that the interface is at least similar. But yes, it will be some<br>
work to use the updated libraries. Especially because there are some<br>
RTEMS-patches in the legacy libraries to work around some bugs.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Was the original software committed unmodified? If so, then the changes to fix bugs should be easy to find via git.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards<br>
<br>
Christian<br>
<br>
Am 26.11.18 um 18:37 schrieb <a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a>:<br>
> It will be some work to update. I believe what’s in the existing port<br>
> is from this:<br>
> atmel-software-package-samv7: Legacy software package for samv7, same70<br>
> and sams70 product families.<br>
> while the newest software that supports the ATSAMA5 is here, with a<br>
> different directory layout.<br>
> atmel-software-package: Atmel Software Package<br>
> <br>
>> On Nov 25, 2018, at 14:45 , Christian Mauderer <<a href="mailto:list@c-mauderer.de" target="_blank" rel="noreferrer">list@c-mauderer.de</a><br>
>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank" rel="noreferrer">list@c-mauderer.de</a>>> wrote:<br>
>><br>
>> Hello Peter,<br>
>><br>
>> Thomas mentioned already the bug that has been reported to Microchip.<br>
>> Please note that I had two more problems with the BSP on another<br>
>> customers board:<br>
>><br>
>> - The core clock couldn't be set to the maximum frequency from the data<br>
>> sheet. Both possible configurations for that frequency didn't work. The<br>
>> first one would have set the PLL to the same frequency as the CPU core<br>
>> clock. With that the system was not stable. The other setting (a divider<br>
>> of two after the PLL) seemed to work better but that forced me to set<br>
>> the PLL to a higher frequency than the data sheet specified. I ended up<br>
>> with the lower frequency.<br>
>><br>
>> - The external SDRAM seemed to introduce some jitter into the core PLL<br>
>> too (not only in the USB PLL which was the reason for the USB bug). With<br>
>> higher frequency configurations the system sometimes had an odd<br>
>> behaviour: A comparison went wrong when it should go well. Again that<br>
>> lead to a slightly lower frequency that seemed stable. So the board now<br>
>> runs on only about two thirds of the maximum frequency specified by<br>
>> Microchip.<br>
>><br>
>> If you still want to use the ATSAM chip: Microchip managed to get a<br>
>> better community around the libraries that are used in the BSP for that<br>
>> chip. There is a newer version of them somewhere on github. If there is<br>
>> funding for it, I would suggest to update the ones that are integrated<br>
>> in the ATSAM BSP by the newer ones. They contain quite some bug fixes.<br>
>> But it will need some work to do that.<br>
>><br>
>> With kind regards<br>
>><br>
>> Christian Mauderer<br>
>><br>
>> Am 25.11.18 um 19:42 schrieb <a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a>>:<br>
>>> Thank you for the advice. I will not need USB, but will need SDRAM and<br>
>>> don’t need poor support. Microchip? You tried to push RTEMS for this<br>
>>> platform tied to space applications, are you monitoring this? The<br>
>>> platform looks like just what I need but not if you’re not supporting it.<br>
>>><br>
>>>> On Nov 25, 2018, at 13:23 , Thomas Dörfler<br>
>>>> <<a href="mailto:thomas.doerfler@embedded-brains.de" target="_blank" rel="noreferrer">thomas.doerfler@embedded-brains.de</a><br>
>>>> <mailto:<a href="mailto:thomas.doerfler@embedded-brains.de" target="_blank" rel="noreferrer">thomas.doerfler@embedded-brains.de</a>><br>
>>>> <mailto:<a href="mailto:thomas.doerfler@embedded-brains.de" target="_blank" rel="noreferrer">thomas.doerfler@embedded-brains.de</a>>> wrote:<br>
>>>><br>
>>>> Peter,<br>
>>>><br>
>>>> just to make you aware: we designed a board with the ATSAMV7 chip and<br>
>>>> hit some nasty and at least one really ugly bug: operating the USB<br>
>>>> interface concurrently with external SDRAM does not work. Half a year<br>
>>>> after reporting this bug, Microchip confirmed it, but did not plan any<br>
>>>> fix for it. BTW: The conbination (USB+SDRAM) was also available on<br>
>>>> Microchip's evaluation board, but obviously was not tested together at<br>
>>>> Microchips labs...<br>
>>>><br>
>>>> So: I recommend you to tripple check, whether the ATSAMA5 meets all of<br>
>>>> your expectations.<br>
>>>><br>
>>>><br>
>>>> Kind regards,<br>
>>>><br>
>>>> Thomas.<br>
>>>><br>
>>>> ----- Ursprüngliche Mail -----<br>
>>>> Von: "Peter Dufault" <<a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a>><br>
>>>> <mailto:<a href="mailto:dufault@hda.com" target="_blank" rel="noreferrer">dufault@hda.com</a>>><br>
>>>> An: "Development" <<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a>><br>
>>>> <mailto:<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a>>><br>
>>>> Gesendet: Sonntag, 25. November 2018 18:38:19<br>
>>>> Betreff: BSP for Microchip ATSAMA5D27-SOM1-EK1<br>
>>>><br>
>>>> I need to evaluate this for a multi-chip application.<br>
>>>><br>
>>>> This part is a result of Microchip’s take-over of ATMEL. I’m<br>
>>>> double-checking that to create a BSP based on this I should start with<br>
>>>> the existing ATSAMV7 BSP, I think the peripherals (e.g. network chip<br>
>>>> and so on) are the same as the existing ATSAMV7 port.<br>
>>>><br>
>>>> Peter<br>
>>>> -----------------<br>
>>>> Peter Dufault<br>
>>>> HD Associates, Inc. Software and System Engineering<br>
>>>><br>
>>>> This email is delivered through the public internet using protocols<br>
>>>> subject to interception and tampering.<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> devel mailing list<br>
>>>> <a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a>> <mailto:<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a>><br>
>>>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
>>>> -- <br>
>>>> -- <br>
>>>> --------------------------------------------<br>
>>>> embedded brains GmbH<br>
>>>> Thomas Doerfler<br>
>>>> Dornierstr. 4<br>
>>>> D-82178 Puchheim<br>
>>>> Germany<br>
>>>> email: <a href="mailto:Thomas.Doerfler@embedded-brains.de" target="_blank" rel="noreferrer">Thomas.Doerfler@embedded-brains.de</a><br>
>>>> Phone: +49-89-18 94 741-12<br>
>>>> Fax: +49-89-18 94 741-09<br>
>>>> PGP: Public key available on request.<br>
>>>><br>
>>>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
>>><br>
>>> Peter<br>
>>> -----------------<br>
>>> Peter Dufault<br>
>>> HD Associates, Inc. Software and System Engineering<br>
>>><br>
>>> This email is delivered through the public internet using protocols<br>
>>> subject to interception and tampering.<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> devel mailing list<br>
>>> <a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a>><br>
>>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
>>><br>
>><br>
> <br>
> Peter<br>
> -----------------<br>
> Peter Dufault<br>
> HD Associates, Inc. Software and System Engineering<br>
> <br>
> This email is delivered through the public internet using protocols<br>
> subject to interception and tampering.<br>
> <br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div></div></div>