Skip to content

[protocol] Convert jtag to use the new compact error format - #291

Open
esnguyen wants to merge 1 commit into
google:mainfrom
esnguyen:convert_jtag
Open

[protocol] Convert jtag to use the new compact error format#291
esnguyen wants to merge 1 commit into
google:mainfrom
esnguyen:convert_jtag

Conversation

@esnguyen

@esnguyen esnguyen commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Signed-off-by: Ellis Sarza-Nguyen <sarzanguyen@google.com>
Comment thread protocol/jtag.c
"HOTH_JTAG_OPERATION expected exactly %zu response bytes, got %zu\n",
sizeof(response), response_length);
return LIBHOTH_ERR_CONSTRUCT(HOTH_CTX_CMD_EXEC, HOTH_HOST_SPACE_LIBHOTH,
LIBHOTH_ERR_FAIL);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Would it be a good idea to create a different error code for this condition? It can be done in a separate PR if you prefer to do so

Comment thread protocol/jtag_test.cc
EXPECT_NE(libhoth_jtag_read_idcode(&hoth_dev_, interface_id, clk_idiv,
&received_idcode),
-1);
HOTH_SUCCESS);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: For the failure cases, do you think checking that a particular error code is returned for the particular scenario in the test would be useful? Or would it be too cumbersome to manage the tests if error codes are tied to particular error scenarios

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants