How to add Subsystem to Offline Update Lockbox

Technical Support
, , ,
1

Hello,

i am trying to add a Subsystem Update to my Offline Update. I uploaded a package to the Torizon Cloud with Torizon Core Builder.

grafik
grafik438×155 4.42 KB

Now i want to add it to a Lockbox, but i can only choose following points

grafik
grafik891×256 11.8 KB

So how am i supposed to add the Subsystem Update?

Thanks for your help!

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Subsystem Updates and Offline Updates

Based on the documentation, Subsystem Updates work with both online and offline update scenarios(1). The key point is that Subsystem Updates work the same way for Remote and Local Update scenarios, allowing you to update connected and air-gaped products(1).

How Subsystem Updates Work with Lockboxes

When creating a Lockbox for offline updates, you should be able to include your subsystem packages. The Lockbox definition process allows you to:

  1. Select the desired OS and/or application packages(2)
  2. Give it a name, so you can refer to it in future steps(2)

The Lockbox creation process through the POST /lockboxes/{lockbox_name} endpoint supports adding custom packages via the packageIds parameter(3).

Troubleshooting Steps

If your subsystem update package isn’t appearing in the Lockbox creation interface, verify the following:

1. Package Upload Verification

Ensure your subsystem package was properly uploaded to Torizon Cloud using TorizonCore Builder(4).

2. Package Compatibility

For offline updates, packages must be canonicalized, which can be done using the --canonicalize argument(2). If you specified a package name explicitly with --package-name, it should end with .lock.yml or .lock.yaml(2).

3. Package Name Requirements

The package name must only use basic ASCII characters excluding control ones and those in the set \/:*?" ><|, otherwise the Lockbox generation may fail(2).

Expected Workflow

The typical workflow for subsystem updates includes:

  1. Provision the Torizon OS device to Torizon Cloud(4)
  2. Configure the Aktualizr update client to handle the target subsystem packages on the device(4)
  3. Write a custom action handler script(4)
  4. Create the target subsystem in Torizon Cloud(4)
  5. Upload the update payload to Torizon Cloud(4)
  6. Initiate the update with the new package(4)

If your subsystem package still doesn’t appear in the Lockbox selection, double-check that the package was successfully created and is visible in your Torizon Cloud package list.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Greetings @DoSi,

I was able to reproduce this issue on my side as well. Something may have changed as I recall being able to include whatever arbitrary subsystem before. I’ll bring this up to our team to see if there is a possible bug here.

Best Regards,
Jeremias

4

After, speaking with the team it seems the behavior of the Lockbox UI is as such.

The Lockbox UI will only show subsystem package options for subsystems present in currently provisioned devices.

This means if you want your subsystem package to be an option in the UI you must first provision a device that supports this exact subsystem.

Best Regards,
Jeremias

5

Hi Jeremias,

i was thinking of something like this. As for now we were only using Offline Provisioning at Scale with TCB because chance are small that our customers will ever use remote Updates.

Do you thing the behaviour could be changed for us pure “offline Guys”?

But i will give it a try and provision a device with a subsystem online to see if it works.

Thaks for your help!

6

Hi Jeremias,

when i provision the Device online it works.

grafik
grafik428×321 9.42 KB

Greetings.

7

Do you thing the behaviour could be changed for us pure “offline Guys”?

Our Torizon Cloud team says there is already a ticket in our backlog to review and possibly change the behavior in the UI.

For now though you’ll need to workaround the current behavior by having at least one device provisioned that contains the subsystem. The device doesn’t even need to be online after provisioning, so you can just provision a device and then reflash it for other purposes.

Best Regards,
Jeremias

9

Okay, thanks for the information.

Have a great week!

10

Glad we were able to help clarify.