Closed AlSa-91 closed 4 years ago
There were 2 problems for you:
Thank you for the quick reply! 1) Actually i have limited the ram to 3072Mb by the command, exactly as you described on simple robot. could the connected touchscreen be the cause of the error? 2) So "Xenomai for Raspberry pi 4" on simple robot is just to make the RPI4 real-time capable without PiCAT or in my case wiz550io. Nice to know! is there a reason why you prefer xenomai over rt? or is this a wrong assumption on my part? Otherwise i would try to switch to the rt kernel, if this does not have a significant negative effect and i don't have the described issues. Thanks a lot for your help!
Hi,
1) cmdline.txt, config.txt files and output from kernel log dmesg: cmdConfDmesg.txt
2) Thank you very much for the detailed answer to this question, as I am only just getting into the subject of EtherCAT, Linux and real-time applications for the construction of a test bench.
As I suggested, you made several mistakes in both cmdline.txt and config.txt files.
...rootwait quiet splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=0 dwc_otg.fiq_fsm_enable=0 dwc_otg.nak_holdoff=0 isolcpus=0,1 xenomai.supported_cpus=0x3
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
total_mem=3072
Update these stuffs and Xenomai will work, You should read instruction on http://www.simplerobot.net/ more carefully! Goodluck,
This solved my USB issues, Thank you very much!
Dear @thanhtam-h I can just thank you for this great work. I downloaded the prebuilt kernel and installed it, do the post processing and all the stuff you described on http://www.simplerobot.net/. The result of the latency tool is positive. The Problems are that my wirless keyboard (and other USB stuff like the mouse) doesn't work any longer and slaveinfo with wiz550 (v1.3) per ssh doesnt work too. I repeatedly checked the cable arrangement and also measured the resistance of the cables. Could you give me a hand? On Simple Robot you mentioned Problems with USB, but I thought that the pre-patch fixed it. Thank you!