Search the Community

I may have messed up my STM32F4 board. I accidentally plugged the 74HCT541 in backwards while trying to power it up for the first time. No lights came on. I replaced both chips on the core module and got the boot loader and LCD working. I installed Midibox NG 1.032 but my SD card fails. :( From MIOS Studio 2.4.6 (here are the details) [319531.507] sdcard [319531.499] SD Card Informations [319531.500] ==================== [319531.500] ERROR: Reading CID failed with status -256! [319531.500] ERROR: Reading CSD failed with status -256! [319531.500] [319531.500] Reading Root Directory [319531.500] ====================== [319531.500] SD Card: not connected [319531.500] Failed to open root directory - error status: 12 [319531.500] done. I tried two 8 gig sd cards (one Ultra) format FAT 32. ========================== I checked continuity between the solder pads of the sd card before assembly nothing seemed to be causing a short circuit. Is there a way to trouble shoot SDCard or Connector and the STM32F4 board ? I couldn't locate error status codes while searching the forum. Thanks, A confused GuitarNut

Hi all, I want to build the STM32F4 module pcb, but I'm not sure what the parts list is for what goes on the PCB. Is there a parts list anywhere for what goes on this PCB? Is there a SmashTV kit available that has all of the parts that go on the PCB, or would I need to order those from another supplier? Thanks, John

Hey, I'm experiencing something odd - if I call EEPROM_Init(0) in APP_Init then I cannot upload code using the bootloader unless I reset the board and hold the user (blue) button. Has anyone else experienced this? I'm guessing this has to do with EEPROM_Init touching the flash and somehow messing it for the bootloader... Thanks :)

I came across this today https://github.com/MrBlueXav/Dekrispator I've loaded it on to a STM32F4 and it actually sounds rather good. Has anyone else tried this out? I can imagine a very cool cheap synth based on this code.

Hello, I got my STM32F4 board today, and for reasons beyond my understanding I cannot get any LEDs other than LED1 to light up. I am modifying the application template - so my code is as minimalistic as it gets. If I call MIOS32_BOARD_LED_Set(1,1), the green LED turns on. MIOS32_BOARD_LED_Set(2,1) or even MIOS32_BOARD_LED_Set(0xF, 1) do nothing. Some answers to potentially obvious questions: 1) I am certain I am properly recompiling the code and uploading, as I see the green led no longer lighting up when trying MIOS32_BOARD_LED_Set(2, 1) and lighting up again when I switch to MIOS32_BOARD_LED_Set(0xF, 1). 2) I tried commenting out the code in the timer function and simply turning the LEDs on in APP_Init() 3) I am compiling using the following env variables: export PATH=$PATH:/Users/eran/Projects/mutebox/gcc-arm-none-eabi-4_7-2013q3/bin export MIOS32_PATH=/Users/eran/Projects/mutebox/mios32-svn export MIOS32_BIN_PATH=$MIOS_PATH/bin export MIOS32_GCC_PREFIX=arm-none-eabi export MIOS32_FAMILY=STM32F4xx export MIOS32_PROCESSOR=STM32F407VG export MIOS32_BOARD=MBHP_CORE_STM32F4 export MIOS32_LCD=universal What am I missing? Thanks!

Hi everyone, I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio. I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks. To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting. I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour. Is this midibox_seq_v4_086 messing up the USB midi drivers somehow? Or perhaps some residual code somewhere if it connects under boot hold? Any help is much appreciated!

Hallo zusammen, ich stehe mal wieder auf dem Schlauch. Möchte gerne meinen DIY-Tube-Preamp midifizieren. In einem ersten Schritt soll für einen Prototypen der Volume-Poti verschwinden und eine Lautstärkeregelung über das PGA2311 erfolgen. Es hapert im Moment an der Verdrahtung von diesem IC mit dem STM32F4. Hat jemand einen Schaltplan hierfür?? Mwpost

So reading through the documentation, I find this statement: "..but as long as only OSC messages should be sent and received, the external MBHP_ETH module might be sufficient..." I'm thinking about laying out a combo ETH/USB module for the core and am a little concerned about the "might" part of that. Is this something that is not tested at all and should work in theory or not tested at all and who knows if it will work?

