Search the Community

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

i have built the stibl stc32f4disc midibox correctly and after upload mios studio hex program also seq v4 already appear on my lcd 2x20 with brand not hd447780 (hitachi) but i try to insert mb ng through mios not show in my lcd i please give in suggestion , whether the lcd does not match the driver in mb ng or there is a system that must be in input as shown in my picture

Hi all, I received my STM32F4 board in anticipation of building my SeqV4. I flashed the bootloader with ST-LINK on Win7 x64, and then used MIOS Studio to upload the SeqV4 application. From there, MIOS Studio doesn't want to talk to my STM32F4 anymore -- it sees 4 Midi ins and 4 Midi outs from the Seq, but no combination of those four ports will let me talk to it -- it says 'no response from device' or something similar. The bootloader fail-safe mode works (holding the USER button down on reset keeps it in the bootloader). But I can't communicate to it while it's actually running the Seq app. I think this is because of the known Win7x64 USB MIDI driver issues. But I find " The GM5 driver is currently not supported for the MBHP_CORE_STM32F4 module, but it's planned to provide it in future!" on the MIOS32 download page... so this driver won't help in this situation? I'd like to keep the four USB Midi In/Outs because I'll be using this thing with Linux mostly, but I can't get MIOS_Studio working on my Arch Linux install at the moment. The pre-compiled version didn't work, and compiling it from source caused me some GTK errors that I haven't sussed out. I'd also like to be able to update the Seq App in the future without having to disassemble my device to get to the button... Any help? I'll probably continue debugging the MIOS_Studio app on Linux to avoid Windows as much as possible, but I thought I'd ask here if there were any suggestions.

Hello all! I've run into a problem while implementing a granular synth on a STM32F4 Discovery using MIOS32. The synth algorithm makes use of floating point operations - I thought it would not be a source of performance issue, since the MCU has a dedicated unit for floating point calculations. Actually, there are performance issues, because the FPU is not enabled for the compiler (I'm using the original toolchain). There's a line commented out in trunk/include/makefile/common.mk: ifeq ($(FAMILY),STM32F4xx) # leads to a crash - reason not analysed yet #CFLAGS += -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mthumb -mfloat-abi=hard -mlittle-endian -ffunction-sections -fdata-sections -fomit-frame-pointer # works (but FPU not enabled) CFLAGS += -mcpu=cortex-m4 -mlittle-endian -ffunction-sections -fdata-sections -fomit-frame-pointer endif I tried to uncomment that line, it compiled, but crashed for real on the MCU. Do you know if there's a workaround for that? What can be the source of this problem? Rewriting the synth algorithm is not an option, this is my thesis project, and the deadline is close. Thanks in advance!

Found some, thx!

i am always interested into stm32F4 cores and stuff --- but RE_ take it - i am not interested into all off it --- but you will need all off it to build a seqV4 - so RE_ take it!

Hello where do we connect the CS1 and CS2 of a GLCD 128x64 to the STM32F4 core. This is the way I think should be connected: GLCD STM32F4 1(CS1) ? 2(CS2) ? 3(VSS) VS(J15A) + 10K Pot 4(Vdd) VD(J15A) 5(Vo) 10K Pot 6(D/I) ? R/S(J15A) 7(R/W) RW(J15A) 8(E) E(J15A) 9(DB0) D0(J15A) 10(DB1) D1(J15A) 11(DB2) D2(J15A) 12(DB3) D3(J15A) 13(DB4) D4(J15A) 14(DB5) D5(J15A) 15(DB6) D6(J15A) 16(DB7) D7(J15A) 17(RST) ? 18(VEE) 10K Pot 19(A) B+(J15A) 20(K) B-(J15A) Attached the specifications of the GLCD I searched for this all over the site but I didn’t find anything about it. Have I missed something? Thank you WDG0151.pdf

Hi all For info I just check STM32F4disco at one of my regular component supplier, and there is a new one coming soon. So I check at manufacturer and the board is now NRND, replaced by something looking absolutely the same but with STM32F407VG in place of STM32F407VE. http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 I have no knowledge for understanding/comparison about change. Just to let you know there is certainly a need to check what's going on, and be sure MIOS/MBHP will run fine with new STM32F4 board Best Zam

