Jump to content

lakewood

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

lakewood's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. Yes, i ordered a M-Audio MIDISport 2X2 Interface! Cheers
  2. Okay, good to know ;) I just ordered a different midi Interface and i'll let you know if it solved the problem! Cheers!
  3. Okay, that could be the problem! I'll try to get a different MIDI-Interface! Thanks!
  4. I just checked the voltages, should be fine: IC5:MCLR(1) - IC5:Vss(12) = 4,98V IC5:Vdd(11) - IC5:Vss(12) = 4,97VIC5:Vdd(32) - IC5:Vss(31) = 4,97VIC9(8) - IC9:(5) = 4,97V
  5. Reading mios8_v1_9h_pic18f452.hex Trying to contact the core... mios8_v1_9h_pic18f452.hex contains 12826 bytes (52 blocks). Range 0x00000000-0x00002fff (12288 bytes) - MIOS8 area Range 0x00003000-0x000033ff (1024 bytes) - PIC Flash Range 0x00007c00-0x00007fff (1024 bytes) - PIC Flash WARNING: no response from core Please reboot the core (e.g. turning off/on power)! Waiting for upload request... still got no respond from core :/ the only thing that changes is this constant MIDI IN stream: [10223.823] ff [10225.221] ff [10225.222] df 7f Chn#16 Aftertouch G-8 [10225.222] df 7d Chn#16 Aftertouch F-8 [10225.222] ff [10225.223] fd [10225.862] ff [10225.905] ff [10226.061] ff [10226.881] ff [10227.116] ff [10227.720] ff [10227.919] ff [10228.341] ff [10228.978] ff [10229.619] ff ...
  6. The MIDI-Interface should work fine, i get a signal from the burned PIC and the MIDI IN status LED of my interface is blinking (recieving information). But this information looks like this: Scanning for MIDI Inputs... [1] USB Midi MIDI Monitor ready. [6104.260] ff [6104.920] ff [6106.760] ff [6109.840] ff [6111.680] ff [6112.941] ff [6114.219] ff [6114.239] ff [6115.839] ff [6119.102] ff [6121.122] ff [6121.460] ff [6121.740] ff [6122.722] ff ...endless... i burned the PIC with PICkit 2 v2.61 and there was no error at all... :/
  7. The problem is that I can't do anything in MIOS Studio, so how do I upload the bootloader? I still get the message: No response from MIOS8 or MIOS32 core! Check MIDI IN/OUT connections and Device ID! For debugging see also Help->MIDI Troubleshooting
  8. Hey guys! Im completely new to midibox and mios things but i plan to build a daw controller for my studio! so i just soldered a MBHP_MF_NG module together and burned the bootloader_v1_2b_pic18f452.hex file via PIC programmer onto my 19F452. The next step would be to enter MIOS Studio (version 2.4.6) and load the firmware of the board via MIDI. I connect the module with my MIDI interface (klick) the the IN-LED of the MIDI-interface starts blinking -> i get a signal from the module. In MIOS Studio i get the error message: No response from MIOS8 or MIOS32 core! Check MIDI IN/OUT connections and Device ID! For debugging see also Help->MIDI Troubleshooting and in the MIDI IN section an endless list of signals appear (everytime the IN-LED of the interface blinks the list updates): Scanning for MIDI Inputs... [1] USB Midi MIDI Monitor ready. [6104.260] ff [6104.920] ff [6106.760] ff [6109.840] ff [6111.680] ff [6112.941] ff [6114.219] ff [6114.239] ff [6115.839] ff [6119.102] ff [6121.122] ff [6121.460] ff [6121.740] ff [6122.722] ff ... This is my MIDI OUT section: Scanning for MIDI Outputs... [1] Microsoft GS Wavetable Synth [2] USB Midi (*) MIDI Monitor ready. [6554.222] f0 00 00 7e 32 00 00 01 f7 [6554.222] f0 00 00 7e 40 00 0d 02 00 00 00 00 00 00 01 00 00 00 00 f7 [6554.429] f0 00 00 7e 40 00 02 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [6554.632] f0 00 00 7e 40 00 02 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [6554.835] f0 00 00 7e 40 00 02 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [6555.038] f0 00 00 7e 40 00 02 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [6555.241] f0 00 00 7e 40 00 02 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 I already tried to choose different Device IDs but it doesn't work! I hope someone can help me, i have no idea how to fix this problem :( cheers, Leo!
×
×
  • Create New...