Search the Community

                                                                        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 ;)    

I currently want to build the MIDIO 128 v3 (including the lpc17) so i managed to buy a lpxpresso1769. The components are easy to get, but i didnt find any way to get the PCB. Is there any way to buy a PCB online thats already made? oh, and does anyone know what the dimensions of the PCB are? i just found the datasheet including the Value 100 x 120, but im not sure about the unity. Greetings, Kilian

Hello all,     i am finally after 5 years coming to the point of trying to finish off my SID module :) Since i got a lot of nanoSIDs and now trying to build a full 10 SID chip device, yeah :)   I have a question, since, in my humble opinion, the documentation is quite not good, sorry to say so, but I am missing a lot of documentaiton on the schematics, for me the best of coourse would be to have some eagle pcbs files or at least double layed brd and sch files as gif or pdf, to controll all the values.   But what i am really missing big time is some real schematic of my mb6582 modules.   Here is my first question:   in each core module there is a Diode on Pin 35, it gives 5 V thru the pull up? R80 which should be 1k.   Where can i possibly find that in any schematic? Or to put it another way, does anyone have a full schematic of the modular addict mb6582 PCBs?     Would appreciate any help, otherwise i will maybe continue to post my built process. cheers, seb

hi my idea is: put a *.syx on the SD-Card put the SD-Card in a STM34F4 core var a. Core recognizes a *.syx and send it out on Port 32 (Midi A) var b. I activate something in the program (with a Dip switch for example) and now it loads up   for what: in use with generic Midicontrollers (BCR2000) to transfair a CC-Layout that is fitting to the Midibox programm   for which project: http://wiki.midibox.org/doku.php?id=msq-cc-bcr   what i have up to now... char filepathL[8]; //Number of Pathsymbols tm/bcr.sys >>> 8 max! MUTEX_SDCARD_TAKE; statusDir = FILE_DirExists("syx"); MUTEX_SDCARD_GIVE; if(statusDir != 1) {MUTEX_LCD_TAKE; MIOS32_LCD_DeviceSet(0); MIOS32_LCD_Clear(); MIOS32_LCD_PrintFormattedString ("%s %d", "no bcr.syx", statusDir); MUTEX_LCD_GIVE;} if(statusDir == 1) { sprintf(filepathL, "tm/bcr.syx"); FILE_ReadOpen (&midifile_fi, filepathL); //normally i then start by reading the content and transfair it into variables..... but happens if i have Sysexfile instead? how to tunnel this to midiport? FILE_ReadBuffer((u8 *)file_typeBank, 4); //"MQ01" = 4 Positons FILE_ReadBuffer((u8 *)CC_SEQ, 32); //Container for static not touchable Variables FILE_ReadBuffer((u8 *)CC_Morph, 128); //Container for morphable Variables FILE_ReadBuffer((u8 *)Velo_Morph, 256); //Here we have 8x32=256, FILE_ReadBuffer((u8 *)CC_Store, 256); //Here we have 8x32=256, FILE_ReadBuffer((u8 *)MSQ_Store, 65536); //Motion-Sequence-Data 8x32*256=65536 FILE_ReadClose (&midifile_fi); MUTEX_SDCARD_GIVE      

for those who don't find a sd card socket for the core stm32F4. you could use micro SD card and the ADAPTATOR will be the socket like:http://www.ucapps.de/mbhp_sdcard.html first solder unused component legs to the adaptator: solder to the core but leave some space to the board for avoid short (be carefull pinning): you could fix it (glue) if you want (not done for me legs are sufficiant) et voila!

Hi all,   I've been lurking around here on the forums for a while now. Some years ago i built my first MBSID v2, completely based on the modular mbhp. The device didn't last very long as i decided to do some modifications and then never finished the work. So poor little sid had to wait for some time, but now i'm back putting the system back together. this time with a mb6582 board.   Now, this board is actually finished and tested and looks good and is supposedly working. But there's this one annoying problem i can't get rid of:   i can upload to the first core (id 0) and it clones to the second core (id 1). After that it resets again and gets stuck for a while with this display output:   Cloning Slave 02 Address: 0r Reset   After this core 4 (id 3) gets cloned properly.     Sadly, uploading the SID application to each core separately doesn't solve the situation. The problem stays and after every "cold" boot, the problem occurs again, sometimes even after the reset after core 3 got cloned.   important to know: i'm working with an adapted setup_8580 at the moment, the control surface i (re)built is customized and a mix between mb6582 cs and old sid v2 cs. but that's another topic, first i have to get the thing to boot properly. I've also tried all the other .hex files, but they don't help either.     Well, i've already spent way too much time on this, any input is appreciated,   cheers, Jakob    

Sorry all the Items are Sold Out. I also sell these items 1x LPC Core Board V1.0 in Red with Ethernet (MAGJACK)    14€             1x LPC Core Board only V1.0 in Green without Ethernet         14€   2x GM5 Board                         5€ for One 2x GM5 Chip for the Board      6€ for One   I Live in Berlin Germany   Best Regards   Sven     Sorry all the Items are Sold Out.

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!

Hi - I was about to order parts to put together an MBSeqv4 when I noticed that there is a core stm32f4 module available. Is this now the preferred core to use with seqv4 or is it still the LPC17 (which seems more expensive, and seems to now feature a mismatched pin config...)? I've looked through Ucapps and this forum and was left feeling unsure.     

I'm using it to trigger a relay for solenoid fun. I'm waiting for some transistor to see if i can get those to work in place of the relays. Also testing encoders to add to my old box. I need and encoder for selecting scenes in ableton.   Previous build.   here's a video of the solenoid in action   have fun! K-rAd   http://www.padk-rad.com

bonjour   je passe a ma deuxieme Midibox et j'ai un soucis avec le core.   J'utilise un core flasher et marchant sur une carte V3 construite il y a 10 ans. Il marche tres bien sur cette carte. Dernierement j'ai acheter chez smash une nouvelle carte Core V4. Visdiblement aucun probleme de soudure ni de test des Vdd et Vss. Les test de midi trouble ont ete fait. La seul chose qui bug c'est que la LED brancher sur Midiout ne clignote pas.   Cependant quand je lance le Mios Studio, il ne le reconnait pas. Il le reconnait sur l ancienne carte mais pas la nouvelle.   Auriez vous une solution?   Merci d'avance