This is an informational post:

I got the following error while trying to debug under Ubuntu:

"SiAgent launched but did not report its status. Please check your installation."

When trying to do a "Bare run" got SiAgentARM error 127

This was because "siagentarm" depends on libQtNetwork.so.4 which is not installed by default, since 18.04 installs libqtnetwork5.

Just run:

sudo apt install libqt4-network

That simple: debugger is running normally, but when the code gets a call to I2C_TransferInit() it disconnects, power cycle actually.

I can't find anything in the docs referring to SWD and I2C overlapping internally. I'm routing I2C to location 4.

I am working with an STK3400 as debugging interface connected to a custom board. Everything was working, so I know it can be done and my setup is supposed to work. PC runs Linux.

Two days ago I intended to keep working and things didn't work, found some tips in the forum, and it seemed to work yesterday. I even able to work this morning and suddenly again: fails.

Now, this is what I mean by it doesn't work.

1) STK3400 is detected when Simplicity is started. Sometimes connection is lost, and need to restart Simplicity.

2) Target device is detected, but it is never programmed... but I get no error!!! Program is not updated, and debugging is not available.

3) If I use the flash programmer and hit "erase", the progress bar goes all the way, but nothing is erased.

4) If I try to flash the device with the flash programmer I get no error, but no updated program either.

Is there any way to figure out what is going wrong? For example a log o TCF agent output window.

I can confirm this problem too, along with the solution.

I also can add that I did not had this problem while trying to debug a small (blinker) test program (probably everything happens in less than 5s device detection interval).

What I found out now is that in my case (Linux version) Simplicity Studio does not update the building after the configuration has been changed. For example, if I change optimze to -Os, in the building process I still get -O0.

I have a working Debug configuration. The Release configuration does not build because it fails to include a header file located in the same folder the source code is.

The path to the corresponding directory is included in both cases and actually in both cases I can see the corresponding gcc parameter (-I"/path/to/src") including it in "All options" ... BUT in the Release configuration the parameter is not included in the subdir.mk file. Furthermore, if I edit subdir.mk to include this parameter, it builds.

What may be wrong here?

There are many logs, did you check them all? You can get Simplicity to generate a compressed file containing all the logs.

Also, if you search for libswt-pi-gtk.so you'll find a lot of errors related to Eclipse on Debian or Ubuntu, but usually somewhat old releases.

Update: I downloaded Simplicity Studio again (md5sum was different from the previous file) to solve a problem with the IDE, and this time the link was included!

Well... here it is some plugins are trying to link to libjlinkarm.so.5 which does not exist (libjlinkarm.so.4 is there though). I have libjlinkarm.so.5 for 64bit which won't link, so just created a symbolic link from libjlinkarm.so.4 to libjlinkarm.so.5 and it worked. Not elegant, but allows me to me work.

Logs of the error are attached. The error can be seen in siagent_log_3707.txt

Thanks guys!!!

udev rules are as correct... actually, JLinkExe found the device.

I found an error log, but there are only complains about optimization level settings.