about the things above... well most of the things you dont need... you need 3x DINX4 1x DOUTx4 2x 2x40 LCDs 17x encoders a lot off buttons and LEDs 1x core 1x DIN MIDI much wires... a custom frontpanel big breatboards - to build a custom UI better go to V4, search the flearmarked forum for a "wilba" frontpanel pcb, and a stm32F4 core with discovery board, and a Midi IO Board Frontpanels you can order from "the beast" from UK.

Christmas time is time to get some serious projects started! Hi, my name is Roberto this is one of my bigger DiY project and my first post here. first of all, this is a very cool platform, well documented and really expandable. what i was looking for! I bought a MBHP CORE STM32F4 and some modules like DIO, DOUT, AINSER64, MIDI IO and AOUT_NG. My goal is to build a midi controller to interact with an attached computer and software via usb midi. later i want to extend it to work with midi and control voltage outputs for synths/modular application. I have basic knowledge in electronics, decent soldering and some beginner programming skills. so more or less I’m a NOOB. I soldered all the boards except MIDI IO and AOUT_NG and made some tests and detected that i have PROBLEMS WITH THE INPUTS. Although i am able to send midi notes to the DOUT and light LED’s, I’m not able to get any inputs from the DIN (with buttons) nor AINSER64 (with faders). So, i’m stuck here right now and have some questions about it: The SD-Card Holder (and the SD Card) is missing on the MBHP Core, because i still wait for it to be delivered. Is it crucial to have it soldered? And, i didn’t planed to attach a LCD. Is it needed to make the whole thing work? here is what i did until now: checked for shorts checket IC, caps and cable polarity installed bootloader and firmware: https://www.dropbox.com/s/mg1oudmpp6ekajq/bootloader_firmware.png?dl=0 installed MIOS : https://www.dropbox.com/s/fo84lnr3t7h8610/mios.png?dl=0 installed MIDIO 128 V3 : https://www.dropbox.com/s/yhp1phjezwotdgx/midiio128.png?dl=0 checked DOUT with a RGB LED: https://www.dropbox.com/s/5txs634ny5yjple/RGBLED.mov?dl=0 checked DIN : https://www.dropbox.com/s/3p5clopkz8eivwl/DIN.jpg?dl=0 The button is attached to J3 (VS - D0) of a DIN module. I can’t see any incoming messages in MIOS Studio… Can i measure the functionality with a multimeter? All i see is a drop from 4.8v to 0v at pin 11 of IC1. But i guess it’s not possible to use a multimeter to measure the serial output… The same with AINSER64, Pot attached to VS - VD on the sides and A0 on the middle, no messages on the MIOS Studio terminal… The green LINK LED stays lit on the AINSER64, so i guess some communication is missed somewhere. I searched for solutions all over the site and i didn’t find any satisfying answer. did i miss something? all the best and cherry friskmas roberto

Hello all, I've build my core stm32F4(fantomxr pcb) + diomatrix + fatar adapter to connect my 88 keyboard. I installed midibox kb and connected everything, but i can't output any midi, so i guess i did something wrong :) I tried the virtual keyboard and i didn't receive any midi input in my daw, so i was wondering if my setup was correct, it seems midibox kb is loaded correctly(cf picture). Here's the setup of my midibox kb: [13020.190] kb 1 debug on [13020.190] kb 1 midi_ports 0x0001 [13020.190] kb 1 midi_chn 1 [13020.190] kb 1 note_offset 21 [13020.190] kb 1 rows 12 [13020.191] kb 1 velocity on [13020.191] kb 1 release_velocity off [13020.191] kb 1 optimized on [13020.191] kb 1 dout_sr1 1 [13020.191] kb 1 dout_sr2 2 [13020.192] kb 1 din_sr1 1 [13020.192] kb 1 din_sr2 2 [13020.192] kb 1 din_key_offset 40 [13020.192] kb 1 din_inverted off [13020.193] kb 1 break_inverted off [13020.193] kb 1 make_debounced off [13020.193] kb 1 break_is_make off [13020.193] kb 1 delay_fastest 50 [13020.194] kb 1 delay_fastest_black_keys 0 [13020.194] kb 1 delay_fastest_release 150 [13020.195] kb 1 delay_fastest_release_black_keys 0 [13020.195] kb 1 delay_slowest 1000 [13020.195] kb 1 delay_slowest_release 1000 [13020.196] kb 1 ain_pitchwheel off [13020.196] kb 1 ctrl_pitchwheel 128 (PitchBend) [13020.196] kb 1 ain_pitchwheel_inverted off [13020.196] kb 1 ain_modwheel off [13020.198] kb 1 ctrl_modwheel 1 (CC) [13020.198] kb 1 ain_modwheel_inverted off [13020.198] kb 1 ain_expression off [13020.198] kb 1 ctrl_expression 11 (CC) [13020.199] kb 1 ain_expression_inverted off [13020.199] kb 1 ain_sustain off [13020.199] kb 1 ctrl_sustain 64 (CC) [13020.205] kb 1 ain_sustain_inverted off [13020.205] kb 1 ain_sustain_switch off [13020.205] kb 1 ain_bandwidth_ms 0 [13020.205] AIN Calibration Mode disabled. Then i wanted to check if my diomatrix was ok so i connected I1 to O1 on J3 to check for midi input, but i did not receive anything(no data in mios input). Is there a way to troubleshoot easily diomatrix ? or some tension to check on the core stm32F4 , i've checked my soldering and connection with a multimeter and everything seems ok. Thanks!

