Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I know each device is ready to receive a Greengrass deployment?
In AWS IoT Core, confirm the device is registered as a Greengrass core device and appears in the thing group you plan to deploy to. If it isn’t in the group, add it before creating the deployment.
What result should I expect from the PAC/BTI test on Raspberry Pi 5 versus Jetson Thor?
Raspberry Pi 5 (Armv8.2-A) should report PAC and BTI as not supported. Jetson Thor (Armv9-A) should report both PAC and BTI as supported.
Where should I store the custom component artifact before creating the deployment?
Upload the component artifact to an Amazon S3 bucket created in the AWS console. Keep the default bucket settings for this tutorial and ensure the artifact is available for the component to use during deployment.
Which target should I select to deploy the component to both devices at once?
Select a Greengrass thing group (for example, My_PAC_BTI_Test_Devices) as the deployment target. This delivers the same component set to both core devices in the group.
How do I trigger and validate the PAC/BTI checks after deployment?
Use MQTT to trigger the checks as described in the steps, then review the results reported for each device. Expect outputs that let you interpret PAC/BTI support per platform.

Share

Tell others about this Learning Path.

Back