"atsamv" BSP legacy network driver status

[dufault at hda.com]

> On Jan 28, 2020, at 04:46 , Christian Mauderer <christian.mauderer at embedded-brains.de> 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 libbsd code?  Where do you run the code from?

The application I'm testing doesn't fit in the internal SRAM provided by the default "linkcmds" in the libbsd case, partly because libbsd is bigger and partly because when I build for "libbsd" it needs "libblock".

It fits if I use "linkcmds.sdram", but then I can't run it because the SDRAM must not be set up properly at reset, I guess I'd need to come up with something using "openocd" that will set up the SDRAM before starting the program.

I then tried putting just REGION_START in internal flash but it fails when it jump through a trampoline to "system_init_flash" which was still in the SDRAM.

Then I tried using "linkcmds.qspiflash" but the program didn't fit again since more space was required in the internal SRAM.

I need to:
- reduce the size by figuring out how to get rid of "libblock" (it isn't needed in the non libbsd case);
- figure out how to set things up so that "openocd" works using the SDRAM;
- or relocate everything needed prior to initializing SDRAM to be in the internal flash.
 
This is still an evaluation so I only want to see it run.

Peter
-----------------
Peter Dufault
HD Associates, Inc.      Software and System Engineering

This email is delivered through the public internet using protocols subject to interception and tampering.