Hi, i compiled an unaltered NG app and uploaded it to the core ( STM32F4). MIOS Studio told me it was uploaded successfully. During upload i could see 'bootloader mode' on the display. But now the core is unresponsive and MIOS Studio doesn't find it anymore. One red led is blinking the other is permanently on. A green led near the micro USB port is on as well. The Display which is connected to the core shows nothing. How can i check what's wrong? Thank you

@tago Thorsten released the Windows toolchain - and it is working, just accessing the 64KB extra memory region of STM32F4 will crash the app, maybe it is a simple linker setting, but i investigated a while back and found no easy solution. On top, under windows, USB MIDI transfers are often very unstable, i.e. when flashing new firmware releases when developing you often have to either rescan MIDI ports or restart MIOS Studio for continuous uploads, which is really frustrating when developing. That is not necessary on a Mac, so you know my recommendation - you can get a used macbook air for ~300€ - while it's not as fast as an M1, it will do the job - imho for that price, it's not worth trying to improve the windows situation with the upper 64kb block, as the Windows USB stability situation cannot be fixed by us. Many greets, Peter

@tago i switched to a Mac m1 a while ago and never looked back, it's awesome, as powerful as my 8-core i7, which cost a lot more, using a fraction of the electrical power at a higher single-core speed (a lot more responsive). You can still get a mini m1 for a bit above 600€, which is a steal for the offered package. The existing (old) toolchain/compilation works fine here, also working with 64kb "upper RAM" for the STM32F4. Upgrading the toolchain to the newest release would be some work, so i'd recommend going the established route - i had used a "free" Hackintosh before, so it's also a possibility to build e.g. MIDIbox NG on most common PC hardware, too. The MIDI implementation on Mac is also way better than anything Windows, so i did not investigate further. Best regards and enjoy! Peter

interested in stm32f4 and discovery.

Hi, Any tips how to optimize NG to get better velocity performance? I'm getting very few velocities. I'm getting a very coarse velocitiy resolution. I'm using a STM32F4 core and have a 5 octave keyboard plus an AINSER8 attached. No menu or displays. I'm thankful for any tips.

I finished my build today, turned on my SeqV4.... some LEDs lit up, and there are solid top rows (black bar) on the LCD displays. There is a red LED flashing on the STM32F4. What's going on? I built my core and tested the discovery board months ago with LCDs attached. Successfully set up, read SD card, screens displayed as expected. I haven't turned on the core since then as I've been focused on enclosures and other aspects of the build. Now today, I assemble the enclosure with my CS board, two MIDI I/O, one Quad IIc, and one Line Tx. I removed the USB Power jumper and connected this 5V DC/DC converter that was recommended to me by another SeqV4 builder https://www.adafruit.com/product/1385 The AC adapter I used was 7.5V/2A. When I turned it on, I got the results described at the top of this post. I powered off, disassembled, and tested the output of the converter which measured 5.27V. Next, I replaced the USB Power jumper, disconnected all peripherals except the LCDs, and powered up using the USB port. Same result, core won't boot. Could the 5.27V supply have damaged the discovery board? Do these symptoms sound indicative of some other failure or user error? Thanks so much for any help!

