The leon3 BSP also supported something similar at one point. If the two applications do not need to communicate, then it should not be an issue. If the do need to communicate, then this might be a case where the original distributed multiprocessing in RTEMS makes sense. It isn't used much but is still there. Or you could just reserve some RAM for a shared communications area and manage it yourself.
The key is going to be keeping the two really separate and making sure you can load two images. --joel On Mon, Oct 24, 2022 at 8:03 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Jens, > > in general, such a setups works. We used it some time ago on the NXP > P1020 before the SMP support was available. You just have to provide two > MEMORY definitions for the linker. You also have to make sure that you > don't accidentally share hardware modules between the two RTEMS > instances without synchronization. > > -- > embedded brains GmbH > Herr Sebastian HUBER > Dornierstr. 4 > 82178 Puchheim > Germany > email: sebastian.hu...@embedded-brains.de > phone: +49-89-18 94 741 - 16 > fax: +49-89-18 94 741 - 08 > > Registergericht: Amtsgericht München > Registernummer: HRB 157899 > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler > Unsere Datenschutzerklärung finden Sie hier: > https://embedded-brains.de/datenschutzerklaerung/ > _______________________________________________ > users mailing list > users@rtems.org > http://lists.rtems.org/mailman/listinfo/users
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
