Can the OPI5 be Configured to Run LCNC?
With the non rt kernel it does boot from the nvme?
Are you sure you're writing the right uboot to mtd?
Here are some others:
github.com/7Ji/orangepi5-rkloader/releases/tag/nightly
Download: wget github.com/7Ji/orangepi5-rkloader/releas...ddr-v1.16-spi.img.gz
extract: gzip -d rkloader-mainline*.gz
erase mtd: flash_erase /dev/mtd0 0 0
write mtd: dd if=rkloader-mainline*.img of=/dev/mtdblock0 bs=4K
Uploaded an image (without hw acceleration) with the rt kernel already installed.
For better latency results add the following line to armbiEnv.txt :
extraargs=isolcpus=5,7
and disable screensavers/standby etc
Installed the kernel on my OPI5 and installed the (sata) bootloader from that image to the mtd and it still boots from the M.2 sata. The OPI5 plus also still boots from NVME.
Please Log in or Create an account to join the conversation.
Here is the u-boot from the original Orange Pi 5 image which should work with a nvme:
drive.google.com/file/d/1LqVTgFD2e_3kkF-.../view?usp=drive_link
Please Log in or Create an account to join the conversation.
Kernel 5.10_nvme:
Kernel 6.1_SDcard:
Please Log in or Create an account to join the conversation.
github.com/orangepi-xunlong/linux-orange...s/rockchip_rt.config
Already tried another power cord/adapter?
Did you try to write the bootloader to mtd (spi flash) from my previous message?
Are there other people who experience the same when booting from nvme?
Mine shows the same cpu usage by the way, even while running latency-histogram. You'll see that rtapi (the realtime component) with priority -99 runs on the last cpu, so it works how it should.
Please Log in or Create an account to join the conversation.
The 5 and 7 cores are isolated and linucnc works with highest priority on 0,1,2,3,4,6 cores (Htop shows this).
So nobody uses 5, 7 cores. Why isolate them if you don't put linuxcnc on them?
I noticed that my linuxcnc works better with all cores enabled. I actually watch StarTrek when the cnc is running.
Please Log in or Create an account to join the conversation.
drive.google.com/drive/folders/1r76sUsfG...6fGcz?usp=drive_link
The realtime component is on core 7 by the way, in htop you should select the one with -99 priority before you press "a'. The gui isn't realtime so no need to put that one on a isolated core. But without isolating cores the results are still good enough indeed, so if that experience is better it might be the better choice.
Just tested without isolating a core and the latency on the servo thread went up to 40us, while when I only isolate core 7 until 3.3us. The kernel in the Test folder is with cpu governors, so I put these via armbian-config at performance and lowest frequency at the highest.
With only core 7 isolated it has no frame drops at 1440p@30fps, unfortunately there is no full (ffmpeg) hw acceleration in chrome anymore, where the cpu usage stayed below 10% @4k.
Attachments:
Please Log in or Create an account to join the conversation.
I downloaded the image you put "Armbian-unofficial_24.11.0-trunk_Orangepi5_bookworm_vendor_6.1.75_cinnamon_desktop-002.img" and big surprise, it stuck when booting.
I used the image "Armbian_24.8.1_Orangepi5_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img" (the one in your link on page 35), and it boots and I can apply rt kernel to it.
The answer lies in the differences between the two non real time images. One boots and the other doesn't.
Do you think that if you applied configuration for rt-kernel on the image "Armbian_24.8.1_Orangepi5_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img" it would result in deb's that would work?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Maybe it's me but it's not clear to me, the message above means that you can boot now from nvme with the last rt kernel on the image I suggested in the first place?I used the image "Armbian_24.8.1_Orangepi5_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img" (the one in your link on page 35), and it boots and I can apply rt kernel to it.
The answer lies in the differences between the two non real time images. One boots and the other doesn't.
Please Log in or Create an account to join the conversation.