You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently in the process of building a Yocto image for the Raspberry Pi 3 device. Our objective is to incorporate the aziot-edge and defender-iot-micro-agent-edge into the Yocto build so that it is present and functional on the target device. To achieve this, we have upgraded the meta-iot edge layer to version 1.4.9. However, even after flashing the image, we are unable to use or observe the presence of the aziot-edge and defender-iot-micro-agent-edge on the target device. We are seeking guidance on how to include the aziot-edge and defender-iot-micro-agent-edge in the Yocto build effectively, ensuring it is reflected and accessible on the target device. The commit IDs for the relevant layers are as follows:
We are currently in the process of building a Yocto image for the Raspberry Pi 3 device. Our objective is to incorporate the aziot-edge and defender-iot-micro-agent-edge into the Yocto build so that it is present and functional on the target device. To achieve this, we have upgraded the meta-iot edge layer to version 1.4.9. However, even after flashing the image, we are unable to use or observe the presence of the aziot-edge and defender-iot-micro-agent-edge on the target device. We are seeking guidance on how to include the aziot-edge and defender-iot-micro-agent-edge in the Yocto build effectively, ensuring it is reflected and accessible on the target device. The commit IDs for the relevant layers are as follows:
meta-iotedge: db4541e
meta-rust: 5656b5ad104bbbbe1b711e3bbe35c88f0d9c9a05
Please help us to fix this issue.
The text was updated successfully, but these errors were encountered: