Search the Community

Selling due to being too lazy to ever actually do any projects anymore... I have basically all the actual parts needed to build a MIDIbox Quad Genesis - barring all the generic parts like resistors/capacitors/ICs you'd need to add. That is: these boards and associated kits, including MIDI DIN sockets, included resistors, etc. - as originally bought from the MIDIbox Shop - so please see the links below for the full specs of what you'll be getting. 1 x Core STM32F4 kit + board = RRP $34 2 x MIDI I/O module kit + board = RRP $27 x 2 = $54 4 x MIDIbox Genesis Board (for YM2612) = RRP $5 x 4 = $20 1 x front panel PCB - this is a rare one, bought from Sauraen! = RRP $50 -- These are in brand new condition - I'd never even opened the parcels until recently... - and ready to go. Original prices are in the list above. That totals $158 USD, which is about £120 right now, but I'd definitely take £100 all in. I'm open to sensible offers. They need a home that'll use them, not just to lie in my next cupboard! Shipping will be from the UK. If you're in the UK, I'll ship for free. As for elsewhere, I've had a lot of experience of shipping cheaply worldwide lately, so it should be quite cheap, but message me first for a quote to confirm. -- Pictures of the items and original invoices showing the quoted RRPs are on imgur, since I get errors when trying to upload here: https://imgur.com/a/MNv5hE0 For more detail, I have uploaded front/rear pics of the front panel PCB, as well as front/rear photos of the 3 sets of kits: see them here: https://imgur.com/a/RY1RtLO The board in the photos captioned "OPN2 boards" are still shrink-wrapped, and I didn't disturb them by unwrapping. However, you can see they are more than just the OPN2 boards! We have 4 of the Genesis/OPN2 boards that were sold at the Shop (link), i.e. the green ones other, black PCBs: 2 shown on the top, which based on the IN/OUT connectors are definitely the MIDI PCBs another black PBC in between the above 2 sets, which must be that for the Core CPU kit. As for buying YM2612/YM3438/PSG chips, it looks like there are still plenty for sale on eBay, and probably elsewhere too. I might have some in storage that I could sell, but need to check.

EDIT: For project documentation, see http://www.midibox.org/dokuwiki/doku.php?id=midibox_quad_genesis and the pages it links to, specifically including http://www.midibox.org/dokuwiki/doku.php?id=mbhp_genesis ! This semester I will be building a MIDIbox Quad Genesis synthesizer for Josh Whelchel. The synth will be based on my MIDIbox FM V2.1 (dual OPL3) synth, except it will contain four OPN2 (YM2612) and four PSG (SN76489/SN76494). We are still in the early planning stages of the project, so many of the details are not set yet. However, one thing that's pretty sure is that I will produce a custom PCB for a "MBHP_GENESIS" module, containing one of each sound chip with a parallel interface to the STM32F4 core. These modules will be stackable with pin headers, and their outputs will be correctly mixed with no external circuitry when they are stacked, allowing up to four modules to be connected to the same core. I'm also planning for them to be supplied by the +5V rail (after heavy filtering), with rail-to-rail op-amps, so a separate +/-12V supply would not be necessary. Of course, the more that I have manufactured, the cheaper they will be for everyone. For budgeting purposes, I would like to know how many people here would be interested one or four of these boards. For now I don't need a commitment, just a statement of interest. Depending on what we decide for the project, I also may be producing a large, custom front panel board, which will be VERY expensive unless we find other interested people. The design is barely even started, so of course there would be no commitment; but if you'd consider building a MIDIbox Quad Genesis with a large front panel, let me know that you might be potentially interested. Here's a Google Form for letting me know your interests about this project, please fill this out if you would be interested in a board: http://goo.gl/forms/4Gg5JX6GpX

