i586-intel-elfiamcu-ar: ../build/debug/quark_d2000/libqmsi/lib/libqmsi.a: No such file or directory

[DGoek]

Hey,

i am using win7 pro x64 SP1

i just install issm, java jdk1.8.0_102 x64 and created a java environment variable in my system settings

i have set my user rights to allow everything and started issm as admin

from building the hello_world example i get the following log

.....

make[1]: Entering directory `C:/IntelSWTools/ISSM_2016.0.027/eclipse/workspace/hello_world/bsp/drivers'

CreateProcess(C:\WinAVR-20100110\utils\bin\sh.exe,C:/WinAVR-20100110/utils/bin/sh.exe -c "md ..\build\debug\quark_d2000\libqmsi\lib > nul 2>&1 || exit 0",...)

Putting child 0x01d2f1b8 (../build/debug/quark_d2000/libqmsi/lib/libqmsi.a) PID 30596128 on the chain.

Live child 0x01d2f1b8 (../build/debug/quark_d2000/libqmsi/lib/libqmsi.a) PID 30596128

Reaping winning child 0x01d2f1b8 PID 30596128

i586-intel-elfiamcu-ar rcs ../build/debug/quark_d2000/libqmsi/lib/libqmsi.a ../drivers/debug/quark_d2000/obj/qm_adc.o ../drivers/debug/quark_d2000/obj/qm_aon_counters.o ../drivers/debug/quark_d2000/obj/qm_comparator.o ../drivers/debug/quark_d2000/obj/qm_flash.o ../drivers/debug/quark_d2000/obj/qm_fpr.o ../drivers/debug/quark_d2000/obj/qm_gpio.o ../drivers/debug/quark_d2000/obj/qm_i2c.o ../drivers/debug/quark_d2000/obj/qm_identification.o ../drivers/debug/quark_d2000/obj/qm_init.o ../drivers/debug/quark_d2000/obj/qm_interrupt.o ../drivers/debug/quark_d2000/obj/qm_mpr.o ../drivers/debug/quark_d2000/obj/qm_pic_timer.o ../drivers/debug/quark_d2000/obj/qm_pinmux.o ../drivers/debug/quark_d2000/obj/qm_power.o ../drivers/debug/quark_d2000/obj/qm_pwm.o ../drivers/debug/quark_d2000/obj/qm_rar.o ../drivers/debug/quark_d2000/obj/qm_rtc.o ../drivers/debug/quark_d2000/obj/qm_scss.o ../drivers/debug/quark_d2000/obj/qm_spi.o ../drivers/debug/quark_d2000/obj/qm_uart.o ../drivers/debug/quark_d2000/obj/qm_wdt.o

CreateProcess(C:\IntelSWTools\ISSM_2016.0.027\tools\compiler\bin\i586-intel-elfiamcu-ar.exe,i586-intel-elfiamcu-ar rcs ../build/debug/quark_d2000/libqmsi/lib/libqmsi.a ../drivers/debug/quark_d2000/obj/qm_adc.o ../drivers/debug/quark_d2000/obj/qm_aon_counters.o ../drivers/debug/quark_d2000/obj/qm_comparator.o ../drivers/debug/quark_d2000/obj/qm_flash.o ../drivers/debug/quark_d2000/obj/qm_fpr.o ../drivers/debug/quark_d2000/obj/qm_gpio.o ../drivers/debug/quark_d2000/obj/qm_i2c.o ../drivers/debug/quark_d2000/obj/qm_identification.o ../drivers/debug/quark_d2000/obj/qm_init.o ../drivers/debug/quark_d2000/obj/qm_interrupt.o ../drivers/debug/quark_d2000/obj/qm_mpr.o ../drivers/debug/quark_d2000/obj/qm_pic_timer.o ../drivers/debug/quark_d2000/obj/qm_pinmux.o ../drivers/debug/quark_d2000/obj/qm_power.o ../drivers/debug/quark_d2000/obj/qm_pwm.o ../drivers/debug/quark_d2000/obj/qm_rar.o ../drivers/debug/quark_d2000/obj/qm_rtc.o ../drivers/debug/quark_d2000/obj/qm_scss.o ../drivers/debug/quark_d2000/obj/qm_spi.o ../drivers/debug/quark_d2000/obj/qm_uart.o ../drivers/debug/quark_d2000/obj/qm_wdt.o,...)

Live child 0x01d2f1b8 (../build/debug/quark_d2000/libqmsi/lib/libqmsi.a) PID 30596128

i586-intel-elfiamcu-ar: ../build/debug/quark_d2000/libqmsi/lib/libqmsi.a: No such file or directory

Reaping losing child 0x01d2f1b8 PID 30596128

make[1]: *** [../build/debug/quark_d2000/libqmsi/lib/libqmsi.a] Error 1

Removing child 0x01d2f1b8 PID 30596128 from chain.

make[1]: Leaving directory `C:/IntelSWTools/ISSM_2016.0.027/eclipse/workspace/hello_world/bsp/drivers'

