Quantcast
Channel: Processors
Viewing all articles
Browse latest Browse all 125225

Forum Post: RE: PROCESSOR-SDK-OMAPL138: CSL update breaks project

$
0
0
Details regarding CSL documentation are provided in the SOftware developers guide here: http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_device_drv.html#am57x-k2x-c66x-c674x Users are required to include top level CSL header for the module for example for GPIO include cslr_gpio.h and csl_gpio.h and then add a compiler define for the SOC being used -D SOC_OMAPL138. the macro definition defines the version of the IP included and pulls in the required APIs. We also provide GPIO driver for the processors supported in the Processor SDK RTOS which abstracts the underlying IP implementation details and provides common API interface. GPIO driver source that uses CSL is provided here: You can look at the GPIO driver example as a starting point. http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_device_drv.html#building-gpio-examples If you still prefer to use the CSL for programming the GPIO interface then here are are the key things from an SOC perspective that are required. 1. Setup the PINMUX for the SOC to configure the GPIO pin as input or output and configure the mux mode. 2. Enable the power to module using PSC 3. Use CSL API to indicate pin and port number of the GPIO 4. Setup the GPIO output using GPIOPinWrite_vX or GPIOPinRead_vX. where X is the version number of the IP on the SOC. OMAPL138/C6748 uses version v0. Your understanding of banck number and pin number is correct. The base address that you pass will provide the port number. Regards, Rahul

Viewing all articles
Browse latest Browse all 125225

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>