Maybe it would be good to take a couple of steps back. Does your board look like this?
https://developer.mbed.org/platforms/ST-Nucleo-F401RE/If so, it is very likely mbed compatible. When you connect it to your laptop do you see a new disk drive? Does it have the .htm file? You need that! You open that file with your browser to get registered at mbed.org. I have forgotten the process.
Just give up on the installed toolchains and consider revisiting the issue when you have more experience. They don't really bring all that much to the dance anyway.
The online mbed compiler will work very well and having the board attached to your computer will allow you to just place the automatically downloaded .bin file directly onto the board using ordinary file manager operations. Drag and drop works... It actually works better with Win 7 than Win 10 but it doesn't matter.
My process: I have an open File Explorer window looking at my Downloads directory. I 'cut' the new file, move over to a second File Explorer window looking at my mbed board. I delete the existing .bin (not truly necessary) and paste in the new version. Hit the reset button and done.
On Windows 7 I seem to recall the download targeting the mbed directory directly.
So, with this setup what do you lose? Well, you lose everything you have installed, you don't need any of it. You gain a built-in serial port so printf() works (but you'll have to install a serial port driver) and you gain access to a TON of working code. Yesterday I was fooling around with the new Ethernet stack. A few lines of code and I'm making a connection.
If you don't have an mbed compatible board, get one. You will save yourself days and days of struggling against a tide.
Here is a link to the serial port driver:
https://developer.mbed.org/handbook/Windows-serial-configurationI followed the instructions completely and it wouldn't install. So, I unplugged the board and tried again. Then I plugged in the board and tried a third or fourth time and it installed. Keep kicking it until it works! It will work eventually and, once it does, life with printf() is a lot nicer.
You can chase toolchains down a rathole. Who cares? Most are based on GCC anyway whether they say so or not. They wrap a fancy GUI around it and call it theirs (Eclipse, etc). Truth be known, it is probably faster to just use the command line with Linux. You can build up a Makefile that handles everything. But that's a project that will take another week. I have written a lot of code using GEDIT (a minimal windowing editor for Linux) and a Makefile. So what did I do when I wanted to try out a little networking on my mbed? I just used the online toolchain. It's faster getting started.
When you go to mbed.org, there's a button at the upper right labeled "mbed Classic Developer Site" - that's where you want to go. Of the several buttons on this page, I spend most of my time using the Compiler - blue button in upper right. Once you register (whatever that means these days), entering the Compiler will bring up an IDE and you're almost ready to go. You will have registered your board and now you need to select it in the upper right corner of the IDE.
That's it! Sign up, open up the compiler, pick your board and you're good to go.
Yes, you lose debugging. Mostly it's a PITA anyway. Stack traces sound a lot cooler than they are. Core dumps are worthless - I learned that on the IBM 1130 back in '70. What can you possibly do with 8K words of dump. Yes, that's all the memory we had but it still took up pages and was nigh on worthless!
Hint: Don't put bugs in your program and you won't have to root them out.
Home
Help
Search
Login
Register
