I am using DS5 evaluation version. I created a simple hello world C project in eclipse for DS5. Project type chosen while creating the project is Bare Metal executable->Empty project. Tool chains ARM Compiler 5 was selected. I complied the code and generated the axf file. When i right click on the axf file and select debug as->debug configurations->Connection tab->ARM FVP VE_Cortex_A7x1->Bare Metal Debug->Debug Cortex-A7 and click on debug I am facing the error as in the image.
Please let me know how to resolve the same.
The reason you're seeing that error is that the evaluation version of DS-5 Professional Edition gives you access to the Cortex-A8 and Cortex-A9 FVPs, not the Cortex-A7 one.
Extra FVPs need to be purchased separately from ARM.
Related
New laptop with GTX 1060. Just installed Ubuntu 16.04 and Cuda Toolkit 8.0.
I start with creating a new project:
Cuda C/C++ Project-> CUDA Runtime Projekt -> give name etc.
Then we get to the Generate PTX/GPU Code Setting. If i choose standard 3.5 and create project and run the generated example everything works as expected.
But if i choose only 6.0 on PTX and GPU code generation the example project will still run, but i will not have any cuda syntax highlights or auto completes in the file. Adding certain header files like cuda_runtime etc does not fix it.
I thought this setting is somewhat like "set compute capability to X.X" to get all the new cuda features with the higher version (like shfl, dynamic parallelism and so on). That's why i thought it should work like everything else if i select 6.0 instead of 3.5.
Am i missing something or am i just wrong about the expected behaviour?
I install these Plug-in in eclipse to build the stm32 develop environment:
GNU ARM Eclipse Plug-in
CDT GNU Cross Development Tools
Sourcery CodeBench Lite 2014.05-28 for ARM EABI
J-Link ARM V4.15e
I am trying to run a USART1 program in eclipse and check the output of the USART1,but when I debug this code,I got the wrong output message. The message I send is "DECA0130",but what I got is "???????"，this is obviously a garbled.
At first, I think the problem is I didn't write a write code .I checked my project again.But didn't find any error.
Then I build a new project in Keil Mdk use the same code.This time I got the right message from USATR1.I receive the string "DECA0130".
It's very strange. Because I'm not familiar with eclipse environment,I used Keil do my coding before.But the recent projects have forced me to write code .I think maybe somewhere I forgot to configure.
Because it's a new user，I don't know how to insert the program。If there is any need, please tell me.I will try my best to let you see
Thanks in advance
Seems to be a clock issue. Check the clock settings. The eclipse ARM plugin generates some configs for that. Check the function SetSysClock in the system/src/cmsis/system_stm32*.c file. I think the Keil MDK does this too, but with differnt config.
Edit: The function SetSysClock i mentioned is wrong. The clock config is done in the configure_system_clock function (file _initialize_hardware.c).
With Vuforia's ImageTargets sample application, I tried using OpenGL ES 1.1 by setting USE_OPENGL_ES_1_1 to true in jni/Android.mk and uncommenting and changing the corresponding line in AndroidManifest.xml (). After converting the project so that it has a C++ perspective and associating ndk-build and the proper include directories, I could successfully run the application on my Android device.
However, the problem is that once I open up jni/ImageTargets.cpp, I get several errors from Eclipse, all from places where OpenGL ES 2.0 code would execute, the first one being:
Description Resource Path Location Type Symbol 'vertexHandle' could
not be resolved ImageTargets.cpp /ImageTargets/jni line 402 Semantic
Error
Sure enough, vertexHandle is defined at the top of the ImageTargets.cpp, inside the "#ifdef USE_OPENGL_ES_2_0" block. Because USE_OPENGL_ES_2_0 is not defined (per Android.mk), the code should be able to compile successfully, and sure enough, ndk-build does not report any problems. So it seems that only Eclipse reports the problems and when I run the project, Eclipse says, "Your project contains error(s), please fix them before running your application." And thus, I cannot run my application anymore. In a sense, it's kind of strange that this never occurred until I opened ImageTargets.cpp and Eclipse "discovered" the errors.
The best work-around I've found so far is to just delete or comment out those lines (that should not be causing problems because USE_OPENGL_ES_2_0 is not supposed to be defined)... Is there a better way to deal with this problem? Did I miss a setting in Eclipse that should solve this?
I've found a solution: go to the project properties -> C/C++ Build -> Discovery Options -> Check "Automate discovery of paths and symbols"
Hello Everybody ,
I am using following tools & SDK for Blackberry Native development in Windows
10 Native SDK 10.0.9.1673
BlackBerry10Simulator-Installer-BB10_0_10
Virtual Machine VMware-player-4.0.3-703057
Let me know, following configuration is correct for BB Cascaded Development.
Because I am getting the following problems
"ldd:FATAL: Unresolved symbol "_ZN2bb8cascades11QmlDocumentC1Ev" called from Executable" error when I am trying to run binaries on
simulator.
If I import a BB Cascaded sample project in SDk then "BAR PACKAGES" Folder show by default , if I create my own project then
"BAR PACKAGES" then it will not show .
Actually it's not a answer I don't have any choice for image post that's why I follow this way ,here I am showing you the Snapshot of my QNX-IDE , I have imported GoodCitizen & Falling Blocks from sample projects . Good-Citizen Project is working fine compile as well as run on Virtual Machine. But in the Falling Blocks Project no BAR Packages create why this is happening , can any one explain me the scenario.
Have you declared your QML Document in either your main.cpp or app.cpp?
QmlDocument *qml = QmlDocument::create("asset:///main.qml").parent(this);
I think you need to update api level
help-->updade api levels & install new software
Keep on update your tools to avoid errors
I've got a Android AppEngine Connected Project I'm trying to build using GWT2.4 RequestFactory and Objectify on my Eclipse IDE.
Apparently I need to run the RequestFactory Validation Tool because I'm using ServiceName and ProxyForName annotations (these are required especially when working on the Android client side). My problem is the Eclipse can't validate it and the solution provided at http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation#IDE_configuration is enough to make me rip my eyes out.
Since I'm working on a Windows machine, the shell script provided is not very useful. Trying to run Validation Tool from a cmd propt returns the error message:"This tool must be run with a JDK, not a JRE"
Can someone explain how this Tool is supposed to be run? Is there a way to use it as an External Tool in eclipse?
Normally if you follow carefully the instructions in the link you show, and run the GWT Development Mode from Eclipse, the Validation should be done automatically at the time you access the development URL with your browser.
For the record, I've actually had some problems with it, but launching the application several times maked it work.
Well, I ran into the same problem as well. When I tried annotation processing (under Java Compiler-> Annotation processing )was being disabled. So RequestFactoryDeobfuscatorBuilder was not being generated. Try enabling that and rebuilding your project.
I've just recovered from two days of hunting this bug down in a project that used to run validation properly but stopped.
In my case I had a new-ish generic BaseRequestContext and a specific sub-interface that extended it. My parent interface declared a method that didn't match the Locator's exactly (e.g. getThing(T) vs get(T)) and this wasn't reported as an error but did stop the validation tool from completing.
Apt is also removed in Java 8 : http://openjdk.java.net/jeps/117 . So beware.
Switching back to Java 7 will fix the issue if you are using Java 8.
I understood why the error happens sometimes in a project: the compiler was complaining it cannot find the directory .apt . But when I tried to create it manually it was not possible (under windows). I think the validation tool mutes the exception of not being able to create the directory: try renaming .apt in your validation tool calls (do a text search in your project)