Sebastian Huber commented on a discussion on bsps/arm/xilinx-zynqmp-rpu/start/bspreset.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112332 > (void) source; > (void) code; > > zynqmp_debug_console_flush(); > > + /* > + * This is a workaround for: > + * > + * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658 > + */ > + __asm__ volatile (""); > + > while (true) { > - /* Wait */ > + /* Request a soft system reset */ > + *reset_ctrl |= UINT32_C(0x10); No matter which implementation we choose, there will be always applications for which this choice is wrong. In a complex system like the Zynq UltraScale+ you have to work out your own application-specific reset procedures. With the fatal extension RTEMS has an excellent place for this job. In my test setup, the RPU is started by the FSBL running on the APU. So for the test runs it was quite handy to reset the overall system. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112332 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
