Skip to main content
Topic: ST Link and VirtualBox. (Read 14318 times) previous topic - next topic

Re: ST Link and VirtualBox.

Reply #15
[quote author="arhi"][quote author="andersm"]
http://www.yagarto.de/
[/quote]

Dead

[quote author="andersm"]
https://launchpad.net/gcc-arm-embedded/+download
[/quote]

Just a compiler without any libraries nor tools (debugger, programmer..)

[quote author="andersm"]
https://sourceforge.net/projects/devkitpro/
[/quote]

never used it but from what I see it's using mingw - that's immediately turning on red lights

[quote author="andersm"]
http://www.mentor.com/embedded-software ... e-edition/ (can't use the hardfp abi, not otherwise limited)
[/quote]

closed, no debugger

[quote author="andersm"]
http://www.coocox.org/
[/quote]

- very limited support for mcu's (especially for stm32f4)
- uses their own libs (not that bad) but not simple to add native stm32 libraries in it

all in all - a simple to install and setup toolchain with ide, debugger and programmer that's free and unlimited .. I do not know about it[/quote]


Thanks for the back-up, researched coocox and yagarto, and paid for solutions with their free-but-no-but-yes options.
Ubuntu (or different flavour) seems the only solution to un-restricted development.

Re: ST Link and VirtualBox.

Reply #16
[quote author="arhi"][quote author="andersm"]
http://www.yagarto.de/
[/quote]
Dead[/quote]
Latest release is from December and has the current versions of all its components. That's over a year after the "goodbye" message was written.

Quote
[quote author="andersm"]
https://launchpad.net/gcc-arm-embedded/+download
Just a compiler without any libraries nor tools (debugger, programmer..)[/quote]
If you need libraries download them directly from ST. It's not too hard to find binaries for OpenOCD, and I bet a GDB binary is just as easy to find.

Quote
[quote author="andersm"]
https://sourceforge.net/projects/devkitpro/
never used it but from what I see it's using mingw - that's immediately turning on red lights[/quote]
Any GCC build for Windows will be using a POSIX layer. MinGW is the most native of them.

Quote
[quote author="andersm"]
http://www.mentor.com/embedded-software ... e-edition/ (can't use the hardfp abi, not otherwise limited)
closed, no debugger[/quote]
The GNU bits are open as required by the license. 90% of all the selfbuilt toolchains seem to use Mentor/CodeSourcery's source code packages.

[quote author="andersm"]
http://www.coocox.org/
[/quote]
- very limited support for mcu's (especially for stm32f4)
- uses their own libs (not that bad) but not simple to add native stm32 libraries in it[/quote]
You need a toolchain that supports Cortex-M4, not a specific chip (which CooCox definitely supports). If the chip vendor offers any support libraries of their own just download and add them. There's also no requirement that all components come in the same installer. If you're going to be switching OS just for that, keep good backups of your data files because you will be doing it a lot.

Re: ST Link and VirtualBox.

Reply #17
wrt yagarto, the guy said he will not work on it any more, him adding some upgrades from time to time ain't something I'd like to depend on .. especially when he said he will not do it

wrt coocox, have you tried pushing st libs into it .. I gave up after a week

rest of them .. donno .. have no good experience with them ... I use mentor myself (codesourcery) on linux .. that's closed but works

Re: ST Link and VirtualBox.

Reply #18
[quote author="arhi"]
wrt coocox, have you tried pushing st libs into it .. I gave up after a week [/quote]

So none of the ST standard libs work under coocox, I guess?  I thought they were written to be GCC compilable (which coocox uses).  I only used it to the "hello world" extent - and checking for hardware floating point support, which turned out to be a simple switch in the GUI

I seem to remember seeing something mentioned about getting the ST libs working in their forums, but I certainly don't remember the outcome - actually, searching back through their forum's you're on the post I was thinking of, ahri.  I'm actually a little confused as to why there's talk of "supporting" individual MCU families (all of which are Cortex M3 variants (F2, F4, etc) - I guess if the ST libs don't work and need to be ported for some reason that would make sense from the library "integration" point of view. . .

Re: ST Link and VirtualBox.

Reply #19
[quote author="bearmos"][quote author="arhi"]
wrt coocox, have you tried pushing st libs into it .. I gave up after a week [/quote]

So none of the ST standard libs work under coocox, I guess?  I thought they were written to be GCC compilable (which coocox uses).  I only used it to the "hello world" extent - and checking for hardware floating point support, which turned out to be a simple switch in the GUI

I seem to remember seeing something mentioned about getting the ST libs working in their forums, but I certainly don't remember the outcome - actually, searching back through their forum's you're on the post I was thinking of, ahri.  I'm actually a little confused as to why there's talk of "supporting" individual MCU families (all of which are Cortex M3 variants (F2, F4, etc) - I guess if the ST libs don't work and need to be ported for some reason that would make sense from the library "integration" point of view. . .[/quote]

I was actually trying to push ST libs inside coocox to be visible like coocox libraries .. I guess if you just put a ST lib dir inside your project that would work immediately without much hassle.. but that I didn't even try ('cause I was not too interested in setting up a windoze ide 'cause I run linux host myself :D ) ...

The worse part is - on linux I use codesourcery + makefile + vi to do arm dev and I'm not too happy with it but can't find time to setup a proper dev envinronment

Re: ST Link and VirtualBox.

Reply #20
[quote author="arhi"]I was actually trying to push ST libs inside coocox to be visible like coocox libraries .. I guess if you just put a ST lib dir inside your project that would work immediately without much hassle..[/quote]
that's encouraging at least - like i said I have virtually no experience with coocox outside of some boiler plate type code - I normally use Keil (free up to 32k - expensive after that).

From what I saw with CooCox I like quite a bit, native support for the ST Link on the discovery boards was a bonus.

[quote author="arhi"]
The worse part is - on linux I use codesourcery + makefile + vi to do arm dev and I'm not too happy with it but can't find time to setup a proper dev envinronment[/quote]
I did on-target development for a few embedded linux boxes with a similar setup (gcc+make+vi) and it worked OK - that was largely before IDE's had code completion though - I find that it tends to really speed up coding, personally - it was one of the things I liked about CooCox.


Re: ST Link and VirtualBox.

Reply #22
Greets, everyone.

I had the same problem as the OP in this thread, but I was able to solve it using this thread on the virtualbox forum. 

I just managed to get virtual development for the STM32F4 working.  I'm running Ubuntu in a virtual machine on my Win7 host.

Unfortunately, I'm still a new user, so I can't post the URLs of the links I used, but I'll come back in 24 hours when I'm validated and share them.  Here's the post with the URLs removed in the meantime:

Basically, you have to also download the "Extension Pack" from the virtual box website.  And you have to enable USB 2.0 EHCI in the VM Settings.  And you have to create a filter for the ST-Link.  It's a bit tricky and it took me a few tries, but it's well worth it.

I have been keeping track of my notes to devise an easily-recreated virtual development environment for the STM32F4 .
 over on my website.  It's still evolving, so if anyone has any suggestions, they would be useful.

Happy hacking on the STM32F4, it's one of my favorite chips to come along in a while :)

 

Re: ST Link and VirtualBox.

Reply #23
[quote author="diydsp"]
Basically, you have to also download the "Extension Pack" from the virtual box website.  And you have to enable USB 2.0 EHCI in the VM Settings.  And you have to create a filter for the ST-Link.)[/quote]

If you need USB support, yes, you do need the extension pack.  I always install this w/ VirtualBox so I thought you did as well...VBox prompts you to install if after it's installed.
I'm glad it works well...it doesn't work for all USB devices, but printers and serial ports on USB work well..