Skip to main content
Visitor II
July 5, 2005
Question

STVD7 3.0 eeprom problem

  • July 5, 2005
  • 6 replies
  • 1149 views
Posted on July 05, 2005 at 06:43

STVD7 3.0 eeprom problem

    This topic has been closed for replies.

    6 replies

    Visitor II
    June 24, 2004
    Posted on June 24, 2004 at 10:00

    Hi,

    I'm working with STVD7 3.0 (Cosmic Toolchain) and target MCU ST7FLITE29.

    I want to use the onboard data eeprom. I know that the eeprom area must be defined in the linker command file but I cant find the way to do it in STVD7. Of course I can do it manually by simply add ''+seg .eeprom -b 0x1000 -m256'' in the .lkf file, but I want STVD7 to do it. All other segments can be defined in the Linker->Input options, but not eeprom. Why?

    Regards

    bood
    Visitor II
    July 2, 2004
    Posted on July 02, 2004 at 06:10

    Apparently there was not enough room on the window for displaying all the possible options and the EEPROM was not implemented. You just have to untick tha auto check box and add the correct lines in the .lkf file which I guess you already did.

    Do you feel that this is a real draw-back ?

    [ This message was edited by: Alaini on 02-07-2004 09:41 ]
    Visitor II
    July 2, 2004
    Posted on July 02, 2004 at 07:01

    Thanks for response.

    I believe that data eeprom is commonly used in applications. Therefore it's a pity that the Auto function cant be used in such cases because of lacking window space !?

    Regards

    bood

    Visitor II
    July 7, 2004
    Posted on July 07, 2004 at 06:40

    Hi Bood,

    thats's what I told to the development team. They are thinking how to overcome this limitation but the solution is apparently not so simple. Sorry for the inconvenience.
    Visitor II
    June 28, 2005
    Posted on June 28, 2005 at 23:21

    Hi All,

    a simple trick to solve the problem:

    add the following lines to the ''Pre-Link'' tab of Project Settings:

    cmd.exe /C rename $(OutputPath)$(TargetSName).lkf $(TargetSName).$$$

    cmd.exe /C echo # > $(OutputPath)$(TargetSName).lkf

    cmd.exe /C echo # >> $(OutputPath)$(TargetSName).lkf

    cmd.exe /C echo +seg .eeprom -b 0x1000 -m256 >> $(OutputPath)$(TargetSName).lkf

    cmd.exe /C echo # >> $(OutputPath)$(TargetSName).lkf

    cmd.exe /C echo # >> $(OutputPath)$(TargetSName).lkf

    cmd.exe /C copy $(OutputPath)$(TargetSName).lkf+$(OutputPath)$(TargetSName).$$$ $(OutputPath)$(TargetSName).lkf

    cmd.exe /C del $(OutputPath)$(TargetSName).$$$

    the result is that the LKF file contains the eeprom seg definition

    Regards

    StefanoM

    Visitor II
    July 5, 2005
    Posted on July 05, 2005 at 06:43

    Very clever Stefano but take care that you make the assumption that the lkf file is regenerated each time by STVD7. This may not be true in the next version so check that the trick works with each new version of STVD7.

    [ This message was edited by: Alaini on 06-07-2005 09:55 ]