Serial Terminal in nRF Connect for Desktop Linux version not working poolside

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Fri, 14 Jun 2024 00:36:04 GMT

The Windows version is working great now.

The Linux version on my unsupported Ubuntu 24.04 LTS is a mess due to other issues. It crashes if I change the window size, or suspend--and I don't know if it is due to my too new Ubuntu. Oh, well, I hope that can be looked at or added to your Ubuntu 24.04 to do list.

Burt

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Einar Thorsrud — Wed, 12 Jun 2024 08:48:49 GMT

Hi,

The issue should be resolved now. You need to open the app with internet connection one last time, and then nrfutil core will be updated to not require internet connection after that.

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Mon, 10 Jun 2024 15:06:49 GMT

Thanks for the gtkterm tip, Einar. It is pretty; I wish it had that linemode that Serial Terminal has. Also, I got hung up on trying to figure out their macro capability--it seems like they never completed the implementation but left it in under configuration to cause confusion!

Burt

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Einar Thorsrud — Mon, 10 Jun 2024 13:37:54 GMT

Hi,

I did not reproduce a crach, but I see that re-connection does not work without network connectivity.

There is a generic issue in how this is handled in nRF Connect for Desktop and the team is on it. But for this specific use case I would recomend using another terminal until the issue is resolved (my personal faviourit serial port emulator for Linux is GTKTerm which I highly recommend).

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Mon, 10 Jun 2024 13:21:46 GMT

Thank you, Einar. Also, please see if you can replicate my finding under Linux that even if you have Internet access when starting the program, but then shut off the Internet link, and then you remove the USB cable used for UART, you can crash the nrfconnect appimage program. This is significant: on Windows I can start Serial Terminal with Internet at my house and then continue to use it when I go somewhere without Internet access, but that method is not reliable with Linux.

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Einar Thorsrud — Mon, 10 Jun 2024 12:19:01 GMT

Hi Burt,

I have reproduced the same on my end. The Serial Terminal requiers internet access when it starts. I have contacted the team working on this to have it addressed, but for now, that is unfortunately how it is.

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Sat, 08 Jun 2024 20:40:29 GMT

Argh, I cannot trust the Linux version--you never know when it will get a Seg fault if Wi-Fi is off and you use suspend.

Note that I am using Ubuntu 24.04 but I don't know if that is the issue; it might be orthogonal to the real problem.

Burt

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Sat, 08 Jun 2024 20:28:20 GMT

Here is an example of something bad in Linux when I disconnected the dongle (the program crashed):

Error occurred in handler for 'serialport:is-open': Error: PORT_NOT_FOUND
    at zxe (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:5753)
    at /tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:445:6842
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:82809)
    at WebContents.emit (node:events:518:28)
Error occurred in handler for 'serialport:is-open': Error: PORT_NOT_FOUND
    at zxe (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:5753)
    at /tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:445:6842
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:82809)
    at WebContents.emit (node:events:518:28)
Error occurred in handler for 'serialport:open': Error: FAILED
    at Hxe (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:4645)
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:82793)
(node:7283) UnhandledPromiseRejectionWarning: Error: PORT_NOT_FOUND
    at c8 (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:6269)
    at WebContents.<anonymous> (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:8038)
    at WebContents.emit (node:events:530:35)
(Use `nrfconnect --trace-warnings ...` to show where the warning was created)
(node:7283) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see nodejs.org/.../cli.html. (rejection id: 1)
(node:7283) UnhandledPromiseRejectionWarning: Error: PORT_NOT_FOUND
    at c8 (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:6269)
    at WebContents.<anonymous> (/tmp/.mount_nrfconMPmc5U/resources/app.asar/dist/main.js:640:8038)
    at WebContents.emit (node:events:530:35)
(node:7283) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see nodejs.org/.../cli.html. (rejection id: 2)
Segmentation fault (core dumped)
burt@T420s:~/Downloads$

RE: Serial Terminal in nRF Connect for Desktop Linux version not working poolside

Burt — Sat, 08 Jun 2024 20:24:13 GMT

I made some progress. It helps to have nrfutil in the PATH, in both Linux and Windows cases. With that, I think Windows works completely. Linux may need the Internet to start up nRF Connect for Desktop. Maybe it will take more than one time for the Serial Terminal to find the board (or dongle, if using our custom board). I think I can then put the laptop into suspend and resume successfully, with no Internet.

Can you verify my findings, and see if there are any improvements you should do? Like telling the user to put nrfutil into his PATH, etc. Thank you.

Burt