Open dombru54 opened 3 months ago
Both core are needed, on core1 i run the bus emulation, that had a timing aligned with console and can't stop never. On core 0 run all other stuff.
Il giorno mer 7 ago 2024 alle ore 11:53 dombru54 @.***> ha scritto:
You use Core1, but why ? Code : multicore_launch_core1(core1_main); Is Core0 more sensitive to interrupts or others hardware interactions ? Thanks for your expertise.
— Reply to this email directly, view it on GitHub https://github.com/aotta/PiRTOII/issues/6, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACV2MY3JMZMMANPU2I6LBWLZQHVB7AVCNFSM6AAAAABMEBNNHSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TGMBWGY3TIOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I understand now the uncommented line : multicore_launch_core1(core1_main); Maybe, i can add comment : // Core1 run the unique function "core1_main()"
then, in function "void __not_in_flash_func(core1_main())", you must specify this function : multicore_lockout_victim_init(); Maybe, i can add comment : // Core1 is obliged to do a pause in knew state by Core0.
Is Core0 more sensitive to interrupts or others hardware interactions than Core1 ?
You use Core1, but why ? Code : multicore_launch_core1(core1_main); Is Core0 more sensitive to interrupts or others hardware interactions ? Thanks for your expertise.