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.

RE: AISgen installer for Linux

Other Parts Discussed in Thread: OMAPL138, OMAP-L138, DA8XX

Hi, I'd like to know where to download the Aisgen for Linux, Does anyone know?

  • Hi Daniel,

    The AISGen GUI has an dependency on .Net hence, you may not be able to use the GUI based tool but we provide a command line equivalent utility HexAISgen_OMAPL138.exe which you can use under Linux OS using Mono. We don`t provide a linux installer for the AISGen package provided on ti.com but can send you the installer in a separate email.

    Regards,

    Rahul

  • Hi Daniel,

    For step by step instruction, on how to use the "HexAIS"tool through "mono" please refer to "Flashing Boot Images on Linux Without CCS" at

    http://processors.wiki.ti.com/index.php/GSG:_DA8x/OMAP-L1/AM1x_DVEVM_Additional_Procedures#Flashing_Boot_Images_on_Linux_Without_CCS

    The steps given are for OMAPL138. You may have to use it appropriate to your hardware.

     

    Regards,

    Shankari.

     

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • I appreciate your answer, I just can't boot my device, because the u-boot you have in the pre-built images doesn't recognize the "usb" command when I write "usb reset", How could I enable(configure) this command?.

    I have one more question: How could I use the HexAIS tool? I mean, looking at the example the file to be converted is .ini, and the compiled u-boot is .bin, How would be the command? Something like : mono ./HexAIS_OMAP-L138.exe  u-boot.bin(input) -o u-boot_ais.bin(output), because I look in the help menu and I can't figure it out, I am working with the omapl138 L.C.D.K. board, I just want to convert the u-boot obtained in the building process in an usable u-boot in the board,

    Thanks

    Daniel

  • Hi, I am still working on that I figure out how to use the tool you mentioned, now I am stuck trying to make it works. My principal aim is to flash the kernel and the filesystem using an usb mass storage. I change the /include/configs/omapl138_lcdk.h with that:

    /*
     * USB configuration
     */
    #define CONFIG_USB_DA8XX        /* Platform hookup to MUSB controller */
    #define CONFIG_MUSB_UDC

    #ifdef CONFIG_USB_DA8XX

    #ifdef CONFIG_MUSB_HCD          /* include support for usb host */
    #define CONFIG_CMD_USB          /* include support for usb cmd */

    #define CONFIG_USB_STORAGE      /* MSC class support */
    #define CONFIG_CMD_STORAGE      /* inclue support for usb-storage cmd */
    #define CONFIG_CMD_FAT          /* inclue support for FAT/storage */
    #define CONFIG_DOS_PARTITION    /* inclue support for FAT/storage */

    #ifdef CONFIG_USB_KEYBOARD      /* HID class support */
    #define CONFIG_SYS_USB_EVENT_POLL
    #define CONFIG_PREBOOT "usb start"
    #endif /* CONFIG_USB_KEYBOARD */

    #endif /* CONFIG_MUSB_HCD */

    #ifdef CONFIG_MUSB_UDC
    /* USB device configuration */
    #define CONFIG_USB_DEVICE               1
    #define CONFIG_USB_TTY                  1
    //#define CONFIG_SYS_CONSOLE_IS_IN_ENV    1
    /* Change these to suit your needs */
    #define CONFIG_USBD_VENDORID            0x0451
    #define CONFIG_USBD_PRODUCTID           0x5678
    #define CONFIG_USBD_MANUFACTURER        "Texas Instruments"
    #define CONFIG_USBD_PRODUCT_NAME        "Omapl138 L.C.D.K."
    #endif /* CONFIG_MUSB_UDC */

    #endif /* CONFIG_USB_DA8XX */

    I get the u-boot.bin, now I use the tool in this way:

    mono ./HexAIS_OMAP-L138.exe -ini OMAP-L138-uart.ini -o <path>/u-boot.bin@0xc1080000

    and it generates the file, but when I try to use it, it doesn't work, I think is in the ais convertion because I use the same tool with the usb-boot-lcdk.bin in the prebuilt-images and it doesn't work either.

  • Hi Daniel,

    The file that you are using is probably for the EVM UART boot mode. please try the following INI file for NAND boot on OMAPL138 LCDK. Are you using the latest version of the AIS Gen tools. If yes, then look for the OMAP-L138_ARM_nand_ecc_patch_lcdk.ini INI file for the LCDK under the patch_binaries/INI . This should configure the PLL, DDR2, and the NAND for the LCDK boot.

    Let us know if you still have any issues.

    Thanks and Regards,

    Rahul

  • Hi, I couldn't find the .ini you mentioned, Coul you please give the web page link, of the latest AIS Gen tools, because I download the software tools of this page:

    http://software-dl.ti.com/dsps/dsps_public_sw/c6000/web/omapl138_lcdk_sdk/latest/index_FDS.html

    and is the same that I have, and there I just can find the omap_la138_uart.ini and the omap_l138.ini.

  • I have attached the INI file for the LCDK NAND boot.

    http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/115/7853.OMAP_2D00_L138_5F00_ARM_5F00_nand_5F00_lcdk.ini

    Regards,

    Rahul

    PS : Download the AISGen package from the bootloader application Notes

  • Thank you, but I still can't generate successfully the u-boot_ais.bin, I write:

    mono ./HexAIS_OMAP-L138.exe -ini 7853.OMAP-L138_ARM_nand_lcdk.ini -entrypoint 0xc1080000 ARM_AISExtra_OMAP-L138.out <path>/u-boot-lcdk.bin,

    the answer is:

    Begining the AIS file generation.
    AIS file being generated for bootmode: NAND.
    Parsing the input object file, ARM_AISExtra_OMAP-L138.out.
    ERROR: Not a valid object file.
    AIS file generation was successful.
    Wrote 680 bytes to file u-boot-lcdk.bin.
    Conversion is complete.
     

    Is obviously that the file is wrong generated, because its size is 680 bytes, and the u-boot-lcdk_ais.bin pre-built is about 353 Kylobytes. I read the document you sent but I still don't know what's missing in the command. And without the .out file the size of the generated file is 68 bytes.