Explain about SSLDD 3.0 Design setup
SSLDD 3.0 design set up contains the following features
- Static Configuration header file
- Static configuration header file contains set of configuration macros.
- Device Initialization
- Initialize the Peripheral.
- Initialize the Device Drivers structures.
- Configure the peripheral using static configuration (if available).
- Install the interrupt handlers with interrupt service.
- Return a device Handle to the application.
- Data transfer APIs – Blocking/Core vs non-Blocking/DMA.
- Blocking mode: A read or write call does not return until the read or write transaction has completed. SSLDD 3.0 implements core mode as blocking mode.
- Non-Blocking mode: a read or write call does returns immediately, even if the read or write transaction has not completed yet. The device driver executes the callback, registered by the application, when the read or write transaction completes or when an error occurs.
- Interrupt Handling
- When an event occurs the micro-controller generates a hardware interrupt. So upon generating a hardware interrupt, program execution jumps to the interrupt handler and executes the code in that handler.
- Other APIs
- Callback Registration - By default, device drivers do not provide callbacks to the application. If required, an application can register the callback with the driver after it is opened.
- Low level APIs use to override the configuration which we had done in static configuration header file
- Operating System Abstraction layer(OSAL) and FreeRTOS
- OSAL layer acts an abstraction for various underline RTOS and users can use it to integrate the RTOS of their choice.
- By default, CCES provides OSAL with no-OS implementation underline