No response from "Choose a board"

Development Tools App Lab
1

Hello!

I've read just a few earlier posts, but I am unable to proceed after launching App Lab and choosing a board. As a newbie, I would appreciate getting off the starting gate with guidance from more experienced persons.

The board is detected by App Lab (as NEW BOARD) with the USB icon (tooltip - Connected via USB). But after I choose the board (clicking anywhere in the image frame for the board) nothing happens. There is no feedback to continue working on the subsequent steps that are documented for App Lab and UNO Q.

What is my mistake? Irrespective of the confirmation by App Lab, I have checked the board using USB listing utilities (USBview, lsusb, ec.). All utilities report the correct vendor and model IDs. I am using Ubuntu 26.04 and I have updated all common/known USB "drivers" but I cannot proceed with after selecting the board. I have changed the USB-C cable several times. What other methods can I use? Thanks.

Regards.

$ cat ./99-arduino-uno-q.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="2341", MODE="0666", GROUP="dialout"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666", GROUP="dialout"
$
2

Hi @baqwas. I'm going to ask you to provide some additional information that might help us to identify the problem.

:red_exclamation_mark: This procedure is not intended to solve the problem. The purpose is to gather more information.

Please do this:

  1. If Arduino App Lab is already running, close the window.
  2. Start Arduino App Lab.
  3. Press the Ctrl+Shift+F12 keyboard shortcut.
    The "DevTools" window will open.
  4. Select the "Console" tab in the "DevTools" window.
  5. Right-click on the main panel of the "DevTools" window.
    A context menu will open.
  6. Select "Clear console" from the menu.
    The existing content will be cleared from the console panel.
  7. Switch to the Arduino App Lab window.
  8. Select the board, just as you did before.
  9. Verify that the "nothing happens" fault occurred, as before.
  10. Switch back to the "DevTools" window.
  11. Right-click on the main panel of the "DevTools" window.
    A context menu will open.
  12. Select "Copy console" from the menu.
    This will copy the logs recorded in the console panel to the clipboard.
  13. Open a reply here on this forum topic by clicking the "Reply" button.
  14. Click the <CODE/> icon on the post composer toolbar.
    This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
    Code block icon on toolbar
    Code block icon on toolbar390×118 4.25 KB
  15. Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
    This will paste the copied logs into the code block.
  16. Move the cursor outside of the code block markup before you add any additional text to your reply.
  17. Click the "Reply" button to publish the post.
3

Thank you!

Here are the steps that I performed in chronological order:

  • ✓ If Arduino App Lab is already running, close the window.

  • ✓ Start Arduino App Lab.

  • ✓ Press the Ctrl+Shift+F12 keyboard shortcut.
    ✓ The "DevTools" window will open.

  • ✓ Select the "Console" tab in the "DevTools" window.

  • ✓ Right-click on the main panel of the "DevTools" window.
    ✓ A context menu will open.

  • ? Select "Clear console" from the menu.
    The existing content will be cleared from the console panel.
    “Clear log” was displayed and selected.

  • ✓ Switch to the Arduino App Lab window.

  • ✓ Select the board, just as you did before.

  • ? Verify that the "nothing happens" fault occurred, as before.
    Status message in DevTools window:
    Failed to select board – “failed to connect to board: ADB device is offline”
    Error fetchin boards: - “failed to detect boards: no found for FQBNs arduino:zephyr:unoq, arduino:zephyr:ventunoq”

  • ✓ Switch back to the "DevTools" window.

  • ✓ Right-click on the main panel of the "DevTools" window.
    ✓ A context menu will open.

  • :no_entry: Select "Copy console" from the menu.
    “Clear log” was displayed
    This will copy the logs recorded in the console panel to the clipboard.

Since I could not perform the "Copy console" operation, I am sorry that I could not complete your instructions fully. The App Lab version is displayed as 0.8.0 in title bar of the App's main window. I repeated the entire process from the top three times with identical results (to avoid operator keyboard errors).

Looking forward to your next steps. Thanks.

$ ps aux | grep adb
reza 173899 0.0 0.0 463200 6228 ? Ssl Jul08 0:36 adb -L tcp:5037 fork-server server --reply-fd 4
reza 321513 0.0 0.0 9308 2524 pts/0 S+ 07:39 0:00 grep --color=auto adb
reza@BeUlta:~/projects$ killall adb
$

Restarted the steps from the top after killing adb but still no change in results.

4

Hello @ptillisch!

Story of my life - operator error!!

I didn't log out after changing the udev rules and log back in again. Once I did that 2-step, I was able to get past the starting gate. Sorry for the false alarm.

Regards.

5

Excellent work troubleshooting the problem! I'm glad it is working now. Thanks for taking the time to post an update with your findings.

Regards, Per