Jump to content

MidiAccordion

Members
  • Posts

    1
  • Joined

  • Last visited

MidiAccordion's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. [edit: solved] I'm having trouble getting started. I need help running the goom software on bare STM32F4 (specifically, STM32F407G). Successfully installed the MIOS32 bootloader with ST_Link (downloaded from st.com), and then when plugged in with the micro USB (while still providing power through the mini USB, either from a usb port or a wall wart--[edit: either works]) in windows the board appears as a midi device MIOS32. Then, running MIOS Studio and selecting "MIOS32" for Midi In and Midi Out, I believe that the bootloader is recognized because upon pressing the Query button it reports: Operating System: MIOS32. Board:MBHP_CORE_STM32F4, etc. Then I try to program the board with the Goom project.hex downloaded from this thread. I tried a few of the versions. After selecting a project.hex, MIOS Studio prompts "Press start button to begin upload." The upload goes to 100% with a blue barber pole animation, and then reports "Upload of 48640 bytes completed [. . .] 1 ignorable errors during upload solved (no issue!)." The status on the left window starts with "Waiting for reboot" and then fails with "No response from MIOS8 or MIOS32 core! Check MIDI IN/OUT connections and Device ID!" I interpret that to mean the Goom program was not successfully installed. [edit: probably wrong interpretation. Probably just need to disconnect and power down, then reconnect.] Not being totally sure, I downloaded Ctrlr and downloaded the "Goom Editor" panel to open in Ctrlr. Fussed with the panel controls. Also tried using MIOS Studio to send CC commands to the board on Channel 1 (CC7 for volume, etc.). Just to cover bases, I also updated the STM32F4 firmware with ST_Link. I'm out of ideas. Thanks in advance! EDIT: This is working for me now. While I tried a number of things (including re-reading MIOS32 Bootloader for Newbies and using "MIOS32 Bootloader" mode with black/blue buttons during programming), I think the essence was that I hadn't gotten the parameters right in Ctrlr for the synth to generate noise. (At a minimum, I believe can get noise with CC106=127, CC108=90 (get clicky attack with higher volumes), and CC30=127.) The first couple project.hex files attached in this thread are several notes out of tune. The one attached by martindunne1 Posted 7 Jul 2015 is usable (slightly sharp). When sending serial midi to pin PA3 (versus usb midi), power is only required through the micro USB connector. As an example to define a patch, I'm sending the Continuous controller code (0xb0 for channel one) and the controller numbers Goom accepts and values like this: byte GoomControllerNumber[]={0x10, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17, 0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f, 0x66, 0x67, 0x68, 0x69, 0x6a, 0x6b, 0x6c, 0x6d}; byte GoomPatch1[]= {0x21, 0x7f, 0x00, 0x00, 0x00, 0x00, 0x00, 0x31, 0x11, 0x00, 0x40, 0x00, 0x4b, 0x57, 0x11, 0x46, 0x5c, 0x00, 0x3f, 0x5e, 0x10, 0x2c, 0x4a};
×
×
  • Create New...