Ok, I think I found the answer: The PRU task period is set using the pru_period= parameter when loading the module (default is 10,000 nS or 10 uS if not specified). If you want to reduce this value, make sure you leave enough overhead for the worst-case timing path through the PRU code. You can monitor the PRU active and idle time using the pru_busy_pin (defaults to enabled on PRU direct output 0). The PRU busy pin *MUST* be a PRU direct I/O, and you have to setup pin muxing to send the PRU bit to the I/O pin. By default the LCD/HDMI signals is using the PRU I/O bit 0, so you either need to move this signal to another pin, disable (or override) the HDMI pin multiplexing for PRU I/O 0, or just shorten the PRU task period and hope for the best (not recommended). -- Charles Steinkuehler
(source: https://emc-users.narkive.com/z4IjLdcX/linear-delta-kinematics-stepper-setup-bbb-bebopr-bridge) HurthLF4 schrieb am Mittwoch, 14. Juli 2021 um 11:46:43 UTC+2: > The missing attachments (does only work for me if the files are in archiv) -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/297822b8-3efc-4a34-8069-cbd0a7a1446en%40googlegroups.com.
