CCS 5.3.0, very slow flashing when going into debug mode

Hi Davor,

One suggestion: if you are not using all the flash sectors, you may want to check the "Erase Sector Selection" options in the "Flash Settings" and uncheck the sectors not being used. Otherwise the debugger will erase all the sectors every time before flashing and this can add quite a bit of time.

Hope this helps

ki

Erase-time is not the issue.

When I say section, I am refering to  .text .cinit .const etc.

So:

Erasing the flash sectors takes as long time as before.

When the debugger starts Flashing, the pauses are introduced between each section. During these pauses there is no apparent activity.

This is not how CCS 5.2 and earlier version behaved.

Hi Davor,

Could you provide the out file that you see the issue with? I would like to try to reproduce this locally. If you do not wish to post it publicly on the forum, please start a private conversation with me.

Thanks

ki

out file sent in PM.

Hoping for a quick fix for this. :D

Ricky,

The new dll worked very well. Thank you for the quick response!

Some details about my machine in case it helps you:

Windows 7 Enterprise, SP1, 64 bit

Intel Core i7-2760QM

16GB RAM

Hello Ricky,

I have a similar problem. I just got a new machine this week and when debugging an existing code that worked #1 on my old computer wit ccs 5.1, it seems to take an eternity a section where my codes reads external nand flash... I copied the dll as mention above but it does not solve the problem.  We have 2 version of the program, one that works on a C6748 dsp and the other is about the same code but it runs on a c6745.  The c6748 is about 10-20 time slower and the c6745 is absolutely riduculously slow...

I have windows 7(french) pro SP1 with an I7 processor, ccs 5.3.0.00090 

8GB of ram

Simon,

The original issue is related to the integrated Flash Manager in CCS, which only supports internal Flash on MCUs (for now). The issue you are experiencing sounds different in that it is dealing with external Flash on DSPs, and therefore I don't have the expertise to help debug it.

The best approach is to start a new topic in the forums, so that it will get the right visibility by the necessary people.

Thanks,
Ricky

Have the same issue. It takes an enternity until...

1. CCS 5.3 launches the application that flashes the device (msp430)

2 CCS 5.3 enters the debugger.

From the CPU load it looks, as if my machine was just idle.

What is an interesting new information to you is that these two long delays (about 40 sec each) vanish, if I disable my network connection!

Best regards

Paul

Paul,

Can you try downloading CCS5.4? We have made some changes to a component in CCS5.4 that fixes a case with users experience delays launching CCS and launching the debugger. If you are experience the same problem, updating to 5.4 might fix the problem you are seeing.

Please let me know.

Thanks,

Ricky

Ricky,

thank you for your quick reply.

Unfortunately CCS 5.4 didn't solve my problem.

It takes a very long time before...

1. the flash programing routines, and

2. the debugger

... are invoked.

During this time, you get the following reading in the status bar "Launching ProjectName: (100%)", and the small progress bar in the status line will spin.

As said before, it doesn't look as if the system was doing much during this time. And by deactivating my network this issue just doesn't come up.

Even deactivating the network during CCS 5.4 is running will "solve" the problem. Reactivating the network (CCS 5.4 still running), will bring the delays back. It is the same if I suht down CCS 5.4 or the whole PC. It's just as simple as the problem arises, when the network is running.

It looks to me as if CCS tries to do something on the network and only proceeds, after it gets a timeout. This happens quickly, if there is no network, and takes much longer, in case a net is actually available.

As this problem only arises on my PC at home, I can live with it. On my PC at work I have no issues.

Regards,

Paul

Paul,

If you have some time, can you help me perform some testing to determine the cause of the problem?

First, I have attached a java.zip file to this post. Please extract and place it at the following location within your CCS5.4 install directory:

<installDir>/ccsv5/ccs_base/DebugServer/packages/ti/dss/

You should backup the original java folder in case you want to return it to original. This new version adds extra logging to help determine if a specific component is taking a long time to complete.

After that, just start CCS and run your test cases. The log file, lmlog.txt should be created in <installDir>/ccsv5/eclipse/

If you are able to create this log, please send it to me and I can analyze the information.

Thanks,

Ricky

Ricky,

first of all many thanks to you and the TI team for the excellent support you offer to your user.

Secondly, sorry for answering so late. But as written before, I encounter this problem at home only. And as you may imagine, I very seldemly have the FET-Deubug-Interface and our host at home. So testing is very rare.

