I am really confused with the contiki-NG platform naming. I am new to contiki-NG so after reading their docummentation i bought the CC2650 LaunchPad.
I decided to build the BLE-IPV6 examples in examples/platform-specific/cc26x0-cc13x0/ble-ipv6 but it doesn't work because it want board -> launchpad/cc2650 and platform -> cc26x0-cc13x0 but at the TI homepage the CC2650 LaunchPad is a simplelink.
The funny thing is if i build the project with
make TARGET=cc26x0-cc13x0 BOARD=launchpad/cc2650
it compiles but doesn't run on the device.
What is the difference between the platform cc26x0-cc13x0 and simplelink ?
Related
Is there a way to compile with MingW with CodeBlocks in Windows so they can be used in Ubuntu or Centos distros?
I've tried compiling with GNU GCC option then got the output file with .o extensions under obj/Release/ folder.
When I run I get this error under my Vagrant Ubuntu machine:
-bash: ./main.o: cannot execute binary file
How can I compile it so it runs on my Linux machines?
The technical term for what you're trying to accomplish is cross-compilation. For that, you need to build a specific cross-compiler using GCC sources. If you still want to keep MinGW, there is a page explaining the steps needed to create a ARM cross-compiler : http://www.mingw.org/wiki/HostedCrossCompilerHOWTO. (you'll have to modify the target)
List of targets supported by GCC :
armv5te-android-gcc armv5te-linux-rvct armv5te-linux-gcc
armv5te-none-rvct
armv6-darwin-gcc armv6-linux-rvct armv6-linux-gcc
armv6-none-rvct
armv7-android-gcc armv7-darwin-gcc armv7-linux-rvct
armv7-linux-gcc armv7-none-rvct
mips32-linux-gcc
ppc32-darwin8-gcc ppc32-darwin9-gcc ppc32-linux-gcc
ppc64-darwin8-gcc ppc64-darwin9-gcc ppc64-linux-gcc
sparc-solaris-gcc
x86-android-gcc x86-darwin8-gcc x86-darwin8-icc
x86-darwin9-gcc x86-darwin9-icc x86-darwin10-gcc
x86-darwin11-gcc x86-darwin12-gcc x86-linux-gcc
x86-linux-icc x86-os2-gcc x86-solaris-gcc
x86-win32-gcc x86-win32-vs7 x86-win32-vs8
x86-win32-vs9
x86_64-darwin9-gcc x86_64-darwin10-gcc x86_64-darwin11-gcc
x86_64-darwin12-gcc x86_64-linux-gcc x86_64-linux-icc
x86_64-solaris-gcc x86_64-win64-gcc x86_64-win64-vs8
x86_64-win64-vs9
universal-darwin8-gcc universal-darwin9-gcc universal-darwin10-gcc
universal-darwin11-gcc universal-darwin12-gcc
generic-gnu
There is only one big caveat : since Windows is not POSIX compliant, I don't think you can use signals or pthreads.
Finally, brace yourself because it's a tedious task to build a cx-compiler (lots of obscure bugs). That's why profesionnal devs pays $$$ for "plug'n'play" solutions.
EDIT : this MXE project can be useful to you
I'm currently implementing a FreeRTOS-based program on the Arduino platform.
I would like to use the Arduino MEGA 2560 Rev3 (which is based on an ATmega2560) for this project, but I couldn't find a working port.c file.
Could anyone please share a working port.c ?
I'm using Eclipse IDE, WinAVR, AVR Plugin, Arduino Lib, FreeRTOS 7.6.0 (I will eventually switch to v8.0.0) and C++ as the main programming language.
Thanks.
EDIT:
I've came across avrfreertos which generates a FreeRTOS static library for the ATmega2560, but when I link my project against it, I get the following error:
c:/winavr-20100110/bin/../lib/gcc/avr/4.3.3/../../../../avr/bin/ld.exe: section .task [00003282 -> 0000328f] overlaps section .data [00003282 -> 0000339d]
make: *** [MY_PROJECT_NAME.elf] Error 1
EDIT:
I found a fix for the linking problem
http://sourceforge.net/p/avrfreertos/discussion/general/thread/f0552383/
http://feilipu.me/2011/09/22/freertos-and-libraries-for-avr-atmega/comment-page-1/#comment-14
Your issue is resolved by the change to avr6.x as you found. There is a .task attribute included in the portmacro.h file, which is needed to keep the freeRTOS task you define in the lower part of flash.
Good news. There are some updates in the latest avrbinutils and avrlibc 1.8.0 that include a .lowtext attribute, which has similar functionality to the .task attribute I added to the avr6.x file.
In the port for freeRTOS800 I changed the attribute defined in portmacro.h to point to .lowtext. This means there is no need to change the avr6.x file any more.
Either, change to use the freeRTOS800 port AVRfreeRTOS or just make the change in portmacro.h yourself.
For further reference, I've made an Arduino Library that can be included in Arduino to get experience with freeRTOS on any AVR device.
I am trying to get started with EDSDK to control my Canon 500D. I'm new to cpp, and windows XP apps and I'm using visual studio. After a great deal of blind trial and error I have finally managed to get the app to compile the basic sample code from the documentation. To do this I have the EDSDK.h, EDSDKTypes.h and EDSDKErrors.h headers in the right places and the EDSDK.dll and EDSDK.lib in the same folder as the code. It seems to be picking these up. I have got the 500D to be recognised by the PC so I believe the USB drivers are there.
The code is just trying to pick up the camera:
EdsError err=EDS_ERR_OK;
EdsCameraListRef cameraList=NULL;
err = EdsGetCameraList(&cameraList);
if(err == EDS_ERR_OK)
{...}
However, when I run this console app the error is picked up as 10 - which suggests, according to the document, that there is a missing subcomponent. This happens both if the camera is connected or not, so I'm thinking this is something missing from the compile. But I am getting nowhere with the documentation.
I have installed the edsdk 2.4 Windows version from a download not the official route, so this may be an issue.
Can anyone help? Specifically how can I find out what the missing subcomponent might be so I might include it. Is this a subcmponent of the build like a header file or something like a driver?
I know, old question but still it might help someone with the same problem.
From the documentation:
All DLLs are required in order to execute an EDSDK client application.
All of the modules in the DLL folder must be copied into the same folder where the EDSDK client application is in.
This means you'll have to have all DLLs beside your *.exe. Namely these DLLs:
DPPDLL.dll
DPPLibCom.dll
DPPRSC.dll
EDSDK.dll
EdsImage.dll
Mlib.dll
Ucs32P.dll
I just upgraded to Mac OSX 10.7 Lion. First of all, I hate the new spaces, I dislike not being able to access any directories deeper than my user directory, but lets get to the question.
I develop Audio Unit Plugins. I have a few whose code is compiling and working perfectly (they're even released for sale) in XCode 4.0.
But after upgrading to Lion and XCode 4.1, there are now two major compiling failures in the main audio unit .cpp file (mine is named TestAU.cpp) where the Process method resides. Below is the code that fails.
#include "TestAU.h"
COMPONENT_ENTRY(TestAU) // FAIL c++ requires a type specifier for all declarations.
TestAU::TestAU(AudioUnit component) : AUEffectBase(component) // FAIL Expected ';' after top level declarator.
{
CreateElements();
Globals()->UseIndexedParameters(kNumberOfParameters);
SetParameter(kParam_One, kDefaultValue_ParamOne );
#if AU_DEBUG_DISPATCHER
mDebugDispatcher = new AUDebugDispatcher (this);
#endif
}
I'm having trouble solving this failure. Any help would be great. Thanks.
Search in the Xcode documentation for Technical Note TN2276 for instructions on updating an existing audio unit for Lion.
You have to replace
COMPONENT_ENTRY(TestAU)
with
AUDIOCOMPONENT_ENTRY(TestAU, Filter)
But there is a little more so read the document.
Edit:
BTW regarding your comment about not being able to access all directories you can find many locations in the Go menu of finder.
Here's what i've done:
i choose Test -> create new test -> wizard
Then it asked me to enter a proj name. i did.
then it told me to select a source proj to test, i chose my working proj... but...
a warning dialog popped up saying : "Unknown virtual address 0" and refuse to continue.
i tried rebuilding my source proj many times... no luck
can anyone help me out?
Here you will found full description of VS tests usage in c++. Citate - If your production code is written in Visual C++, you can generate unit tests only if your product uses the /clr:safe compiler option.