Closed jcady closed 9 years ago
gcc4mbed samples/ folder has a BLEHearRate sample already. Can you start with that first?
Well, would you look at that. I completely missed that sample. That looks like it will be of some help!
It looks like the libs are about a month or so old, though. So it's still a little worth it to me to figure out how to drop in the newest ones myself. Do you have any idea what might be going on?
Maybe you need to match the mbed SDK in external with the BLE / nRF51822 libs? Are you able to build the existing sample for your new NRF51-Dongle?
Hmmmm, that is a good idea. I'll give that a shot.
The sample built no problem.
Looks like the problem persists, even with the latest mbed.
If you pull down the latest mbed SDK into the external directory of gcc4mbed, make sure that you do a "make clean-all" before attempting the first build. That will make sure that any old files get cleaned out.
I didn't do that, but the build files for mbed rely in the mbed directory itself, right? I did delete the entire mbed directory and replace it with the one I pulled down, so that shouldn't be the issue.
Ok. I guess I don't know what is causing the problem then. It sounds like you have done what I would have done.
I can look at it when I update gcc4mbed to a newer version of the mbed SDK later in the year and run the accompanying test pass.
Sounds good to me, thanks for the support. For now, the sample fulfills my needs, so I'm satisfied!
I was able to reproduce this problem when I upgraded to the latest mbed sources and I now have a fix in the working branch with commit 61ae5063846cc8412890e051f0a7dd59967ce8ff. This should be merged into the master branch soon. Thanks for reporting.
Fix now merged into master.
My target is the NRF51-Dongle (I know it isn't supported, but I added support for it, it's pretty close to the NRF51822).
I am able to compile just fine using gcc4mbed in Eclipse with a simple project, like HelloWorld. My project is a Bluetooth LE project, so I need to include the BLE_API and NRF51822 libraries that MBED makes. The issue is that whenever I put those directories into my build directory (without even calling) and attempt to compile, the build fails with a slew of errors. I've attached the full output of the errors below.
As a test, I exported the BLE_HeartRate test program, which includes those two libraries, for the NRF51-Dongle target to GCC. I made a makefile project with the MBED generated makefile in Eclipse. I set the path for arm-none-eabi and it compiled successfully, libraries in all.
It's nice that MBED can export straight to GCC and have everything work out of the box. But I really don't want to have to copy everything to the online IDE and re-export every time I want to add a file, just so it can generate a proper makefile. It also doesn't seem to support incremental builds (it builds everything every time, unlike gcc4mbed), which is a bit of a pain. Are those the main advantages of using gcc4mbed over exporting to gcc from the MBED online compiler?
Do you know how I can include the BLE_API and NRF51822 libraries and have them build properly with gcc4mbed?
And here is the makefile that MBED generates for the BLE_HeartRate example, in case it helps diagnose what's going on: