Hmmm...I'm having a number of problems getting a clean build for the Audio DJ board (the first thing I want to do is to replicate what's on there now, before I start modifying it!).
I attempted to follow the directions in section 5.1.1 of the latest USB-Audio-Software-Design-Guide (6.6.0rc5.a), and I'm using the latest xTimeComposer (Community_13.2.0, on Mac OS X), and the latest downloaded firmware ZIP file (USB-Audio-2.0-Device-Reference-Design-Software(6.6.0). But:
- warnings.xc warns me that I am not picking up customdefines.h (the one I want for the DJ board is in app_usb_aud_skc_su1/src/core, right?)
- a bunch of other warnings, but I am betting that these are all caused by not picking up customdefines.h
It's building and generating a .xe file, but I'm sure it must be incorrect, given the multiple warnings.
So, what's the right way to get the build to pick up customdefines.h in the src/core directory of the current project (app_usb_aud_skc_su1)?
Thanks!
Mike
Having trouble compiling for Audio DJ Topic is solved
-
- Newbie
- Posts: 1
- Joined: Tue Oct 14, 2014 4:47 am
-
- XCore Expert
- Posts: 589
- Joined: Wed Feb 29, 2012 10:03 am
The warnings you are referring might be the following ones:
#warning MIN_FREQ not defined. Using 44100
#warning VENDOR_STR not defined. Using "XMOS"
#warning PRODUCT_STR_A2 not defined. Using default XMOS string
#warning PRODUCT_STR_A1 not defined. Using default XMOS string
#warning BCD_DEVICE not defined. Using XMOS release version number
If these are the warnings you are referring to, you can ignore them. They are telling you that you haven't defined the paramemetrs and the default parameters will be used. You can eliminate these by defining the macros in the customdefines.h file.
#warning MIN_FREQ not defined. Using 44100
#warning VENDOR_STR not defined. Using "XMOS"
#warning PRODUCT_STR_A2 not defined. Using default XMOS string
#warning PRODUCT_STR_A1 not defined. Using default XMOS string
#warning BCD_DEVICE not defined. Using XMOS release version number
If these are the warnings you are referring to, you can ignore them. They are telling you that you haven't defined the paramemetrs and the default parameters will be used. You can eliminate these by defining the macros in the customdefines.h file.