Finally got the dust off of my STM32F4 board to work on a project I started 3 years ago. Sad news, I cannot get these OLED displays working. They're factory wired for 4SPI, which I tried initially and no dice. Realized they might need to be I2C (IIC), so I moved/added the SMD resistors for that, but still no dice. Blank. Also edited the DEFAULT.NGC file to add: RESET_HW LCD "%C" LCD "@(1:1:1)OLED1" LCD "@(2:1:1)OLED2" LCD "@(3:1:1)OLED3" LCD "@(4:1:1)OLED4" LCD "@(5:1:1)OLED5" LCD "@(6:1:1)OLED6" LCD "@(7:1:1)OLED7" LCD "@(8:1:1)OLED8" Been several years since I've played around with building a MIDIBox project, and the last one was a LPC17 so I'm admittedly rusty as well as new to the STM32F4 board. What am I missing? Also, LD1/COM LED onthe STM32F4 board is red and blinks, is that normal? For what it's worth, the displays I am able to get working in Arduino projects, so it must be something I'm not doing right here. Img-4490.m4v

Welcome to my guide! The very first thing you should do is read the MIDIbox Quad Genesis section on the wiki as much as you can: http://wiki.midibox.org/doku.php?id=midibox_quad_genesis Especially the MBHP_GENESIS, MBHP_Genesis_LS and MBHP_FP pages. If you would like to build the wooden case before soldering the electronics then please jump to this post: Step 1:Installing the MIOS32 Bootloader on STM32F407G-DISC1 This is already explained in the STM32F4 Based Core page on ucapps.de. Simply scroll down to: Installing the MIOS32 Bootloader and follow the guide. Remember that the Micro-USB cable must be inserted upside down on the left hand side of the board. Step 2: Soldering the Core STM32F4 Breakout board: This is also already explained on the STM32F4 Based Core page on ucapps.de Simply scroll down the page further to: Soldering Guide and follow the instructions. After the soldering is complete please make sure to set the Jumper at J15_S to 5V, by connecting the 2 pins on the left hand side with the jumper. This will feed our LCD display with 5 Volts. If your LCD Display uses 3.3V, then put the jumper to the 2 pins on the right hand side.

Dear Forum, I am trying to attach my SD Card using direct wiring, so no Core Board to host the STM32F4 Disc Board. For this I connected the SD Card Holder as written in red into the scheme, but Mios_Studio keeps on telling me, that no SD Card is found... Any help is appreciated, thanks! Emre

Hi I am in the research phase to build one of these beauties. I want to add an Ethernet port for the BLM emulator. Since the LPCXPRESSO is unavailable I believe I have to go with the MBHP_CORE_STM32F4. Has anybody used the MBHP_ETH sucessfully with this core? Is there a pcb/gerber for the MBHP_ETH available to buy? Cheers 6040

I remember that I added STM32F1 support on a "good will basis" without continuous testing, therefore it's not officially available (means: you've to try it, and if it doesn't work anymore, roll back to a working version) Limitations: only 24k instead of 64k configuration memory (.NGC file) .NGR files are directly processed from SD Card and not from RAM, which means that such scripts are much slower - however, as long as NGR files are not processed by your use case, or only sporadically used, no real impact on the overall performance only 1 DIO port: // STM32F1: J5A+J5B // STM32F4: J5A+J5B, J10A, J10B // LPC17: J5A+J5B, J10, J28 only 6 (instead of 8) direct AIN inputs only 3 UART based MIDI IN/OUT (instead of 4) Best Regards, Thorsten.

-edit- all parts are now sold! I have some kits for building Midibox Seq v4, all unbuilt/unused. SEQ CS pcb (smashtv) SEQ CS parts kit (smashtv) AOUT_NG kit (smashtv) STM32f4 core kit 2x MIDI IO kit I think I paid around £220 inc import taxes for the smashtv parts, the other bits were around £80. Asking £200 or make an offer. Located in UK, will ship WW.. happy to split shipping costs. Will add photos asap.

Hi i want to extend my project with 16 GLCD's. i found several threads about it but i'm still unsure how to connect the additional CS lines. the first 8 GLCD's work perfect connected to J15A... now i need to know how to connect the other 8 lines. found this wiki where it's stated how to connect additional lines from a J28 named connector. but on a "normal" STM32F4 the J28 isn't available... I read on an other thread that several lines are available on connector J10B. If I look at the schematic J10B is a normal GPIO against the J28 is a audio DAC. Can I use the GPIO's directly as they are to make 8 additional CS lines? if yes, do I need 220 ohm resistors on it? do I need an other boot loader configuration as the one described here in the MBNG manual? if no, how to use a SN74HC595N IC to generate additional lines? Where do i get the clocks (RCK and SCK, Pin 11/12 on 74HC595) and where comes the DISP SER IN (Pin 14 on 74HC595) from? thanks for some enlightenment, roberto

