WEBENCH® Tools/MSP-EXP430FG4618: TI Cloud Tools : CCS Cloud crashes : Ubuntu 19.10 Freezes : Reboot needed

Hello Jonathan,

Jonathan Roberts14 said:

When I attempted to copy the blink.out file from the TI Cloud Tools CCS IDE, on about three occasions now, it simply crashes and completely freezes the OS.

Just to confirm - you trying to simply download the out file you built in CCS Cloud to your local PC so that you can then use it in your desktop CCS IDE environment for debug? And it hangs on this download?

Jonathan Roberts14 said:

Further, for some unknown reason, every now and then, when I click on the CCS Cloud button, it comes back with the message:
104 - Login Failed: Maximum login attempts reached, please retry later.

Usually that just mean that the Cloud server is busy because of too many concurrent users. Most of the time if you try later, it will work. I would not expect switching browsers or a reboot to have an impact here.

Jonathan Roberts14 said:

would like to ask how I can save/export/download the binary files, generated by the TI Cloud Tools, to my laptop please.

Typically you can just right-click on the file in the left pane and select "Download File" in the context menu. But I assume this is where you see the OS crash/hang.

It could be specific to your host environment. Ubuntu 19 is not officially supported so it hasn't been tested in that environment. I'll set up my Ubuntu 19 environment later today and give it a try.

ki

Ki said:

Ubuntu 19 is not officially supported so it hasn't been tested in that environment. I'll set up my Ubuntu 19 environment later today and give it a try.

I tried downloading the file from CCS Cloud (in FireFox) to my local machine running Ubuntu 19.04. It successfully saved to my Downloads folder without any issues.

Hi Ki,

Thanks for getting back to me.

Ki said:

Just to confirm - you trying to simply download the out file you built in CCS Cloud to your local PC so that you can then use it in your desktop CCS IDE environment for debug? And it hangs on this download?

Yes, exactly right. I am unable to get any of the TI tools, which include, CCS (locally installed) CCS Cloud or MSPFlasher, to connect to my target, so I am using MSPDEBUG to connect to my target.

Ki said:

Usually that just mean that the Cloud server is busy because of too many concurrent users. Most of the time if you try later, it will work. I would not expect switching browsers or a reboot to have an impact here.

I am sure this is not the issue, because I have left it for a long time, like 10-15 minutes and tried again, but no-go. If I leave Firefox and connect to the TI Cloud Tools from Chromium, it connects immediately.

Ki said:

Typically you can just right-click on the file in the left pane and select "Download File" in the context menu. But I assume this is where you see the OS crash/hang.

