I was connecting through usb to MIOS from stm32f core and 4.086 with no issues.
Then i uploaded 4.087 and MIOS cannot find the core now.
I can see midi input on the midi monitor when i start and stop a sequence.
What happened?
Midi connection to mios is working fine.
I’m running WIN XP. MIOS 2.4.6
Any ideas?
On the positive note: .087 is running and i’ve successfully configured the 8 analog gates from my dout! 
And i know the drum trigger and clock functions will work as well!
Very strange!
Could you please try the following: open the device manager in XP and remove the USB device corresponding to your MIDIbox.
Re-Plugin the USB cable. The USB MIDI driver should be installed again.
Best Regards, Thorsten.
I’ll give that a shot. thanks for the reply TK.
Hmmm. Still no good. I found a usb device called “USB Composite Device” that appeared when plugging in the midibox.
I removed it.
Then replugged.
Then finds new hardware “seq v4”.
your new hardware is ready…
but still no go.
tried again by removing “USB audio device”.
finds new hardware, reinstalls drivers.
but no usb connection in mois.
I’m stummped.
Again, i can see midi input via the mios midi monitor with start stop. also seeing input on the mios terminal.
Just seems no midi output via USB.
This is my on and only issue. Everything else works! 
<___base_url___>/gallery/image/2847-mios/?do=embed
previosly with .086 when i would plug in the USB the seq would hang at “searching for sd card”. Then when the mios connection was established it would continue into pattern edt mode.
But this looks different: actually there is a MIDI connection, e.g. you are able to send terminal commands via USB, correct?
Just the query function doesn’t get a response from the core, and you also don’t get MIDI notes, right?
Could you please enter “router” in the MIOS terminal and post the output of this command?
Best Regards, Thorsten.
[14650.487] router
[14650.462] MIDI Router Nodes (change with 'set router <node> <in-port> <channel> <out-port> <channel>)
[14650.462] Example: set router 1 IN1 all USB1 all
[14650.462] 1 SRC:Def. off DST:Def. off
[14650.462] 2 SRC:Def. off DST:OUT1 off
[14650.462] 3 SRC:Def. off DST:OUT1 off
[14650.462] 4 SRC:Def. off DST:OUT1 off
[14650.462] 5 SRC:Def. off DST:OUT1 off
[14650.462] 6 SRC:Def. off DST:OUT1 off
[14650.462] 7 SRC:Def. off DST:OUT1 off
[14650.462] 8 SRC:Def. off DST:OUT1 off
[14650.462] 9 SRC:Def. off DST:OUT1 off
[14650.462] 10 SRC:Def. off DST:OUT1 off
[14650.462] 11 SRC:Def. off DST:OUT1 off
[14650.462] 12 SRC:Def. off DST:OUT1 off
[14650.462] 13 SRC:Def. off DST:OUT1 off
[14650.463] 14 SRC:Def. off DST:OUT1 off
[14650.463] 15 SRC:Def. off DST:OUT1 off
[14650.463] 16 SRC:Def. off DST:OUT1 off
[14650.463]
[14650.463] MIDI Clock (change with ‘set mclk_in <in-port> <on|off>’ resp. ‘set mclk_out <out-port> <on|off>’)
[14650.463] USB1 IN:on OUT:on
[14650.463] USB2 IN:off OUT:off
[14650.463] USB3 IN:off OUT:off
[14650.463] USB4 IN:off OUT:off
[14650.463] MID1 IN:off OUT:on
[14650.463] MID2 IN:off OUT:off
[14650.463] MID3 IN:off OUT:off
[14650.463] MID4 IN:off OUT:off
[14650.463] IIC1 IN:— OUT:—
[14650.463] IIC2 IN:— OUT:—
[14650.464] IIC3 IN:— OUT:—
[14650.464] IIC4 IN:— OUT:—
[14650.464] OSC1 IN:off OUT:off
[14650.464] OSC2 IN:off OUT:off
[14650.464] OS IN:off OUTf
i do get notes on the usb midi in
sorry i cant be as attentive as id like to be today. i’m having a little party at my house cooking mexican. wish i could give you a taco.
Something overloads the CPU, this is indicated by the “system” command which shows 216% in your first snapshot.
Actually it should be around 50% on a STM32F1 core (when no sequence is running) and around 60%..80% when the sequencer is running.
I need more input: you’ve to find out, which configuration causes the overload - I can’t help you to find this remotely…
I know that there are many many many mode & parameters which could influence this (users requested so many features ;-)) - but at least I can say that you are using some kind of configuration which I haven’t selected by myself in the past (I’m using a STM32F1 as well)
It could make sense to start with a new session.
Just enter “new <name-with-8-characters”> to create a new one
If this already helps, then please attach your previous session directory to this posting.
Best Regards, Thorsten.
with a new session i see 236 cpu! when stopped.
and 00 cpu when playinng.
something is goofy:)
At this point i believe i have fried my sd card and this is why the sudden change in everything!
I will need to get a new SD card to confirm.
After re installing the bootloader. and reinstalling .086. the midibox refused to recognize the sd card. “searching forsd card forever”
going to buy a new sd card tomrw.
So after wiping everything and getting a new sd card. i’ve installed 4.086 and the wilba MBSEQ_HW.V4.
And i have %235 cpu when stopped!
What is going on?
Maybe the disconvery board is messed up?
You are using a STM32F4! Of course, this changes the situation.
The idle value is ok, same at my side with this core.
Query is working at my side.
Maybe the only difference: I’m using the latest bootloader
Could you please update to the latest version (V1.018) as well?
Since the query function doesn’t work during runtime, you’ve to press&hold the blue button on the discovery board.
Re-connect the USB cable
Keep the blue button pressed!
WinXP should install the USB MIDI driver for the bootloader (if this hasn’t been already done)
Restart MIOS Studio, select the right USB MIDI interface and upload the bootloader update application.
All this by keeping the blue button pressed (to prevent that the MBSEQ app will be started)
Release the blue button during the hex upload - the bootloader app will be started thereafter.
Once the bootloader has been updated, upload the MBSEQ app
Best Regards, Thorsten.
Holy Crap!
All of my issues are fixed!
Due to installing the GM5 DRIVER!
This explains why my mios sessions were so hit and miss.
It would work and not work intermittently. The larger the file the less likely it would make the transfer.
I was getting corrupted sysex dumps causing all sorts of issues!
It corrupted my SD card it won’t work now?
Now i can succesfully us the mios file browser! It was acting very strange previous to the GM5 install.
I missed that part of the documentation.
So very sorry to have wasted your time TK.
And yes i’m using the stm32f4!
So the 230% cpu on idle is ok then? seems to run just fine.
Thank you so much for all of your help!
Your the best TK!
" Windows7 64bit: the SysEx communication gets stucked if a MIOS32 core opens more than one USB port (like MIDIbox SEQ V4).
This was true for my version of XP SP3 as well. The real story is that i ignored this because it said win7 64bit.
GM5 device driver is the answer!
Yes! The sysex gets stucked!