Hey everyone I'm trying to connect my MF_NG module to my STM32F4 Core via the MIOS IO. When connected via a different midi interface, the MF_NG module works perfectly fine. But I cannot get the connection via the MIDI IO module to work. Is there any special configuration in the NGC file I need to consider? I tried to route the incoming midi signals to the core like this: EVENT_MF id=2 ports=11111111000000000000 MF n=1 enabled=1 midi_in_port=IN1 midi_out_port=OUT1 config_port=USB2 chn=1 ROUTER n=1 src_chn=All dst_port=OUT1 I'm guessing it's wrong. Has anybody the answer to this? I'm starting to loose my mind over here... All the best! Frederik

If anybody wants to sell me their STM32F4 Core board please contact me. I am located in Germany... Thanks, Emre

Hi Here, I would like to know if it is possible to flash the mios Bootloader and mios applications on other cards than STM32F4-DISCO, for exemple on this boards : https://github.com/mcauser/MCUDEV_DEVEBOX_F407VGT6 I would like to know how it would be difficult to make Mios studio working with newer stm32 board like Teensy 4.0 or Stm32H743 board like https://github.com/mcauser/MCUDEV_DEVEBOX_H7XX_M Thanks for all, Best

see title.... a friend of mine has a iOS device (apple), there it shows only 1 USB-Midiport, while on his Win-PC with the same STM32F4-Board it shows 4 Ports! any idea to fix this on iOS?

