[USB Host support for MBHP_CORE_STM32F4]

Hi, I get similar behavior as described by Djordje using my STM32F4discovery as a USB-host Midi Bridge. Trying to play a Yamaha P-80 from a Oxygen61 controller a get plenty of hanging notes. I guess it could be a problem queuing the received midi messages from the USB-host, which are processed in real time and resend to the other MIDI-Ports.

How can this behavior be debugged? Which development environment is need for debugging. Can point someone to related documents, tutorials or application notes?

Best regards, Matthias

[USB Host support for MBHP_CORE_STM32F4]

Hi Yogi,

Thanks for your advice. I will check the your link.

My intention using the "discovery" board and MIOS32 as dedicated embedded OS is to learn how develop MIOS based applications, especially synthesizers.

best regards
Matthias
 

[USB Host support for MBHP_CORE_STM32F4]

Hi Thorsten,

Thanks for your reply.

Here the messages I get from MIOS Studio:

This message is display when MIOS-Studio is started with the STM-Discovery board flashed from scratch with a ST-Link utility:

Operating System: MIOS32
Board: MBHP_CORE_STM32F4
Core Family: STM32F4xx
Chip ID: 0x10036413
Serial: #2B004D000B51333335393336
Flash Memory Size: 1048576 bytes
RAM Size: 196608 bytes
Bootloader 1.018
(C) 2014 T.Klose

Then when I select the "usb_midi_2x2_v1_010" application for upload I see this:

Reading project.hex
project.hex contains 67262 bytes (264 blocks).
Range 0x08000000-0x08003fff (16384 bytes) - BL excluded
Range 0x08004000-0x080041ff (512 bytes) - STM32 Flash
Range 0x08010000-0x0801c5ff (50688 bytes) - STM32 Flash
Press start button to begin upload.

and after pressing the START button I get this text in the two message boxes

Upload of 51200 bytes completed after 1.33s (37.68 kb/s)
1 ignorable errors during upload solved (no issue!)
--------------------------------------
No response from MIOS8 or MIOS32 core!
Check MIDI IN/OUT connections
and Device ID!
For debugging see also
Help->MIDI Troubleshooting

I think this is because after the application upload the "discovery"-board perform a reset and come up with the OTG-USB port in host mode. But why, if I press the reset button on the "discovery"-board it still comes up in host mode when it is still connected to the PC?

after rescan of the midi ports MIOS-Studio shows:

Scanning for MIDI Outputs...
[1] Midi Through
[2] USB MIDI 2x2 (1)
[3] USB MIDI 2x2 (2)
[4] Juce Midi Input
MIDI Monitor ready.

Scanning for MIDI Inputs...
[1] Midi Through
[2] USB MIDI 2x2 (1)
[3] USB MIDI 2x2 (2)
MIDI Monitor ready.

MIOS Studio show MIDI Output messages when keys on integrated the virtual keyboard are pressed and the green led on the core is flashing, but the MIDI message is not present on PA2/PA3 (I'am used a terminal program).

Please help me to find what I am doing wrong.

Best regards
Matthias

[USB Host support for MBHP_CORE_STM32F4]

Hello all, I'am started today with MIOS32 on bare STM32F4DISCOVERY and I try to run it as a MIDI Host for the M-Audio Oxygen, as Master-Keyboard, in my life-performance setup (Korg R3 synth and a Technics KN920 keyboard).

While the Keyboard is connected to the STM32F4DISCOVERY the USB-OTG port is not longer available to MIOS-Studio. As suggested before, the MIDI-BOX should be configured before usage using der USB-mini connector to configure the MIOS32 core. I tried to upload the application "usb_midi_2x2_v1_010" to get a brigde between the USB-MIDI Host Port and the classic MIDI-IO Port.

The upload of the "usb_midi_2x2_v1_010" application ends with an error message. After that MIOS Core can't be accessed by MIOS-Studio only until I reload the MIOS_bootloader via the STlink interface.

Has anyone an idea what I'm doing wrong or have a suggestion where to get some documents which may lead to a solution.

Best regards, Matthias