This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

building u-boot for da850evm vs building u-boot for LCDK

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

For the da850evm, you can build u-boot in ais form from the command line:

make distclean
make da850evm_config
make u-boot.ais


and flash it using sfh_OMAP-L138.exe without a separate "generate AIS" step.  Why hasn't the omapl138_lcdk configuration been set up the same way?

  • Hi Peter,

    make distclean ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi-
    make omapl138_lcdk_config ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi-
    make u-boot.bin ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi-

    You need to convert u-boot.bin to u-boot.ais through AIS gen tool with below configuration.

    http://processors.wiki.ti.com/index.php/How_to_boot_OMAP-L138_LCDK_from_SD_card

    http://processors.wiki.ti.com/images/7/71/LCDK_MMC.zip

  • Thanks, but

    1. I was already aware of that material,
    2. It doesn't actually answer my question.

    My question was not "How do I generate an AIS image?"  It was "Why was the LCDK not set up to do the whole thing off the u-boot build like it's been done for the EVM?"   And I'll put  a following question: Why is the only configuration for doing the conversion the *.cfg file rather than the *.ini file for the command line version of the kernel tool?  Not only do you take what should be a single-step process and make it a two-step process, but you also make it so I can't even run the second step on the machine I've just done the first step on.  I have to copy the u-boot.bin to a Windows machine, run the gui version of the converter to produce the AIS image, then copy it back to the linux machine which is attached to the LCDK to flash it to the board.  When that should all be covered by "make u-boot.ais" like it is for the da850evm.

  • HI Peter,

    EVM board has SPI flash and SPL code had support for SPI flash whereas LCDK board has NAND flash and unfortunately we don't have code for NAND flash in SPL.

    u-boot's Makefile,

    $(obj)u-boot.ais:       $(obj)spl/u-boot-spl.bin $(obj)u-boot.bin
    		$(obj)tools/mkimage -s -n /dev/null -T aisimage \
    			-e $(CONFIG_SPL_TEXT_BASE) \
    			-d $(obj)spl/u-boot-spl.bin \
    			$(obj)spl/u-boot-spl.ais
    		$(OBJCOPY) ${OBJCFLAGS} -I binary \
    			--pad-to=$(CONFIG_SPL_MAX_SIZE) -O binary \
    			$(obj)spl/u-boot-spl.ais $(obj)spl/u-boot-spl-pad.ais
    		cat $(obj)spl/u-boot-spl-pad.ais $(obj)u-boot.bin > \
    			$(obj)u-boot.ais
    		rm $(obj)spl/u-boot-spl{,-pad}.ais

  • Thanks, that's making a bit more sense.  So, If I understand things, the u-boot.ais produced for the EVM via make, and the ais image produced by the conversion tool for the LCDK are not really equivalent.  That correct?

    So does a comprehensive *.ini to use with HexAIS anywhere?  The examples provided in the dev kit are really templates, and it would be good to start with a working file.  Or can you not use HexAIS with the LCDK?

    Thanks.

  • A1) Yes, you are right

    A2) I haven't tried HexAIS (commnad) tool but I worked with AISgen (GUI) tool that need .cfg and got working fine (my own u-boo,ais for LCDK board with the following .cfg file).

    2086.LCDK_AISGen_Config.cfg

    Also follow the steps that mentioned in the following link.

    http://processors.wiki.ti.com/index.php/How_to_boot_OMAP-L138_LCDK_from_SD_card#Generate_AIS_version_of_U-Boot_using_AISGen

    Try it and let me know.

  • Apologies for the delay in replying . . . I wanted to sort out something first.

    I have played with AISGen and although it's still not my preferred option, it works fine in creating a u-boot image I can flash to the LCDK and have working.

    The thing I wanted to sort out is, I've ported the TI-supplied u-boot code for the LCDK onto the upstream u-boot repo. So if you clone the main u-boot git repo you have omapl138_lcdk as a target you can configure and build, and it should appear in the v2015.07 release.
  • Thanks Peter.
    I've already used and got working the latest u-boot.
    e2e.ti.com/.../418150