hi everyone! I just refreshed spe according to the guide
and successfully tried IVC-echo-task. Now I want to check the spe log. How can I do it? The kit I use is Jetson orin nano36.4.3 developer kit
hi everyone! I just refreshed spe according to the guide
and successfully tried IVC-echo-task. Now I want to check the spe log. How can I do it? The kit I use is Jetson orin nano36.4.3 developer kit
Refer to Tegra Combined UART — NVIDIA Jetson Linux Developer Guide 1 documentation for details.
br
ChenJian
sorry,my code reports this error. I have no idea how to use it. Can you teach me?
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$ ./nv_tcu_demuxer <options>
-bash: syntax error near unexpected token `newline'
I don’t quite understand what command to use to launch the “nv_ tcu _demuxerand” only get the spe logs, I’m so sorry, could you teach me?
Please check the full doc.
It provides sample command at Tegra Combined UART — NVIDIA Jetson Linux Developer Guide 1 documentation
br
Chenjian
I got this error when I ran the example command. Why?
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$ ./nv_tcu_demuxer -d /dev/ttyACM0 &
[1] 2657
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$ ERROR: failed to open /dev/ttyACM0
open_tty_device: failed
ERROR: failed to open in read mode /dev/ttyACM0
[1]+ Exit 255 ./nv_tcu_demuxer -d /dev/ttyACM0
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$ ./nv_tcu_demuxer -d /dev/ttyACM0 &
[1] 4926
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$ ERROR: failed to open /dev/ttyACM0
open_tty_device: failed
ERROR: failed to open in read mode /dev/ttyACM0
[1]+ Exit 255 ./nv_tcu_demuxer -d /dev/ttyACM0
rvbust@ubuntu:~/Jetson_36.4.3/Linux_for_Tegra/tools/demuxer$
Also, can I only view the spe log in the virtual machine?
Hi, I think I may have misspelled my device name, how do I determine the name of the device on my host UART?
That device does not exist.
Maybe you have to study from beginning. Check Welcome — NVIDIA Jetson Linux Developer Guide 1 documentation
and search some keywords like debug uart port, or something like that.
br
ChenJian
Thanks! it help me a lot!
o. I just noticed that you are running the command with your own user.
Please try sudo
such device may have access permission issue.
You can check whether the device exists.
Generally, such commands need root permission.
br
ChenJian
Thanks for ur help! I check my /dev/ and find which tty-name i should use.Now I’m reading ivc-echo-task.c
static void ivc_echo_task_process_ivc_messages(struct ivc_echo_task_state *state)
{
int ret;
const char *rx_msg;
bool non_contig_available;
int count, i;
for (;;) {
rtosSemaphoreAcquire(state->ivc_sem, rtosMAX_DELAY);
count = tegra_ivc_rx_get_contiguous_read_available(
state->id->ivc_ch, &rx_msg, &non_contig_available);
rtosSemaphoreRelease(state->ivc_sem);
dbgprintf("IVC read count: %d\r\n", count);
error_hook("11111111111111111111111111111");
if (count < 0) {
error_hook("tegra_ivc_rx_get_contiguous_read_available() failed");
return;
}
if (!count) {
return;
} else {
for (i = 0; i < count; i++) {
ivc_echo_task_write_msg((void *)rx_msg, 64);
rx_msg += 64;
}
}
rtosSemaphoreAcquire(state->ivc_sem, rtosMAX_DELAY);
ret = tegra_ivc_rx_notify_buffers_consumed(state->id->ivc_ch,
count);
rtosSemaphoreRelease(state->ivc_sem);
if (ret) {
error_hook("tegra_ivc_rx_notify_buffers_consumed() failed");
return;
}
}
}
Something I don’t understand about this code, I want to know if rx_msg
is the data I’m sending out for example sudo su -c ‘echo 66666 > /sys/devices/platform/bus@0/bus@0:aon_echo/data_channel’
rx_msg
is 66666
And what is the difference between dbgprintf and error_hook?