Hei I have some SPI problems here... A AINSER slows down the SD-Card Access - so the programm is not usable anymore. I already optimized the Ainser-Side (see below), but that is not enough, I dont know if it is the prescaler Factor, that also changes SD-Card in a way (since booth are SPI...) I save a lot off informations on the SD-Card, so each percent off performance makes seconds off less waiting time. Is there something like a prescaler that can be set for the SD-Card?= How give the SD-Card more priority? I know how to give prioritys for RTOS Task that i created, but i dont know how to do that with SD-Card (on rootlevel) thx for any info! I have 2 AINSER8 moduels connected to a STM32F4(disconver), not multiplexed - i have 16 faders connected directly to them. as soon i scan the AINSER: static void TASK_AINSER_Scan(void *pvParameters){ // This task scans AINSER pins and checks for updates portTickType xLastExecutionTime; xLastExecutionTime = xTaskGetTickCount(); while( 1 ) { vTaskDelayUntil(&xLastExecutionTime, 10 / portTICK_RATE_MS); // 202 orginally 1ms // scan pins AINSER_Handler(APP_AINSER_NotifyChange); } } The Write or Read on the SD-Card goes up from 1seconds to 14seconds (in my case) so i copied the ainser.c to my project, and made some edits, the most significant emprovement was to change the prescaler from 64 to 8: // init SPI port for fast frequency access MIOS32_SPI_TransferModeInit(2, MIOS32_SPI_MODE_CLK0_PHASE0, MIOS32_SPI_PRESCALER_8); // Initialisierung des SPI-Ports i also tryd other values, but on some values the Ainser didnt react at all, or i got random values. When i remove this Prescaler LINE, the AINSER gives no output to my code, what makes me a bit wondering since in MIOS-FUNCTIONS there is statet: So my expirience - the Prescale may not have a effect on SPI2, but on SPI0 (where my SD-Card is connected). I also changed to get this Prescaler8 working, The driver from MIOS32_SPI_PIN_DRIVER_STRONG to MIOS32_SPI_PIN_DRIVER_WEAK (which is i know not recommented): // pins in push-poll mode (3.3V output voltage) MIOS32_SPI_IO_Init(2, MIOS32_SPI_PIN_DRIVER_WEAK); // 2: Ainser_SPI - J19 i then tryed to remove the Multiplexer Code, and fixed the modules to a count off 2, At the end i have 4 seconds Access Time to my SD Card which was without AINSerial 1second And without my modifications 14 seconds I already set the priority off Tasks like this: // TASK - PRIORITYS #define PRIORITY_TASK_SEQ ( tskIDLE_PRIORITY + 5 ) // higher priority than MIDI receive task! #define PRIORITY_SD ( tskIDLE_PRIORITY + 3 ) #define PRIORITY_LOPRIO ( tskIDLE_PRIORITY + 2 ) #define PRIORITY_LCD ( tskIDLE_PRIORITY + 0 ) // idle #define PRIORITY_PAD ( tskIDLE_PRIORITY + 0 ) // idle #define PRIORITY_TASK_AINSER_SCAN ( tskIDLE_PRIORITY + 0 ) // orginal this was 3 So the SD-Task (where i write things on the SD-Card with mutexes and stuff...) is already High priority > off course the SEQuencer is higher... the whole Ainser.c code then looked like this: #include <mios32.h> #include "ainser.h" #include <string.h> ///////////////////////////////////////////////////////////////////////////// // Local variables ///////////////////////////////////////////////////////////////////////////// static u8 ainser_enable_mask; static u8 ainser_muxed_mask; static u16 ain_pin_values[16]; //2 Modules 8 pins static u16 previous_ain_pin_value; const u8 pin_lookup[8] = {7,6,5,4,3,2,1,0}; ///////////////////////////////////////////////////////////////////////////// // Local Prototypes ///////////////////////////////////////////////////////////////////////////// static s32 AINSER_SetCs(u8 module, u8 value); ///////////////////////////////////////////////////////////////////////////// //! Initializes AINSER driver //! Should be called from Init() during startup ///////////////////////////////////////////////////////////////////////////// s32 AINSER_Init(u32 mode){ // pins in push-poll mode (3.3V output voltage) MIOS32_SPI_IO_Init(2, MIOS32_SPI_PIN_DRIVER_WEAK); // 2: Ainser_SPI - J19 // orginal this was MIOS32_SPI_PIN_DRIVER_STRONG MIOS32_SPI_PIN_DRIVER_WEAK // ensure that CS is deactivated AINSER_SetCs(0, 1); // CS für Module 0 AINSER_SetCs(1, 1); // CS für Module 1 // Dont use Muxes ainser_muxed_mask &= ~3; // Sets the enable mask for modules which should be scanned ainser_enable_mask |= 3; // clear all values memset(ain_pin_values, 0, sizeof(ain_pin_values)); previous_ain_pin_value = 0; return 0; } ///////////////////////////////////////////////////////////////////////////// //! This function should be periodically called to scan AIN pin changes. //! A scan of a single multiplexer selection takes ca. 50 uS on a LPC1769 with MIOS32_SPI_PRESCALER_8 ///////////////////////////////////////////////////////////////////////////// s32 AINSER_Handler(void (*_callback)(u32 module, u32 pin, u32 value)) { static u8 first_scan_done = 0; // Variable zur Verfolgung des ersten Scans // init SPI port for fast frequency access MIOS32_SPI_TransferModeInit(2, MIOS32_SPI_MODE_CLK0_PHASE0, MIOS32_SPI_PRESCALER_8); // Initialisierung des SPI-Ports // loop over connected modules int module; int chn; for (module=0; module<2; ++module){ // Schleife über die angeschlossenen Module for (chn = 0; chn < 8; ++chn) { // Schleife über die Kanäle AINSER_SetCs(module, 0); // Setzen des Chip-Select-Pins auf LOW MIOS32_SPI_TransferByte(2, 0x06 | (chn >> 2)); u8 b1 = MIOS32_SPI_TransferByte(2, chn << 6); // Übertragung der Datenbytes über SPI u8 b2 = MIOS32_SPI_TransferByte(2, 0); AINSER_SetCs(module, 1); // Setzen des Chip-Select-Pins auf HIGH u8 pin = pin_lookup[chn]; // Berechnung des Pin-Index u16 value = (b2 | (b1 << 8)) & 0xFFF; // Kombination der Datenbytes zu einem Wert previous_ain_pin_value = ain_pin_values[module * 8 + pin]; // Speichern des vorherigen Pin-Werts int diff = value - previous_ain_pin_value; // Berechnung der Differenz zum vorherigen Wert int abs_diff = (diff > 0) ? diff : -diff; // Berechnung des absoluten Werts der Differenz // Überprüfung, ob der Pin-Wert sich ausreichend geändert hat if (!first_scan_done || abs_diff > 31) { ain_pin_values[module * 8 + pin] = value; // Speichern des neuen Pin-Werts if (first_scan_done && _callback && pin < 8) _callback(module, pin, value); // Aufruf der Callback-Funktion } } } if (first_scan_done == 0) first_scan_done = 1; // Setzen der Flag, dass der erste Scan abgeschlossen ist return 0; } ///////////////////////////////////////////////////////////////////////////// // Internal function to set CS line depending on module ///////////////////////////////////////////////////////////////////////////// static s32 AINSER_SetCs(u8 module, u8 value){ switch( module ){ case 0: return MIOS32_SPI_RC_PinSet(2, 0, value); // spi, rc_pin, pin_value // 2: SPI - J19 case 1: return MIOS32_SPI_RC_PinSet(2, 1, value); // spi, rc_pin, pin_value // 2: SPI - J19 } return -1; } i use to write to SD-card directly with File.c, like this: // Speicherung der Daten auf der SD-Karte MUTEX_SDCARD_TAKE; FILE_WriteOpen ("0.p4", 8); FILE_WriteBuffer(buffer2, sizeof(buffer2)); FILE_WriteClose(); MUTEX_SDCARD_GIVE;

Hi! I am looking for Core STM32F4 kit + board. Maybe someone has one for sell? Regards, Michał

Hello, This is an introduction for my new baby, a really funny toy, the HAARP (yes I like conspiracy theory ;) It's a pure MIDIbox Project, just a dedicated CS and some coding. It works with any STM32F4 Core. Why? Many synths have an integrated arpeggiator, the SH-101 is well known for that, but the available parameters are still limited. There is also some good plug-in I think especially of the Ableton live's one but it's software. So I designed an hardware one, "LIVE" oriented, starting from the @TK.'s arp example. No encoder(except for MENU section Data entry), all parameters are directly accessible and are potentiometers. The screen is a small color TFT with a resolution of 128x160(sorry for picture, colors are better in real). It's 8 independent voices. 8 banks of 8 Presets. Session are saved/loaded from the SD Card. The Arpeggio parameters are divided in 3 sections: First is the TIMING Section (Purple pots): On/Off button, HOLD Button, it holds or releases the Notes in the notestack. The MODE Pot, it's UP, DOWN, UP-DOWN and AS-PLAYED, fr the moment but I will implement more. The RATE, from slowest to fastest, from 4 Bar to 32nd with dotted and Triplet value. The RESYNC, it retriggers the arpeggio, values are the same as RATE parameter. The OFFSET, it will shift left or right the starting step(note). Is Note Stack and MODE dependent. The DELAY, it will delay the whole arpeggio within the step range(duration), is RATE dependent. The GATE, the length of the Note, max is STEP length, is RATE dependent. The SHUFFLE, it will delay all the odd steps, in the range of an half step, is RATE dependent. Second is the TRANSPOSITION Section (Yellow, Orange, Red): Simple Transposition On/Off (Yellow). Simple OCTave Transposition, +/- 10. Simple SEMItone Transposition, +/-12 Repeat On/Off. Repeat, LOOPS number, 1 to 8. Repeat, SHIFTing on each loop, +/-32 semitones. Force to Scale On/Off Force To Scale, SCALE, list is the same as the Force to Scale example from the repo. Force To Scale, ROOT from C to B semitone. Third is the VELOCITY Section. REGEN Pre/Post(Target process) button. REGEN, +/- 100% Target process On/Off. TIME, the time to reach the target value, in PRE initial value is the regenerated value. in POST initial value is the one stored in the Note Stack. TARGET is the targetted value, 0 to 127. RETRIG, if on the TIME is retriggered by the RESYNC parameter. The main page of the screen represents an octave range, the note color changes depending on the octave, there's a Velocity section on the bottom, it's like a piano-roll. In the code, the arpeggio processing is ready, it remains me to complete the MENU section, I was waiting for the CS PCB to write it, now I can... ;) This little guy is to much fun, so I can't keep it for me. Then i will propose it to you ASAP. and I hope it will help me to finance some other bigger projects I've got in my back-pocket ;) I will try to make it available in two format, I'm currently working on a PCB for USB host/device, sdCard MIDI etc.. which will fit for both version and will be reuse for other small toys like that. An Eurorack version for the patching addicts. I used a MCP3204(4 channels) instead of a MCP3208(8 channels) for the AINSER, it's an AINSER32. I use only 2 channels for the 16 pots(8Multiplexed lines * 2 channels), it remains 16 analog Inputs which are accessible to connect some CV In Modules, thanks to @Hawkeye for making me think about this. The SRIO Chain is available too, you can connect GATE In (DIN) easily. You will be able to connect the MIDIPHY CV/GATE Out Modules which will be available soon. @latigid on is working on it. MCAN will be available, for an internal MIDI bus within your Eurorack, I reuse the BUS1 and 2 from the Euro Power connector for that purpose. A Desktop version, for MIDI purpose only(except if i find a way to add some CV/Gate without designing a too much big box). Voilà! More information will be available soon. For the moment this is a small video I made, I seem a little febrile but it's because I continue to discover it every day. I really love this little toy, it is very effective and musical, even in LIVE and if the Force To Scale is activated, there's no wrong note ;) Best regards Bruno

