Re: "atsamv" BSP legacy network driver status

2020-01-31 Thread Christian Mauderer
On 31/01/2020 13:39, dufa...@hda.com wrote: > > >> On Jan 31, 2020, at 01:31 , Christian Mauderer >> wrote: >> >> On 30/01/2020 22:12, dufa...@hda.com wrote: >>> >>> On Jan 30, 2020, at 01:24 , Christian Mauderer wrote: The SDRAM initialization is done in

Re: "atsamv" BSP legacy network driver status

2020-01-31 Thread dufault
> On Jan 31, 2020, at 01:31 , Christian Mauderer > wrote: > > On 30/01/2020 22:12, dufa...@hda.com wrote: >> >> >>> On Jan 30, 2020, at 01:24 , Christian Mauderer >>> wrote: >>> >>> The SDRAM initialization is done in bsp_start_hook_0. Most >>> initialization is done in bsp_start_hook_1.

Re: "atsamv" BSP legacy network driver status

2020-01-30 Thread Christian Mauderer
On 30/01/2020 22:12, dufa...@hda.com wrote: > > >> On Jan 30, 2020, at 01:24 , Christian Mauderer >> wrote: >> >> The SDRAM initialization is done in bsp_start_hook_0. Most >> initialization is done in bsp_start_hook_1. You should be able to put >> the following into SDRAM without problems: >>

Re: "atsamv" BSP legacy network driver status

2020-01-30 Thread dufault
> On Jan 30, 2020, at 01:24 , Christian Mauderer > wrote: > > The SDRAM initialization is done in bsp_start_hook_0. Most > initialization is done in bsp_start_hook_1. You should be able to put > the following into SDRAM without problems: > > - REGION_WORK > - REGION_BSS > - REGION_DATA > -

Re: "atsamv" BSP legacy network driver status

2020-01-29 Thread Christian Mauderer
On 29/01/2020 22:30, dufa...@hda.com wrote: > > >> On Jan 29, 2020, at 08:12 , Christian Mauderer >> wrote: >> >> On 29/01/2020 13:15, dufa...@hda.com wrote: >>> On Jan 29, 2020, at 03:13 , Christian Mauderer wrote: Hello Peter, On 28/01/2020 22:37,

Re: "atsamv" BSP legacy network driver status

2020-01-29 Thread dufault
> On Jan 29, 2020, at 08:12 , Christian Mauderer > wrote: > > On 29/01/2020 13:15, dufa...@hda.com wrote: >> >>> On Jan 29, 2020, at 03:13 , Christian Mauderer >>> wrote: >>> >>> Hello Peter, >>> >>> On 28/01/2020 22:37, dufa...@hda.com wrote: > On Jan 28, 2020, at 04:46 ,

Re: "atsamv" BSP legacy network driver status

2020-01-29 Thread Christian Mauderer
On 29/01/2020 13:15, dufa...@hda.com wrote: > >> On Jan 29, 2020, at 03:13 , Christian Mauderer >> wrote: >> >> Hello Peter, >> >> On 28/01/2020 22:37, dufa...@hda.com wrote: >>> On Jan 28, 2020, at 04:46 , Christian Mauderer wrote: Before our customers migrated to libbsd

Re: "atsamv" BSP legacy network driver status

2020-01-29 Thread dufault
> On Jan 29, 2020, at 03:13 , Christian Mauderer > wrote: > > Hello Peter, > > On 28/01/2020 22:37, dufa...@hda.com wrote: >> >>> On Jan 28, 2020, at 04:46 , Christian Mauderer >>> wrote: >>> >>> Before our customers migrated to libbsd (to get some of the features >>> there) the driver

Re: "atsamv" BSP legacy network driver status

2020-01-29 Thread Christian Mauderer
Hello Peter, On 28/01/2020 22:37, dufa...@hda.com wrote: > >> On Jan 28, 2020, at 04:46 , Christian Mauderer >> wrote: >> >> Before our customers migrated to libbsd (to get some of the features >> there) the driver in legacy worked. But that is a few years back. >> Currently I only know of

Re: "atsamv" BSP legacy network driver status

2020-01-28 Thread dufault
> On Jan 28, 2020, at 04:46 , Christian Mauderer > wrote: > > Before our customers migrated to libbsd (to get some of the features > there) the driver in legacy worked. But that is a few years back. > Currently I only know of applications using the libbsd driver. > How are you linking the

Re: "atsamv" BSP legacy network driver status

2020-01-28 Thread Christian Mauderer
Hello Peter, On 27/01/2020 22:10, Peter Dufault wrote: > The "rtems-libbsd" "if_atsam.c" driver is derived from the legacy one. Correct. > What's the status of the two drivers? I ask because I'm trying to do some > small memory testing with the legacy stack on the . It is building but not

"atsamv" BSP legacy network driver status

2020-01-27 Thread Peter Dufault
The "rtems-libbsd" "if_atsam.c" driver is derived from the legacy one. What's the status of the two drivers? I ask because I'm trying to do some small memory testing with the legacy stack on the . It is building but not working, I don't think network packets are going out even though the