TMDSPLCKIT-V3 can't connect to GUI

Mariusz,

Ok...Let's summarize what we have now (if I will wrong, correct me):

1 For loading flash memory you apply C2Prog Code Skin or embedded flasher of CCS.

2 Kit allows to load any firmware into flash accessfully always (no matter with CCS or C2Prog).

3 Firmware "phy_example_project" it seems works because LEDs are blinking when you connect both complects ( PLC modems) to one another.

Now my question:

When you have original TI firmware (not "phy_example_project") inside flash memory and you open Zero Config application at PC, did you try open menu "Serial port connection"? If XDS100 driver works correctly, then you should see at drop-down list: the standartd COM ports of your PC & COM port connected to kit. If you see kit's COM port, then choose it at list. Check, please it, at first (of course kit should be power on at that time).

Igor

1. Yes

2. Yes

3. Yes

Answer to your question:

I tried to select manualy COM but it didn't work. I can see COM port connected to the device but when i choose it also nothing happens.

Could you please upload this file

C:\Program Files\Texas Instruments\PLC Application Suite\ PLC_Application_Suite.exe.config

it would be interesting to look at one.

Igor

Sure, here it is:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="PLC_Application_Suite.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</sectionGroup>
</configSections>
<applicationSettings>
<PLC_Application_Suite.Properties.Settings>
<setting name="DefaultDeviceType" serializeAs="String">
<value>G3</value>
</setting>
<setting name="DefaultFirmwareVersion" serializeAs="String">
<value>33554432</value>
</setting>
<setting name="DefaultG3Security" serializeAs="String">
<value>Disabled</value>
</setting>
<setting name="Disabled" serializeAs="String">
<value>3</value>
</setting>
<setting name="ConnectionAttempts" serializeAs="String">
<value>3</value>
</setting>
<setting name="EnableDiagMessages" serializeAs="String">
<value>False</value>
</setting>
<setting name="EnableScripts" serializeAs="String">
<value>False</value>
</setting>
<setting name="FileTransferPageSize" serializeAs="String">
<value>256</value>
</setting>
<setting name="CloseAllOnExit" serializeAs="String">
<value>False</value>
</setting>
<setting name="DefaultSCIPort" serializeAs="String">
<value>SCI_B</value>
</setting>
</PLC_Application_Suite.Properties.Settings>
</applicationSettings>
</configuration>

1 <setting name="DefaultDeviceType" serializeAs="String">

<value>G3</value>

it is very strange, if you used PRIME firmware only or G3 firmware also (from another SDK packages)?

2 But it is right (connection via USB-JTAG):

<setting name="DefaultSCIPort" serializeAs="String">
<value>SCI_B</value>

1. I have installed anothe packages but didn't use them. Second modem works fine with that configuration.

2. I think the probmem might be on the board because i send this frame:

0C 80 0A 00 A3 9B 00 00 01 00 01 00 00 00

which means:

0C - LOAD SYSTEM CONFIG

80,0A,00,A3,9B,00,00 - doesn't matter

01 00 - Port designation (config type)

01 00 - config length

00 - Data Port designation : SCI-A

00 - Diagnostics Port : SCI-A

According to PRIME_HOST_MESSAGE_SPECIFICATIONS.PDF.

If there is anyway to erase it I would be greatfull. I finish my work for this week. See you on monday.

Thanks again for help.

OK, nice weekend!

Igor 

Hello Mariusz!

When you wrote:

Mariusz Kowalski said:

If there is anyway to erase it I would be greatfull.

did you mean revert your choise and recover the device as brand new? In this case you can try to reflash the firmware again through C2prog and the modem will be automatically set with SCI-B as both Diag and Host port (default options).

If Zero Configuration GUI still has its original xml configuration file (the one you posted), it will look for devices connected on SCI-B and you will have the device under control again.

@Igor: I have the

<setting name="DefaultDeviceType" serializeAs="String">
<value>G3</value>

in my configuration file too, but I use Zero Configuration GUI on PRIME devices without any issue. Is it possible that this setting it's just ignored if a PRIME device is detected?

Regards,

Diego

@Diego

DB said:

in my configuration file too, but I use Zero Configuration GUI on PRIME devices without any issue. Is it possible that this setting it's just ignored if a PRIME device is detected?

Perhaps you are right. At least this setting is not presented among settings for chanching (refer to the table of the items that may be change and their description at UG of GUI).

Regards,

Igor

I flashed the device many times with no efect. 

@Mariusz

If I understand from your above post , there is problem with one modem only. The second modem works fine. Do you use the same PC to connect to the modems or two different PC? Or, did you try connect "damaged" modem to another PC?

Igor

Before the weekend I could connect to only one modem, but today I can't connect to any of them. I am going to try reinstall all the drivers and try again.

I would recommend you using  two different PC to avoid possible confusion with the connection ports of modems at GUI. 

Hi, Mariusz!

Well, I'm glad you decided your problem by yourself and acquired new useful experience!

Good luck,

Igor

Hello, Mariusz!

I'm glad you solved your problem. Your solution could be a hint for others users who experience similar malfunctions. The matter it's possibly related to the G3 predefined option which we discussed previously. Maybe, at first, Zero Configuration GUI looks for a G3 device on SCI-B (as it's written on xml config file) and than, if it's not found, it tries with PRIME. Perhaps, the reflashing procedure with the PRIME hex file doesn't overwrite all settings (I left selected Smart Sector Selection option in C2Prog), as a proof of this I noticed that the serial number of the devices it's still the same I set before flashing.

Regards,

Diego

Another hint might be that i deselected "Smart Sector Selection" in C2Prog and manually selected all flash sectors to be erased.

Hello Mariusz!

So, if I understand correctly, after you loaded the PRIME hex firmware nothing should still remain in flash memory. Hence, presumably, all settings must be reverted to default, diag port and host port settings included. According to my experience, the only explanation that remains it's in the way Zero Config GUI works. But here we are entering in the mysterious world of undocumented features of TI software.

Regards,

Diego

Mariusz Kowalski said:

Another hint might be that i deselected "Smart Sector Selection" in C2Prog and manually selected all flash sectors to be erased.

As for me, I have tried different TI firmwares but with selected option "Smart Sector Selection" always and there were not any problems with GUI.

Regards,

Igor 

I am just saying what  I had done befor everything started to work. Maybe without this option this would also work properly. 

Unfortunatelly the documentation isn't very good, but in comparison to other companies, the TI documentations are much better.

Mariusz.

Well, if the issue is exhausted at now, then hit please button "YES" at your post, where your solution is presented, and you will close this thread as answered. Perhaps your solution will be useful not only for you ;-)

Good luck,

Igor

Hello everyone,

I also had this problem. I changed the default SCI-B port to SCI-A port in the diagnostic and data port. After re-starting the zero configuration tool it detected no PLC. I flashed with the PRIME firmware both modems but the problem persisted. Strangely it actually worked when flashing with the G3 firmware. But when flashing PRIME again the problem persisted.

Finally I solved this issue simply by using a null-modem cable (null modem cable + RS232-Usb). Strangely the zero configuration tool detected the PLC modems with the SCI-B ports as default, even when I was only using the null-modem cable (SCI-A).  I change to SCI-A and saved the configuration, then changed again to SCI-B and saved once again. I disconnected the cable and then closed the zero configuration tool. After this the zero configuration tool recognized again the modem using only the SCI-B interface.

Regards,

Diego Cantor