From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 6 Aug 2015 16:28:38 +0200 Subject: [U-Boot] Using spi_alloc_slave() from SPL In-Reply-To: References: <55C36368.1070701@denx.de> Message-ID: <201508061628.38401.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thursday, August 06, 2015 at 04:14:34 PM, Fabio Estevam wrote: > Hi Stefano and Marek, > > Thanks for the suggestions. > > On Thu, Aug 6, 2015 at 10:38 AM, Stefano Babic wrote: > > There is the possibility to set a malloc area inside SPL: > > > > CONFIG_SYS_SPL_MALLOC_START > > CONFIG_SYS_SPL_MALLOC_SIZE > > you do not need a lot of space, and you can try to put it inside the > > IRAM. > > > > This should guarantee that spi_alloc_slave() works. > > So I tried moving them to the internal RAM: > > --- a/include/configs/imx6_spl.h > +++ b/include/configs/imx6_spl.h > @@ -70,8 +70,8 @@ > #else > #define CONFIG_SPL_BSS_START_ADDR 0x18200000 > #define CONFIG_SPL_BSS_MAX_SIZE 0x100000 /* 1 MB */ > -#define CONFIG_SYS_SPL_MALLOC_START 0x18300000 > -#define CONFIG_SYS_SPL_MALLOC_SIZE 0x3200000 /* 50 MB */ > +#define CONFIG_SYS_SPL_MALLOC_START 0x900000 > +#define CONFIG_SYS_SPL_MALLOC_SIZE 0x8000 > #define CONFIG_SYS_TEXT_BASE 0x17800000 > #endif > #endif > > but still getting spi_alloc_slave() to fail. You want to avoid this "CONFIG_SYS_SPL_MALLOC_*" stuff, as it increases the SPL size by 3kiB compared to MALLOC_F . Also, MALLOC_F needs just the base address of the malloc area to work (see my email). Do you know the return value ? Best regards, Marek Vasut