Search the Community

Showing results for tags 'mios studio'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 5 results

  1. Hi Fellow DYI-ers, I have 4 DIN,  4 DOUT, Midi IO, and MBPH_DIO_MATRIX_V1; all fully assembled and a  MBHP_CORE_STM32F4 module for converting an old Church Organ to play Virtual Pipe Organ using Midi. I have Download all files such as MIOS_Studio_2_4_9, en.stsw-link004 Utility, en.stsw-link008usb drivers, mios32_bootloader_v1_018 and SetupSTM32CubeProgrammer-2.4.0 all of which are installed. I followed the direction on http://ucapps.de/mbhp_core_stm32f4.html. with success with the  exception of running MOIS Studio Please look at the picture below and I attempted to run Mios Studio This 1 picture is the result of when I 1st open Mios Studio. Everything looks ok. The 2nd picture showed my file path to upload the " project.hex file to  MIOS Studio This picture shows after my file path has been selected. The final picture shows the result after starting the upload The only device connected at this point was the MBHP_CORE_STM32F4 only. Please help me. I am completely new to this. Do have to  module connect the organ keyboard prior to monitor the midi msg.    
  2. Hi TK,   In midi-ox, it shows me C-1 with value 0x18 and in MIOS-Studio it shows me C-0 with a value of 0X18. Traktor C-1 has a value of 0X18. See attached photo.   Marco.
  3. Hi all, I am facing a very, very strange problem with MIOS Studio under Windows 10. I have created an application using Eclipse with MIOS32 on my Win10 machine, but when this application is loaded in the STM32F407 via MIOS Studio, I loose the USB connection between MIOS Studio and the MBHP. I thought first it was my application, but when I upload it with MIOS Studio on a XP machine, the USB connection works Here are the steps I follow : - installation of MIOS Bootloader V1.0.18 on the MBHP using ST LINK - I start MIOS Studio 2.4.6 : the USB MIDI port appears and MIOS Studio displays the bootloader message - I select the HEX file compiled from Eclipse and upload it into the board : application is uploaded correcly. MIOS Studio looses the USB connection when the STM32 restarts (normal behavior up to now) - if I scan now the MIDI devices on the computer : no more MIOS32! I can try anything from disconnecting USB, power supply, etc... It never appears again I then reloaded the bootloader using ST LINK : USB connection to MIOS Studio works again. At this level, I thought it was an error on my side, blocking USB. I connect now the MBHP to a WinXP machine and I take the HEX file compiled on the Win10 machine. The bootloader appears as expected and I am able to upload the HEX file into the MBHP. But now, when the MBHP restarts (with the application compiled on Win10 machine), it works perfectly with MIOS Studio under XP! If I connect it to the Win10 machine again : fail! So the problem is clearly not in my code, nor in the toolchain being run under Win10. Did somebody already saw that?   Benoit
  4. Complete Beginner

    I have built two CORE 8 and seven DIN cards from Smash TV.  A friend laid out my Hex files and others and walked me through loading them into my CORE 8s.  I have wired up two manuals and connected them to the first four DINs.  He built the HEX files and the others to fit my two manual old Conn.  The #0 CORE is for the two manuals and the #1 CORE is for the pedals and stop tabs.  I have also loaded the St. Anne's free version to my Win 8 PC.  All manual keys work properly except for the E-1 on the swell.  In watching the output I noticed the E-1 shows Channel 7 rather then Channel 1.  So I need to correct this but don't know how.  My friend is very ill and can not help me at this time. I have MIOS Studio on the PC but other than monitor the keys I don't have a clue.  It would appear to me that the key is incorrectly listed in the file that is loaded on the CORE.  I do recall using some program to make minor changes to the codes, but don't recall what or where is was or how to do it. All I know is to run a cable from the CORE Out to MIDI In on my USB Midi device and also run a cable from the CORE In to MIDI Out on the USB Midi. Can anyone point me in the right direction?  I did download the "tutorial" on MIOS Studio but that isn't much help.  More confusing then helpful. I am located in the US in Berkeley Springs, WV.   My friend was in California and he send me the files and walked me through over the phone.  The files I have are: HEX FILES: device_id_00,   device_id_01,   device_id_02,   device_id_03,   main_swell_3,   and   setup_midio128  all with ".hex" MISC:  Beckham 0.syx,   Beckham 1.syx,   midio128_v2_2b.zip,   MIOS_Studio.exe Any help would be greatly appreciated.   I am presently wiring the pedals and may use a touch screen for the stops and couplers. Jay Beckham  
  5. Hi everyone,   I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio.   I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks.   To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting.   I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour.   Is this midibox_seq_v4_086 messing up the USB midi drivers somehow?  Or perhaps some residual code somewhere if it connects under boot hold?   Any help is much appreciated!