Author Topic: Customize CodeBlocks for ARM Development (Toolchains)  (Read 3230 times)

Offline hentaiw

  • Single posting newcomer
  • *
  • Posts: 3
Customize CodeBlocks for ARM Development (Toolchains)
« on: March 26, 2016, 01:05:30 am »
Hello,
I have been trying to get Code::Blocks to work with my ARM development.
I am using TI Tiva C TM4C123G.
I have 3 steps:
1. Run this to make my Linux terminal recognize GCC-ARM.
Code
export PATH=$PATH:$HOME/Embedded/gcc-arm-none-eabi-5_2-2015q4/bin
2. Go to project folder, use the make file.
Code
make
3. Run this in /$HOME/Embedded/lm4tools/lm4flash/
Code
sudo ./lm4flash /home/kudy/Embedded/tivaware/examples/boards/ek-tm4c123gxl/project0/gcc/project0.bin

I really want to use CB, code in there, hit the compile and run button, and CB automatically does those steps for me.
Also if I can avoid sudo in the third code, that would be great.
Thanks in advance.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: Customize CodeBlocks for ARM Development (Toolchains)
« Reply #1 on: April 02, 2016, 03:18:21 pm »
1. Run this to make my Linux terminal recognize GCC-ARM.
Code
export PATH=$PATH:$HOME/Embedded/gcc-arm-none-eabi-5_2-2015q4/bin
You can try to use Settings->Environment settings->Environment variables with Project->Properties->EnVars options

2. Go to project folder, use the make file.
Code
make
You can use a custom make file project:
Project->Properties->Project settings->Makefile and the "This is a custom Makefile" settings

3. Run this in /$HOME/Embedded/lm4tools/lm4flash/
Code
sudo ./lm4flash /home/kudy/Embedded/tivaware/examples/boards/ek-tm4c123gxl/project0/gcc/project0.bin
You can use the Tools+ plugin: Tools+->Configure Tools
For the usable variables in the tools plugin see: http://wiki.codeblocks.org/index.php/Variable_expansion

Quote
Also if I can avoid sudo in the third code, that would be great.
this is a general linux question and this forum is not the right place to ask this question... i think you should add your usb programming device to the /etc/udev/rules.d
google for this, or read a similar topic about avrdude: http://mightyohm.com/blog/2010/03/run-avrdude-without-root-privs-in-ubuntu/

i hope i could help
greetings