Karg

Members
  • Content count

    48
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Karg

  • Rank
    MIDIbox Newbie

Contact Methods

  • Website URL http://karg-music.blogspot.de/

Profile Information

  • Gender Male
  1. MIOS32 File Browser

    Thanks Peter, I got is working :)
  2. Hello, I would like to give my application MIOS32 File Browser capabilities. Having not found much information about this, I just started playing around a bit: Reading other peoples source codes, my impression is that the corresponding code is in terminal.c (LoopA and Seq4 code - is my impression correct?). Thus, I have begun by adding TERMINAL_Init(0); into my APP_Init routine. Further, I added several programming models to my Makefile: ################################################################################ # Include source modules via additional makefiles ################################################################################ # sources of programming model include $(MIOS32_PATH)/programming_models/traditional/programming_model.mk # application specific LCD driver (selected via makefile variable) include $(MIOS32_PATH)/modules/app_lcd/$(LCD)/app_lcd.mk # MIDI Router (and port handling) include $(MIOS32_PATH)/modules/midi_router/midi_router.mk # MIDImon include $(MIOS32_PATH)/modules/midimon/midimon.mk # UIP driver include $(MIOS32_PATH)/modules/uip/uip.mk # UIP Standard Task (with DHCPC + OSC server and client) include $(MIOS32_PATH)/modules/uip_task_standard/uip_task_standard.mk # generic sequencer modules #include $(MIOS32_PATH)/modules/sequencer/sequencer.mk # MIDI file Player #include $(MIOS32_PATH)/modules/midifile/midifile.mk # FATFS Driver include $(MIOS32_PATH)/modules/fatfs/fatfs.mk # FILE Access Layer include $(MIOS32_PATH)/modules/file/file.mk # USB Mass Storage Device Driver include $(MIOS32_PATH)/modules/msd/msd.mk # common make rules # Please keep this include statement at the end of this Makefile. Add new modules above. include $(MIOS32_PATH)/include/makefile/common.mk and also put the MUTEX routines into mios32_config.h: // map MIDI mutex to UIP task // located in app.c to access MIDI IN/OUT mutex from external extern void APP_MUTEX_MIDIOUT_Take(void); extern void APP_MUTEX_MIDIOUT_Give(void); extern void APP_MUTEX_MIDIIN_Take(void); extern void APP_MUTEX_MIDIIN_Give(void); #define UIP_TASK_MUTEX_MIDIOUT_TAKE { APP_MUTEX_MIDIOUT_Take(); } #define UIP_TASK_MUTEX_MIDIOUT_GIVE { APP_MUTEX_MIDIOUT_Give(); } #define UIP_TASK_MUTEX_MIDIIN_TAKE { APP_MUTEX_MIDIIN_Take(); } #define UIP_TASK_MUTEX_MIDIIN_GIVE { APP_MUTEX_MIDIIN_Give(); } Similarly, I have the following in my app.c: ///////////////////////////////////////////////////////////////////////////// //! functions to access MIDI IN/Out Mutex //! see also mios32_config.h ///////////////////////////////////////////////////////////////////////////// void APP_MUTEX_MIDIOUT_Take(void) { MUTEX_MIDIOUT_TAKE; } void APP_MUTEX_MIDIOUT_Give(void) { MUTEX_MIDIOUT_GIVE; } void APP_MUTEX_MIDIIN_Take(void) { MUTEX_MIDIIN_TAKE; } void APP_MUTEX_MIDIIN_Give(void) { MUTEX_MIDIIN_GIVE; } Yet, I still get the following error messages, and have not found a solution yet. I hope I am not on the completely wrong path for the MIOS32 File Browser implementation :)   Cheers, Karg
  3. midiphy SEQ v4+

    What I wanted to add: great work by everyone involved!!I was really enjoying building the sequencer, and using it is a pleasure!
  4. midiphy SEQ v4+

    Thanks :) Unfortunately, all pictures were a bit overexposed. To fit into the theme, the record LED is blue as well, which is not reallz visible on the Foto but looks well.
  5. midiphy SEQ v4+

    After a couple of troubleshooting issues in the correspsonding threat, I am finally the proud owner of:  
  6. Troubleshooting midiphy SEQ v4+

    Yes, it happens so quickly, and it is not that there aren't any warnings to pay particular attention to use the bussed network. :)
  7. Troubleshooting midiphy SEQ v4+

    @latigid onAll assembled and works well! Thanks a lot for the help again, it always pointed to the right location. Pictures for the s/n will follow soon :)
  8. Troubleshooting midiphy SEQ v4+

    @latigid onObviously, the SJs were the problem. I swapped their positions, and all tests work well now. Will continue with the build, there should be only the case left now :) Thanks a lot for the help again!!!  
  9. Troubleshooting midiphy SEQ v4+

    I sense that it is the SJs. Indeed, I use a different LED configuration for the Matias switches: Blue/Green. How does this affect the MEC leds?
  10. Troubleshooting midiphy SEQ v4+

    SJs are soldered from center pin to 1. (what are the configuration options?).  
  11. Troubleshooting midiphy SEQ v4+

    Thanks again! That hint pointed into the right direction. I exchanged the diode last night and then the switch worked :) Unfortunately, I directly experience the next problem. In this context, my appologies for bothering you so much. I have not fully understood yet how the wiring works, thus I am constantly fishing in the dark with my troubleshooting attemts and eventually run out of reasonable ideas. Your help is greatly appreciated!! The next (and hopefully) last problem is, after soldering the MEC/Leds the latter don't light up on both LeMEC boardsn when performing the l_seq.ng testing. I discovered it right after exchanging the diode last night, and have tried to isolate the exact problem since then. What I have done so far: Confirmed orientation of major parts, including LEDs Resoldered most connections Testing in MIOS Studio: l_seq.ng: MEC swithes are all recognized full Jog section works, including 16x8 matrix ngr set led:XXXX 127 switches all Flux LEDs on (checked by bridging the cathodes)
  12. Troubleshooting midiphy SEQ v4+

    I don't fully understand :( However, if I use a wire to connect the "sink bridged by switch" with the pin in the right bottom corner of a MEC switch, I typically get the "keypressed" response in MIOS Studio. However, with this test as well, I do not get this for SW18. All other swotches are working well (MEC and Matias).
  13. Troubleshooting midiphy SEQ v4+

    Troubleshooting round two. I am a lot closer to finishing the build, and just have performed all tests described in the build video 2 around 1:30-1:40. All tests were successful but one: the MEC switch SW18 on one of the LeMEC boards (R, the larger one) does not respond. I took the switch out and shortened the pads to rule out a defective switch already. Further, I have traced the diode next to it to pin4 on IC3. Judging with my multimeter, this conenction seems good. My plan was to trace the other pins of SW18 of the working board, to then compare with the non-functional one, but I am failing to correctly trace them. Any hints towards the right direction?    
  14. Troubleshooting midiphy SEQ v4+

    Works like a charm now! Still annoys me, that mistake :) Particularly since it is mentioned everywhere to check the parts number (and I actually confirm every single item). I guess mistakes happen. Thanks a lot again for the quick and competent help!!! A beer is coming your way :) Actually, you don't happen to live in the Rhein-Main Area in Germany? Then we could have that one in person...  
  15. Troubleshooting midiphy SEQ v4+

    Aaaaah, this could have been so obvious. I will see that I change the ICs and then report back. Thanks a lot already!!!