I would like to propose as my project a hardware based implementation of a "RAD hardware reference design". The idea is to break the barrier between the Pc world and the MCU world and bring a more RAD like experience by providing a mediator layer to manage the intercommunication between pc and mcu.
The hardware design should use the simplest hardware of the lowest level with no heavy protocols/standards in between. The last protocol on the Pc side, the fence, is USB. From here we must manage the 'dimensional shift' from Pc/Master application--->Hexadecimal transformation---> SPI or UART---> MCU slave application, and back to the Master/Pc. Success would equal a piece of hardware that is barely distinguishable from a Lazarus component, including a simple interrupt based 'event model'.
Here is the hardware reference design I am thinking about for starters:
Master- PIC16f84(program data)---> NRF24l01 RF based wireless transceiver (all communication)
Slave- 'The project hardware'---->PIC16f84(program data)---->NRF24l01
So think of the 'Master' as the 'modem for objects/components' and the 'Slave' as the 'component/wrapper of actual hardware' with networking back to the master seamless and transparent over RF.
The workflow would look something like this. You want to make a 'RAD videocam' based upon a raw SPI based camera. You start by using the 'slave reference design', wire the SPI from the camera, write the MCU code following the 'RAD protocol' that we must establish (which will be hard wired into the master/modem reference design). Success means at the end of the day, you have a hardware camera that looks and behaves like a Lazarus component... and wirelessly.https://i.ytimg.com/vi/OWyHnAlJhpw/hqdefault.jpghttps://www.zigobot.ch/images/stories/v ... mini-1.jpg