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.

Hercules Launchpad (TMS570LS04x) not useable because of problems with programming the flash

Other Parts Discussed in Thread: UNIFLASH, TMS570LS0432

Hi,

I recently bought a Hercules Launchpad (with TMS570LS04x).

I tried project0 but I am not able to start debugging because I always get the following messages:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Writing Flash @ Address 0x00000000 of Length 0x000043CC CortexR4: Flash operation timed out waiting for the algorithm to complete. Operation cancelled. CortexR4: Error Writing Flash @ Address 0x00000000 of Length 0x000043CC CortexR4: GEL: File: C:\MG\InstallSetup\TI\Project0\N2HET\TMS570LS04_Proj\Debug\N2HET_LS04.out: Load failed.

I also downloaded the project0 here http://processors.wiki.ti.com/index.php/Hercules_LaunchPad:_Project_0 and tried it. But I have the same problems.

The Hercules Safety MCU Demo runs without problems always: First the flash is erased and then programmed.

I am using CCS 5.5.0 on windows 7 pro x64 (vmware). I installed the latest updates. With UniFlash (V3.0.0) I have the same errors.

Thanks for any hint.

Best regards,

Michael

  • Can you connect to the TMS570LS04x?

    If not, can you check the "TEST connection" function like in another post (you post there too).

    If "TEST connection" does not work, can you go to windows device manager to see if "XDS100V2" presents there?

    Regards,

    Haixiao

  • Thanks for your answer.

    The „Test connection“ works fine. The “XDS100V2” is present in the device manager.

    Mostly I am able to erase the flash without any error:

    [16:27:01] Begin Launching session operation.

    [16:27:02] Operation Launching session returned.

    [16:27:02] Loaded target configuration from: C:\Users\MICHAE~1\AppData\Local\.TI\ti\0\0/temptargetconfiguration.ccxml

    [16:27:03] Settings purged.

    [16:27:50] CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0

    [16:27:51] CortexR4: Erasing Flash memory...

     [16:29:23] CortexR4: Erasing Flash Bank 0, Sector 0

     [16:29:29] CortexR4: Erasing Flash Bank 0, Sector 1

     [16:29:34] CortexR4: Erasing Flash Bank 0, Sector 2

     [16:29:40] CortexR4: Erasing Flash Bank 0, Sector 3

     [16:29:46] CortexR4: Erasing Flash Bank 0, Sector 4

     [16:29:51] CortexR4: Erasing Flash Bank 0, Sector 5

     [16:29:57] CortexR4: Erasing Flash Bank 0, Sector 6

     [16:30:02] CortexR4: Erasing Flash Bank 0, Sector 7

     [16:30:08] CortexR4: Erasing Flash Bank 0, Sector 8

     [16:30:14] CortexR4: Erasing Flash Bank 0, Sector 9

     [16:30:30] CortexR4: Erasing Flash Bank 0, Sector 10

     [16:30:49] CortexR4: Erasing Flash Bank 0, Sector 11

     [16:30:54] CortexR4: Erasing Flash Bank 0, Sector 12

     [16:31:00] CortexR4: Erasing Flash Bank 0, Sector 13

     [16:31:05] CortexR4: Erasing Flash Bank 0, Sector 14

     [16:31:10] CortexR4: Erasing Flash Bank 7, Sector 0

     [16:31:16] CortexR4: Erasing Flash Bank 7, Sector 1

     [16:31:21] CortexR4: Erasing Flash Bank 7, Sector 2

     [16:31:27] CortexR4: Erasing Flash Bank 7, Sector 3

     [16:31:31] CortexR4: Operation completed successfully.

     

    Then the process is interrupted before it is finished.

    As I said, the “Hercules Safety MCU Demo” runs without problems every time.This demo is using the same connection. 

    I think if the "other post" would be solved my problem would be solved as well.

    Michael

     

  • I just tried with win7/64bit ccs5, works fine on my bench.

    Did you tried nowFlash? After you installed  the safety demo, the nowFlash should be installed too.

    The safety demo actually call the nowFlash to program the device.

    Regards,

    Haixiao

  • Hi,

    thanks for the hint with nowFlash.

    I was able to do a step ahead but I have still problems.

    I found that nowFlash creates a log-file.

    Here is the contend of the log-file when I run the MCU Demo:

    Errorlevel=0        
    nowFlash version 3.42  Build  (OFFICIAL)
    Config file C:\ti\nowFlash\v3.42.3\nowFlash.cfg Revision: 3
    Port address 0x000 target..initialize..connect..reset..halt..complete
    Device ID value read=0x8048AD05 on port 0x000
    Device is Hercules type  with ECC, Unique ID=0x8048AD05, Minor Revision 0.
    Device Identification=TMS570LS0432.0
    Target Frequency 80.00 MHz
    Configuration file: v3.42 , file rev: 3
    Algorithm library: F021_R4_BE.x70, Version 1.60
    Command: -pr -cs C:\ti\Hercules\Hercules Safety MCU Demos\TMS570LS04x_demo_software.out -w 1 -q -emu TIXDS100V2 -p 000 -cpu CORTEX_RXX_NODAP -targets 1 -no_freq_check
        Programming from 0x00000000 to 0x0000A49F
        Programming from 0xF0400000 to 0xF0401493
        Elapsed execution time 318.31 seconds.
        Total elapsed time 354.10 sec
    No Errors

    Here you can see that the cpu type is "CORTEX_RXX_NODAP". I used "CORTEX_RXX" always. After I changed the cpu type to "CORTEX_RXX_NODAP" I was able to programm the hercules launchpad with nowFlash otherwise it will fail.

    Here is the contend of the log-file when I run nowFlash by my self:

    Errorlevel=0        
    nowFlash version 3.42  Build  (OFFICIAL)
    Config file C:\ti\nowFlash\v3.42.3\nowFlash.cfg Revision: 3
    Port address 0x000 target..initialize..connect..reset..halt..complete
    Device ID value read=0x8048AD05 on port 0x000
    Device is Hercules type  with ECC, Unique ID=0x8048AD05, Minor Revision 0.
    Device Identification=TMS570LS0432.0
    Target Frequency 80.00 MHz
    Configuration file: v3.42 , file rev: 3
    Algorithm library: F021_R4_BE.x70, Version 1.60
    Command: -pr C:\ti\Hercules\Hercules Safety MCU Demos\TMS570LS04x_demo_software.out -w 1 -q -emu TIXDS100V2 -p 000 -cpu CORTEX_RXX_NODAP -targets 1
        Programming from 0x00000000 to 0x0000A49F
        Programming from 0xF0400000 to 0xF0401493
        Elapsed execution time 2542.08 seconds.
        Total elapsed time 2893.76 sec
    No Errors

    As you can see it looks almost the same but the total time is 8x longer than the MCU Demo.

    What I can see the MCU Demo is using the setting -no_freq_check which is not possible to set by the GUI.

    What do you think about this?

    Why is the the cpu type CORTEX_RXX_NODAP?

    Is "-no_freq_check" the reason for the long time?

    How can I solve the problem with CCS v5.5?

    Best regards

    Michael

  • Do you really see it consumes 2893.76 seconds? That is like one hour. If it is true, I think the MCU is sth wrong.

    This will cause a time-out in CCS5.

    -no_freq_check measures the actually freq that device is running. Should not matter.

    CORTEX_RXX_NODAP means the DAP (Data access port) can not be used to exchange data between the MCU and the emulator/PC. In other words, every write has to go through R4 cpu. So, it is slow. But it is the only choice for this device. For the other TMS570LS1x/2x/3x, you can use CORTEX_RXX, whichi is much faster.

    One trick to save time in CCS5 flash programming: in the debug view:

    tools->on-chip flash, select "Necessary Sector Only".

    Regards,

    Haixiao

  • What is the reason for the big time difference between the MCU Demo Software and if I run nowFlash by myself?

    - Total elapsed time 354.10 sec by MCU Demo Software

    - Total elapsed time 2893.76 sec if I run it by myself

    Please can you repeat the two tests on your bench with a hercules launchpad and check the times reported by nowFlash?

    I want to make sure that it is a problem with the board before I buy a new one.

    Thank you very much for your help.

    Best regards,

    Michael

  • Michael,

    If I understand your setup, you are running win7 under a virtual machine using VMware.
    This could explain the reason it's taking so long to erase and program a part.

    Also if i'm correct, when the part is programmed via the MCU Demo software, only the used sector in the flash are erased. When you are doing it via nowflash, by default the full flash is erased. You may have to play with the range option to limit the flash to the minimum size used by the application. (Check the map file to figure out how much flash is needed).

    Please have a try and let us know.

  • Hi Jean-Marc,

    I'm afraid, but VMware is the problem. So you are right.

    I installed CCS 5.5 on my Windows 8.1 machine, checked and installed the available updates and everything is working fine now.

    This makes me a little bit sick...but on the other hand it is great. Now I will try to find out with VMware what is going on but I am not very confident that there will be an easy solution. And at the end I have to live without VMware.

    Thanks a lot for helping.

    Best regards

    Michael