Hello,
Currently, I am testing RT-kernel using Jetson Thor Devkit, and the system version is R38.2.1. Recompile and burn the system after enabling rt-kernel based on the official instruction manual.KernelCustomization.html
Load the CPU throughstress and test it through cyclictest.
The same method and the same instructions, but when looking at the data, it seems that the latency is higher when rt-kernel is applied. I don’t know if there’s something wrong, but I can see that the kernel is indeed rt-kernel.
I also encountered the same problem. After applying the RT patch, the /proc/version does not have the PREEMPT_RT flag, and the kernel configuration options about PREEMPT are as follows:
CONFIG_PREEMPT_NONE_BUILD=y
CONFIG_PREEMPT_NONE=y
CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT is not set
CONFIG_PREEMPT_DYNAMIC is not set
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_KEY=y
CONFIG_PREEMPTIRQ_DELAY_TEST is not set
However, when checking the l4t-rt package, it was found that only the R38.2.0 version was available. Could it be that there are still issues with the RT-kernel in R38.2.1?
And I do indeed need to apply the RT-kernel patch through the kernel, rather than via OTA!
Please take a look at this question as soon as possible and give a reply.
Hello,
Currently, following the guide step by step to enable the Real-Time kernel under JetPack 7.1, but the result remains the same as before. The Real-Time kernel updated via OTA performs as expected in actual tests, as shown in the figure below.
Great! Just modified the generic_rt_build.shscript as suggested in the post, recompiled, flashed, and tested again — and it’s working now! I’ll continue further verification, but thank you so much!