[U-Boot] u-boot 2018 SPI SPL

[Mehmet Ali İPİN]

Dear Fabio,

Windows 10 tried but could not load the device driver of our eMMC (micron tech MTFC4GLDDQ). Then

I programmed SPL and u-boot.img into eMMC with u-boot commands; even SPI flash based SPL see the MMC1(eMMC), u-boot did not run correctly.

As shown below, I put printf/puts messages in function entry and exit to debug SPL:

U-Boot SPL 2018.05-rc1 (Apr 27 2018 - 04:15:59 -0700)
SPL set_bd()
SPL Malloc; gd flags
SPL init_i
SPL init_exit
boot mode bmode =32000001
boot mode reg =18080030
SPI serial mode return
board boot order boot list
spl_boot_list:8
spl_boot_list:8
SPL image loader boot device 8
boot device name:MMC1
boot device name:MMC1
boot device name:MMC1
boot device name:MMC1
SPL image loader Not Found
Trying to boot from -442503140
SPL: Unsupported Boot Device!
spl_boot_list:1
SPL image loader boot device 1
boot device name:MMC1
Trying to boot from 1
Trying to boot from MMC1
SPL load image


I disabled #CONFIG_SPL_OS_BOOT=y flag, to disable direct boot linux kernel code, changed boot from SD directives to spi, tested many other serial SPI boot config definitions, included all congatec cgtqmx_defconfig definitions;

İn my SPI SPL, SRC_SBMR1 read returns 0x18080030 which is exactly my spi nor flash register boot setting,  and spl_boot _list:8 (SPI NOR Boot setting, (which is verified by my "SPI serial mode return" printf message), boot device name is always MMC1. Its always trying to boot from -442503140, and can not find SPL image loader finally.. 

Since they did not give all of their u-boot source and config files, It is impossible for me to know how congatec succeded from SPI boot of SPL+u-boot.img,  

But my test of u-boot 2018.01/05 shows, even my DCD header in SPI is correct, even I proceeded congatech's SPI  SPL u-boot.img flash loading sequences, after testing many configurations in 2/3 weeks I am sure there is a problem with SPL u-boot.img for SPI boot such that:

Even on chip ROM code detects correct boot register settings,  jumps to spi flash, starts executing SPL codes, it always search MMC/SD card.

Since it is very important for us to bring this i.mx6 board, which several projects depend on it;

And since I did not see your name in SPL files, May I request your kind helps, if you can direct me to whom developing SPL codes for u-boot 2018 in  list.denx.de group?

Thanks and best regards.

Mehmet Ali Ipin.


-----Original Message-----
From: Fabio Estevam [mailto:festevam at gmail.com] 
Sent: Saturday, April 21, 2018 2:40 AM
To: Mehmet Ali İPİN <mehmet.ipin at pavotek.com.tr>
Cc: u-boot at lists.denx.de; Kutsal ANIL <kutsal.anil at pavotek.com.tr>
Subject: Re: [U-Boot] u-boot 2018 SPI SPL

On Fri, Apr 20, 2018 at 3:43 AM, Mehmet Ali İPİN <mehmet.ipin at pavotek.com.tr> wrote:
> Dear Fabio
>
> Thank you very much for your directives and helps.
>
> I applied the steps in WARP board readme file, for the command
>
> => ums 0 mmc 2
>
> I received Unknown command 'ums' - try 'help'
>
> I compared with  WARP7 defconfig and mx6sabresd_defconfig files added some definitions in WARP, but got error messages in make file.
> Therefore I would appreciate your helps/commends if you write me the definitions in config/defconfig files to enable u-boot to run this command?

You can take a look at this commit for reference:

commit 506abdb4ee9664cc0d6d1321e96f7fb8dae72eb9
Author: Marek Vasut <marex at denx.de>
Date:   Sun Oct 22 10:22:40 2017 +0200

    ARM: imx6: Enable UMS and DFU on DHCOM i.MX6 PDK

    Enable UMS and DFU, so that the eMMC can be accessed via the
    USB gadget port on the board.

    Signed-off-by: Marek Vasut <marex at denx.de>
    Cc: Stefano Babic <sbabic at denx.de>