Slackware- Help linking libraries STM32F4
 

Hi Guys!

I having problem getting working a tool chain for STM32F4 for whom dont know this is an ARM processor.

I did have to spend some time getting some packed in. I had to install some package from 13.xxsomething for my 14 current version using. (I will add details later to review this installation due to is not what I am asking now)

I know what is wrong but I dont know how to fix it.

The problem is that when I try to compile it does not see the files:

when I do make I get:

What I have done:
I looked for arm-none-eabi-gcc I know where is:
it storage on roo/sat/bin

if I called in a terminal I get:

I have created a link to bin folder and added to the project but it can not see it.

I also have changed the makefile by modifying:

But it does not seen to work also.

I know in Ubuntu I will do it by exporting the path how do I do it in Slackware? Can it be done without setting the environmental path?

in a terminal, and in top source, try (presuming bash)

export PATH=/root/sat/bin:$PATH;
export CC=/root/sat/bin/arm-none-eabi-gcc
make

If you use another shell, adjust accordingly, but you get the idea.

Thanks business_kid for your input. (I have some more question about it, but it does work it link this way)

I want to write here to see if you could help with something else, I am trying to compile also Openocd as this link:
I have got openocd from here:

I cloned on a folder and then run in a terminal
./bootstrap
then
./configure --enable-ft2232_libftdi --enable-usbprog
then make
but I am getting this error:

Do you know what is it wrong?

Hi! I think I fix it but I am not sure because its not working

I am getting the following error:


Its like cannot open the device?

I create my own cfg file

And I am using:

target script:

But I think there is something wrong because its not a M3 cortex if not a M4

Peter, I'm up to my neck in my own project. Yours looks interesting, but . . .

BTW, Fedora do an Electronic Spin. I have it, and it has all sorts of arm goodies compiled and sitting there ready to be used. FC-18 is a right royal bitch to install, but the Electronic spin is good.Comment 33 on this shows how I finally got going. I ended up booting on a slackware-huge kernel to remake the initrd so the thing would boot. I wish you better luck.

Hi1 Business_kid thank for looking anyway! ;-).

For the rest which have some knowledge of what I am doing feel free to comment :-/ .

I though I give an Update here, last night after getting stuck on no being able to talk to the board through Openocd I use a VM and lest than 5 minutes I can talk to the board and programe it through the stlink Utility software, I have to say that I did also try with 11.xxsomething ubuntu machine and that is one of the thing I have to say bad about slackware it should have a faster way to get the package in. I just type openocd in, and done, use Synaptic to look for depended folder and and files and in lest than 5 minutes I was trying to connect to the board at to the point where I did in Slackware which I spent hours to get to the same point.

After all that jut to say the hardware is working so for sure is a system/driver problem. Now I have something working through the VM I am going to get back and try to play with the files I could not install the latest to see if that fix this problem..

Feel free to comment ...

Sorry if I asked you about this, the reason this add the path in the terminal, but what about if I want this to be able from any terminal I open. If there a file which it can be added and always be available from any terminal? Thanks

UPDATE:
I've manage to connect through the USB cable to ARM board. I had to review openocd option because that interface mention before (hla) was not up. and I had to change some cfg files path too.

If I do:

I get:

But still not there .... :-(

When I try to send something now

I get:

If should do something like:
But it just hang there! :-( What is it wrong?

Go back to building gdb. At the configure stage there is --host(=the box it's going to be running on) --target(= the box it's going to be debugging, I imagine)

You need to configure it --host=arm-none-eabi --target=arm-none-eabi along with your other options
and rewinstall it completely, before you can debug on the arm.

I dont think I even configure gdb I looked there is installed gdb-7.5-i486-1 but that was there I didnt installed.

Regarding arm_tool_chain. I looked and the only thing I did was = ./summon-arm-toolchain from
https://github.com/esden/summon-arm-toolchain

I looked and there is not option for host. But the Arm is connected to the PC by USB cable so the hist should not be the PC?

Do you actually mean openocd? I cannot see anything about on the tool chain for arm-none-eabi

But in openocd said something about the host but I try to reconfig with:

and if fails for compiling issues, if I leave out:
CC=/root/sat/bin/arm-none-eabi-gcc CPP=/root/sat/bin/arm-none-eabi-gcc

its give error earlier.

without CC and CPP

and with CC and CCP trying to force the compiler:

I am not sure know how to force all the flags manually. :-(

I probably do mean opencd.
That bit is wrong. If you're running on arm --build = --host. The --build=i686-pc-linux-gnu builds a debugger to run on x86 to debug arm

I did play with different configuration to the ./config file, but I cannot get it running. The problem is that it cannot see the compiler which is on /root/sat/bin/arm-none-eabi-gcc if I leave out that option it does:

If I added it fail much earlier:

you can do

export CC=/path/to/compiler

and check the Makefile makes use of $CC.

Sorry I am late getting back to this!

I have tried adding into the terminal

That is where its "arm-none-eabi-gcc"

but the terminal response is the same as before:

Stop in the compiling checks I looks a makefile was before adding the path and looking a CC I see:

But this is the makefile, Should we be looking at config files?