• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 82 subscribers
  • Views 1485 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

C28xx: File Loader: Verification failed errors. Load to FLASH on F28027 fails, but load to RAM works.

Ciaran Brennan
Intellectual 775 points
Part Number: TMDSCNCD28027
Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28027, LAUNCHXL-F28027, C2000WARE, BOOSTXL-BUCKCONV, LAUNCHXL-F28069M

Tool/software: Code Composer Studio

C28xx: File Loader: Verification failed.  Errors when loading program to FLASH on F28027 Control Card, but loads to RAM OK.
We are having trouble loading the "Example_F2802xLEDBlink" to a TMDSCNCD28027 F28027 Control Card which is in the TMDSHVRESLLCKIT High Voltage LLC Converter. We have searched the E2E forums, and while this appears to be a common problem it is also seems to have many causes.  We've tried many of the suggested fixes without success, and need help!  The error is:
C28xx: File Loader: Verification failed: Values at address 0x3F7000@Program do not match Please verify target memory and memory map.
C28xx: GEL: File: C:\Users\Jeremy\Documents\workspace_v9\Example_F2802xLEDBlink_card\Flash\Example_F2802xLEDBlink.out: a data verification error occurred, file load failed. 
We also see problems erasing the FLASH memory.  Sometimes the load hangs while erasing the flash memory.  In addition, the GUI program that shipped with the TMDSHVRESLLCKIT will not connect to it.
The same project works when the build configuration is set to RAM.  It loads and runs successfully.  The only modification to the code loaded from controlSuite is the GPIOs used to blink the LEDs were changed to GPIO-12 and GPIO-34, as these drive LD2 and LD3 on the control card.  No other files or project configurations were changed.  I created a Target Configuration file with Connection=XDS100v1 and Board=TMS320F28027.
We also have a C2000 Picolo LaunchPad LAUNCHXL-F28027.  The project runs perfectly on that card with in both Flash and RAM configurations.  We've compared the .cmd file, the makefile, the .map file, the GEL file, etc, between the successful LaunchPad version and the unsuccessful control card version, but don't see any differences (other than file paths).
This is the .ccxml file.  The test connections returns successfully.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Debug Probe_1">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Debug Probe_1" href="connections/TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Debug Probe_1" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" desc="Texas Instruments XDS100v1 USB Debug Probe_1" id="Texas Instruments XDS100v1 USB Debug Probe_1">
            <instance XML_version="1.2" href="drivers/tixds100c28x.xml" id="drivers" xml="tixds100c28x.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="0" id="dataFileRequired"/>
            <property Type="choicelist" Value="0" id="The JTAG TCLK Frequency (MHz)">
                <choice Name="Fixed with user specified slower value" value="SPECIFIC">
                    <property Type="stringfield" Value="500KHz" id="-- Enter a value from 488Hz to 1.0MHz"/>
                </choice>
            <choice Name="Fixed with user specified faster value" value="SPECIFIC">
                    <property Type="stringfield" Value="2.0MHz" id="-- Enter a value from 1.0MHz to 6.0MHz"/>
                </choice>
            </property>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28027_0" href="devices/f28027.xml" id="TMS320F28027_0" xml="f28027.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>
We studied the Data Verification Errors document at software-dl.ti.com/.../troubleshooting-data_verification_errors.html and tried all the things that seemed to relate to our problem without success.  Changing the JTAG clock speed to a lower value didn't work.  We tried 100kHz, 200kHz, 500kHz.  We also tried running at 2MHz.  We observed no difference in behavior based on JTAG frequency.  We launched the target manually and tried to browse the memory, but the memory browser window is blank, so we did not succeed.  We launched the On-chip FLash tool to erase the FLASH memory successfully, and checked that the FLASH was unlocked.
We double checked all the jumper connections and switch positions on the TMDSHVRESLLCKIT and the control card and studied the schematics of both and compared them to the Lauchpad schematics. As far as we can tell, the hardware boot configuration and JTAG connections are the same in the control card and the launchpad.