Hi here, I try to modify the pin definition mapping between MIOS and hardware because I use a STM32F4VGT alternative board with a sd card directly implemented and the pins are differents for the midibox standard pins. I need to swap this standart Midibox Ports to this new ones : Midi box | Alternatie board From : To : How can I do that ? Thanks a lot by advance !

Lets get started... Goal is a midicontroller for Ableton live, at the beginning as simple midicontroller, maybe later to transfair Labels via max4Live to the controller... it will not a midibox-ng script, it will be a own program based on the MIOS-platform. Hardware first, i designed a 6xSSD1306 + 9 Encoder Board, that is scaleable --- i will use 8-10 off it, its documented here (incl gerbers): http://wiki.midibox.org/daw-encoder-display i already have the Motorfaders and the ready soldered and flashed mf-ng boards, i will controll them with a stm32F4 board... which also handles the encoders and displays. in order to drive the displays stable, i use latigid-ons display driver board. - this is also the offical discuss topic for this project (which is linked in the wiki)

ich hätte da noch eine andere Frage . Bisher habe ich mit einem LPC Core gearbeitet. Es soll aber demnächst auch ein STM32F4 Core her . Muss ich die Toolchain um die apps zu compilen dann jedesmal umstellen . e.g export MIOS32_FAMILY=LPC17xx export MIOS32_PROCESSOR=LPC1769 export MIOS32_BOARD=MBHP_CORE_LPC17 .. export MIOS32_FAMILY=STM32F4xx export MIOS32_PROCESSOR=STM32F407VG export MIOS32_BOARD=MBHP_CORE_STM32F4 oder kann ich 2 Toolchain profile haben (mit verschiedenen Pfaden ) ? lg , jascha

