TIVA Launchpad TM4C123 Part 1 - Blinking RGB LED

-
Before we start writing programs, we need to install the following softwares.

1. Download and install the latest version of Code Composer Studio (CCS):

http://processors.wiki.ti.com/index.php/Download_CCS

2. Download and install the full version of TivaWare from below link. The file name to download is SW-TM4C-x.x.exe

http://www.ti.com/tool/sw-tm4c

3. Download and install the latest LM Flash Programmer

http://www.ti.com/tool/lmflashprogrammer

4. Download the TM4C123GHGPM Microcontroller datasheet and User Guide

http://www.ti.com/lit/ds/symlink/tm4c123gh6pm.pdf

http://www.ti.com/lit/ug/spmu296/spmu296.pdf

5. Run the Code Composer Studio


6. File -> New -> CCS Project

7. Select 'TIVA TM4C123GH6PM' from the drop down list, enter the Project Name: 'LED_BLINK' and click on 'Finish'


8. On the board, PF1 is connected to RED LED, PF2 is connected to BLUE LED and PF3 is connected to GREEN LED.

GPIO Registers in TM4C123:

 Data Direction Register (GPIODIR): Set the input pin as output/input
Data Register (GPIODATA): Write to the pin or read from the pin
Pull Up Register (GPIOPUR): Pull up the pin
Digital Enable Register (GPIODEN): To select the digital I/O Functionality of the Pin
Clock Enable (RCGCGPIO): This register is common for all ports, and used to enable the clock source for the port. If Port is not used, we can disable the clock source to save power. Access to the port registers with clock not enabled will result in hard fault and the program crashes.

 Steps to Blink LED

 1. Enable the clock source of PortF
2. Set the direction of PortF PF1, PF2, PF3 as output using Data Direction Register
3. Enable the Digital I/O feature of PORTF PF1, PF2 and PF3
4. Write HIGH on the PORTF pins to set the LED
5. Call a delay
6. Write LOW on the PORTF pins to clear the LED
7. Call a delay
8. Repeat the steps 4 to 7

main.c:

 To build the project, Right Click on the Project in the LED_BLINK and click on "Build Project"

To flash the firmware, we need to generate the .bin file. Code Composer generates .out file.

To generate a .bin file, right click on the project, click on Properties and Click On Build, then steps and add the following in Post-build steps.

 C:\ti\ccsv8\tools\compiler\gcc-arm-none-eabi-7-2017-q4-major-win32\bin\arm-none-eabi-objcopy -O binary  "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin"

 Now, right click on the project in the project explorer and click on Rebuild Project.




To flash the firmware on the TIVA board, connect the board to the PC over USB and open LM Flash Programmer and Select "TM4C123G Development Board"




Click on "Program" tab and browse the ".bin" file and Select the other options as per the screenshot



Click on "Program" to flash the firmware

Comments

  1. Geetanshu Chhajed4 May 2021 at 07:45

    I would really like to appreciate your work. This is damn good. It really helped me out.

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more