Hi everyone & Happy New Year!
I am hoping my problem is very simple to fix!
If anyone can help me it would be very much appreciated!
I have read quite a few threads to try & find a solution, but I am still unsure of how to proceed as I am a newbie & I am very inexperienced with midibox.
The midiboxSEQv4 works fine with current firmware 0.89 apart from usb does not make contact to receive or pass information to computer or MIOS software
When I plug my midiboxSEQv4 in by usb to my computer (WIN7x64) nothing happens apart from powering the midibox.
I have tried installing the gm5x64 usb driver but it times out when midibox is connected.
I have tried a WIN7x32 computer too with the gm5x32 usb driver & I get the same result, time out.
In mios software using both Win7x64 & Win&x32 when the SEQv4 is connected by usb, no core/midibox is found in mios software midi ports.
If I use midi interface Edirol UM-880, 8 midi ports are picked up In & Out with mios software.
Using midi ports 1 In & Out on midibox results in contact with mios software
Checking midi on the thread How to debug midi loopback works with midi using my interface UM-880 using mios virtual kb as can be seen below.
None of my usb ports are enabled on the SEQv4 if I understand this system information & that is why I can not upload firmware.
I can not seem to find the bootloader information using mios software, which from what I understand is what I need to enable usb.
When I have reset the SEQv4 using mios software it shows Bootloader mode for may be a second, then loads in to 0.89 firmware.
So there must be Bootloader already flashed?
Reading the MIOS32 Bootloader for Newbies thread & Experts thread, From what I understand is that if the Bootloader is already present which it seem it is, I shouldn’t have to open the actual midibox If I wanted to upload firmware.
Possibly fastboot is enabled, stopping upload?
How come my usb ports are disabled, when they should be enabled by default?
Quote
Explanation of the most important parameters:
- fastboot: normaly after power-on the bootloader waits for an upload request for ca. 3 seconds before the actual application will be started.
This is a fail-safe measure which is mainly relevant for developers who don’t want to open their MIDIbox and stuff the “BSL Hold” jumper (J27) if the application crashed during the initialisation phase.
However, for common users this wait phase shouldn’t be really necessary, especially if they are using a stable application.
Therefore: enterset fastboot 1
store
in the MIOS Terminal to skip this phase, and to start the application immediately!
You will like this option!
Note that no MIDI upload request will be sent during power-on anymore!
Please consider this when reading documentation about MIDI troubleshooting.
- single_usb: use this option if you are working with a Windows PC which can’t handle multiple USB ports correctly.
E.g. applications like MIDIO128, MIDIbox SEQ or MIDIbox NG enable 4 USB ports by default. Certain Windows versions (such as Windows XP) are failing: sometimes MIDI events get stucked, MIOS Studio filebrowser operations abort with an error message, etc.
Even the installation of the GM5 USB MIDI driver doesn’t help (which sometimes solves the issues under Windows7), or causes new issues when multiple core modules are connected.
As a workaround, it’s possible to enforce that only a single USB port is enabled:set single_usb 1
store
This should solve the windows USB MIDI issues - with the drawback of the reduced functionality.
- enforce_usb_device: this option has only an effect on core modules which support USB Host mode such as the MBHP_CORE_STM32F4 module.
If set to 1, USB device mode will be selected regardless of the cable type A or B. If set to 0 (default), USB host mode will be selected with A type cables, and USB device mode with B type cables.
This type of selection is also known as USB OTG (on-the-go).
The usage of the default setup is normally save, “set enforce_usb_device 1” only if you are using an “unusual” cable.
Note that setting this parameter could lead to a dilemma: it can only be set with a bidirectional MIDI connection between the core module and the MIOS Studio terminal. If you don’t own a Micro-USB B type cable to establish this connection, the only possibility to change this parameter is a “traditional” MIDI connection via MIDI IN/OUT between the core module and your PC/Mac!
If you don’t own a MIDI interface for such a connection, it’s cheaper to buy the right Micro-USB cable - once you’ve changed the parameter, you can use the “improper” cable for your core!
Do I have to follow the instructions on the MIOS32 Bootloader for Newbies thread to achieve the upload of the new MBSEQv4 firmware & to find out what version of Bootloader?
Quote
MBHP_CORE_STM32F4 and STM32F4DISCOVERY: press and hold the blue “User” button, trigger the black “Reset” button shortly. This will restart the core and enforce bootloader mode as long as the blue “User” button is pressed
Any ideas what I need to do?
If any more pictures or info is needed I will try to provide, no problem.
Sorry for the newbie questions everyone.
Thanks in advance
All the best
Long Shore Drift