How much do you ask for the stm32F4 discovery board?

I have some midibox kits lying aroud, but no plans.. It is: a fresh STM32F4 core a core kit from Smash TV plus the pcb with all parts two midio part kits, also with pcbs They are here in .NL. Asking price is €125 including shipping in EU. Or shoot me an decent offer if you wish..

also have a stm32F4 discovery board link to pics: https://www.facebook.com/groups/synthdiy/permalink/10158778005481313/

Hello, This is about a new STM32F4 mbhp, a very compact one. This concept is an answer to these three topics: I tried to draw the most compact core and mbhp board. It's an STM32F405RG instead of the regular 407VG. The 405RG is the smallest package of the M4 Series, this is a LQFP64, a 10x10mm package with only 64 pins. Because these two Processor are from the same family, we don't need deep changes in MIOS32. They have exactly the same functions, memory, speed and peripherals. I put the STM32F4 on a DIP-40 format pcb, in order to get a core that can also replace a PIC in some application, I strongly think of my sammichSid. At the same time it must provide the legacy functions and ports of MIOS32 of course. Some compromise have been made in comparison to a 407VG mbhp. - Only 2 MIDI I/O. - J15, the LCD port is now a serial one only(SSD13xx). - No more general purpose port J10x. This is the list of the 'remaining' ports and changes. - J1A and J1B are the USB and Power ports, J1A is compatible with latigid on's USB wCore module. J1B can be a common header on top or a Micro-Match connector on bottom to stack another board under. - J4 is a dual I2C connector, I put both on the same connector to save space. - J5 is a 2 channels only ADC, they can be used for expression pedal input for example. - J8/9 and J19 stay the Legacy 5V SPI ports, the dipCoreF4 includes the octal buffer(74HCT541); - J11 is now a 6pin and 2 MIDI I/O port. - J16E is the 3.3V SPI port, commonly dedicated to the SD Card it is compatible with latigid on's RES-SD modules. it is extended by the Reset input, the user button and 2 outputs for LEDs. - J18 has changed, it is now able to connect a CAN tranceiver, but stay compatible with the MBNET connection. About the dimension, the ensemble is very compact 65x46mm, but the Core can be used alone and measures 51x17.8mm. A 3D view of the ensemble(sorry this is not a render, I shoot the screen): You will find some more information on the dokuwiki, dipCoreF4 and dipBoardF4 Feel free to ask me question or give me any constructive criticism. I will order some board very soon, if some want to participate in the tests they are welcome, just contact me. I will provide the beta boards for free I just ask you to play the game and seriously help me to improve it ;) Thank you Best regards Bruno PS: sorry for my English as usual ;)

hi i cant find in the documentation/remember/no-search-results: which pin on the discovery board i have to solder a cable and a switch, to get into boatloader mode with a switch from the outside of without opening the midibox... thx for help

Hi All, I've got an stm32F4 and a speakjet chip knocking around, so I thought I'd try out the speakjet synth for mios32 in mios32\trunk\apps\synthesizers\midibox_sj_v2. . Unfortunately, the schematic in the svn repo for the app. is for the lpc core module, looking at the schematic compared to the lpc module pinout, if I've got this right, the speakjet chip connects d2,m0,m1,rst to J10.d3, .d2, d1 and .d0 and the speakjet rcx pin connects to J5b.A7, will the midibox_sj2_v2 app. work if I connect the respective pins as they're laid out on an stm32F4 (pe8,9,10,11 for the J10 pins and pb1 for the j5b.a7-rcx connection)?

I'm building an NG as a central controller for several synths, so that I'll be able to control parameters for a bunch of synths using one NG interface. Right now I'm thinking the controller will have two 4x20 LCD displays, with 16 or 32 encoders, and about 40 buttons. Is there any real advantage to basing a MIDIbox NG controller on a STM32F4 core? Or could I use an LPC17 core without any real difference in performance?

Hey all, I finally got a Discovery board and managed to get the MIOS bootloader installed on it, but when I flipped the board around after connecting PA9 to the 5V pin, nothing. The computer won't even recognize that anything is plugged in. Is there anything I can do to fix this? I'm running Windows 7 64 if that makes any difference.