• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 100 subscribers
  • Views 2532 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.

EEPROM read error, after trying to burn POST application

Koray Korkmazer
Intellectual 820 points

Hello,

I just started to use EVM6678L.

I am using CCS 5.0.3 and MCSDK 2.00.00.11 .

After trying to burn POST application to the EEPROM, I started to get 'EEPROM read failed' error. And since then I couldn't succeed to read EEPROM.

Here is what I have done:

1. First I burned i2crom_0x51_c6678_le.dat file to EEPROM at i2c address 0x51 using EEPROM Writer project.  I saw 'EEPROM programmed succesfully' comment in the console.

For burning POST to EEPROM:

1. I started 'post_romparse.bat' which is under 'C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin'.

2. In the same folder, there should have occur a file called 'post_i2crom.dat'. But it didn't occur. Although the other temporary files occured(like i2crom.ccs) , the resulting dat file had not been created. So I had a look to the post_romparse.bat file, and seemed to me that somehow the last two commands had not been executed. The last two commands were mv and rm commands. So I decided to do them manually and renamed i2crom.ccs file as post_i2crom.dat.

3. I programmed it to EEPROM using EEPROM writer project to the i2c address 0x50. I saw 'EEPROM programmed succesfully' comment in the console. But since then I couldn't read the EEPROM. When I execute eeprom test process in POST, I get 'EEPROM read test failed' comment. When I had gone deeper into the eeprom test process to see what is going on, I saw that in  i2cEepromWriteBlock function, it can not see the transmit ready signal.

4. I thought that EEPROM may have been damaged and decided to change it. After changing the EEPROM, it worked with no problem.  

But after I burned the applications as I described above to the new EEPROM,  I had an 'EEPROM read test failed' error again.

Do you have any idea about the cause of the problem?

thanks in advance,

koray.

  • 0
    TI__Genius 9915 points

    Did you get any error when running the romparse.bat files?

     

    thanks,

    arun.

  • 0 in reply to ArunMani
    Intellectual 820 points

    Yes Arun,

    I saw there are some warnings, here is the resulting output after running post_romparse.bat:

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>pos
    t_romparse.bat

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>set
     C6000_CG_DIR="C:\Program Files\Texas Instruments\ccsv5\tools\compiler\c6000"

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>set
     TARGET=6678

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>set
     ENDIAN=little

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>set
     IBL_ROOT_DIR="..\..\..\boot_loader\ibl"

    C:\Program Files\Texas Instruments\mcsdk_2_00_00_11\tools\post\evmc6678l\bin>set
     PATH=C:/Program Files/Texas Instruments/xdctools_3_20_08_88;C:\oracle\ora92\bin
    ;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\
    WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\c
    ommon;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Micr
    osoft Visual Studio 8\VC\bin;C:\Program Files\Windows Imaging\;C:\Program Files\
    Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\D
    TS\Binn\;C:\Program Files\010Editor;;C:\Program Files\IBM\RationalSDLC\ClearCase
    \bin;C:\Program Files\IBM\RationalSDLC\common;C:/Program Files/Texas Instruments
    /xdctools_3_20_08_88;C:\WINDOWS\system32;C:\WINDOWS;
    C6000_CG_DIR set as: "C:\Program Files\Texas Instruments\ccsv5\tools\compiler\c6
    000"
    TARGET set as: 6678
    IBL_ROOT_DIR set as : "..\..\..\boot_loader\ibl"
    Converting .out to HEX ...
    Translating to ASCII-Hex format...
       "post_evm6678l.out"   ==> .text
    warning: section post_evm6678l.out(.text) at 0830000h falls in unconfigured
       memory (skipped)
       "post_evm6678l.out"   ==> .const
    warning: section post_evm6678l.out(.const) at 08435f0h falls in unconfigured
       memory (skipped)
       "post_evm6678l.out"   ==> .cinit
    warning: section post_evm6678l.out(.cinit) at 0843b9ch falls in unconfigured
       memory (skipped)
    Translating to ASCII-Hex format...
       "post_evm6678l.out"   ==> .text      (BOOT LOAD)
       "post_evm6678l.out"   ==> .cinit     (BOOT LOAD)
       "post_evm6678l.out"   ==> .const     (BOOT LOAD)
    Generating I2C ROM data ...
    'mv' is not recognized as an internal or external command,
    operable program or batch file.
    'rm' is not recognized as an internal or external command,
    operable program or batch file.

  • 0 in reply to Koray Korkmazer
    Intellectual 820 points

     

    The addresses in the warnings correspond to the L2 Memory.

    But I thought it must already be configured, right ?

    koray.

  • 0 in reply to Koray Korkmazer
    TI__Genius 9915 points

    Hi Koray,

    Sorry for the delay. Do you have a Cygwin or Msys environment installed in the PC. The romparse util need these tools. This is documented build instructions under ibl folder. Please let me know if you still have problems.

     

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Intellectual 820 points

    Hello Arun,

    The cygwin is installed. But I noticed that its path wasn't defined in PATH environment variable so I defined it. And re-executed the post_romparse.bat.

    But this time I got  "could not open the file post.b for reading" error.

    However, the main point I didn't understand is even if I burned a wrong file to the EPROM, how it is possible to completely lose EPROM connection? I even can't read it right now.

    koray.

  • 0 in reply to Koray Korkmazer
    TI__Genius 9915 points

    It is possible that you might have corrupted the EEPROM header itself. One thing to check is you can reflas the default post out file in the MCSDK and see if that helps. For the error, please follow all the steps as mentioned. I haven't tried out myself. But I will try to reproduce your issue here and let you know a solution.

     

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Intellectual 820 points

    I've already tried flashing post.out to EPROM again but unfortunately the result is the same. I2c read error...

  • 0 in reply to Koray Korkmazer
    TI__Expert 7460 points

    Hello Koray bey,

    As you confirmed that the problem has been solved with the new EVM, so could you please confirm that the problem was releated to the EEPROM IC on your EVM?

    Best Regards

    Yunus Karaborek

  • 0 in reply to Yunus Karaborek
    Intellectual 820 points

    Yes ,

    I tried the same process with an another EVM and managed to program EVM succesfully. It seems that somehow my EVM's EEPROM is unreachable .

    koray.

  • 0 in reply to Koray Korkmazer
    TI__Expert 7460 points

    Hello Koray Bey,

    Thanks for your confirmation. 

    Please let us know if you have any question.

     

    Best Regards

    Yunus Karaborek

  • 0 in reply to Koray Korkmazer
    Guru 10750 points

    Hi Koray,

    I failed program post to the EEPROM (No issues with the EEPROM writer), post_i2crom.bin or post_i2crom.dat as you mentioned (rename i2crom.ccs to post_i2crom.dat) have you done something special for having it working? Why do I need to use Cygwin or Msys environment for running romparse?

    Thanks,

    HR