I did as you asked me. Please note that the log file <lmlog.txt> was located in C:\documents and settings\<username\ on my XP system.

Atteched two log files:

1. <lmlog (network enabled).txt>   which shows the problem.

2. <lmlog (network disabled).txt>   which is ok.

In the first log file I marked the time during which the system was displaying "Launching PrejectName: (100%)". It is steps 3A to 3G which take exactly 60 seconds to complete! The same steps take about 0 seconds, in case the network is disabled.

I also made tests with firewall disabled. There was no change to the configuration with firewall enabled.

Hope this helps other users as well. As written before, I very seldemly work at home and when I do, it is acceptable to me to disable the network.

thanks again,

Paul

Paul,

Thank you very much for generating the logs. They definitely show some interesting information. Unfortunately I don't have a clear solution on how to resolve the issue at this point. I am glad to hear that it is not affecting you too much before you do not work at home too often.

I will update you on the progress of this issue once we have more information to share.

Thanks,

Ricky

Paul, thanks again for your help with understanding what is going on here.

Would you be able to try the following in your home environment when you get a chance? This is just from a Windows command prompt (no CCS or FET required).

Start "nslookup", and then type flames-usa8.sc.ti.com and a couple of other test names at the ">" prompt. You should see something like this (your input is underlined):

C:\>nslookup
Default Server: nameserver.domain.com
Address: 10.0.0.1

> flames-usa8.sc.ti.com
Server: nameserver.domain.com
Address: 10.0.0.1

*** nameserver.domain.com can't find flames-usa8.sc.ti.com: Non-existent domain

> test.ti.com

Server: nameserver.domain.com
Address: 10.0.0.1

*** nameserver.domain.com can't find test.ti.com: Non-existent domain
> ti.com
Server: nameserver.domain.com
Address: 10.0.0.1

Non-authoritative answer:
Name: ti.com
Address: 10.4.1.14

> exit

C:\>

Hi Paul,

I was not expecting the first two ti.com host names to be found, or at least to get the same IP address as the 3rd one. The addresses being returned for the first two are Deutsche Telekom servers, although I don't know what their function is. The end result is CCS thinks it is on the internal TI network and is trying to collect some test data for internal users. This of course fails and it takes awhile for the timeouts to occur.  

I don't know why the DT IP addresses would be returned for host names that are not resolvable by you. If you know of anything in your router configuration that would explain this, please let us know.

Hello Andy,

Changed the TCP/IP settings of my OS. It no longer asking the router for the DNS, it will now contact the DNS directly. Please checked the attached file which shows the setting.

After repeating the nslookup as you asked me to, the results seems to be as you expected:

> nslookup
Server:  dns.isp.t-ipnet.de
Address:  194.25.2.129

*** nslookup wurde von dns.isp.t-ipnet.de nicht gefunden: Non-existent domain
>
> flames-usa8.sc.ti.com
Server:  dns.isp.t-ipnet.de
Address:  194.25.2.129

*** flames-usa8.sc.ti.com wurde von dns.isp.t-ipnet.de nicht gefunden: Non-exist
ent domain
>
> test.ti.com
Server:  dns.isp.t-ipnet.de
Address:  194.25.2.129

*** test.ti.com wurde von dns.isp.t-ipnet.de nicht gefunden: Non-existent domain

>
> ti.com
Server:  dns.isp.t-ipnet.de
Address:  194.25.2.129

Nicht autorisierte Antwort:
Name:    ti.com
Address:  198.47.29.34

Unfortunately, I can not test, if this solves the problems I encountered. But according to what you say it probably will.

I will ask the manufacturer of my router, if they can tell me, why they return my provider's IP in case they can not resolve the domain name.

Thank you,

Paul

Thank you Paul! I hope your new settings do not cause you any other issues, but that should resolve the launch delay with CCS. If you find out anything, please pass it along.

Hello there,

CCS  5.4.0.00091 shows the same behaviour on every machine I own. To solve the issue I had to use a different DNS. I used googles DNS servers with the IP 8.8.8.8 and 8.8.4.4 

That solved the problem for me.

Jan,

What router do you use? I own a Fritz!Box 7330SL.

Didn't contact AVM jet ;-)

Regards,

Paul

Hello Paul,

I use a Speedport W921V from "Deutsche Telekom". It seems that it is common practice to redirect unknown DNS queries to "some place" or 127.0.0.1.

Bad practice!

Jan