Running Nuttx RTOS on EK-TM4C123GXL

-
This is the short tutorial on how to build and flash Nuttx, the real-time operating system on TM4C123G LaunchPad on fresh installed Ubuntu 16.04 LTS.

More about Nuttx for TM4C123G LaunchPad:

https://bitbucket.org/nuttx/nuttx/src/42a0796615909b301273ee30fd5af907f4253347/configs/tm4c123g-launchpad/?at=master


Building Nuttx


In terminal run this commands:

mkdir nuttxdir
cd nuttxdir
git clone https://bitbucket.org/nuttx/nuttx
git clone https://bitbucket.org/nuttx/apps
git clone https://bitbucket.org/nuttx/tools
sudo apt-get install gperf flex bison libncurses5-dev
cd tools/kconfig-frontends/
./configure --enable-mconf
make
sudo make install
sudo ldconfig
cd ../..

Without libncurses5-dev you will have the problem with kconfig-mconf, so don't miss to install it. 

cd nuttx/tools

./configure.sh tm4c123g-launchpad/nsh
cd ..
make menuconfig

Inside menu config, you need select System Type -> Toolchain Selection -> Generic GNU EABI toolchain under Linux


For debugging you will need to add debugging symbols.

Build Setup -> Debug Options ->  Generate Debug Symbols


Press exit couple of time until ask you to save it. Now run make and you will have nuttx firmware inside this folder ready to be uploaded to your board.



make


Setup VisualStudio Code for debugging Nuttix


For debugging Nuttx inside Visual Studio Code here is launch.json configuration.

{
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch", "type": "cppdbg",
"request": "launch",
"miDebuggerPath": "arm-none-eabi-gdb",
"targetArchitecture": "arm",
"debugServerPath":"openocd",
"debugServerArgs":"-f /usr/share/openocd/scripts/board/ek-tm4c123gxl.cfg",
"filterStderr": true,
"serverStarted": "Info\\ :\\ [\\w\\d\\.]*:\\ hardware",
"program": "/home/osboxes/nuttx/nuttx/nuttx",
"args": [],
"stopAtEntry": true,
"cwd": "${workspaceRoot}",
"environment": [],
"externalConsole": true,
"MIMode": "gdb",
"setupCommands": [
{ "text" : "target extended-remote :3333"},
{ "text" : "monitor halt"},
{ "text" : "load /home/osboxes/nuttx/nuttx/nuttx"}
]
}
]
}

If you got problems with a running debugger then try to reconnect the cable of the board.

Inside tiva_start.c source set some breakpoints and you are ready to go.

If you wish to connect to NuttShell (Nuttx shell) you can do it with the screen.


 
sudo apt-get install screen
screen /dev/ttyACM0 115200


To get out from screen press disconnect the cable or software way out is Ctrl + A + D. After that you will need kill screen process.  Here is the example:

 
osboxes@osboxes:~/nuttx/nuttx$ pgrep screen
21386
osboxes@osboxes:~/nuttx/nuttx$ kill -9 21386

That is all. Thanks for reading this blog. Igor


Comments

Post a Comment

Popular posts from this blog

AUTOSAR and CRC calculation

-
Image
If you find yourself reading AUTOSAR document Specification of CRC Routines you are probably looking for a solution on how to implement it in your code. This is short instruction without explaining how CRC works. It includes working CRC code with examples from the mentioned documentation. Explanation of CRC8 CRC 8 it means, the polynomial of CRC is 8 bit long.  Explaining chapter 7.2.1: CRC result width - it is the return value, it says it is 8 bits long Polynomial - this value is used to calculate CRC. In this case, it is 0x1D Initial value - CRC calculation start with this value. It is usually all F's or zeros.  Input data reflection - it says if the data which you want to do CRC need to be reflected or not. Example of data reflection: hex: 0x73 or binary: 1110011, reflected value is: 1100111 or hex 0x67 Result data reflected - same as input data, but the only result is reflected XOR value - result value need to be XOR-ed with this value before is r
Read more

Flashing/debugging/running code at external memory in the memory-mapped mode

-
Image
  STM32 microcontrollers have special capabilities running code directly from external flash. To make it possible STM32 made a special set of instructions called memory-mapped mode where the microcontroller is reading instructions from the external flash. Since to read data from an external flash can take some time there is QSPI protocol witch basically four wires used as SPI MISO (Master Input Slave Output) to make throughput 4x time faster than classical SPI.   Figure 1 - Illustration of STM32H750 connected to W25Q128JV 
Read more

Debugging EK-TM4C123GXL with Visual Studio Code on Linux

-
Image
If you have TM4C123G LaunchPad Evaluation Kit and you like Visual Studio Code here is how to setup debugging on this board. This is the tutorial how to do that on clean Ubuntu 16.04 LTS. ARM GCC Compiler Setup Download the latest GCC cross compiler for the ARM from here:  https://launchpad.net/gcc-arm-embedded/+download In the time of writing this text, the last one is    gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 Run this commands in Linux console. wget https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q3-update/+download/gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 tar -jxf gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 rm gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 exportline="export PATH=$HOME/gcc-arm-none-eabi-5_4-2016q3/bin:\$PATH" echo $exportline >> ~/.profile source ~/.profile sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libc6:i386 lib32ncurses5 Without i386 architecture you will
Read more