• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 769 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AISgen for D800K003 fails to generate SPI slave boot file for TMS320C6747

DKumar
Prodigy 90 points
Other Parts Discussed in Thread: TMS320C6747, OMAP-L137

We have a custom board based on a TMS320C6747.  We built protos using the rev 1.1 silicon which are fully functional and we are moving to the 2.0 silicon.

Rev 1.1 silicon uses the D800K001 bootloader.

Rev 2 silicon uses the D800K003 bootloader.

When we try to use the D800K003 AISgen utility (version 0.1.0.0) to make a boot image for the rev2 silicon using  SPI0 slave-mode boot, it fails.  AISgen claims the operation is successful, but it isn't if you read the log file (AISgen.log shows "Requested value 'SPI' was not found" and an exception dump).and no new file is created.

Any ideas?

  • 0
    TI__Intellectual 1870 points

    Hi,

    Sorry for inconvenience. Upgrading AISgen for D800K003 to version 0.4.0.0 (latest as of now) should solve your issue. Please contact your TI contact to get it.

  • 0 in reply to Urmil Parikh
    Prodigy 90 points

    I obtained D800K003 v0.4.0.0 from my TI contact.  It still fails for a SPI0 slave boot configuration.  The only difference is that now the AISgen utility reports that an error occurred as opposed to silently failing before.  The log file AISgen.log is shown below.  My guess is that the utility is generating the wrong text in the config file.

    ; Created by AISgen for D800K003 v0.4.0.0

    [General]
    BootMode = SPI
    crcCheckType = SECTION_CRC

    [PLLCONFIG]
    PLLCFG0 = 0x17010202
    PLLCFG1 = 0x000501C2

    ; DIV4p5
    [AIS_Set]
    TYPE    = 0x00020004
    ADDRESS = 0x01C14188
    DATA    = 7
    SLEEP   = 0

    [EMIF3SDRAM]
    SDCR    = 0x1c420
    SDTIMR  = 0x0e9129d0
    SDTIMR2 = 0x7d2
    SDRCR   = 0x30090005

     

    -ini AISgen.ini -o "C:\Documents and Settings\Derek\My Documents\Visual Studio Projects\dsprecv2\Release\dsprecv.bin" "C:\Documents and Settings\Derek\My Documents\Visual Studio Projects\dsprecv2\Release\dsprecv.out"

    -----------------------------------------------------
       TI AIS Hex File Generator for OMAP-L137
       (C) 2010, Texas Instruments, Inc.
       Ver. 1.19
    -----------------------------------------------------


       at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
       at TI.AISLib.AISGen.GeneralIniSectionParse(AISGen devAISGen, IniFile iniFile)
       at TI.AISLib.AISGen.GenAIS(AISGen devAISGen, List`1 inputFileNames, IniFile iniFile)
       at TIBootAndFlash.Program.Main(String[] args)
    Requested value 'SPI' was not found.
    Unhandled Exception!!! Application will now exit.

     

  • 0 in reply to DKumar
    Prodigy 90 points

    For the benefit of others who read this forum, it turns out there are several serious underlying problems:

    1)   AISgen for D800K003  bombs out and fails to generate files for SPI slave boot modes or other boot modes.  The GUI is generating the .ini file incorrectly.

    2)   Rev2 silicon of the TMS320C674x parts have a bug in their CRC calculation in the mask ROM for SPI slave boot mode.  I don't know is this applies to other modes.  

    I obtained a patch command line version of  AISgen D800K003 for the OMAPL137 from that factory that provides a workaround for item 2) above.   However, anyone who has existing boot images from rev 1.1 silicon with CRC enabled will have to re-generate the bootable image for rev2 devices.

  • 0 in reply to DKumar
    TI__Intellectual 1870 points

    Issue #1 has been addressed and AISgen v0.5.0.0 is released for publication.

  • 0 in reply to Urmil Parikh
    Prodigy 30 points

    Where can we find the AISGen for D800K003 version 0.5.0.0? sprab04d still appear to include V0.1.0.0.

    Also, any other info about the CRC calculation? Does it affect the master SPI boot mode too?

    Finally, the 'Sequential Read' checkmark didn't seem to have any effect in V0.1.0.0 (no command in bin file), is this fixed in V0.5.0.0?

    Thanks,

    Guy Caron