10 years, 7 months ago.

Crossworks compiler and MBED

Hello:

Starting from the description given by Timothy Teh I installed and did get the MBED up and running with an offline compiler.

This is really good news as I am now able to single step the code and this adds some amazing debugging ability instead of the blinky-led or printf debugging techniques that I am sure that everyone is accustomed to.

My problem is two fold. One, I am in a really remote location (cruising around on my boat with my family) and there is limited to no internet access.

Second, I am not a really good C/C++ programmer so I need a lot of assistance to figure things out. I am actually surprised on how much we depend on the internet from a day to day perspective.

What I have determined is that when including the standard mbed library pretty much the only thing that works is DigitalIN and DigitalOut. All other functions have compilation errors that are way above my pay grade.

This means no serial, i2c, spi, analogin, etc...etc...etc. There is not a lot that I can do with just DigitalIn and DigitalOut.

Errors include such things as the following: Linking Testbed.elf "undefined reference to 'vtable for cxxabiv1::si_class_type_info'

Other errors that are seen when compiling serial.h (and others) are include not having the following files that I cannot seem to locate: Cannot locate these items:

1. include <sys/fcntl.h>
2. include <sys/types.h>
3. include <sys/syslimits.h>

Has anyone been able to solve these problems and can offer assistance? I would really like to have the opportunity of making some really cool telemetry sensors on my boat but need the ability to code offline.

Is there a way to include all of the standard mbed libraries, that work, in Crossworks?

Thanks again for your time with this. I should have internet for the next few days so hopefully I can continue to move forward. I have a lot of untested hardware just sitting around now.

Cheers,

Steve