I am going to try this again a report back later. (I don't want to try now, because it could crash and delete this message)

Ki said:

It could be specific to your host environment. Ubuntu 19 is not officially supported so it hasn't been tested in that environment. I'll set up my Ubuntu 19 environment later today and give it a try.

I am not sure whether it is to do with this release or not, however, I can say that I have found Ubuntu 19.10 to be reliable so far and haven't experienced any other issues.

Thanking you for your continued help and support.

Best Regards,

Jonathan Roberts

Hi Ki,

Jonathan Roberts14 said:

Typically you can just right-click on the file in the left pane and select "Download File" in the context menu. But I assume this is where you see the OS crash/hang.

I followed your recommendation and was able to download the binary file.
Previously, I had been looking on the CCS Cloud file menu for a download command, after selecting the file.
Thanks a lot for your help with this.

Since none of CCS (local install) CCS Cloud or MSP430Flasher are able to detect my MSP-FET430UIF tool, I have now tried installing Uniflash, which requires the TI Cloud Agent to run. I have tried a number of times to install the TI Cloud Agent, using ticloudagent.run and going through the installation steps, without any errors, however, subsequent to doing this, Uniflash is still unable to detect my FET tool.

This is extremely frustrating and a huge waste of time.

Any help you may be able to offer, would be most appreciated.

Best Regards,

Jonathan

Jonathan Roberts14 said:

Since none of CCS (local install) CCS Cloud or MSP430Flasher are able to detect my MSP-FET430UIF tool, I have now tried installing Uniflash, which requires the TI Cloud Agent to run. I have tried a number of times to install the TI Cloud Agent, using ticloudagent.run and going through the installation steps, without any errors, however, subsequent to doing this, Uniflash is still unable to detect my FET tool.

A lot of these tools use the same underlying drivers for the MSP-FET430UIF tool so it is not surprising that the same issue impacts multiple tools.

If you run lsusb in the terminal, is there an entry for "Texas Instruments" which represents the MSP-FET430UIF probe?

I will bring this thread to the device experts. They can provide more suggestions for the MSP-FET430UIF detection issue.

Thanks

ki

Hi Jonathan,

Do you mean that you plugin your MSP-FET430UIF tool to your PC and no device is detected?

Then my first guess would be that the FET tool is broken. As you may know that the FET430UIF tool is built up mainly by a USB-UART conversion interface IC and a MSP430F1612, with other components. Since your issue is that device can't be detected, I would suspect the USB-UART conversion interface IC is broken.

Do you get any other FET430UIF tool there to give a try firstly? Also, do you still remember when the last time your FET430UIF tool works well?

Regards,

Harry

Hi Ki,

Sorry for the delay in getting back to you. I have been busy resolving an MSP430-ELF-GCC issue, with the help from the staff at Mitto Systems.

Yes, as you can see, the FET tool is being recognized:

=====================================================================

jona@bimbo:~/ti/mspgcc/msp430-gcc-8.3.0.16-source-full/install/opt/msp430/bin$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 010: ID 0930:0227 Toshiba Corp.
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 04ca:7046 Lite-On Technology Corp. TOSHIBA Web Camera - HD
Bus 001 Device 012: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

====================================================================

and is appearing in /dev as either, ttyUSB0, ttyUSB1 or ttyUSB2.

When I run mspdebug, I check which one it is attached as, and declare it on the command line, like this:

: mspdebug -j uif -d /dev/ttyUSBx

With the TI tools, there is no option that I am aware about, to specifically define where the target is attached.

I agree with your assessment that this is probably all related to one driver, which is used by all the TI tools.

Thank you for referring this issue to the appropriate team member.

Best Regards,

Jonathan

Hi Harry,

Harry Qiu said:

Then my first guess would be that the FET tool is broken. As you may know that the FET430UIF tool is built up mainly by a USB-UART conversion interface IC and a MSP430F1612, with other components. Since your issue is that device can't be detected, I would suspect the USB-UART conversion interface IC is broken.

There is nothing wrong with my FET tool. I in fact have two of them and know for a fact that they both work correctly, because I am able to connect to both JTAG and Spi-bi-Wire targets and load firmware using them in conjunction with mspdebug which, you may be aware, is an open-source MSP430 debugger, written by Daniel Beer.

From what I have been able to observe, there are clearly issues with the TI target connection driver.

Please ask your team to look into on your end.

Thank you.

Jonathan

Hi Jonathan,

So do you mean for now after Ki's suggestion your PC could recognize the FET430UIF tool but TI tools can't detect/connect it, while mspdebug can?

Hi Harry,

That is correct. I can connect to the FET tool with MSPDEBUG, but none of the TI tools connect.

It seems to me that the issue points toward a library file called libmsp430.so, which, as I understand it, is used by all of the TI tools.

Owing to this, since I have been unable to obtain further help on this issue from TI, I am trying build the library myself, however,
I am busy trying to get to the bottom of an error:
===================================================================================================
BSL430_DLL/Physical_Interfaces/MSPBSL_PhysicalInterfaceSerialUART.cpp:216:25: error: reference to ‘chrono’ is ambiguous
  216 |  this_thread::sleep_for(chrono::milliseconds(250));
===================================================================================================
which I am getting.

As I have mentioned to the other TI support team members who I have been in communication with, I am concerned that something
has caused the on-chip flash memory on the target devices (MSP430F2013 & MSP430F4618) to become corrupted, and I am
unable to recover from this.

Although MSPDEBUG can connect to and load firmware onto these devices, something is causing execution of the code to halt,
as if a breakpoint has been set, however, none have been set.

Build the above library file is no easy task, since there are quite a few complicated prerequisites which need to be satisfied.

As far as I can ascertain, from various discussions which I have read from open-source developers, there is apparently some
resistance within TI to maintain and release certain sources to the open-source community, which requires some complicated
workarounds, so that a TI, Windows DLL, can be somehow built into the above library.

This has been, and continues to be an extremely frustrating and time-wasting exercise and I would like to ask you to please
raise this for discussion within your support team, so that (many) other users do not have to deal with kind of annoyance.

Thanking you in advance.

Best Regards,

Jonathan

Hi Jonathan,

Really sorry for all the trouble and time wasting.

I've already seek help internally to try to find out the issue. I'll get back to you as soon as I get an answer.

Apologize again for this.

Regards,

Harry

Jonathan, sorry for all the pain. I just want to clarify one thing:

jonahugh said:

That is correct. I can connect to the FET tool with MSPDEBUG, but none of the TI tools connect.

Can you describe the connection error when trying to connect with CCS? What is the exact error message given?

Thanks

ki

Hi Ki,

I have done the following tests:

Connected a MSP-FET430UIF to the MSP430F2013 JTAG connector (Spi-Bi-Wire) : BATT Jumper open :  VCC1 & VCC2 -> FET PWR

From a terminal:

jona@bimbo:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0930:0227 Toshiba Corp.
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 002: ID 04ca:7046 Lite-On Technology Corp. TOSHIBA Web Camera - HD
Bus 001 Device 008: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

==============================

jona@bimbo:~$ ls /dev | grep USB
ttyUSB1

==============================

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
MSP430F2013
++++++++++++

CCS -> New Project -> Target : MSP430x2xx Family : MSP430F2013

Connection :  TI MSP430 USB1 (Default) -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

Connection :  TI MSP430 USB2 -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

Connection :  TI MSP430 USB3 -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

+++++++++++++++++++++++++++++++++++++++++++++++++++

With the FET tool connected to the same MSP430F2013 JTAG (Spi-Bi-Wire) port:

jona@bimbo:~$ sudo mspdebug uif -d /dev/ttyUSB1
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.13.0.601 Copyright (C) 2013 TI, Inc.

Trying to open /dev/ttyUSB1 at 460800 bps...
Initializing FET...
FET protocol version is 20408002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0xf201
  Code start address: 0xf800
  Code size         : 2048 byte = 2 kb
  RAM  start address: 0x200
  RAM  end   address: 0x27f
  RAM  size         : 128 byte = 0 kb
Device: MSP430F20x3
Number of breakpoints: 2
fet: FET returned NAK
warning: device does not support power profiling
Chip ID data:
  ver_id:         01f2
  ver_sub_id:     0000
  revision:       30
  fab:            40
  self:           0000
  config:         03
  fuses:          00
Device: MSP430F20x3

Available commands:
    !               fill            power           setwatch_r      
    =               gdb             prog            setwatch_w      
    alias           help            read            simio           
    blow_jtag_fuse  hexout          regs            step            
    break           isearch         reset           sym             
    cgraph          load            run             verify          
    delbreak        load_raw        save_raw        verify_raw      
    dis             md              set             
    erase           mw              setbreak        
    exit            opt             setwatch        

Available options:
    color                       gdb_loop                    
    enable_bsl_access           gdbc_xfer_size              
    enable_fuse_blow            iradix                      
    enable_locked_flash_access  lowercase_dis               
    fet_block_size              quiet                       
    gdb_default_port            

Type "help <topic>" for more information.
Use the "opt" command ("help opt") to set options.
Press Ctrl+D to quit.

(mspdebug)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
MSP430F4618
++++++++++++

jona@bimbo:~$ ls /dev |grep USB
ttyUSB0
(note that the USB dev number changed from ttyUSB1 to ttyUSB0 when I disconnected and reconnected the USB cable, which is normal behaviour)

++++++++++++++++++++++++++++++

Connected a MSP-FET430UIF to the MSP430F4618 JTAG connector : BATT Jumper open :  VCC1 & VCC2 -> FET PWR

CCS -> New Project -> Target : MSP430x4xx Family : MSP430F4618

Connection :  TI MSP430 USB1 (Default) -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

Connection :  TI MSP430 USB2 -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

Connection :  TI MSP430 USB3 -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found
===========================================================================

+++++++++++++++++++++++++++++++++++++++++++++++++++

With the FET tool connected to the same MSP430F4618 JTAG port:

jona@bimbo:~$ sudo mspdebug -j uif -d /dev/ttyUSB0
[sudo] password for jona:
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.13.0.601 Copyright (C) 2013 TI, Inc.

Trying to open /dev/ttyUSB0 at 460800 bps...
Initializing FET...
FET protocol version is 20408002
Set Vcc: 3000 mV
Configured for JTAG (2)
Device ID: 0xf46f
fet: unknown device
msg28_data: [0x1a bytes]
    f4 6f 32 40 00 00 00 00 00 00 02 12 01 47 d6 7a
    81 00 89 00 00 00 00 00 00 00
Using Olimex identification procedure
Device ID: 0xf46f
  Code start address: 0x3100
  Code size         : 118528 byte = 115 kb
  RAM  start address: 0x200
  RAM  end   address: 0x9ff
  RAM  size         : 2048 byte = 2 kb
Device: MSP430FG4618
Number of breakpoints: 8
fet: FET returned NAK
warning: device does not support power profiling
Chip ID data:
  ver_id:         6ff4
  ver_sub_id:     0000
  revision:       32
  fab:            40
  self:           0000
  config:         47
  fuses:          00
Device: MSP430FG4619

Available commands:
    !               fill            power           setwatch_r      
    =               gdb             prog            setwatch_w      
    alias           help            read            simio           
    blow_jtag_fuse  hexout          regs            step            
    break           isearch         reset           sym             
    cgraph          load            run             verify          
    delbreak        load_raw        save_raw        verify_raw      
    dis             md              set             
    erase           mw              setbreak        
    exit            opt             setwatch        

Available options:
    color                       gdb_loop                    
    enable_bsl_access           gdbc_xfer_size              
    enable_fuse_blow            iradix                      
    enable_locked_flash_access  lowercase_dis               
    fet_block_size              quiet                       
    gdb_default_port            

Type "help <topic>" for more information.
Use the "opt" command ("help opt") to set options.
Press Ctrl+D to quit.

(mspdebug)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

As you can see from these results, in both instances, I was unable to connect using CCS, however, was able to connect using MSPDEBUG.

I am still struggling to build libmsp430.so from source code, since I believe that this is the most-likely cause of the connection issues which I have been experiencing with CCS, CCS Cloud and MSP Flasher. (I included the error message during build, in my previous response.)

I appreciate your ongoing cooperation in helping me to resolve these issues.

Thanks and Regards,

Jonathan

jonahugh said:

Connection :  TI MSP430 USB1 (Default) -> Identify : Error initializing emulator: No USB FET was found -> Cancel :
Starting Debug Server ...
MSP430: Error initializing emulator: No USB FET was found

Thanks. The CCS debugger is unable to detect the MSP-FET430UIF. 

I'll need to MSP430 tools team to investigate the issue further

Hi Jonathan,

From my side, it'll still take us some time to figure out what happened here. I'm not sure if you get any update for this. If have, please also post here for our reference. Thanks and apologize again for all the trouble.

Regards,

Harry

Hi Jonathan,

Really sorry this takes so long and still our guys are looking into this.

Do you get any update from your side as well?

Regards,

Harry

Hi Harry,

I received a response from Josef Larynowycz and am going to try his suggestion when I have time.

Thanks and Regards,

Jonathan

Hi Jonathan,

Firstly I do apologize that I still get any answer internally.

Then I may guess if you get it resolved since didn't hear your response for a while.

May I mark this as a resolved and close this thread? You still can post your any related question here, or other questions in the forum.

Apologize again and thanks a lot for choosing MSP430.

Regards,

Harry

Hi Harry,

I received some good support from Josef Larynowicz of Mitto Systems, however, am still waiting to hear back from my latest response, after following his recommendation to install the TI XDS GDB agent, which I did, however still am unable to connect to the target.

Best Regards,

Jonathan

Hi Jonathan,

According to the internal experts' analysis, seems that you don't have a sudo permission thus unsuccessfully installed the udev rules.

I attached a zip file including the rules and a .sh script. Please make sure to run the script with sudo.

Let me know if it works for you.

install_scripts.zip

Hi Harry,

Thank you for following up. I ran the script as follows, but noticed that it does not seem to add the rules file into /etc/udev/rules.d

===============================================

jona@bimbo:~/ti/mspgcc/ti/install_scripts/install_scripts$ sudo -s
root@bimbo:/home/jona/ti/mspgcc/ti/install_scripts/install_scripts# ls -l
total 8
-rw-r--r-- 1 jona jona 2145 Jul 18  2017 70-mm-no-ti-emulators.rules
-rw-r--r-- 1 jona jona 1999 Jul 18  2017 msp430uif_install.sh
root@bimbo:/home/jona/ti/mspgcc/ti/install_scripts/install_scripts# chmod +x msp430uif_install.sh
root@bimbo:/home/jona/ti/mspgcc/ti/install_scripts/install_scripts# ls -l
total 8
-rw-r--r-- 1 jona jona 2145 Jul 18  2017 70-mm-no-ti-emulators.rules
-rwxr-xr-x 1 jona jona 1999 Jul 18  2017 msp430uif_install.sh
root@bimbo:/home/jona/ti/mspgcc/ti/install_scripts/install_scripts# ./msp430uif_install.sh

root@bimbo:/home/jona/ti/mspgcc/ti/install_scripts/install_scripts# ls /etc/udev/rules.d -l
total 116
-rw-r--r-- 1 root root   386 Oct 24 21:10 61-msp430uif.rules
-rwxr-xr-x 1 root root   711 Oct 24 14:16 70-mm-no-ti-emulators.rules
-rw-r--r-- 1 root root  6142 Dec  5 10:32 70-snap.chromium.rules
-rw-r--r-- 1 root root 63742 Sep 22 21:55 70-snap.core.rules
-rw-r--r-- 1 root root  1891 Oct 10 09:10 70-snap.git-cola.rules
-rw-r--r-- 1 root root   525 Dec  9 09:30 70-snap.kig.rules
-rw-r--r-- 1 root root 14132 Oct 10 09:10 70-snap.scrcpy.rules
-rw-r--r-- 1 root root  2565 Nov 29 19:39 71-ti-permissions.rules
-rw-r--r-- 1 root root    79 Oct 12 15:03 99-msp430.rules
-rw-r--r-- 1 root root   161 Oct 24 14:05 99-slusb.rules

===============================================

As you can see from the above, there was already a 70-mm-no-ti-emulators.rules file in the /etc/udev/rules.d directory, however, the script did not copy the 70-mm-no-ti-emulators.rules file which you sent me, into this directory, which you can see  from the timestamps.

As you can also see, there are other msp430 related .rules files in the /etc/udev directory, from previously running the install scripts for CCS and also MSPFLASHER.

Further, I did a file comparison between the above-listed file, 70-mm-no-ti-emulators.rules and the file with the same name, which was included in the ZIP file which you sent me, and noticed that there are quite a few differences.

It does seem to be a possibility that there may be some issue/s with the udev rules in these file/s, however, I am not sure how confirm this.
As mentioned previously, when my MSP-FET430UIF tool is connected, it appears in my /dev directory as ttyUSBx, whereas, all of the above rules files mention ttyACM*
This seems somewhat suspicious to me, however, I don't know how to confirm/correct this.

I have attached a ZIP file containing all of the rules files in my /etc/udev/rules.d directory, for your reference.

Thank you for your continued help.

Jonathan

rules.d.zip

Hi Harry,

I tried to reply to your message, however, I have been having Internet connectivity issues, and my response did not appear.

I attempted your suggestion, however, this was not successful, however, I believe that the person who suggested this, may have been on the right track.

I am taking this up further with Josef Larynowicz of Mitto Systems, on a separate thread. He has also been trying to help me with this issue.

What I noticed, when I looked at all of the udev rules files in /etc/udev/rules.d is that they all refer to ttyACM* whereas, the MSP430FETUIF tool appears as /dev/ttyUSBx

I will let you know if we manage to make any further progess.

Best Regards,

Jonathan

jonahugh said:

Yes, as you can see, the FET tool is being recognized:

=====================================================================

jona@bimbo:~/ti/mspgcc/msp430-gcc-8.3.0.16-source-full/install/opt/msp430/bin$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 010: ID 0930:0227 Toshiba Corp.
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 04ca:7046 Lite-On Technology Corp. TOSHIBA Web Camera - HD
Bus 001 Device 012: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

See CCS6 on linux : No USB FET was found

Hi Chester,

Thank you very much for picking up on this.

Although I am willing to try your suggestion if there is no other option, I do recall other people reporting issues with version 3 firmware, which makes me a little hesitant.

Since you mention this, I am going to try altering the udev rules, to reflect the idVendor and idProduct which the FET tool is configured to.
If that doesn't work, I will take up on your suggestion.

It has been a long road to this point and I am most grateful that you spotted this.
(Once I get the FET tool sorted, I will have to get my experimenter boards working again, since the on-chip flash on all four devices seems to be corrupted.)

Much obliged,

Jonathan

Hi Chester,

Please could you send me some details about the udev rules needed for CCS, MSP430-Flasher and also TI XDS GDB agent, to suit the MSP-FET430UIF with version 2 firmware.

I would also like to ask for confirmation as to which udev rules file relates to which application.
As I understand it, 61-msp430uif.rules is for MSP430-FLASHER and 70-mm-no-ti-emulators.rules is for TI XDS GDB agent and 71-ti-permissions.rules is used for CCS, however, I am not sure what 99-msp430.rules is used for?

I have tried various combinations of rules, restarting the udev daemon each time, but no luck so far.

Specifically I have been trying commenting/uncommenting the following:

ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", MODE="0666"
#ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", GROUP="plugdev", MODE="0666"
#SUBSYSTEMS=="usb", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", GROUP="plugdev", MODE:="0666"
#KERNEL=="ttyUSB*", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f430", GROUP="plugdev", MODE:="0666"

and using the following to restart udev:

sudo udevadm control --reload-rules
sudo udevadm trigger

also tried:

sudo service udev restart

At this point, I am focussing on trying to get the TI XDS GDB agent and MSP430-FLASHER working, because it is much quicker than trying to start CCS every time I make a change.

Any help you may be able to offer, would be appreciated please.

Thanks and Regards,

Jonathan

jonahugh said:

Please could you send me some details about the udev rules needed for CCS, MSP430-Flasher and also TI XDS GDB agent, to suit the MSP-FET430UIF with version 2 firmware.

However, I don't think just changing the udev rules will help since:

a. A MSP-FET430UIF with version 2 firmware enumerates as a /dev/ttyUSBx device under Linux.

b. A MSP-FET430UIF with version 3 firmware enumerates as a /dev/ttyACMx device under Linux.

c. The TI msp430 debug stack supplied with CCS under Windows can communicate with either a MSP-FET430UIF with either firmware version 2 or 3, including allowing a switch between the two firmware versions. Where a downgrade from a version 3 to 2 firmware was to allow use of a MSP-FET430UIF with older tools.

d. With the TI msp430 debug stack supplied with CCS under Linux I have only seen communication with a MSP-FET430UIF with firmware version 3.  

My suspicion is that when CCS support was added for Linux, it only supported a MSP-FET430UIF with the later firmware version 3. Hopefully a TI employee can confirm this. 

Hi Chester,

Thank you for shedding further light on this issue.

I have started trying to tweak the msp430-flasher source code, but so far no luck.

It really beats me as to why TI would just decide to drop support for debug hardware, of which, I imagine there are many out in the field.
When the firmware was upgraded, they must have been aware that changes, such as ttyUSB to ttyACM, would prevent the previous version tools from working.

I tried requesting further help from Mitto Systems, but so far have not heard back.

Thank you for your continued help.

Best Regards,

Jonathan