46
Messages
This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.
Messages - senso
47
General discussion / Re: Getting started in the ARM world
But I just think, after reading and following the nice tutorial given by mr. drwho9437 I have created/compiled my toolchain, but in this part:
http://fun-tech.se/stm32/gcc/compile_blinky.php
When the tutorial author says that I should not get any errors or warnings I get this:
Code: [Select]
tiago@tiago-laptop:~/stm32-example/projects/stm_h103$ make clean
rm crt.lst a.lst main.lst crt.o main.o main.out main.hex main.map stm32f10x_rcc.o stm32f10x_gpio.o
rm: impossÃvel remover `crt.lst': Ficheiro ou directoria inexistente
rm: impossÃvel remover `a.lst': Ficheiro ou directoria inexistente
rm: impossÃvel remover `main.lst': Ficheiro ou directoria inexistente
rm: impossÃvel remover `crt.o': Ficheiro ou directoria inexistente
rm: impossÃvel remover `main.hex': Ficheiro ou directoria inexistente
rm: impossÃvel remover `main.map': Ficheiro ou directoria inexistente
make: [clean] Erro 1 (ignorado)
tiago@tiago-laptop:~/stm32-example/projects/stm_h103$ make
.compiling
arm-none-eabi-gcc -I./ -c -fno-common -O0 -g -mcpu=cortex-m3 -mthumb main.c
main.c:76:6: warning: conflicting types for 'myDelay'
main.c:61:14: note: previous implicit declaration of 'myDelay' was here
main.c:90:6: warning: conflicting types for 'Clk_Init'
main.c:43:4: note: previous implicit declaration of 'Clk_Init' was here
.compil
arm-none-eabi-gcc -I./ -c -fno-common -O0 -g -mcpu=cortex-m3 -mthumb stm32f10x_rcc.c
.compili
arm-none-eabi-gcc -I./ -c -fno-common -O0 -g -mcpu=cortex-m3 -mthumb stm32f10x_gpio.c
..linking
arm-none-eabi-ld -v -Tstm_h103_blink_rom.cmd -nostartfiles -o main.out main.o stm32f10x_rcc.o stm32f10x_gpio.o
GNU ld (Sourcery G++ Lite 2010.09-51) 2.20.51.20100809
...copying
arm-none-eabi-objcopy -Obinary main.out main.bin
arm-none-eabi-objdump -S main.out > main.list
tiago@tiago-laptop:~/stm32-example/projects/stm_h103$
So, I get 4 warnings, the only difference is that I used the most actuall release of CodeSourcery, have I done bad by choosing it?
48
General discussion / Re: Getting started in the ARM world
Wish me luck, I will now start the Arm gcc toolchain install/build!
49
General discussion / Re: Getting started in the ARM world
Yes, I also know that without Keil or similar software I will have to do a lot of work that I dont usually do to compile a simple program to an AVR, but I'm an electronic and telecommunication student in University, so I'm in the right place to learn, but I will not have much help, in my university they only work with pics and almost all are the 18F family, so talking about ARM's with my professors is a lost cause, but they are gurus using linux and making custom anything runing in linux, so the makefile question will be aided by then, the rest of the compiler chain will be a great challenge to me.
Even without actually creating the compiling tool-chain I have already read some code and its exactly like you say, full of pointers, I can get samples of the 256k flash chips or more, and I will only use the ARM's as an hobby tool, so I might just use what is done in the CMSIS libs, creating those from scratch is really to much for me :/
I only use the arduino as an easy to use breakout board for the atmega328 and the FTDI chip, the rest in done under the AvrStudio, and I dont really understand what you want to mean about optimizing, but the WinAvr uses gcc so it is a optimizing compiler.
In fact I think that the examples have another bad thing, they use 4 or 5 .c and .h files just to make a simply blinky demo, thats pretty irritating to read 10 lines of code in 10 different files.
50
General discussion / Re: Getting started in the ARM world
I still dont understand all about the make files, but thats a mather of time (I hope).
Mr.drwho9437 the peripheral lib is not in fact a big big problem for me, I started with Arduino, and 2 weeks later I was using AvrStudio and plain C, and no library bloat from the Arduino crew, it can be good to make something in short time, but all their libs are just a great mess and very slow and made from people that are used to programm in pc's with loads of ram and not a small micro-controller.
I will settle in the future with the ST chips, or if you really think that the TI ones are better, I will switch to TI, as I can get samples from both of then, but not from NXP.
Thanks for all the help provided here!
51
General discussion / Re: Getting started in the ARM world
Thanks again.
52
General discussion / Re: Getting started in the ARM world
I hope that in the future I can also help in the development of this great projects, I have some (very very) basic knowledge about makefiles, but only simple ones to use the gcc compiler and only to compile files in my computer, nothing about cross-compiling, but I can get some help for my teachers and some friends.
Last year I used an old 80186 dev-board made by my university and for the ease of use of the Assembler I made a little makefile, but it had only 4 lines, so it was very simple to create.
Thanks for your suggestions, mr. Ian and mr.Trev.
53
General discussion / Re: Missing DSP, Audio, Analog.
54
General discussion / Re: Getting started in the ARM world
After some more reading and searching I think I will settle for the CodeSourcery and Eclipse, and OpenOCD, following this great tutorial:
http://newwiki.openpilot.org/display/Do ... t+on+Linux
I have yet another question to you, the BusBlaster can be used as an JTAG programming tool, right?
And it will work with the OpenOCD at least to program Arm chips, and CPLD's as after reading about then here I got some curiosity about then!
EDIT: I have been reading the Wiki about the BusPirate and it says it can also act as an Jtag programmer, that would be awesome, the BusPirate looks like a great tool for general testing and hacking, having it act also as a Jtag programmer would be top notch, is this info correct?
55
General discussion / Re: Getting started in the ARM world
For the LPCXpresso there is the codered IDE that compiles up to 128Kb, thats more than enought for what I do, but I think I will chose the STM32 arm's because I can get free samples from then and if I understand correctly they have a serial bootloader in a ROM memory, so I dont need a JTAG programmer(at least not essencial, but I'm following the BusBlaster project and will get one when they are good to use
)So, I think that one of the most complete guides about setting up a toolchain for STM32 arms is the wiki of the OpenPilot project:
http://wiki.openpilot.org/Flight_Softwa ... _Toolchain
Its all very well explained, but I dont really understand if the makefiles are handmade or if the Eclipse IDE takes care of that, and this brings me to my other option, which is the Attolic True Studio, a friend of mine as already shown me how to edit a small config line and add the Yagarto files so the Attolic True Studio will give out the build-size and some other small things, that makes it almost perfect, but I like to know what is going on, so maybe I should try the tutorial from the OpenPilot guys, but then again, makefiles and not really knowing how to even make a simple blinky because I dont know what files I should include to have the CMSIS and the registers definitions up and running for each arm model is intriguing me.
What is your opinion sir?
56
General discussion / Getting started in the ARM world
Thanks in advance to this community, and yours great products like the bus pirate and the logic analyser.