MIDIFighter Source - Page 3
Page 3 of 3 FirstFirst 123
Results 21 to 30 of 30
  1. #21

    Default

    Im still working on this, just super slowly, hehe, school has started so I havent got much time, Ive been trying to efficiently read a bunch of buttons, I think this may be the hardest thing to do, because the Midifighter latches and shifts, so I cant just steal its code
    Anyways, I'm still chugging along,

    Ben

  2. #22
    Tech Mentor DjWindzOne's Avatar
    Join Date
    Apr 2010
    Location
    San Diego, CA
    Posts
    238

    Default

    Definatley looking into expanding. . .Keeping an eye out on this. . .but I do have a few questions about expanding (I'm SOOO in over my head on this). .

    What I'm trying to do is add a few more inputs rather than the standard 4 Digital + 4 Analog buttons. In my case, I'm trying to add a couple more analog inputs (2 arcade buttons, 4 Rotaries, and 2 Faders.)


    Will the use of a MUX Breakout board from Sparkfun be okay to expand it a bit further?
    http://www.sparkfun.com/commerce/pro...oducts_id=9056

  3. #23

  4. #24

  5. #25
    Tech Wizard
    Join Date
    Dec 2009
    Posts
    20

    Default

    If i try to build the firmware i get the following error:

    Compiling C: menu.c
    menu.c:136: error: expected identifier or '(' before 'const'
    menu.c:136: error: expected ')' before '<' token
    menu.c:136: error: expected ')' before '?' token
    menu.c:137: error: expected identifier or '(' before 'const'
    menu.c:137: error: expected ')' before '>' token
    menu.c:137: error: expected ')' before '?' token
    make: *** [menu.o] Error 1

    These are the two lines of code:

    inline uint8_t MIN(const uint8_t a, const uint8_t b) { return a<b ? a : b ; }
    inline uint8_t MAX(const uint8_t a, const uint8_t b) { return a>b ? a : b ; }


    Anyone know how to fix this?

    Thank you for helping.

  6. #26
    Tech Mentor
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    118

    Default

    What compiler version are you using?

  7. #27
    Tech Wizard
    Join Date
    Dec 2009
    Posts
    20

    Default

    i use avr-gcc (GCC) 4.3.3

    I've tried the old LUFA091122 library and only had these warnings:

    Makefile:712: warning: overriding commands for target `doxygen'
    LUFA091122/LUFA/makefile:53: warning: ignoring old commands for target `doxygen'
    Makefile:717: warning: overriding commands for target `clean_doxygen'
    LUFA091122/LUFA/makefile:58: warning: ignoring old commands for target `clean_doxygen'
    Last edited by jobber; 11-06-2011 at 10:29 PM.

  8. #28
    Tech Mentor
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    118

    Default

    Hrm, sorry, I have no idea as I am using the same version without problem (on windows).

    I assume you didn't change anything related before compiling and that you are using the makefile to build?

    Code:
    C:\Users\dan\Desktop\mf>avr-gcc -v
    Using built-in specs.
    Target: avr
    Configured with: ../gcc-4.3.3/configure --enable-win32-registry=WinAVR-20100110
    --with-gmp=/usr/local --with-mpfr=/usr/local --prefix=/c/WinAVR --target=avr --e
    nable-languages=c,c++,objc --with-dwarf2 --enable-doc --disable-shared --disable
    -libada --disable-libssp --disable-nls --with-pkgversion='WinAVR 20100110' --wit
    h-bugurl='URL:http://sourceforge.net/tracker/?atid=520074&group_id=68108&func=br
    owse'
    Thread model: single
    gcc version 4.3.3 (WinAVR 20100110)
    EDIT: I am using LUFA101122

    As a matter of interest, cd into the LUFA directory and run "make" (do "make clean" first if its not already clean). Does this build without error?
    Last edited by guywithknife; 11-06-2011 at 10:38 PM.

  9. #29
    Tech Wizard
    Join Date
    Dec 2009
    Posts
    20

    Default

    I've tried the LUFA101122 library and had no more errors.

    Thank you.

  10. #30
    Tech Mentor
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    118

    Default

    Great! No problem.

    I assume you were using 111009 before? I actually ran into this myself but had forgotten that the midifighter does not currently use the latest version of lufa.

    Feel free to get in touch if you have any firmware related questions. I'm pretty familiar with it at this stage.

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •