Add shell command for zero #68
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the firmware update of Zero and Pico, it is necessary to execute commands like `rauc`, `mcumgr`, and crc32, which are already included in out Yocto environment. These commands will be used for file uploads, CRC calculation, and firmware update processes. The commands can accept strings up to 200 bytes in length, and the command responses will be split into 240 byte segments when downlinked. However, to avoid infinite downlinking, a limit is set on the number of responses (50 responses per command). Additionally, to account for potential command hang-ups, the timeout duration can also be specified from the Ground. While we understand that security considerations are necessary, we have not implemented any restrictions in the first commit. Signed-off-by: Takuya Sasaki <[email protected]>
This commit adds the patch for resolve issue below. The Linux USART driver for libcsp calls `exit()` API the rx_thread if a read operation fails. This behavior terminates the entire process, even if communication via interfaces other than USART is still possible. Therefore, the exit() code will be removed. Signed-off-by: Takuya Sasaki <[email protected]>
When executing `mcumgr` using shell commands, the following error occurs. Error: exec: "getent": executable file not found in $PATH However, this error does not appear when logging directly into Zero via SSH. The reason for this behavior is not yet understood, but to expedite testing, we will add the `glibc-utils` package to install `getent`. Signed-off-by: Takuya Sasaki <[email protected]>
sasataku
force-pushed
the
add-shell-command-for-zero
branch
from
4b2fbe4 to
befc4e7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the firmware update of Zero and Pico, it is necessary to execute
commands like
rauc,mcumgr, and crc32, which are already includedin out Yocto environment. These commands will be used for file
uploads, CRC calculation, and firmware update processes.
The commands can accept strings up to 200 bytes in length, and the
command responses will be split into 240 byte segments when downlinked.
However, to avoid infinite downlinking, a limit is set on the number
of responses (50 responses per command).
Additionally, to account for potential command hang-ups, the timeout
duration can also be specified from the Ground.
While we understand that security considerations are necessary, we have
not implemented any restrictions in the first commit.