Hi, I im trying to run simple character lcd, without core module, but keep getting some random chars, or even just blocks, but it keeps blinking. I followed schematic from uCApps page for STM32F4, but the part to set Luminance i dropped and simply connected it to ground, Could be this a problem ? Tried to connect from scratch everything a few times, but still getting the same error... Please, if anyone has a tip what could be the problem, mine is that as i am lame at electronics, somewhere is connection problem maybe, im bit confused about the resistor array. Here is a video showing the behavior of LCD https://drive.google.com/open?id=1CPgCp6t-rewshbGq7Yprdonu_htadADo Thanks, Martin

Alright, now I see the problem - the notation for the "Connections to Pins on STM32F4 DiscBoard" has been added by yourself, and I agree, that the data input of the SD Card has to be connected to the serial data output of STM32F4, and vice versa. Compare with the MBHP_CORE_STM32F4 schematic: http://www.ucapps.de/mbhp/mbhp_core_stm32f4.pdf SDCard J1 DI -> MBHP_CORE_STM32F4 J16 SO (-> PA7) SDCard J1 DO -> MBHP_CORE_STM32F4 J16 SI (-> PA6) Problem solved :) Best Regards, Thorsten.

This is MIDIbox FM V2.1, the STM32F4 version of the Gen 2 MBFM. Please note that this is not an official successor to MIDIbox FM V1.4, nor is it a project that is intended to be easily replicated by members of the community, at least not in the forseeable future. For the thread on MIDIbox FM V2.0, the same synth before I upgraded the processor from the LPC17, see here (some build information, more pictures, etc.): I have successfully upgraded my MIDIbox FM from the LPC17 core to the STM32F4 core, both hardware and software, and re-christened it MIDIbox FM V2.1. A stable, decently full-featured (but not 100% complete) build is available. I upgraded mainly due to RAM limitations on the LPC17 core, and now the LPC17 core will no longer be supported, in favor of STM32F4. Working features: MIDIbox NG V1 integration; all synth controls are MBNG parameters, so you can lay out and wire your front panel how you want. Menus are fixed, though, and certain controls (e.g. 18 voice-selection buttons with two-color LEDs, 8 softkeys, 4 mode buttons) are basically mandatory. Other things (e.g. controls for operator parameters) may be done how you like (e.g. MBNG banking). Supports 1 or 2 OPL3s (potentially 4, now that we have more RAM, though performance may become an issue). With 2 OPL3s (as I have), there are no noticeable performance problems, even when playing 30+-voice MIDI files into the synth. Edit all 18 (per OPL3) 2-operator voices independently; set up six pairs (per OPL3) of 2-operator voices independently to be 4-operator voices; set up one set of 3 (per OPL3) 2-operator voices to become a 5-voice percussion system. All OPL3 parameters editable and modulatable (even bit flags and separate audio outputs for two halves of a 4-operator voice). Set voices as polyphonic copies (DUPL) that follow parameters, or LINK them so they play together but have semi-independent parameters. Customize transpose, tuning, portamento, EG retrigger, and delay per voice. Arbitrarily assign two LFOs, one ADLDSR EG, velocity, mod wheel, and CC2 values to modulate voice, operator, or modulator parameters, per voice, up to 16 modulation connections per 2-op voice. Set up a custom temperament system (e.g. just intonation) with independent root note selection and frequency controls. One-touch switch to equal temperament and back. Intelligently assign voices to MIDI channels, the synth does the DUPL work (unless you disable it for custom configurations). Save and load named patch files from SD card in intelligent folder hierarchy and human-readable (editable, hackable) format. About 75% of General MIDI Bank 0 patches are complete. Customize synth's response to incoming MIDI messages: Bank MSB/LSB, Program, Pan, Volume, Expression. Enable/disable automatic patch loading on Program receive. MIDI mixer window with real-time-updating separate Volume and Expression controls per channel. Control MIDI input behavior per port. Not done yet: MIDI output port menu and behavior. The rest of the GM patch bank. There are some bugs with saving/loading 4-op voices, plus some untested (probably broken) corner cases for saving/loading complex LINK-DUPL voice arrays. The "wavetable" modulator (step sequence of pre-programmed values). The drum sequencer. AOUT support (beyond what is offered in MBNG). If anyone would like to build one of these, please let me know! I can send you information personally, or if applicable make a wiki page and/or put up the code somewhere.

Just want to share, that the new Behringer RD-8 drummachine is using a STM32F405. Maybe MIOS is an option as an alternative Firmware for those of you who own one.

Hey, for sale: GM5x5x5 PCB STM32F4 Disco Waveshare Core STM32F4 Core LPC17 Core Selling for best offer. Chris