xCORE-VOICE-Smart microphone.Invalid build configuration

Voice related projects and technical discussions
OscarMa
Member
Posts: 9
Joined: Mon Jan 23, 2017 3:38 pm

xCORE-VOICE-Smart microphone.Invalid build configuration

Postby OscarMa » Mon Jan 23, 2017 4:13 pm

After following the Getting started configuration from xCORE-VOICE-Smart microphone,
appears an error while building the app_usb_aud_mic.

-> Invalid build configuration: 1i2o2_xvsm2000
->Valid build configuration are: 1i8o2 2i8o2

Could be a problem of the voice libraries?

On the website there is now link to download lib_voice.


Many thanks.
OscarMa
Member
Posts: 9
Joined: Mon Jan 23, 2017 3:38 pm

Postby OscarMa » Tue Jan 24, 2017 11:51 am

The problem is solved with the software: sw_usb_audio-(sw)_6.19.0. Provided by xmos support team.


Now I got a problem regarding the interrupt.c


Here I attach the error:


xmake XVSM=1 CONFIG=1i2o2_xvsm2000 all
Checking build modules
Using build modules: lib_mic_array(2.0.1) lib_logging(2.0.1) module_dfu module_i2c_shared module_i2c_single_port module_usb_audio module_usb_device module_usb_midi module_usb_shared module_xud lib_voice(0.0.3) lib_device_control(2.0.0) lib_xvsm_support(0.4.3) lib_xassert(2.0.1) module_locks module_queue
Analyzing interrupt.c
xcc: >: Invalid argument
xmake[1]: *** [.build_1i2o2_xvsm2000/src/extensions/interrupt.c.pca.xml.decouple] Error 1
xmake: *** [analyze] Error 2



Looks like a string problem, any idea?
User avatar
larry
Respected Member
Posts: 275
Joined: Fri Mar 12, 2010 6:03 pm

Postby larry » Tue Jan 24, 2017 6:25 pm

What's your tools version?
OscarMa
Member
Posts: 9
Joined: Mon Jan 23, 2017 3:38 pm

Postby OscarMa » Wed Jan 25, 2017 11:53 am

Hello Larry,



Tools versions:

-xTIME Composer Studio (Community_14.2.4)
-sw_usb_audio-(sw)_6.19.alpha2
-lib_xvsm_support-(sw)_0.4.3alpha2
User avatar
larry
Respected Member
Posts: 275
Joined: Fri Mar 12, 2010 6:03 pm

Postby larry » Wed Jan 25, 2017 6:44 pm

Does a clean build fail?

Code: Select all

xmake XVSM=1 CONFIG=1i2o2_xvsm2000 clean all
OscarMa
Member
Posts: 9
Joined: Mon Jan 23, 2017 3:38 pm

Postby OscarMa » Thu Jan 26, 2017 10:04 am

Yes, after the incremental build of the configuration 1i2o2_xvsm2000, the clean all seems to fail.




This is the Console message:



16:35:25***Incremental build of configuration 1i2o2_xvsm2000 for project app_usb_aud_mic_array

xmake XVSM=1 CONFIG=1i2o2_xvsm2000 all
Checking build modules
Using build modules: lib_mic_array(2.0.1) lib_logging(2.0.1) module_dfu module_i2c_shared module_i2c_single_port module_usb_audio module_usb_device module_usb_midi module_usb_shared module_xud lib_voice(0.0.3) lib_device_control(2.0.0) lib_xvsm_support(0.4.3) lib_xassert(2.0.1) module_locks module_queue
Analyzing interrupt.c
xcc: >: Invalid argument
xmake[1]: *** [.build_1i2o2_xvsm2000/src/extensions/interrupt.c.pca.xml.decouple] Error 1
xmake: *** [analyze] Error 2

16:36:50 Build Finished (took 1m:24s.287ms)
User avatar
larry
Respected Member
Posts: 275
Joined: Fri Mar 12, 2010 6:03 pm

Postby larry » Thu Jan 26, 2017 5:20 pm

What's the complete path to your current directory?

Are you on Windows, Mac or Linux?

Could you try again with VERBOSE=1?
OscarMa
Member
Posts: 9
Joined: Mon Jan 23, 2017 3:38 pm

Postby OscarMa » Fri Jan 27, 2017 10:20 am

Windows 8 seems to be the problem. The same configuration and same path in windows 7 works correctly.
The current path for the workspace is: C:\Users\"MyName"\workspace
The path for xTIME Composer: C:\Program Files(x86)\XMOS\xTIMEComposer...
User avatar
larry
Respected Member
Posts: 275
Joined: Fri Mar 12, 2010 6:03 pm

Postby larry » Fri Jan 27, 2017 6:07 pm

Thanks for the details. I've created an internal engineering report.
MikePelton
Junior Member
Posts: 4
Joined: Wed Feb 22, 2017 4:03 pm

Postby MikePelton » Wed Mar 01, 2017 11:07 am

This has to be to do with the length of the path - having built identical projects, one in a shallow path and one with a much longer prefix, the one in the short-named folder builds just fine and the one in the deeper path fails with the "interrupt.c" error. I notice quite a few characters get hung on the end of files associated with a given compilation in the build process (to give a filename like "interrupt.c.pca.xml.decouple"_. Windows continues to have a maximum path length (I know, I know) and a beer says that's the issue here.

Who is online

Users browsing this forum: No registered users and 33 guests