Reaping losing child 0x01d759a8 PID 30854144

Removing child 0x01d759a8 PID 30854144 from chain.

make: *** [libqmsi] Error 2

any suggestions?

Thanks, d

[Michelle_C_Intel]

Hi,

It does look like it may be related to you JAVA environment .. Can you try installing the latest version of ISSM available for download here - https://registrationcenter.intel.com/en/forms/?productid=2796 Commercial Product Request - Intel® Products

This was just released today and does have a fix related to the JAVA setup.

The step by step process of setting up ISSM with the Intel® Quark™ Microcontroller Developer Kit D2000 is available here - https://software.intel.com/en-us/iot/hardware/d2000/get-started IoT - D2000 Get Started | Intel® Software

regards,

Michelle.

[DGoek]

Hey Michelle,

-> ISSM_2016.0.027

downloaded it yesterday

and followed the "step by step process of setting up ISSM..."

[Michelle_C_Intel]

The updated version is ISSM_2016.1.067. This was only published today and has the Java fix and multiple other updates included.

-- regards,

Michelle.

[DGoek]

Hey Michelle,

that moment you wrote i noticed the difference in the version-numbers...!

i will give it a try!

:Dirk

[DGoek]

so far i got it working, somehow:

i had to remove WinAVR from my hdd

the new/next problem i have to solve, is, OpenOCD cannot gain contact to the d2000 anymore after updating ISSM to version 2016.1.067

[Michelle_C_Intel]

There is an issue with having other versions of 'make' within your Windows PATH - Did you try removing the WinAVR from the PATH first ?

Do you have the OpenOCD error ?

It may be related to the driver. Can you try running the install.bat in c:\IntelSWTools\ISSM_2016.1.067\tools\debugger\driver directory . This will re-install the driver.

--regards,

Michelle.

[DGoek]

ok, it works now somehow

what i did so far

i removed WinAVR from my PATH, what fixed the problem with the build process, saying -> could not create dir N:\xxxnnn\blabla.o etc.

i removed the ftdi driver including deleting the driver software

i uninstalled ISSM v2016.1.067

i switched Windows TESTSIGNING OFF (it was ON for some unsigned driver issues)

i connected a seperate USB3 adaptor to my laptop

i reinstalled ISSM v2016.1.067

i reinstalled the FTDI driver by using C:\IntelSWTools\ISSM_2016.1.067\tools\debugger\driver\install.bat

now i am able to compile the demos (blinking, accelerometer, magnetometer)

what still does not work is the build in usb-port of my laptop, openocd throws an exception -> Launch of OpenOCD failed. Could not connect device. Check if driver... etc.

when i put the d2000 back to my USB3 adaptor, it works

dirk

[Michelle_C_Intel]

Hi Dirk,

Good to hear you got it working

There are some further troubleshooting steps you can try when you have the board connected directely to the Laptop - These are included in the Release Notes (copied below).

--Michelle.

JTAG Driver Manual Installation Steps:

a. Connect your board (micro USB) to your host machine (USB) and run the driver installer to set up the Microsoft* WinUSB driver for JTAG: C:\IntelSWTools\ISSM_2016.y.xxx\tools\debugger\driver\install.bat

This will attempt to install the correct drivers for the debugger device.

b. If OpenOCD can still not find the device, removal of existing drivers is required:

i. Open Device Manager (WIN + X).

ii. Locate the driver either within the "Universal Serial Bus controllers" group, "USB Serial Converter", "USB Serial Converter A" or "USB Serial Converter B".

iii. Right click on the device and select Uninstall. Make sure to tick the "Delete the driver software for this device". Replug the device.

iv. Repeat this process until Windows recognizes the device as Unknown, at which point run the driver "install.bat" shown in step "a".

v. You should now see the device installed as "OpenOCD JTAG"

c. If OpenOCD fails to detect the device even with the "OpenOCD JTAG" device visible in the device manager here are some troubleshooting steps you can try:

i. Re-plug your target/debugger.

ii. Run the install.bat described in step "a". (Whilst device is connected)

iii. Remove existing FTDI drivers as described in step "b".

iv. Reboot your machine

Warning: These steps may interfere with other FTDI devices in use.