Toolkit Connection

Utilities Targets Requires: signed in

Configure how the toolkit connects to a target device.

Overview

The Toolkit Connection panel, with each field numbered. Your changes save automatically as you type.

1. Platform Family — The display model this connection targets; enables features and configuration specific to that display type.
2. Description — A friendly name for this connection, shown in the connection list on the left.
3. Host Name / IP — The target's network address.
4. Service Port — Talks to a System Service running on the target to get information about the system. (Default = 5001)
5. Security Port — Talks to a Security Service running on the target if secure services are being used. (Default = 5007)
6. API Key — Authenticates this connection with the target, if its Security Service requires one.

While this tab is selected, Toolkit Actions on the right offers device actions like Prep Target, Enable/Disable RDP, and Load Application.

Flash Distribution

Watch video walkthrough

1. A new display needs the most current BSP (Board Support Package) before it can be prepped for this version of the toolkit — that's what Flash Distribution installs. Before starting, verify the display powers on to the installer or application screen, then connect it to your computer with a USB-C cable. Power to the display must stay stable and uninterrupted for the whole flash.

   (Confirming power and the USB-C connection before flashing)

2. Remove power from the display, then boot it into DFU Flash Mode. On an S50 or S70, place a high-powered magnet over the triangle/circle icon on the back of the display, in the area below the USB port.

   

3. On a P100, place the magnet over the microphone hole on the front of the display instead.

   

4. Apply power to the display while holding the magnet in place, then remove the magnet after a few seconds — the screen stays black if DFU mode was entered successfully.

   (The display in DFU mode — the screen stays black)

5. Select the Targets button from the toolbar, then verify the correct Platform Family is selected and the correct Host Name / IP is set for DFU: 192.168.7.1 for an S50 or S70, 192.168.5.1 for a P100.

   

6. Click Flash Distribution. The app switches to Console and looks for a display in DFU mode.

   

7. If no display in DFU mode is found, a Device Not Found dialog explains why: the mask ROM enters DFU mode regardless of what's on the flash, so a display that's connected and still not found isn't a firmware problem — more likely its USB driver isn't installed. Open Plugins and press Install Drivers on that display's platform support card, then try again.

   

8. Once a display in DFU mode is found, the console downloads and writes each firmware partition in turn — fsbl-boot, fip-boot, metadata2, fip-a, bootfs, and more — with its own progress bar, which can take several minutes in total.

   

9. Once every partition finishes writing, power-cycle the display and click Continue once it finishes booting back up.

   (Confirming the display has rebooted with the new firmware)

Prep Target

Watch video walkthrough

1. Prep Target sets up the display's hardware profile — required before it can run a package. Before starting, power-cycle the display unit and wait for it to finish booting to the Helios/Enovation logo screen.

   

2. Select the Platform Family that matches the device's real model — here, OpenViewLinux (S70).

   

3. With a connection to that device selected, Toolkit Actions offers device actions including Prep Target. Click it. A confirmation dialog appears — verify it names the correct display model, here an OpenViewLinux (S70) unit, before clicking Yes to continue.

   

4. The app switches to the Console panel to run the prep process on the device, with a Cancel button while it's in progress. The display won't show a connected status during this phase — that's expected.

   

5. Once prep finishes, the display reboots automatically and the app returns to the Targets panel — no confirmation dialog.

   

6. Click Console to review the full log. A successful run verifies each required service and file (All checks passed), reports prep.sh complete, and schedules a reboot on the device to apply it. Once the display finishes rebooting, it reconnects and shows a connected status again — it's now ready to load a package via Load To Target (see Packaging).

   

Enable RDP

Watch video walkthrough

1. Enable RDP... in Toolkit Actions turns on the target's Remote Desktop (RDP) service so you can connect to it with a standard Remote Desktop client. Click Enable RDP... (highlighted).

   

2. A confirmation dialog explains what it does. Click Yes to continue.

   

3. The app switches to Console to show progress — generating a device certificate for RDP.

   

4. It then returns to the Targets panel on its own once that step starts; the display drops its connected status while the process finishes. Click Console to see the full log.

   

5. A successful run generates a device certificate, then reports Modifying Display Configuration and Rebooting Display — enabling RDP reboots the target, so wait for it to reconnect before continuing.

   

Start Session

Watch video walkthrough

1. Once RDP is enabled on the target, Start Session... opens a Remote Desktop connection to it. Click it.

   

2. The app immediately shows its own Session Started dialog, while Windows' own Remote Desktop Connection client opens separately and asks whether you trust the connection. That trust prompt is a real Windows dialog, not part of the toolkit. Click Connect.

   

3. Remote Desktop then warns that the identity of the remote computer cannot be verified — this is expected, since Enable RDP gives the display its own self-signed certificate rather than one from a trusted authority. Check that the requested remote computer is your display's IP address, then click Yes.

   

4. Remote Desktop connects and opens full-screen, showing whatever is running on the display — here, the Ahsoka.CS.BLE.Select demo project's own UI. The bar at the top shows the display's IP address, with buttons to minimize, restore, or close the session.

   

5. When you're done, close the Remote Desktop window with the X on that bar — it closes right away, without asking. The app's own Session Started dialog is still open behind it.

   

6. Click Finish Session to close out and return to the Targets panel.

   

Disable RDP

Watch video walkthrough

1. Disable RDP... reverses Enable RDP, turning the target's Remote Desktop service back off. Click it.

   

2. A confirmation dialog asks you to confirm before continuing. Click Yes.

   

3. Unlike Enable RDP, there's no progress screen — the app returns to the Targets panel right away. Click Console to see what actually happened.

   

4. This one doesn't check whether RDP was ever installed — it unconditionally reports Removing Device Certificate, Modifying Display Configuration, and Rebooting Display, and the display drops its connected status while it restarts.

   

Load Application

Watch video walkthrough

1. Load Application... installs an .opv package straight onto the target, without going through Load To Target on the Packaging panel. Click Load Application....

   

2. If the display is already running an application, the app shows a Connection Error — No connection available or target is running an application currently. Click Ok.

   

3. Stop the running application first: click the Stop Application icon (the square) at the bottom right.

   

4. There's no confirmation — the application stops right away, and the status shows Waiting for Connection while the display returns to its installer. Click Console to confirm.

   

5. The Console shows Stop Application Sent, and the status bar now shows the display connected to its installer (Ahsoka.Installer.UI). Close the Console with its X to return to the Targets panel.

   

6. Click Load Application... again.

   

7. This time a Pick Application File dialog opens, filtered to .opv files. Navigate to your PackageOutput folder — where Generate Package writes packages — and double-click it.

   

8. Select the package to install — here, Ahsoka.CS.SimpleUI.Select.opv.

   

9. Click Open. The install starts right away — there's no separate confirmation.

   

10. When the install finishes, the status bar shows the new application running — here, Ahsoka.CS.SimpleUI.Select. Click Console to see the log.

    

11. The log ends with Finished File Transfer for File:autoload.opv with Result:Success and Package Load Completed — confirmation the load worked.

    

12. The display itself now shows the installed application — here, the Simple UI Demo's own screen, confirming the package is actually running on the target and not just reported as loaded in the console log.