Dual-Core Inter-Core Communication in FreeRTOS

[codecubepi]

• [x] Re-create AMDC Firmware project in SDK to use Standalone BSP
• [x] #351
• [x] #352
• [x] #353
• [ ] Complete icc.h and icc.c: Implement a MessageBuffer with Callback functions that can send interrupts to each core, letting tasks know data was placed in/removed from the message buffer.
• [ ] Using the MessageBuffer, implement the demo app functionality described below
• [x] C-lang Format and push

Demo Functionality:

• [x] both cores use icc_init() to create their own references to the shared message buffers
• [x] LEDs cycle yellowevery second while sending messages
• [ ] cpu0 to send 5 messages to cpu1 every half second. cpu1 should print a message when it's done, and signal to cpu0, which acknowledges the completion
• [ ] cpu1 to send 5 messages to cpu0 every half second. cpu0 should print a message when it's done, and signal to cpu1, which acknowledges the completion
• [x] Flash all LEDs green when done

Resources:

• https://www.freertos.org/RTOS-Xilinx-Zynq.html

[codecubepi]

Update 16 April 2024:

I've been continuing to try and figure out why bringing my dual-core interrupt code from my test project into the AMDC codebase causes the dual-core-ness of the interrupts to break.

Nuclear strategy going forward is to bring the most offending code over from the AMDC codebase to the example project until I find the piece that breaks the example project.

See #363 for working dual-core interrupt project