Here is the vintage of the hardware and software we are using.  The CCS, ControlSuite, and C2000Ware were downloaded last month.
TMDSHVRESLLCKIT:  Lot: 040116JR02; Date:  4/1/16
LAUNCHXL-F28027:  Lot: 03262017I2; Week: 19/2017
CCS: Version 9.0.1.00004
ControlSuite: v3.4.9 - March 28, 2018
C2000Ware - v:1.00.06.00
We have exhausted all the actions we can think of at the moment.  Please help us!
  • 0
    TI__Guru 71815 points

    Ciaran,

    I've assigned your post to a C2000 expert, but due to the US holiday we will get back to no later than July 8th, by end of day US Central Time.

    Best regards,
    Matthew

  • 0 in reply to MatthewPate
    Intellectual 775 points

    Matthew,

     

    Any progress on this?  We would greatly appreciate some assistance, having made no progress on our own.

     

    Thanks,

    Ciaran

  • 0 in reply to Ciaran Brennan
    TI__Guru** 109155 points

    Hi Ciaran,

    Did you check that device is not secure? Instead of loading the program, can you just connect to device via CCS and check the flash content via CCS memory watch window? If all the flash content is 0x0 then device is secure and that is the reason you are not able to program or erase the flash content. In such case you need to know the password programmed to unlock the device to be able to perform any flash operation. If you do not know the password then you'll have to replace the part.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 775 points

    Vivek,

    When I connect to it and check the on chip flash in CCS it has 8 security codes which are all FFFF.  I assume this means it is not secured.

    Thanks,

    Ciaran

  • 0 in reply to Ciaran Brennan
    TI__Guru 71815 points

    Ciaran,

    If the device is unlocked and the RAM loader is working(meaning that the JTAG connection is stable), I can't explain why the flash example wouldn't load as well.  

    Let's try and load one of the basic examples for the F2802x in ControlSUITE and see if this has the same error.  The project is here C:\ti\controlSUITE\device_support\f2802x\v230\f2802x_examples_drivers\flash_f2802x 

    Import and compile this in CCS and let's see if we get similar verification errors or not.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Intellectual 775 points

    Hi Matthew.  Thanks for the response.

     We imported the project you named, but, it won't compile!  We get this error:


     This project was created using a version of compiler that is not currently installed - 6.4.2 [C2000]. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'.

    and this warning:

    Invalid project path: Include path not found (\packages\ti\xdais).

     

    The compiler currently installed is:

    ti-cgt-c2000_18.12.1.LTS

     

    I'm not sure what to do about this.  Suggestions?

     

    The TMDSHVRESLLCKIT kit came with a USB drive with the 2011 versions of CCS and ControlSuite loaded on it.  I've pulled an old Win7 computer of similar vintage out of the closet and am installing the old software on it.  We'll see if that works better.

     

    FYI, I've been working with the LAUNCHXL-F28027, the LAUNCHXL-F28069M + BOOSTXL-BUCKCONV, and the TMDSHVRESLLCKIT, and I haven't been able to compile and run the example projects out of the box for any of them.  The  LAUNCHXL-F28069M needed its FTDI chip re-flashed, the LAUNCHXL-F28027 had incorrect build settings in the demo project, and the TMDSHVRESLLCKIT - well, we're still working on that.  It's been rough sledding!  

    - Ciaran

  • 0 in reply to Ciaran Brennan
    TI__Guru 71815 points

    Ciaran,

    I'm sorry about this, there are some inherent changes that have occured in the tool chain since the controlSUITE version of those files have last been updated.

    It is possible to fix these in the properties of the projects, but instead let's install C2000Ware package, which has these examples updated for the lastest tools.

    The path once you have installed C2000Ware is C:\ti\c2000\C2000Ware_2_00_00_02\device_support\f2802x\examples\drivers\flash_f2802x

    This should compile and run out of the box.  You will have to delete the project in controlSUITE from your project view since it has the same name as the above.

    Please make sure to select the check box to delete the files from the disk; when you import a project it creates a full copy in your workspace, and uses that for any modifications. This action deletes the local workspace copy, not the root in controlSUITE.  This is necesary since the files names are the same.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Intellectual 775 points

    Matthew,

    C2000Ware was already installed.  After doing as you said and attempting to upload the program to flash we got this error.

    C28xx: File Loader: Verification failed: Values at address 0x3F7000@Program do not match Please verify target memory and memory map.
    C28xx: GEL: File: C:\Users\Jeremy\Documents\workspace_v9\Example_28027_Flash\Flash\Example_28027_Flash.out: a data verification error occurred, file load failed.

    Seems to be the same error as our other attempts to upload to flash.

    Since we can program our other two C2000 boards, we are wondering if there is some hardware problem.  Do you think using a separate XDS100v2 debug probe would help?  I see the main board has a header for it and a jumper to disable the built in debug probe.  Or perhaps we have to replace the controller card.

    One other fact:  This is the second TMDSHVRESLLCKIT unit we have used.  The first one was returned for an unrelated hardware defect.  Both units showed the same problem programming to Flash, and both units would not connect with the GUI demo program.

    Thanks,

    Ciaran

  • 0 in reply to Ciaran Brennan
    TI__Guru 71815 points

    Trying an external emulator is a good idea at this point, from the HW doc file here 

    C:\ti\controlSUITE\development_kits\TMDSHVRESLLCKIT_v1.0\~Docs\HVLLC-HWGuide[R3].pdf

    it looks like you want to populate J5 in the M4 macro to do this.  

    I noticed this section on page 6 of the same document, wanted to make sure this has been followed(since each control card would need to R10 mod)

    3.4 GUI Connection
    The FTDI chip present on the board can be used as an isolated SCI for communicating with a HOST (e.g.
    – a PC). The following jumper settings must be done to enable this connection
    1. Populate jumper [M4]-J4
    2. Remove jumper [Main]-J6
    3. For F28035, put SW3 on the F28035 controlCARD to OFF position
    For F28027, verify that R10 on the controlCARD is removed
    4. Connect a USB cable from [M4]-JP1 to the HOST
    Note: If you are going to boot from Flash & connect using the GUI, you will need to use the proper “Boot
    from FLASH” settings described in Table 1.


    Best,
    Matthew

  • 0 in reply to MatthewPate
    Intellectual 775 points

    Matthew,

    We checked the setup configurations you listed, and they were all correct.  The control card did not have R10 populated as shipped.  

    I've ordered the XDS110 debug probe and another F28027 control card from Digikey.  They should be here tomorrow.  

    Thanks,

    Ciaran

    XDS110 

  • 0 in reply to MatthewPate
    Intellectual 775 points

    Matthew,

    I received the new F28027 control card and the XDS110 debug probe.  We discovered that replacing the control card solved the problem.  We are now able to flash the demo code and run the demo GUI.

    The new XDS110 probe works too, but the onboard XDS100v1 is working OK, so we'll use that for now.

    Thanks for your help.  

    - Ciaran