• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 55 subscribers
  • Views 5604 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/IWR1642BOOST: Cannot start TI Cloud Agent in ubuntu / Chrome

Richard Gears
Prodigy 70 points

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, IWR1642, AWR1443

Tool/software: Code Composer Studio

I'm trying to get the IWR1642BOOST demo board working with the mmWave Demo Viewer web gallery application. I have followed the following procedure:

1. completed both steps (Browser extension and Download of Cloud Agent Application.

2. created link to libudev.so.0.

3. Click on ticloudagent.run and installed into ~/TICloudAgent

4. Restarted (power down/up) the machine.

5. Open Chome, checked Extension is loaded and enabled.

6. Go to TI Gallery and click on mmWave Demo Viewer.

7. Demo Viewer presents a pop-up window "Cannot start TI Cloud Agent"

I've followed the help page with no luck.

Any help would be appreciated! 

Install.log

Fullscreen 0181.ticloudagent_install.log Download 
Log started 10/03/2017 at 21:44:21
Preferred installation mode : gtk
Trying to init installer in mode gtk
Mode gtk successfully initialized
[21:44:21] Installer name: ticloudagent.run
Executing chmod -R ugo+rwx "/tmp/ticloudagent"
Script exit code: 0

Script output:
 

Script stderr:
 

Executing /tmp/ticloudagent/util/testprog 
Script exit code: 0

Script output:
 Checking availability of libraries in ext-depends.txt ...
Done.

Script stderr:
 

[21:44:23] installer_command_line_arguments: 
[21:44:23] installer_command_line_arguments: 
Preparing to Install
[21:44:29] BuildID: 0.5 1555
Preparing to Install
Unpacking files
Executing pkexec /home/richard/TICloudAgent/install.sh --install
Script exit code: 0

Script output:
 Install /usr/share/applications/ticloudagent.desktop
Uninstalling /etc/udev/rules.d/71-ti-permissions.rules
TI XDS100 installation completed successfully.  Some versions of Linux
require a reboot in order for the driver to function properly.  For other
versions restarting udev is sufficient.  Restarting udev now ... 

Script stderr:
 Error in file "/usr/share/applications/evince.desktop": "" is an invalid MIME type ("" does not contain a subtype)
Error in file "/usr/share/applications/evince-previewer.desktop": "" is an invalid MIME type ("" does not contain a subtype)

Executing udevadm trigger
Script exit code: 0

Script output:
 

Script stderr:
 

[21:44:36] no /home/richard/.ti/TICloudAgent
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 10/03/2017 at 21:44:38

Chrome version and extension:

Version 61.0.3163.79 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)

  • 0
    TI__Guru**** 171809 points

    Hi,

    Despite I don't have such board, the TI Cloud Agent installed successfully in my setup here (Ubuntu 16.04/64). I am using the same Ubuntu version as you but, in my case, Chrome reports itself as being 61.0.3163.100-1. It properly acknowledged both serial ports of my standalone XDS110 debug probe and the log I have here is identical to yours (minus directory names, obviously).

    One thing that is very common in later Ubuntu releases is the need for the regular user to be part of the dialout group to have access to serial ports. If you haven't done so, references on how to do this are all around the web:

    https://websistent.com/fix-serial-port-permission-denied-errors-linux/ 

  • 0 in reply to desouza
    Prodigy 70 points
    Thanks for the reply - and good point. I've tried a couple more tests;

    1. I've read the above link and tried to find the /dev/ttyUSB* to check the groups but no mount points exist. Given that Ubuntu doesn't automount, does this indicate that TICloudAgent mounts the USB serial ports on initialisation, or have I missed something in the prerequisites?

    2. lsusb gives-> Bus 001 Device 005: ID 0451:bef3 Texas Instruments, Inc.
    So, the board is detected by Ubuntu, and there's no cable/hardware/port issues.

    3. I've inserted the two lines into ~/TICloudAgent/ticloudagent.sh (first couple of lines now read)
    #!/bin/bash
    export TI_DS_ENABLE_LOGGING=1
    export TI_DS_LOGGING_OUTPUT=/tmp/my.log
    pushd `dirname $0` > /dev/null
    ....etc...

    I've checked that /tmp is writable, restarted the machine and attempted to run mmWaveDemo. It still fails and there is NO /tmp/my.log file generated.

    From this I'm assuming that the extension is not calling ticloudagent.sh, and thus not starting.

    Again, any help much appreciated.
  • 0 in reply to Richard Gears
    Prodigy 70 points
    Further test: I have run UniFlash, manually set the device to IWR1642 to see if it communicated. I have not erased/reprogrammed the board. as I was looking for a communications check function. I then exited UniFlash.

    However, I now have /dev/ttyACM0 and /dev/ttyACM1. I've followed your above instructions and changed the groups so I am part of dialout.

    Still no joy with TICloudAgent ...
  • 0 in reply to Richard Gears
    TI__Guru**** 171809 points

    Hi,

    Richard Gears said:
    1. I've read the above link and tried to find the /dev/ttyUSB* to check the groups but no mount points exist. Given that Ubuntu doesn't automount, does this indicate that TICloudAgent mounts the USB serial ports on initialisation, or have I missed something in the prerequisites?

    Sorry, I forgot to mention the newer Ubuntu releases created /dev/ttyACM* instead. At any rate, if your user is part of the dialout group and you are seeing these two serial ports, I can't think of anything that would prevent you from accessing them. One other idea to get additional information: you can try to access the ports using a simple terminal program (miniterm, putty) and see if it allows you to connect to them. In case negative, double-check the dialout group membership. In case positive, I would remove the cloud agent browser extension, restart the browser and retry - it will prompt you to install the extension again and perhaps it may be successful. 

    I will try to think about other details and get back to this thread in case I find something else - in the meantime I will see if someone can lend me such board. 

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 171809 points

    Hi,

    I asked a colleague to test this demo on his AWR1443 board and he did not get the Cloud Agent errors either. 

    One additional idea is to try and connect to the board via a standalone software such as CCS, or perhaps using a different cloud tool such as Uniflash - this may help evidence something else that may be happening in your system. 

    Despite this, he couldn't get the demo itself to work but we here at the CCS forum do not know it in detail - the knowledgeable folks to talk about it are in the device forum.

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 70 points

    Ok - thanks for that. I'll experiment with UniFlash and if I still cannot get this working get back to our TI sales rep. I'll keep this open for the next week so I can append any solution I find.

    Many thanks for all the help!

  • 0 in reply to Richard Gears
    TI__Expert 4150 points

    Richard,

    Check a log named "my_ticld.log" in tmp folder.

    The logger does a renaming of the log file due to historic reasons.

    I suggest you to find this file, clear it and reproduce the issue again, then send us this file.

    If this file is still not created, there might be some issues with Cloudagent installation. Try the same process again on firefox and let us know your findings.

    BR,

    Victor

  • 0 in reply to Victor Yang
    Prodigy 70 points

    Finally successful, but none the wiser...

    I have two development machines, Windows 10 with Chrome and IE and Ubuntu (16.04, 64 bit) with Chrome(61.0.3163.100, 64 bit) and Firefox(56.0, 64-bit).

    Both Windows/Chrome and Ubuntu/Chrome fail to start the TICloudAgent. There's no log file generated in both cases. 

    Both Windows/IE and Ubuntu/Firefox work. The application loads, configures and runs as expected.

    So I guess this is an issue with Chrome, or some setting within Chrome which I have incorrectly configured.

    I'm now up and running, so I'll resolve this issue.

    Many thanks for all the help.

  • 0 in reply to Richard Gears
    TI__Expert 4150 points

    Richard,

    Please help me look at one more thing to get more insight why it doesn't work for you on Chrome. 

    Please send us the content of these file, on both your windows and linux machines:

    C:\Users\<user_id>\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json

    ~/.mozilla/native-messaging-hosts/com.ti.ticloudagent.json

    Thanks,

    Victor