I have used the software provided by ST to input the bootloader into the Discovery Unit when plugged into the PCB. I have a very small number of components on the PCB . (Namely IC1 and IC2 and their capacitors and the R33 resistor network) The problem I found was that the ST Link software would not recognise the bootloader hex file. I messed around a bit and the tried the exercise again this time using the Discovery unit on its own. The hex file was recognised and the bootloader apparently loaded. Is this normal? I am wondering whether there is a problem due to there being no power on the IC's. Maybe someone can explain. Regards Robin

Gibt es irgendwo ein Layout zum Selberätzen/Lochraster? Danke; Grüße aus Kiel

Having given up on using Windows 7 with MIOS STUDIO I have switched to a PC running LINUX (Mint). MIOS STUDIO seems to work properly. I have managed to download hex files using MIOS STUDIO, it would seem. However I would like proceed slowly and looked for an application that I could use to check that the STM32F4 core is OK. Tutorial 5 seemed to be the ideal candidate as it only needs shorting links to be applied to J5 connector. I am not sure whether this APP is ready for STM32F4. I get no response Please let me know if this is the case and if not let me know if there is another application that would be suitable. Or, whether I am likely to have a fault on the hardware. Thanks Robin

Hi all, i was a little bit surprised when my new STM32F4 board arrived because i ordered this one: Link But i received this Version Now the big question: Is it compatible? If needed it would be no problem to change the core board wiring. Best regards Marxon

