demoDataLogger
응답
17. 9. 14 오전 8:15

Hello,

 

I'm currently trying to get the demoDataLogger project to work. When building the project,some errors occur:

  1. make\mingw32-make.exe[1]: *** [C:/[...]/DDL_demoDataLogger/debug/objects/Main.o] Error 1
  2. mingw32-make: *** [debug] Error 2
  3. application.mk:80: recipe for target 'C:/[...]/DDL_demoDataLogger/debug/objects/Main.o' failed
  4. Makefile:39: recipe for target 'debug' failed

The makefile:39 error appeared already in other projects, but I could solve it by cleaning the project. This doesn't work in this project.

Do you have any solutions to get the demoDataLogger to work, as I suspect these errors occur more often and/or do you have any general solutions to solve to makefile error?

 

regards Michael

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 14 오전 9:33 as a reply to Michael Löhe.

Hello everybody.

Same happened to me. Most of the librarys could not be found. After merging the Workbench 2x and 3x libraries into the same SDK folder the errors reduced quiet a bit, but not to zero...

For me, it is very hard to understand why a new workbench was released, without working samples...

Best regards,

Wolfgang.

+1 (1 투표)
RE: demoDataLogger
응답
17. 9. 14 오후 12:29 as a reply to Wolfgang Huell.
Hello Guys, just as a sanity check, what is the host OS of your workbench?

I actually installed the new 3.X XDK WB, and to avoid conflicting the libs I removed the previous installation, this is because the WB does not generate makefiles automatically, but use a custom made based on XDK toolchain which is majority static. So with the update of to the newer libs it the 2.x stuff will not be backward compatible with 3.x

Using the clean in some cases will solve the issue on building projects, I additionally delete the debug generated folder after a clean command, this will force the build system to start from scratch and remove any outdated/faulty built artifact.

Please let me know if this info was useful.

Best

Felipe
0 (0 투표)
RE: demoDataLogger
응답
17. 9. 14 오후 7:04 as a reply to Felipe Neves.

Hello Michael and Wolfgang,

Makefile errors appear because they are triggered by other errors in your projects, for example, syntax errors. In your case Michael, the Main.o file has an error. I assume this could be caused by an old version of the Data Logger demo. A such, could you please tell me which version of the Data Logger demo you are currently using? Did you download the latest version with the suffix v3? Additionally, how did you import it into your XDK-Workbench? Did you follow the instructions about importing a project from the Workbench Installation guide?

If any of your other projects are affected by the make file error at line 39 too, I would like to know on which workbench version you developed them.

Wolfgang,
your include issue within the Data Logger demo indicates that you are using an older version of it instead of the latest version v3. Otherwise, there could be an issue with old deprecated files of the XDK-Workbench 2.0.1 as Felipe already mentioned. Unfortunately, I cannot confirm that, because I made only an update of the XDK-Workbench and not a clean installation and it is working without issues.

Depending on what caused the include issue, I recommend to check, if you are using the latest Data Logger demo. If you are not using the latest one, please download the latest version three of the Data Logger demo.

Regarding your other non-working XDK-Workbench examples from the Welcome Screen, (I guess you mean them?) I recommend making a backup of them and then deleting the old ones from your workspace and importing new ones from the Welcome Screen of the XDK-Workbench. This is necessary because with XDK-Workbench 3.0.1 was a major change in the startup of the XDK, regarding the appInitSystem() function and the implementation in main.c. As such, XDK projects of the XDK-Workbench version 2.0.1 won’t work without migration in the latest version 3.0.1.

Please note that, if you click on an example project in the XDK-Welcome screen to import it, it will only be imported if there is no project with the same name in your workspace. If there is already an old example in your workspace it won’t work on the new workbench, even if you try to import it again, because the old one will be used instead. As Felipe mentioned, this is caused by the backward incompatibility of the examples associated with the major WB 3.0 changes.

Please let me know if that was helpful and do not hesitate to ask if you have further questions.

Kind regards,
Franjo

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 15 오전 6:10 as a reply to Franjo Stjepandic.

Hello,

 

after reinstalling the workbench v. 3.0.1 my problem seems to be solved.

But to answer your questions:

 

  1. I run the workbench on a Win10 64-bit system.
  2. I used the latest Version of the demoDataLogger
  3. I imported it in the way discribed in your guides

thanks for the support

 

regards Michael

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 15 오전 10:01 as a reply to Michael Löhe.

Hello.

After uninstalling all versions and doing a clean installation of Workbench 3.0.1 Eclipse is not opening anymore. The XDK-Workbench.exe shows up as a process in task manager with 0 CPU and 265.228K Memory usage, but the visualization is missing. Same after reboot...

I installed the 64bit version on a Windows 7 Enterprise Service Pack 1 machine...

Best regards,

Wolfgang.

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 15 오전 11:18 as a reply to Wolfgang Huell.

Hi.

After reinstalling the whole workbench again, the Editor came back, but the XDK window is still not working. See attached picture...

Best regards,

Wolfgang.

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 15 오후 2:16 as a reply to Wolfgang Huell.

Hello Michael and Wolfgang,

I am glad to hear that reinstalling the XDK-Workbench solved your issue Michael and I thank you for answering my questions.

Regarding your issue Wolfgang, I assume it is caused by leftovers of your previous XDK-Workbench installation since Windows does not remove all leftovers during the uninstallation process such as settings and profiles.

To solve this, I recommend installing the freeware tool Iobit Uninstaller. It gives you the advantage to uninstall programs on your OS and afterward check for leftovers and delete them as well.

Then you should be able to reinstall the XDK-Workbench without any issues.

Please feel free to ask if you have further questions.

Kind regards,
Franjo

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 20 오전 8:59 as a reply to Franjo Stjepandic.

Hi Franjo.

Tried everything. Still not working. Always same error message...

Remark: The IOBIT uninstaller webpage is blocked by bosch...

Best regards,

Wolfgang.

0 (0 투표)
RE: demoDataLogger
응답
17. 9. 20 오후 2:20 as a reply to Wolfgang Huell.

Hello Wolfgang,

to find a solution, I would like to know more about your OS and Notebook/Pc. Is that a company Notebook/Pc with restricted admin rights? Or are you using a personal one? Does the XDK-Workbench version 2.0.1 show the same behaviour as the XDK-Workbench version 3.0.1 does? The more information I have, the more likely I may be able to reproduce this issue, which would help in finding a solution. As such, any piece of information I have not asked for, but which you think can be useful, is welcomed.

Regarding the IOBit uninstaller, you are not limited to this tool. If possible, you could look for a similar tool that is not blocked by Bosch.


Kind regards,
Franjo

0 (0 투표)