I'm looking to build this project using only the STM32F4, MIDI IO and AOUT NG (possibly the SCS too). Since it's no longer active, and no download/config info on the main page (http://www.ucapps.de/midibox_cv_v2.html), would it be a better to build the V1 instead of the V2 as there is limited information on the V2 and I only need it for the function of MIDI to CV conversion? Not made a MIDIbox before but from looking around this seems like a good first step as I am trying to learn from scratch the skills necessary to build MIDI controlled acoustic instruments.

Hi all! While working on my Midibox NG, I was careless for a moment and powered the STM32F4 core with too high voltage. :cry: Now it seems that something is faulty on the STM Discovery board because there is a short circuit between the GND and 5V pins (4 ohms). My first thought was to check diode D1, D2 and D3, but they are OK. Now i guess U1 or U3 might be have been destroyed but before i start to desolder them, i first want to ask if somebody might better know what to check . Thanks a lot for your help! :thumbsup: Best regards Marxon

Hello guys, I am facing a stupid problem with a LCD (4x20) connected to the RTP-MIDI core... It simply does not start. I am sure that I forgot something somewhere, but I can't find what I have verified all lines under the bootloader using the testlcdpin command, everything is fine I have set the display size to 4 x 20 in the bootloader In my app, in the APP_Background, I have put this sequence : MIOS32_LCD_Init(0); MIOS32_LCD_Clear(); while (1) { MIOS32_LCD_CursorSet (0,0); MIOS32_LCD_PrintFormattedString ("TEST"); } but my display clearly does not even initialize (I see the "default" squares when I set the contrast to the max). Moreover, I was expecting activity on pins PA8, PD3 and PD6... but nothing at all (checked with my oscilloscope), like if the LCD driver did not start at all. What did I miss ?

Is it possible, as an alternative to STM32F4DISCOVERY board, to use the better STM32F429IDISCO, offered with an integrated LCD and more I / O? Regards Karl

I noticed that a port to the STM32F4 Discovery has shown up in the MIOS sources. What is the status of the port? Is a new Core board planned? The STM32F4 parts have a few features that the LPC1769 doesn't, mainly a proper SD card controller that can use 1 or 4 bit modes instead of SPI, should be a lot faster; and an external memory controller for SRAM or additional Flash. Unfortunately the 100 pin part on the Discovery board doesn't expose all the pins needed to properly interface with external memories, but for synth/sampler-types of instruments the prospects of a MIOS with access to megabytes of fast storage is quite exciting I think :smile: The Discovery board does have the nice feature of an integrated audio quality stereo DAC, which I'd hope to see supported.

I can't find a jumper on the STM32F4 core board for the bootloader hold mode - what is the easiest way to get my core board back to life after it crashes with a hard fault during init? Thanks, ilmenator

Hey all, So, I've been running into this problem with my midibox-seq lately. I haven't used it basically at all last year, and when picking it back up recently, I've been getting a bunch of drum drop outs. Here's a video of the issue in question. -This happens no matter what kind of drum track I choose -Really fast Note tracks aren't effected. -The unit works great with this exception, and has previously been fine. I've tried this across a few different drum machines, but they all seem to be having the same issue. At first I though it might be because of certain drum machines not accepting the shorter version of midi messages, but I don't think that's the case? Both drum machines work fine with my other sequencer. This is the STM32F4 core, all boards from Modular Addict. Is this maybe a firmware issue? or something dumb in track settings that I'm missing?

Hola folks, Jojjelito and myself are currently collaborating on a bigger MIDIboxNG project, that should help facilitate patch programming for all those synth users, that are unhappy with the bad/minimalistic user interfaces of their rack and keyboard synths, especially when programming new patches. This project was planned for years and never took shape... But, thanks to TK., MIDIboxNG came to the rescue! Its codebase has all of the needed functionality integrated in a very generic way, allowing to do so many things! So... why this project, additionally? We thought, for the common usecase of programming patches for (multiple) complex synth engines, it would be nice to have the option to build a MBNG with a standardized component list, a predesigned frontpanel and to have a helpful display layout, with the option to add additional hardware modules (like a joystick vector mixer) later on. So, "MBProgramma" is basically just a name to identify a MIDIboxNG with the hardware properties listed below. The idea of presenting a standardized project yields some benefits: a) most important: we can share synth configurations among other users - they will work on all MBProgrammas without config file changes - if someone is brave enough to build that FS1r configuration, all other owners will benefit from the effort b) newcomers can focus on building a proven setup, which saves time, as they do not have to design everything from scratch. c) we can document and learn from mistakes along the way, so that other people can avoid them :-) d) maybe we can contribute back to MBNG, if TK. accepts some code fragments, like the bitmap graphics loader, or so. e) we can write specialized code for specific hardware, in this case some graphics routines for the 128x64px OLEDs - or something synth-programmer specific... The current hardware requirements for a MBProgramma are as follows: a) a STM32F4 core b) one DOUTx4 digital out module c) four of fairlightiiis LRE8x2 LEDring Modules (ideally equipped with pushable encoders for parameter input acceleration) d) twenty-four SSD1306 compatible 128x64px OLEDs e) a SCS-based menu section, which allows to switch patches (aka switch through programmable synth configurations) and change banks (64 encoders are not nearly enough for the complex synths) f) all is housed below an affordable acrylics frontpanel in MBSEQV4L-style (all boards may be mounted on a wooden construction base, but maybe someone is willing to design a full case?). We will provide the panel file download for formulor/ponoko, when the panel has arrived and has been tested :-). g) an optional analog extension box, allowing for joystick vector input, pot-fader input and analog pedal sockets. Basically, the Programma is a MBNG with four 8x2 LEDring boards and a SCS and maaany displays. We present a novel way of mounting/using the OLEDs to label the encoders and have added some minor code patches to add some extra bling :-) Our tests have shown, that it is next to impossible to use a few banked LEDring boards without proper labels. The displays are mounted on the encoder boards and they support graphical labels, that are directly read from SD-card (and are editable directly in photoshop, without use of a file converter), so we can have a lot of different banks with nice graphics :smile: The project has just started and will be a long ongoing project, also, all those synthesizer programmer configurations will have to be written - we will use this thread to upload pictures and configurations along the way. Feedback is also very welcome! :-) Jojjelito has agreed to do much of the documentation work ;-), so i´ll just chime in from time to time to post pictures and give some free bad advice! :-) Many greets, Peter

Hi, just to let all the KiCAD users know there is a very nice library / footprint with accompanying 3D model for the STM32F4 discovery board (and lots of other good stuff) out there from Walter Lain. Go check his homepage! Best, ilmenator